Bug 14123 - strange logging behavior in AD DC
Summary: strange logging behavior in AD DC
Status: CLOSED DUPLICATE of bug 9673
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB (show other bugs)
Version: 4.10.8
Hardware: All Linux
: P5 normal (vote)
Target Milestone: ---
Assignee: Andrew Bartlett
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-12 01:28 UTC by Adam Xu
Modified: 2019-09-12 11:34 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Xu 2019-09-12 01:28:30 UTC
I'm using sernet version of samba in CentOS7.6. my smb.conf setting here:
[global]
        log level = 1 auth_json_audit:3@/var/log/samba/auth.log
        max log size = 10000

the problem is:
1. the log isn't rotated correctly. the auth.log.old file is larger that 10000kb. It will be 60MB to serveral GB.

2. samba do not always write new log to auth.log. most of the new log writes to auth.log.old (that's why the log.old file so big) , and only a little few new log write to auth.log.

3. when samba is writing log to auth.log.old , I excute "systemctl reload sernet-samba-ad.service" , samba will write new log to auth.log. but serverl minutes later, it will write new log to auth.log.old again.

No related error is displayed in the samba log. the behavior of log.smbd and log.smbd.old is fine.
Comment 1 Björn Baumbach 2019-09-12 11:33:13 UTC
Hi Adam!

This is a known issue which unfortunately exists since a very long time. Please refer to:

https://bugzilla.samba.org/show_bug.cgi?id=9673

The issue which Marc describes there is not related to the variable logfile names. As far as I know we have this issue with all samba (AD) services.

I mark this bug as a duplicate, for now. I'll add some description to bug 9673.

*** This bug has been marked as a duplicate of bug 9673 ***