How can i Limit log size?

Question

Hi all,

I want to limit the size that the daemon.raw can grow, i checked the actual config:

# nsradmin -p nsrexec
NetWorker administration program.
Use the "help" command for help, "visual" for full-screen mode.
nsradmin> . type: NSR log
Current query set
nsradmin> print
                        type: NSR log;
               administrator: root, "user=root,host=myhost";
                       owner: NetWorker;
             maximum size MB: 2;
            maximum versions: 10;
        runtime rendered log: /nsr/logs/daemon.log;
                        name: daemon.raw;
                    log path: /nsr/logs/daemon.raw;

                        type: NSR log;
               administrator: root, "user=root,host=myhost";
                       owner: NMC Log File;
             maximum size MB: 2;
            maximum versions: 10;
        runtime rendered log: ;
                        name: gstd.raw;
                    log path: /usr/aplic_ICM/nsr/LGTOnmc/logs/gstd.raw;

                        type: NSR log;
               administrator: root, "user=root,host=myhost";
                       owner: NetWorker;
             maximum size MB: 2;
            maximum versions: 10;
        runtime rendered log: ;
                        name: nsrcpd.raw;
                    log path: /nsr/logs/nsrcpd.raw;

As you can see the daemon.raw maximun size parameter has the 2MB value, but my daemon.raw size has more than 20MB.

I checked out the article esg53730 wich says that the default value for NSR_MAXLOGSIZE is 1MB, this also does not make sense since my daemon.raw as i said is occupying more than 20MB...

...I don't understand... wich parameter i have to change? the NSR log with the nsradmin or the NSR_MAXLOGSIZE?

Thanks.

masonb · Accepted Answer

The variable can be set to override these settings, however the action is only taken when the NetWorker software is stopped. On start-up the log files will be cycled (from .raw to .001 etc if they are greater than the set size. My guess is it is a while since you stopped your software and this is why you have a 20MB log file. This is itself is not an issue as long as /nsr has plenty of space. I have seen log files far larger than yours without any issue.

Regards,

Bill Mason

SME - Advanced Technical Support

EMC Global Services

Problem Resolution and Escalation Management (PREM)

BURA Software Solutions Group (BSSG)

Office: 44 (0) 208-758-6452

North America Support Line: 1-877-534-2867

mason_bill@emc.com

Please note my regular working hours are Monday to Friday, 07:30am to 14:00 pm GMT, 16:00 pm to 18:00 pm GMT

Please submit all new cases, updates or attachments to existing cases via EMC Powerlink http://powerlink.emc.com/

For new issues & questions, EMC Customer Service is pleased to offer you the support option of Live Chat 24x7 for select products.

To interact with our technical support professionals please visit the Networker Support landing page and select ‘Live Chat’ under Additional Resources.

For a single location for you to gain access to all key Support-related resources on Powerlink related to Networker & Avamar, please check out the appropriate landing page:

EMC Networker Support landing page at: https://support.emc.com/products/NetWorker

EMC Avamar Support landing page at: https://support.emc.com/products/Avamar

Satisfied customers are my top priority. For service feedback & comments, please contact my manager:

Mary ODonoghue - ODonoghue_Mary@emc.com

BGuevara · Answer

Hi William, thanks for the quick reply.

I thought that the nsradmin limit was checked in runtime and not when the services come online. I understand that there is no way to limit the log size in runtime?

Regards.

BGuevara · Answer

Hi Hrvoje, Thanks for the reply. It would be usefull the log rotation since sometimes is hard to render logs of 200MB. Regards.

ble1 · Answer

At the moment there is no way on live system to introduce log rotation, but EMC have RFE for it I believe.

priasys · Answer

Networker just filled up my system drive with its daemon.raw log file. I had 12GB free space and it took only some 30 minutes to fill it all up. And it was all - nsrexecd 27 portmapper poll() error: %s 1 24 62 An operation was attempted on something that is not a socket.

I guess its quite a big problem when there is no runtime log rotation when the software has tendencies to write so much info and so fast to the log file. Networker itself is 7.6 SP2. Is there any plans to add such a feature in future releases?

Thierry101 · Answer

had same issue and same wish list...at the moment, it's reactive actions..

ble1 · Answer

Make it proactive... place cron job which does something like: LOG=/nsr/logs/daemon.raw_`date +%y%m%d` cp -p /nsr/logs/daemon.raw $LOG > /nsr/logs/daemon.raw gzip $LOG or something like that...

priasys · Answer

Or something like that? nsrexecd rotates the log file itself if log is over the limit and I restart the "Networker Remote Exec Service". As I can't move/rename the log file if the service works then I guess the "something like that" must be "stop the service, rename the log and start the service again" after every 15 minutes as the Networker can fill up some 10GB in 30 minutes.

It's not a good solution because the running backups are also cancelled when I restart the "remote exec service". And if I do it after every 15 minutes I never gonna get backups done.

ble1 · Answer

10GB in 30 minutes sounds too much, but I see your previous message about that thingy filling the space.  It looks as if this is triggered by pormapper calls so I wonder if nsr portmapper is clashing with something else on that system to cause this.  Of course, it could be bug so perhaps you wish to check latest incarnation of 7.6.2 first.

NetWorker

How can i Limit log size?

Was this post helpful?