Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

LMS 3.1 syslog collector does not start after restart

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
Cisco Employee

Re: LMS 3.1 syslog collector does not start after restart

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

New Member

Re: LMS 3.1 syslog collector does not start after restart

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.

Cisco Employee

Re: LMS 3.1 syslog collector does not start after restart

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.

New Member

Re: LMS 3.1 syslog collector does not start after restart

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.

New Member

Re: LMS 3.1 syslog collector does not start after restart

It worked! Thanks for your assistance.

153
Views
0
Helpful
5
Replies
CreatePlease login to create content