This article applies to BoKS version 7.0 and 7.1.
An alarm log handling command can be set using the CLI command bokslogadm -C '|...' (or in FoxT Control Center).
This works when it's a command without parameters that processes each line of input at a time, but there are some issues in other cases:
- If the command is given with parameters, e.g. |/bin/mailx -s Alarm root, the alarm log server (boks_blogad) fails to start due to a faulty parameter check.
- Commands that expect an end-of-file before processing the input don't work (e.g. /bin/mailx again); it's started once and then keeps reading lines without processing or terminating.
Additionally, there are some related issues:
- bokslogadm -C ... notifies the log server (boks_blogsd) about the configuration change, but not the alarm log server. As a result, Boot is required for a change to take effect.
- If attempting to set a bad command in FCC (e.g. a non-existing or not executable program), the admin server (boks_bccasd) doesn't handle the error returned from the parameter check correctly and returns "Server returned HTTP response code: 500".
Resolution / Workaround
To resolve this problem, apply the hotfix HFBM-0229 (for BoKS Manager 7.1) or HFBM-0228 (for BoKS Manager 7.0), available for download from the HelpSystems Community Portal.
This hotfix corrects these issues:
- Alarm log commands with parameters now work.
- An end-of-file is now sent after each message, so the command is executed once per message.
- Changing the alarm log command setting now takes affect immediately without restarting boks_blogad or boks_blogsd.
- boks_bccasd now returns a useful error message when attempting to set a bad alarm log command.
Still have questions? We can help. Submit a case to Technical Support.