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

Problems with RME Syslog (LMS 3.1 with W2003)

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

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Problems with RME Syslog (LMS 3.1 with W2003)

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

16 REPLIES
Cisco Employee

Re: Problems with RME Syslog (LMS 3.1 with W2003)

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

New Member

Re: Problems with RME Syslog (LMS 3.1 with W2003)

Hi jclarke, Here is the file pdshow and netstat.

Cisco Employee

Re: Problems with RME Syslog (LMS 3.1 with W2003)

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.

New Member

Re: Problems with RME Syslog (LMS 3.1 with W2003)

JClarke, I realize what that says. also restart the server. the problem persists and I can not subscribe to the syslog server tools from RME.

Deputy pdshow file and netstat.

New Member

Re: Problems with RME Syslog (LMS 3.1 with W2003)

Hi, the problem persists. Who can help?

Cisco Employee

Re: Problems with RME Syslog (LMS 3.1 with W2003)

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

New Member

Re: Problems with RME Syslog (LMS 3.1 with W2003)

thanks. here is the file.

Cisco Employee

Re: Problems with RME Syslog (LMS 3.1 with W2003)

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

New Member

Re: Problems with RME Syslog (LMS 3.1 with W2003)

here is the file (2).

Cisco Employee

Re: Problems with RME Syslog (LMS 3.1 with W2003)

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.

New Member

Re: Problems with RME Syslog (LMS 3.1 with W2003)

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

New Member

Re: Problems with RME Syslog (LMS 3.1 with W2003)

UP......

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

Cisco Employee

Re: Problems with RME Syslog (LMS 3.1 with W2003)

Post the new SyslogCollector.log.

New Member

Re: Problems with RME Syslog (LMS 3.1 with W2003)

ok. thanks.

Cisco Employee

Re: Problems with RME Syslog (LMS 3.1 with W2003)

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.

New Member

Re: Problems with RME Syslog (LMS 3.1 with W2003)

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.

304
Views
0
Helpful
16
Replies
CreatePlease to create content