05-28-2009 09:23 AM
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?
05-28-2009 10:11 AM
This could be a timing issue. Was the hostname on this server changed recently?
05-28-2009 10:53 AM
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.
05-28-2009 11:02 AM
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.
05-28-2009 11:35 AM
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.
06-02-2009 05:32 PM
It worked! Thanks for your assistance.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: