Re: two many NSO logs take up disk space

qiyi · ‎02-25-2019

Hi experts,

I found more and more NSO logs have used a lot of disk space.

Could we control it by some initial configuration ?

Is there any way to handle it ?

Following are partial of them.

root root 417 Feb 13 02:01 rollback11766
root root 946 Feb 13 03:48 rollback11767
root root 417 Feb 13 04:01 rollback11768
root root 416 Feb 13 11:47 rollback11769

Really appreciated for the help.

vleijon · ‎02-25-2019

They can all be controlled through ncs.conf. Please looking at the documentation for ncs.conf (or just edit the file, the default is pretty helpful for these files).

Also, if space is a problem, you are probably running in production. Then you should really consider using a system install.

qiyi · ‎03-14-2019

Thanks a lot for the info.

It really help to limit the maximum of rollback files to the history-size setting in ncs.conf.

But I wonder how to deal with audit.log and devel.log.

They would tar themselves according to some rules.

But they cost two much space.

-rw-r--r--. 1 root root 90830818 Feb 13 12:02 audit.log.1
-rw-r--r--. 1 root root 624720196 Feb 13 12:02 devel.log.1
-rw-r--r--. 1 root root 12416720 Oct 23 10:24 devel.log.2.gz

vleijon · ‎03-14-2019

You can control the logging through ncs.conf, these particular files are controlled by the rollback setting.

It seems like you are using a developer install, it doesn't automatically rotate logs the way a system install does, but you can set up log rotation manually using a tool such as logrotate.

qiyi · ‎03-14-2019

Hi vleijon,

Really appreciated for the help.

Our customer installed using the docker.

How to change the rollback setting to control these particular files such as audit.log and devel.log ?

I only find the following rollback setting in ncs.conf and failed to get any document about it.

<directory>/var/log/robot/ncs-logs</directory>

<history-size>500</history-size>

</rollback>

Thanks