Top
Systemwalker Operation Manager  Message Guide
FUJITSU Software

3.2 Messages Output When Services or Daemons Start up or Shut Down

This section explains messages output by Services or Daemons Start up or Shut down.

[Windows]scentricmgr or pcentricmgr or soperationmgr or poperationmgr has already started.

[Description]

The batch service startup/termination command is already running.

[Corrective Measures]

Check that the batch service startup/termination command has finished, and then run the batch service startup/termination command again. Also use the operating environment maintenance wizard and commands to check if any operations that accompany batch service startup/termination (backup, restore, etc.) are running. If such operations are running, make sure that they are complete before running the batch service startup/termination command again.

To check if the batch service startup/termination command has finished or if any operations that accompany batch service startup/termination are running, use the Processes tab of the Task Manager window to check if the following processes exist:

  • pcentricmgr.exe

  • scentricmgr.exe

  • poperationmgr.exe

  • soperationmgr.exe

  • MpEnvset.exe

  • mpbkc.exe

  • mprsc.exe

  • mpbko.exe

  • mprso.exe

  • mppolcopy.exe

  • mppolclone.exe

  • mppolcollect.exe

[Windows]Incorrect parameter.

[Description]

The option was used incorrectly.

[Corrective Measures]

Check the correct usage and run the command to start or stop the service/daemon again.

[Windows]This program must run on the administrator privileges.

[Description]

Administrator privileges are needed to run this program.

[Corrective Measures]

The batch service startup/termination command should be executed again by a user with Administrator privileges.

[UNIX]Command %1 rejected. already running : %2

[Description]

The command %1 could not be executed because %2 was already running.

[Parameter]

%1: Name of the command that was executed

%2: Name of the command that was running

[Corrective Measures]

Check that the command that was running has terminated, and then run the command again.

To check that the command that was running has terminated, use the ps command to check that the process of that command does not exist.

[When the command that was running is poperationmgr]

ps -ef | grep poperationmgr

Check if any commands that accompany daemon startup/termination (such as backup and restore commands) are running. If such commands are running, execute the command after these commands terminate.

To check if any commands that accompany daemon startup/termination are running, use the ps command to check if the following processes exist:

  • mpbkc

  • mprsc

  • mpbko

  • mprso

  • mppolcopy

  • mppolclone

  • mppolcollect

  • mpbk

  • mprs

  • Other commands (commands in the Systemwalker Operation Manager Reference Guide that start and stop daemons)

[For mpbko]

ps -ef | grep mpbko

[UNIX]The daemon is suppressed from starting. Cannot execute the command.

[Description]

The command could not be executed because startup of the Systemwalker Operation Manager or Systemwalker Centric Manager daemon was suppressed.

[Corrective Measures]

Refer to "swstart Service/Daemon Startup Suppression Release Command" in the Systemwalker Operation Manager Reference Guide and cancel startup suppression of the daemon.

If Systemwalker Centric Manager coexists with Systemwalker Operation Manager, this action will also cancel startup suppression of the Systemwalker Centric Manager daemon.

[UNIX]Usage: %1 %2

[Description]

The option was used incorrectly.

[Parameter]

%1: Command name

%2: Command option

[Corrective Measures]

Check the following commands for any errors in the option usage, and then run the service/daemon startup or termination command.

  • poperationmgr (service/daemon termination command)

  • soperationmgr (service/daemon startup command)

Refer to the Systemwalker Operation Manager Reference Guide for details on the commands.

[UNIX]%1: ERROR: A product older than Systemwalker CentricMGR 10.1 has already been installed. Cannot specify -a parameter.

[Description]

The -a option cannot be used with the command because a version of Systemwalker CentricMGR older than Systemwalker CentricMGR 10.1 has also been installed in the same environment.

[Parameter]

%1: Command name

[Corrective Measures]

Refer to the Systemwalker CentricMGR Reference Guide and execute the daemon startup/termination command without the -a option specified. Also, refer to the Systemwalker OperationMGR Reference Guide and execute the daemon startup/termination command without the -a option specified.

[UNIX]
poperationmgr start...
poperationmgr end.

soperationmgr start...

soperationmgr normal end.

component start :
%1
component stopped normally:%1

component started normally:
%1
component has been stopped:
%1
component has been started:
%1

[Description]

This message shows the execution status of a command.

[Parameter]

%1: Command name

[Corrective Measures]

No action is necessary. A message other than the above may be output to the lines following "component start: %1", but as long as the following messages are output at the end, no action needs to be taken.

  • poperationmgr end.

  • soperationmgr normal end.

If these messages have not been output, refer to "Defining the Collect Maintenance Information Tool" in the Systemwalker Operation Manager Installation Guide and collect maintenance information for all the functions or tools.