cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
493
Views
0
Helpful
5
Replies

LMS 3.1 syslog collector does not start after restart

markschnabel
Level 4
Level 4

every time we restart the server the syslog collector fails to start and we have to manually subscribe. The collector shows up but in a not started status.Any ideas on why?

5 Replies 5

Joe Clarke
Cisco Employee
Cisco Employee

This could be a timing issue. Was the hostname on this server changed recently?

no, but we did have a temp server hostname during the upgrade so actually 2 devices show up as options. I have not figured out how to delete the one device that we dont need.

Yes, this is a timing problem. If you wait long enough, the Collector should get subscribed. In any event, you can clean this up by stopping Daemon Manager, then do the following:

* Clear out the contents of NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/csc/data/filters.dat

* Delete NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/sa/data/collectors.dat

and NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/csc/data/Subscribers.dat

Then restart Daemon Manager, and the local Collector should be automatically resubscribed.

Thank you for the quick update! I will try this during our next change window. Regarding waiting long enough, after 24 hours it still did not get subscribed.

It worked! Thanks for your assistance.