2.2.1 A Process Error is Displayed

Error message

The following messages are output to the application log or system log if any of the Systemwalker Operation Manager processes are not operating normally.

[Windows versions]

[V10.0L20/V10.0L21 or later]
MpPmonO: ERROR: 1000002: Check if the Systemwalker Operation Manager process (XXXX) is running properly.
[V11.0L10 or later]
MpPmonO: ERROR: 10002: Check if the Systemwalker Operation Manager process (XXXX) is running properly.

[UNIX versions]

[10.1 or later]
MpPmonO: ERROR: 1000002: Check if the Systemwalker Operation Manager process (XXXX) is running properly.
[11.0 or later]
MpPmonO: ERROR: 10002: Check if the Systemwalker Operation Manager process (XXXX) is running properly.

Applicable versions and levels

Windows versions: V10.0L20 or later
Solaris versions: 10.1 or later
Linux versions: V11.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 11.0 or later
AIX versions: 11.0 or later

Action 1

Cause

This error occurs if there is a problem with a process when monitoring Systemwalker processes.

Action method

Perform the following procedure to recover the machine on which this problem occurred:

Check the process running status.
On the machine in which the problem occurred, check the running status of the process for each function.
- Windows versions
```
<systemwalker install directory>\mpwalker.jm\bin\mppviewo
```
- UNIX versions
```
/opt/systemwalker/bin/mppviewo
```
Point
If a problem occurs for a process, a message such as the following will be displayed for the function.
```
>>>>> ERROR:Process NOT Found!! : Monitering target process
```
Proceed according to the outcome of the previous step.
If an abnormal process is found, recover Systemwalker. Refer to "2.2.2 A Process Error is Displayed during Check of the Process Running Status" for information on how to take action for each process with a problem.
If an abnormal process is not found, refer to "Action 2".

Action 2

Cause

Did you edit the batch start/stop file (start control file) during startup of Systemwalker Operation Manager?

If the batch start/stop control file is edited during startup of Systemwalker Operation Manager, the process monitoring function may not operate correctly.

Action method

Perform the procedure below to restart Systemwalker Operation Manager:

Stop Systemwalker Operation Manager.
- Windows versions
```
poperationmgr
```
- UNIX versions
```
/opt/systemwalker/bin/poperationmgr
```
Start Systemwalker Operation Manager.
- Windows versions
```
soperationmgr
```
- UNIX versions
```
/opt/systemwalker/bin/soperationmgr
```

Action 3

Points to check

Is there an error in the definition file of the monitoring target process?

Action method

Refer to "Changing the Processes to be Monitored" in the Installation Guide for information on how to check if there are any errors in the definition file of the following processes to be monitored.

Windows

<systemwalker operation manager install directory>
\mpwalker.jm\mpcmtool\pmon\etc\mppmon.usr

UNIX versions
```
/etc/opt/FJSVftlo/pmon/mppmon.usr
```

If there are no errors in the file, use the Maintenance Information Collection Tool to obtain common tools information, and then contact Fujitsu technical support.

Action 4

Points to check

Have the processes to be monitored in a cluster environment been changed?

Cause

If the processes to be monitored in a cluster environment have not been changed, a process monitoring error may be displayed.

Action method

Perform the following procedure to change the processes to be monitored:

Open the definition file of the following processes to be monitored with a text editor such as vi or Notepad.
- Windows
```
<systemwalker operation manager install directory>
\mpwalker.jm\mpcmtool\pmon\etc\mppmon.usr
```
- UNIX versions
```
/etc/opt/FJSVftlo/pmon/mppmon.usr
```

Edit the following rows as shown:

Windows versions

[Before]
Fujitsu MpWalker MpJobsch=1
Fujitsu MpWalker MpMjes=1

[After]
Fujitsu MpWalker MpJobsch=0
Fujitsu MpWalker MpMjes=0

UNIX versions

[Before]
start_jobs=1
S99MJS=1

[After]
start_jobs=0
S99MJS=0

Refer to "Changing the Processes to be Monitored" in the Installation Guide for details.

Action 5

Points to check

Have appropriate system parameter (semaphore) values been tuned? (10.1 or later)

Action method

Refer to "Action 2" in "2.5.1 If Connecting as a User Other than Superuser, the Project is not Displayed Even if the Access Rights have been Set [UNIX Versions]" for information on the action to be taken.

Action 6

Cause

This error may occur during a shutdown or restart of the system. (Windows versions only)

Action method

No action is required, however, you can prevent messages from being output during a shutdown or restart of the system by performing one of the following:

Execute the service/daemon termination command (poperationmgr) before a shutdown or restart of the system. Refer to the Reference Guide for details.
Stop the process monitoring service (Systemwalker MpPmonC or Systemwalker MpPmonO) from the service window before a shutdown or restart of the system.
Stop the process monitoring service (Systemwalker MpPmonC or Systemwalker MpPmonO) using "net stop" or the command for stopping system services before a shutdown or restart of the system.