Error in event_disp_error_file on 10.3.1 on Linux servers.
book
Article ID: 130021
calendar_today
Updated On:
Products
CA Spectrum
Issue/Introduction
After upgrading to version 10.3.1 there are a lot of error messages in the event_disp_error_file. All these errors (nearly 1,000 entries) point to just 2 files.
3/18/19 5:44:20 PMError in file ./CsVendor/SDN/EventDisp, line 26: CA.EventCondition Missing parameter number 2 3/18/19 5:44:20 PMError in file ./CsVendor/SDN/EventDisp, line 26: CA.EventCondition Missing event information input string 3/18/19 5:44:20 PMError in file ./CsVendor/SDN/EventDisp, line 26: CA.EventCondition Error parsing evaluation condition string (" "): syntax error 3/18/19 5:44:20 PMError in file ./CsVendor/SDN/EventDisp, line 26: CA.EventConditionFailed to parse evaluation condition string (" "): could not generate condition The event rule CA.EventCondition is aborted due to errors. No valid event code at start of line 27 of event disposition file ./CsVendor/SDN/EventDisp .... ... Error parsing severity map ./CsVendor/Versa/SeverityMaps/alarmSeverity: syntax error Unparsed remainder: syntax error Unparsed remainder: syntax error Unparsed remainder:
Cause
/CsVendor/SDN/EventDisp and /CsVendor/Versa/SeverityMaps/alarmSeverity
This is caused by 2 EventDisp file being incorrectly formatted to DOS format
Environment
CA Spectrum 10.3.1 installed on Linux
Resolution
and solution as to convert it to UNIX format.
dos2unix /CsVendor/SDN/EventDisp dos2unix /CsVendor/Versa/SeverityMaps/alarmSeverity restart the SS
Please Note If these files were in the SPECROOT/Custom folder, there is an alternative to a restart of the SpectroSERVER: you can update the event configs from the SpectroSERVER control on the VNM model. Outside of the custom folder, a restart is required.
Additional Information
This was documented in DE405049 and has been fixed in 10.3.2