Highlighted
Anonymous_User Absent Member.
Absent Member.
232 views

set size of named.run log file

Hello,

after enabling query logging using rndc I have noticed that the resulting
named.run log file seems to be limit to approx. 20000000 bytes and rolls
over one time. Because of the amount of queries this file size does not
provide enough history in our case.

Can I set the size limit of the named.run file or the number of files to
keep?

Thanks in advance
Frank
Labels (2)
0 Likes
3 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: set size of named.run log file

I'd guess this is handled by logrotate as specified in (if memory serves me correctly)
/etc/logrotate.d/novell-named-logs.logrotate
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: set size of named.run log file

Yes, you are right, there is a /etc/logrotate.d/novell-named-
logs.logrotate.

It specifies size of 20M, as well as to keep 10 versions ("rotate 10").

The latter does not work in my case. Maybe because it is a clustered DNS
server, therefor using an eDir user instead of the regular "named"
user...

In article <mathiasbraun.8zbdqn@no-mx.forums.microfocus.com>,
mathiasbraun@no-mx.forums.microfocus.com says...
>
> I'd guess this is handled by logrotate as specified in (if memory serves
> me correctly)
> /etc/logrotate.d/novell-named-logs.logrotate
>
>
> --
> If you find this post helpful and are logged into the web interface,
> show your appreciation and click on the star below.
> ------------------------------------------------------------------------
> mathiasbraun's Profile: https://forums.novell.com/member.php?userid=9494
> View this thread: https://forums.novell.com/showthread.php?t=512099



0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: set size of named.run log file

As your log is 20MB in size and hence likely uncompressed, i'd assume something goes wrong when logrotate runs. Maybe you have a postrotate statement calling a killall for syslog-ng. If you're on OES2018 (SLES12 basically) you likely don't have syslog-ng installed, which obviously will cause the statement to fail. Seems that if ANYTHING fails in the process stuff such as compressing, renaming a.s.o. doesn't take place.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.