Systemwalker Operation Manager V17.0.1 Message Guide

2.15 Messages Starting with PCMI

This section explains messages starting with PCMI.

Messages that begin with PCMI and contain "(STFJMJAVAEE)" in the message text are messages output by the web server (web console/web API).

INFO: PCMI0000: The %1 command was processed normally.: INSTANCE=%2 (STFJMJAVAEE)

[Description]

Command %1 completed successfully.

[Parameter]

%1: Command name

%2: PCMI instance directory path

INFO: PCMI0011: PCMI service has started.: INSTANCE=%1 (STFJMJAVAEE)

[Description]

The PCMI service started.

[Parameter]

%1: PCMI instance directory path

INFO: PCMI0012: PCMI service has stopped.: INSTANCE=%1 (STFJMJAVAEE)

[Description]

Stopped PCMI service.

[Parameter]

%1: PCMI instance directory path

ERROR: PCMI0013: PCMI service cannot be started.: INSTANCE=%1 (STFJMJAVAEE)

[Description]

Unable to start PCMI service.

[Parameter]

%1: PCMI instance directory path

[System Action]

Cancels processing.

[System Administrator Response]

Investigate the cause according to the corrective action described in the message that was output to the event log (for Windows)/system log (for Solaris/Linux) before this message.

If the cause is unknown, collect maintenance information by using the Maintenance Information Collection Tool then contact a Fujitsu technical support.

ERROR: PCMI0014: PCMI service cannot be stopped.: INSTANCE=%1 (STFJMJAVAEE)

[Description]

Unable to stop PCMI service.

[Parameter]

%1:PCMI instance directory path

[System Action]

Cancels processing.

[System Administrator Response]

Investigate the cause according to the corrective action described in the message that was output to the event log (for Windows)/system log (for Solaris/Linux) before this message.

ERROR: PCMI0028: PCMI service already has started.: INSTANCE=%1 (STFJMJAVAEE)

[Description]

The PCMI service is already started.

[Parameter]

%1:PCMI instance directory path

[System Action]

Cancels processing.

[System Administrator Response]

Use process monitoring or the output of the mppviewo command to check the operation status of the java process.

If it is running normally, no action is required.

If not, restart the Systemwalker Operation Manager.

ERROR: PCMI0029: PCMI service already has stopped.: INSTANCE=%1 (STFJMJAVAEE)

[Description]

The PCMI service is already stopped.

[Parameter]

%1:PCMI instance directory path

[System Action]

Cancels processing.

[System Administrator Response]

If this message is output when the Systemwalker Operation Manager stops, the web server process may not have stopped normally.

Check the status of the java process in the output of the mppviewo command.

In the following cases, ignore this message.

• This message is output when the machine restarts or shuts down.

• This message is output when mpowebsetup (Web server setup command) is executed with the -u option specified.

• If this message is output during uninstallation

In the Linux version, the following messages are also output after this message is output, but these messages should also be ignored.

• systemd: FJSVpcmiglassfish5-STFJMJAVAEE_stop.service: control process exited, code=exited status=5

• systemd: Unit FJSVpcmiglassfish5-STFJMJAVAEE_stop.service entered failed state.

INFO: PCMI1000: The PCMI service has started.: INSTANCE=%1 (STFJMJAVAEE)

[Description]

The PCMI service started.

[Parameter]

%1: PCMI instance directory path

INFO: PCMI1001: The PCMI service has stopped.: INSTANCE=%1 (STFJMJAVAEE)

[Description]

Stopped PCMI service.

[Parameter]

%1: PCMI instance directory path

INFO: PCMI1002: Process was started up.: INSTANCE=%1 ID=%2 ADAPTER=%3 (STFJMJAVAEE)

[Description]

Web server started.

[Parameter]

%1: PCMI instance directory path

%2: Server instance name

%3: Internal information

ERROR: PCMI1003: Process unable to start.: INSTANCE=%1 ID=%2 ADAPTER=%3 (STFJMJAVAEE)

[Description]

Failed to start the web server.

[Parameter]

%1: PCMI instance directory path

%2: Server instance name

%3: Internal information

[System Action]

Cancels processing.

[System Administrator Response]

Investigate the cause according to the corrective action described in the message that was output to the event log (for Windows)/system log (for Solaris/Linux) before this message.

If the cause is unknown, collect maintenance information by using the Maintenance Information Collection Tool then contact a Fujitsu technical support.

ERROR: PCMI1006: The PCMI service has already started.: INSTANCE=%1 (STFJMJAVAEE)

[Description]

The PCMI service is starting.

[Parameter]

%1: PCMI instance directory path

[System Action]

Cancels processing.

[System Administrator Response]

Use process monitoring or the output of the mppviewo command to check the operation status of the java process.

If it is running normally, no action is required.

If not, restart the Systemwalker Operation Manager.

INFO: PCMI1031: Process was stopped.: INSTANCE=%1 ID=%2 ADAPTER=%3 (STFJMJAVAEE)

[Description]

The web server was stopped.

[Parameter]

%1: PCMI instance directory path

%2: Server instance name

%3: Internal information

ERROR: PCMI1102: The startup time of process exceeded the process monitoring time.: INSTANCE=%1 ID=%2 ADAPTER=%3 PID=%4 (STFJMJAVAEE)

[Description]

The Web server startup processing did not complete within the monitoring time.

[Parameter]

%1: PCMI instance directory path

%2: Server instance name

%3: Internal information

%4: Process ID (Note)

Note)

If the process ID (%4) is "unknown," the process ID could not be obtained for one of the following reasons.
- The port used by the web server is a duplicate of another application.
- The process was forcibly stopped by the user or another application.
- Failed to reference resource under [PCMI instance directory path(%1)]/work directory.

[System Action]

Forcibly stops the process with process ID (%4).

[System Administrator Response]

A system overload may have caused a timeout error in the server instance startup process.

At the time this message is output, make sure that there is no cause that could overload the system.

After troubleshooting, restart the Systemwalker Operation Manager.

If the cause is unknown, collect maintenance information by using the Maintenance Information Collection Tool then contact a Fujitsu technical support.