LMS 3.1 syslog collector does not start after restart

Unanswered Question
May 28th, 2009
User Badges:

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?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Thu, 05/28/2009 - 10:11
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

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

markschnabel Thu, 05/28/2009 - 10:53
User Badges:

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.

Joe Clarke Thu, 05/28/2009 - 11:02
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

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.


markschnabel Thu, 05/28/2009 - 11:35
User Badges:

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.

Actions

This Discussion