Problems with RME Syslog (LMS 3.1 with W2003)

Answered Question
Oct 22nd, 2009
User Badges:

Hello, I'm Guilliano and have problems with the operation of syslogcollector and sysloganalysis. The current situation is:

* Unsubscribe the host that was active and I can not subscribe to another host because I get the error: SLCA0152 and SLCA0126. I followed the steps in the User Guide 4.2, and Instalation Guide RME LMS 3.1 and I can not solve the problem. I try to create the certificate that indicates the error in the Commun Services, but does not believe it.

* In windows critical messages appears: DCR is down or inaccessible.


In advance, thank you very much.


Sincerely,

Guilliano Palavecino R.

Support Engineer

Adexus S.A

Correct Answer by Joe Clarke about 7 years 9 months ago

Post the output of the pdshow command as well as the output of "netstat -a -n -o -b".

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Joe Clarke Thu, 10/22/2009 - 13:16
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Post the output of the pdshow command as well as the output of "netstat -a -n -o -b".

Joe Clarke Fri, 10/23/2009 - 07:45
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

It appears some daemons were stopped and started manually, and this has left LMS in a bad state. Restart Daemon Manager, and if the problems persist, post the new pdshow and netstat output before trying to do any daemon changes.

Joe Clarke Wed, 10/28/2009 - 12:44
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

It appears SyslogCollector is not initializing properly. This typically means there is a problem reading the syslog.log file. Post the SyslogCollector.log.

Joe Clarke Wed, 10/28/2009 - 13:34
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Post the C:/PROGRA~1/CSCOpx\MDC\tomcat\webapps\rme\WEB-INF\classes\com\cisco\nm\rmeng\csc\data\Collector.properties file.

Joe Clarke Wed, 10/28/2009 - 13:55
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Shutdown SyslogCollector and SyslogAnalyzer:


pdterm SyslogCollector SyslogAnalyzer


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

NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/sa/data/collectors.dat, and empty out the contents of NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/classes/com/cisco/nm/rmeng/csc/data/filters.dat. Then restart the daemons:


pdexec SyslogCollector SyslogAnalyzer


See if syslog works again.

g.palavecino Thu, 10/29/2009 - 13:41
User Badges:

UP......


ok. I now see that the server has been subscribed, but it is in state NA.


Joe Clarke Thu, 10/29/2009 - 15:36
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Post the new SyslogCollector.log.

Joe Clarke Fri, 10/30/2009 - 10:40
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Okay, now there is a problem reading the syslog.log file. Make sure NMSROOT\log\syslog.log is accessible by the casusers group. This group should have full control over the file.

g.palavecino Mon, 11/02/2009 - 07:18
User Badges:

JClarke thank you very much, the problem has been solved completely. Syslog.log file did not allow access to the group casus.


Again thanks and greetings from Chile.


Guilliano Palavecino R.

Enginner Support Communication

Adexus S.A

Santiago, Chile.

Actions

This Discussion