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.0.1 Excessive growing Daemons.log file

On a Solaris system with LMS 3.0.1 in Multi-server trust (Dec-Update) the daemons.log file on the Campus/RME (DCR-Master) server is growing excessive. Currently 17 Gb (uptime 3 days).

It shows java.net.ConnectException: Connection refused (see attachment)

The system seems to work fine, except for this issue.

7 REPLIES
Cisco Employee

Re: LMS 3.0.1 Excessive growing Daemons.log file

This will occur when Config Archive runs if your selected protocol order under RME > Admin > Config Mgmt > Transport Settings is not as correct as it can be. In any event, you can manage the size of daemons.log using the NMSROOT/bin/logrot.pl tool. First, run NMSROOT/bin/logrot.pl -c to configure log rotation. Specify the path to daemons.log, how large you want the file to be able to grow, and how many archives to keep (if any). then add a cron entry to run logrot.pl as often as you need (e.g. once per day).

More on logrot can be found in the Common Services online help.

New Member

Re: LMS 3.0.1 Excessive growing Daemons.log file

thanks, I've indeed changed the order of the transport protocol i.e. removed telnet from the list because the customer's network does use SSH. So It shouldn't report a connection refused. Is there a way to find out what devices in the DCR are causing this?

In the mean time I will setup a cronjob with logrot.

Cisco Employee

Re: LMS 3.0.1 Excessive growing Daemons.log file

There isn't an easy way to determine this. But if you have disabled telnet from your allowed protocols, you should not enter this code path anymore.

New Member

Re: LMS 3.0.1 Excessive growing Daemons.log file

What if there is certain devices such as the 3500 switch that can't run SSH? We must have the telnet active for that reason, and now our daemons.log is at 11GB after only 24 hours....

I did a

grep "java.net.ConnectException: Connection refused" daemons.log | wc

and got this, 5937014 <---!!!

That is almost 6 million occurrencies, and have in mind that this is only the firs row of 22. 6x22x1000000 rows of pure junk.

There must be a way to shut of this kind of java logging?

Cisco Employee

Re: LMS 3.0.1 Excessive growing Daemons.log file

There is no way to disable this logging. However, I have developed a patch for bug CSCso57052 which will help reduce the amount of these connection refused exceptions. The patch doesn't actually address the logging issue, but it greatly cuts down on the number of connections attempted, and thus will reduce the logging.

For example, before the patch, you could get, say, 100 connections per device. After the patch there will never be more than three.

You can contact the TAC, and reference the above bug to get the patch.

Blue

Re: LMS 3.0.1 Excessive growing Daemons.log file

Is this patch going to be in LMS 3.1?

Cisco Employee

Re: LMS 3.0.1 Excessive growing Daemons.log file

Yes.

229
Views
0
Helpful
7
Replies
CreatePlease login to create content