13.2 Troubleshooting

Setting up or starting service

• A Performance Management program service does not start.

• It takes a long time for a service to start once startup is requested.

• Immediately after a Performance Management program service is stopped, another program service is started, but communication does not function correctly.

• After the message The disk capacity is insufficient is displayed, the Master Store or Agent Store service stops.

• The Agent Collector or Remote Monitor Collector service did not start.

13.2.1

Executing commands

• When the jpctool service list command is executed, the names of services that are not operating are output.

• When the jpctool db dump command is executed, data other than the specified Store data is output.

13.2.2

Report definitions

• There is a time period that is not displayed in historical reports.

13.2.3

Alarm definitions

• The program defined for action execution does not function correctly.

• An alarm event is not displayed.

• An alarm threshold was exceeded, but the alarm icon remains in green in the Alarm Status window in the Agents tree.

13.2.4

Collecting and managing performance data

• The size of the PFM - Agent's Store database does not become smaller even though the data retention period was shortened.

• The message KAVE00128-E Illegal data was detected in the Store database or KAVE00163-E. The database type is illegal was output to the common message log and the startup of Store database fails.

• The message KAVF14173-W The performance data cannot be reported. (record-ID[.field-name]) is output to the common message log.

13.2.5

File monitoring

• JP1 events are not issued successfully (when JP1/Base's log filee traps are used).

• The KAVF14280-W message is output to the Windows event log (in Windows) or to syslog (in Linux).

• The KAVF14281-W message is output to the Windows event log (in Windows) or to syslog (in Linux).

13.2.6