03-23-2010 08:34 PM
Hi,
I've installed LMS 3.2 with RME 4.3.
After service start for a few days, the syslog collector stop unexpectedly.
I can see the syslog.log file being updated but I can't see any syslog from report generator.
Also I got no alarms from automated action.
So I checked SyslogAnalyzer.log file, it shows:
NMSROOT is D:/CSCOpx
propFileD:/CSCOpx\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\csc\data\Collector.properties
Exception in thread "ActionThread3" java.lang.NullPointerException
at com.cisco.nm.rmeng.sa.SaActionProcessor.process(SaActionProcessor.java:173)
at com.cisco.nm.rmeng.sa.SaActionProcessor.run(SaActionProcessor.java:463)
Exception in thread "ActionThread4" java.lang.NullPointerException
at com.cisco.nm.rmeng.sa.SaActionProcessor.process(SaActionProcessor.java:173)
at com.cisco.nm.rmeng.sa.SaActionProcessor.run(SaActionProcessor.java:463)
Exception in thread "ActionThread1" java.lang.NullPointerException
at com.cisco.nm.rmeng.sa.SaActionProcessor.process(SaActionProcessor.java:173)
at com.cisco.nm.rmeng.sa.SaActionProcessor.run(SaActionProcessor.java:463)
Exception in thread "ActionThread0" java.lang.NullPointerException
at com.cisco.nm.rmeng.sa.SaActionProcessor.process(SaActionProcessor.java:173)
at com.cisco.nm.rmeng.sa.SaActionProcessor.run(SaActionProcessor.java:463)
Exception in thread "ActionThread2" java.lang.NullPointerException
at com.cisco.nm.rmeng.sa.SaActionProcessor.process(SaActionProcessor.java:173)
at com.cisco.nm.rmeng.sa.SaActionProcessor.run(SaActionProcessor.java:463)
All other LMS function works normally, except syslog collector.
Any advice?
03-23-2010 11:57 PM
These line numbers don't make any sense. You should shutdown Daemon Manager, clear out this log, the AnalyzerDebug.log, and the SyslogCollector.log. Restart, and if the problem happens again, post those three logs.
03-24-2010 10:12 AM
Thanks for your reply, I will follow your stpes and collector the three log files when the problem happen again
04-15-2010 07:43 PM
I had exactly the same symptons, and tried Joe's solution. It worked a treat.
Previous to this I had tried (in order):
Re-subscribing the Analyzer to the Collector
Restarting the Analyzer and Collector processes
06-14-2012 08:37 AM
I have this same issue and tried the above steps but with no luck, still have the following error in sysloganalyzer.log file
NMSROOT is f:/CSCOpx
propFilef:/CSCOpx\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\csc\data\Collector.properties
Exception in thread "ActionThread2" java.lang.NullPointerException
at com.cisco.nm.rmeng.sa.SaActionProcessor.process(SaActionProcessor.java:173)
at com.cisco.nm.rmeng.sa.SaActionProcessor.run(SaActionProcessor.java:463)
Exception in thread "ActionThread1" java.lang.NullPointerException
at com.cisco.nm.rmeng.sa.SaActionProcessor.process(SaActionProcessor.java:173)
at com.cisco.nm.rmeng.sa.SaActionProcessor.run(SaActionProcessor.java:463)
Any ideas?
06-16-2012 02:03 PM
If restarting the daemons doesn't work, this could be due to a bug that is fixed in LMS 3.2.1 (RME 4.3.2). You can download the LMS 3.2.1 update from Cisco.com.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide