Skip to main content
Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

HabibG2

455 Posts

1380

September 26th, 2007 07:00

Reducing Daemon.log file size.

Hi,

My Daemon.log file size in increasing and is now about 40MB.

I have added the environment variables NSR_MAXLOGVERS and NSR_MAXLOGSIZE as suggested in the doc and also restarted my nsrd. Unfortunately the trimming function does not appear to be working. I shutdown Networker and tried to edit the file and reduce the number - no success as other services are using the files. I currently have only two files; daemon.005 (7MB) and daemon.log (40MB).

Is there another way I can reset the trimming function to work as it should.

Thanks
Habib

ble1

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

September 27th, 2007 14:00

Woops... you stopped NW and you have media db still running? That's bad... unless that is some old incarnation. To bypass that simply stop NW, put services to disable and reboot the box. Once box comes back you should not have any nsr process and services should not run. Change daemon.log to daemon.001 and then change service properties to enabled and start them up.

ble1

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

September 26th, 2007 11:00

I've seen recently something is wrong with log rotation, but I didn't pay much attention to it (what versions and on what platforms). I know log management is about to enhance in new versions, but have no idea what is going with current versions. I know I have requested long time ago log daemon and ability to HUP it thus have manual rotation (and from that point it would not be hard to make it easy to as automatic according to settings).

Workaround in your case is to stop NW, move manually daemon.log to daemon.001 and start NW. It should then create new daemon.log.

HabibG2

455 Posts

September 27th, 2007 03:00

Hi Hrvoje,

Thanks for the information.

I have just upgraded to 7.3.3 from 7.3.2 on W2003 R2 platform. The problem was there even before I upgraded so its not the upgrade that caused it.

I have tried renaming daemon.log to daemon.001 as you suggested, but the system won't let me even when NW has been stopped although I noticed that there are some processes still running under System in Task Manager; nsrmmd.exe, nsrmmdbd.exe, nsrpm.exe..etc.

Thanks
Habib.

HabibG2

455 Posts

September 28th, 2007 07:00

I attempted this yesterday and now waiting for the file to reach its 1024K limits to see if the trimming function works.

Will keep you informed!!

Thanks again.
Habib.

Was this post helpful?

View All

No Events found!

Top