Bug 245506
| Summary: | log.%m naming scheme incompatible with logrotate | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jordan Russell <jr-redhatbugs2> |
| Component: | samba | Assignee: | Simo Sorce <ssorce> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 7 | CC: | jbk, kunci, nerijus |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 3.0.26a-6.fc7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-11-05 15:05:58 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jordan Russell
2007-06-24 16:10:00 UTC
This bug also causes me to get an e-mail from the logrotate cron job every Sunday: /etc/cron.daily/logrotate: error: error opening /var/log/samba/log.machine.4.gz: No such file or directory And here's what my /var/log/samba directory looks like after 5 weeks: -rw-r--r-- 1 root root 0 Jul 6 04:49 log.0.0.0.0 -rw-r--r-- 1 root root 0 Jul 8 05:00 log.0.0.0.0.1.1 -rw-r--r-- 1 root root 146 Jul 8 05:00 log.0.0.0.0.1.1.1 -rw-r--r-- 1 root root 0 Jul 7 04:49 log.0.0.0.0.1.gz -rw-r--r-- 1 root root 164 Jul 7 04:49 log.0.0.0.0.1.gz.1.gz -rw-r--r-- 1 root root 0 Jul 8 05:00 log.0.0.0.0.2.gz.1 -rw-r--r-- 1 root root 163 Jul 8 05:00 log.0.0.0.0.2.gz.1.1 -rw-r--r-- 1 root root 0 Jul 1 05:00 log.0.0.0.0.3.gz ... -rw-r--r-- 1 root root 746 Jul 8 10:59 log.machine -rw-r--r-- 1 root root 28453 Jul 8 05:00 log.machine.1 -rw-r--r-- 1 root root 0 Jul 8 05:00 log.machine.1.1 -rw-r--r-- 1 root root 48104 Jul 8 05:00 log.machine.1.1.1 -rw-r--r-- 1 root root 1042 Jun 10 05:00 log.machine.5.gz -rw-r--r-- 1 root root 51211 Jul 4 17:02 log.machine.old ... -rw-r--r-- 1 root root 3512 Jul 6 11:29 log.nmbd -rw-r--r-- 1 root root 345 Jun 10 05:00 log.nmbd.5.gz -rw-r--r-- 1 root root 3876 Jul 6 11:23 log.smbd -rw-r--r-- 1 root root 205 Jun 11 04:49 log.smbd.1.gz.1.gz -rw-r--r-- 1 root root 0 Jun 11 04:49 log.smbd.5.gz Ping? This obvious regression is still present despite three updates to the Samba packages for F7. The fix, again, is to revert to the naming scheme used previously: - in /etc/samba/smb.conf, change "log.%m" to "%m.log" - in /etc/logrotate.d/samba, change "log.*" to "*.log" The fix proposed in Comment #2 seems to work only for machine-specific logs. I have log.smbd, log.nmbd, and log.swat that don't seem to be affected by the % m.log directive; they all suffer from the recursive log numbering syndrome. Not sure if these paths are compiled into the binaries. Found the solution, I am adding an /var/log/samba/old/ directory to hold rotated logs. This will solve the problem and also keep the main log dir a bit more clean. samba-3.0.26a-3.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update samba' Thanks, looks like that does indeed solve the problem. samba-3.0.26a-6.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update samba' samba-3.0.26a-6.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report. |