AWSBCX - Monman messages
This section lists error and warning monman messages that might be issued.
The message component code is BCX.
AWSBCX001E An internal error has occurred. Monman cannot read a message in a message file. The following gives more details of the error: "error_message".
Explanation
Monman was unable to read a message from its local mailbox: Monbox.msg.
error_message describes the error and includes the operating system error message.
System action
Monman continues.
Operator response
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBCX002E An internal error has occurred. Monman could not set the termination signal handling routines. The following gives more details of the error: "error_message".
Explanation
As message.
error_message contains the operating system error message.
System action
Monman stops.
Operator response
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBCX005E An internal error has occurred. Monman encountered the following error when attempting to open the Symphony file: "error_message".
Explanation
error_message contains the operating system error message.
Operator response
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBCX007E A message file cannot be opened; the operating system gives the following error: "error_message"
Explanation
Monman is unable to open one of its message file: Monbox.msg or Moncmd.msg.
error_message is a message that contains information about the error and includes the operating system error message.
A possible reason is that either your HCL Workload Automation user or your system has too many files open (a typical user is limited to 64 files).
System action
Monman stops.
Operator response
Attempt to resolve the operating system error. Use the limit command to see the user's file limits (the file limit is the 'descriptor' line for csh users).
If the problem is with the number of files open, take one of the following actions, according to whether the problem is with the operating system limits or a user's limits:
- Add the following lines to your system parameters file (/etc/system) and reboot the system:
set rlim_fd_max = 4096
set rlim_fd_cur = 1024
This may consume slightly more available memory, but it speeds up the system. - Modify your HCL Workload Automation user environment (the following is correct for a csh user):
limit descriptors nnn
where nnn is a value greater than the value revealed by the limit command.
Restart Monman.
AWSBCX011E The Event Integration Facility configuration file ("file") cannot be written; the operating system gives the following error: "error_message"
Explanation
Monman is unable to write the configuration file for the Event Integration Facility, the component used to send the events.
file is the name of the file with the configuration that Monman is attempting to write.
error_message is a message that contains information about the error and includes the operating system error message.
System action
Monman stops.
Operator response
Attempt to resolve the operating system error.
Restart Monman.
AWSBCX012E An internal error has occurred. The Event Integration Facility initialization has failed.
Explanation
Monman is unable to initialize the Event Integration Facility, the component used to send the events.
System action
Monman stops.
Operator response
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBCX013E An internal error has occurred. A parsing error has occurred reading the following event "event".
Explanation
Monman is unable to parse the event, it will be discarded and not sent to the event processor.
System action
Monman discards the current event and will not sent it to the event processor. Monman continues
Operator response
Search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBCX015E An error has occurred opening the temporary file "file_name" for writing.
Explanation
See message.
file_name is the file that cannot be opened.
System action
The action stops.
Operator response
Check the following:
- That there is sufficient disk space to open and read a file
- That there are sufficient file descriptors available to open a file.
Correct any errors that you find, and perform the action again.
AWSBCX016E An error has occurred opening the file "file_name" for reading.
Explanation
See message.
file_name is the file that cannot be opened.
System action
The action stops.
Operator response
Check the following:
- That the file exists
- That the file is in the correct directory
- That the file has read permission
- That there is sufficient disk space to open and read a file
- That there are sufficient file descriptors available to open a file.
Correct any errors that you find, and perform the action again.
AWSBCX017E An error has occurred opening the file "file_name" for writing.
Explanation
See message.
file_name is the file that cannot be opened.
System action
Deployconfig action stops.
Operator response
Check the following:
- That the file exists
- That the file is in the correct directory
- That the file has read permission
- That there is sufficient disk space to open and read a file
- That there are sufficient file descriptors available to open a file.
Correct any errors that you find, and perform the action again.
AWSBCX018E An error has occurred writing the file "file_name".
Explanation
See message.
file_name is the file that cannot be written.
System action
The action stops.
Operator response
Check the following:
- That the file exists
- That the file is in the correct directory
- That the file has write permission
- That there is sufficient disk space to write the file
Resolve the problem and rerun the operation.
AWSBCX019E The zip file "file_name" was built incorrectly. The Unzip process is stopped with an error.
Explanation
See message.
file_name is the zip file built incorrectly.
System action
The operation is not performed.
Operator response
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBCX020E An error has occurred extracting the file "file_name". The Unzip process is stopped with an error.
Explanation
See message.
file_name is the zip file that cannot be unzipped.
System action
The action stops.
Operator response
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBCX021E An error has occurred before completing the unzip process.
Explanation
See message.
System action
The action stops.
Operator response
If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBCX022E Monman encountered an error when attempting to open the Mailbox.msg file. The following gives more details of the error: "error_message"
Explanation
Monman is unable to open the Mailbox.msg file.
error_message is a message that contains information about the error and includes the operating system error message.
A possible reason is that either your HCL Workload Automation user or your system has too many files open (a typical user is limited to 64 files).
System action
Monman stops.
Operator response
Attempt to resolve the operating system error. Use the limit command to see the user's file limits (the file limit is the 'descriptor' line for csh users).
If the problem is with the number of files open, take one of the following actions, according to whether the problem is with the operating system limits or a user's limits:
- Add the following lines to your system parameters file (/etc/system) and reboot the system:
set rlim_fd_max = 4096
set rlim_fd_cur = 1024
This may consume slightly more available memory, but it speeds up the system. - Modify your HCL Workload Automation user environment (the following is correct for a csh user):
limit descriptors nnn
where nnn is a value greater than the value revealed by the limit command.
Restart Monman.
AWSBCX023W The Event Driven Workload Automation feature is disabled, Monman stops.
Explanation
The Event Driven Workload Automation feature has been disabled by optman, which set the enEventDrivenWorkloadAutomation option to NO.
Monman exits, as it is not required in this configuration.
System action
Monman stops.
Operator response
None.
AWSBCX024W The Agent is not able to send the Event Driven Workload Automation events to the Event Processor.
Explanation
Monman and/or the SSM Agent are not able to connect to the Event Processor to send the events.
The events are stored locally and will be sent to the Event Processor when the Agent will be able to connect to the Event Processor.
System action
The monitoring status on the workstation status is turned off.
Operator response
If the monitoring status is not restored automatically, check that the Event Processor is running and that there is no network or firewall problem that is preventing the agent to connect to the event processor.