This section explains messages starting with MpJmCal. These messages are output by the calendar function.
[Description]
Calendar function started.
[Description]
Calendar function stopped.
[Description]
Insufficient memory.
[Parameter]
RRRR: Return value of the function
DDDD: Error details(Error no (errno) set by OS)
FFFF: Function name, label etc.
[System Action]
Process stops.
[System Administrator Response]
Increase the usable memory by following methods.
Close other applications
Increase memory
[Description]
Error in file access.
[Parameter]
RRRR: Return value of the function
DDDD: Error details(Error no set by OS(errno))
FFFF: Function name, label etc.
[System Action]
Process continues if possible. Otherwise it will be stopped.
[System Administrator Response]
Check for the free space on hard disk. Also check condition of hard disk.
[Description]
Calendar daemon information is output
[Parameter]
RRRR: Return value of the function
DDDD: Error details(Error no (errno) set by OS)
MMMM: Message of the Calendar daemon or function name in which error occurred.
[Description]
Internal error has occurred in calendar daemon. Or, free space in /var may be insufficient.
[Parameter]
RRRR: Return value of the function
DDDD: Error details(Error no set by OS(errno))
FFFF: Function name, label etc.
[System Action]
Process continues if possible. Otherwise it will be stopped.
[System Administrator Response]
Taken action according to the error contents. If free space in /var is insufficient, reserve the free space and restart the Systemwalker Operation Manager daemon. If you cannot find the cause, collect data of power control and calendar with the Maintenance Information Collection Tool and contact a Fujitsu technical support.
[Description]
An error occurred on the system function.
[Parameter]
FFFF: Function name
MMMM: Error message
DDDD: Detailed error code (errno)
[System Action]
Process continues if possible. Otherwise it will be stopped.
[System Administrator Response]
Take action according to the error contents. If you cannot find the cause, collect data of power control and calendar with the Maintenance Information Collection Tool and contact a Fujitsu technical support.
In case the following message is output, the calendar function is not available since port 9368/tcp for the calendar function is being used by another application. Review ports used by other applications and restart the system.
FFFF: main SSock
MMMM: Address already in use
DDDD: 125
[Description]
Shared trace OPEN was not functioning correctly.
[Parameter]
XXXX : Shows that an error occurred in calendar function server in case of "SRV" and error occurred in calendar API in case of "API".
[System Action]
Process continues. Trace is not retrieved.
[System Administrator Response]
Restart Systemwalker Operation Manager. If this message is output even after restarting Systemwalker Operation Manager, collect data of "Power_Control_Calendar" and "Tool" with the Maintenance Information Collection Tool and contact a Fujitsu technical support.
[Description]
Common trace output was not functioning correctly.
[Parameter]
XXXX : Shows that an error occurred in calendar function server in case of "SRV" and error occurred in calendar API in case of "API".
[System Action]
Process continues. Trace is not retrieved.
[System Administrator Response]
Restart Systemwalker Operation Manager. If this message is output even after restarting Systemwalker Operation Manager, collect data of "Power_Control_Calendar" and "Tool" with the Maintenance Information Collection Tool and contact a Fujitsu technical support.
[Description]
Calendar function service started.
[Description]
Calendar function service stopped.
[Description]
Insufficient memory.
[Parameter]
XXXX : Memory retrieval area
[System Administrator Response]
Increase the usable memory according to the following methods.
Close other applications
Increase memory
[Description]
Error in file access.
[Parameter]
XXXX : Object file name
[System Action]
Process continues if possible. Otherwise it will be stopped.
[System Administrator Response]
Check for the free space on hard disk. Also check condition of hard disk.
[Description]
Policy information setting failed.
[Parameter]
XXXX: Policy information file
[System Action]
Process continues without setting the policy information.
[System Administrator Response]
Confirm the policy information that failed to be set and restart Systemwalker Operation Manager. This will set the policy information.
[Description]
The reschedule date that has been specified in the last calendar saving failed to be loaded.
As a result, the client cannot refer to the reschedule date information. The default value is displayed if a client attempts reference.
[System Action]
Process continues.
[System Administrator Response]
If this warning is output every time Systemwalker Operation Manager is started up, collect data of "Power_Control_Calendar" with the Maintenance Information Collection Tool and contact a Fujitsu technical support. [Windows version]
Collect the data by specifying "Server" in the swcolinf maintenance information collection command and contact a Fujitsu technical support. [UNIX version]
[Description]
The audit log could not be output because a problem occurred when an attempt was made to load the library used to output the audit log.
[System Action]
Continues processing, but does not output the audit log.
[Corrective Measures]
Check whether the following files exist. If they do, one or more of the files may have become corrupted. In such cases, either reinstall Systemwalker Operation Manager or contact a Fujitsu SE.
Systemwalker installation directory\MPWALKER.JM\bin\mpaudito.dll
/opt/systemwalker/lib/libmpaudito.so
/opt/systemwalker/lib/libmpaudito_nt.so
[HP-UX version]
/opt/systemwalker/lib/libmpaudito.sl
/opt/systemwalker/lib/libmpaudito_nt.sl
[Description]
The audit log could not be output because a problem occurred when an attempt was made to open the audit log output file.
[System Action]
Continues processing, but does not output the audit log.
[Corrective Measures]
Check that there is sufficient free space.
Check that the directory where the audit log is to be output exists.
Check the permissions/rights associated with the directory where the audit log is to be output. If user restriction definitions are not used, the directory must be able to be written to by General Users/Everyone.
The audit log output file may be corrupt. Back up the damaged file and then delete it.
If a problem has occurred on the disk where the audit log is to be output, it may be necessary to replace or restore the hard disk.
The audit log output file and directory can be specified using the mpsetlogsend_omgr command. Refer to the Systemwalker Operation Manager Reference Guide for details on the mpsetlogsend_omgr command.
