Has been hit by this bug on two of my servers apparently (both 18.04.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940030
Title:
rsyslog stops working after logrotate until restarted
To manage
I've tested this on Ubuntu 16.04 with rsyslog version 8.16.0-1ubuntu3 on
an install with systemd and I also tested it on the Bionic Beaver, which
will become Ubuntu 18.04, with rsyslog version 8.16.0-1ubuntu10 on an
install also with systemd and was unable to recreate the bug my test
case on both
** Tags added: id-5a7c79cc18860996b26aaa51
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940030
Title:
rsyslog stops working after logrotate until restarted
To manage notifications about this bug
** Tags removed: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940030
Title:
rsyslog stops working after logrotate until restarted
To manage notifications about this bug go to:
** Also affects: rsyslog (Ubuntu Bionic)
Importance: Critical
Assignee: girish (sajjanarg)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940030
Title:
rsyslog stops
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940030
Title:
rsyslog stops working after logrotate until restarted
To manage notifications about this bug go to:
Any updates on this bug? Is there a fix on the way? I'm experiencing
this problem on 16.04 Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940030
Title:
rsyslog stops working after logrotate
A workaround.
Have/Had the same issue.
As the logrotate is executed by the daily cronjob, I modified
/etc/cron.daily/logrotate to the following:
-
#!/bin/sh
/usr/sbin/logrotate -s /var/lib/logrotate/logrotate.status /etc/logrotate.conf
Same issue here with rsyslog and logrotate on many ubuntu 16.04 servers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940030
Title:
rsyslog stops working after logrotate until restarted
To manage
I see the same issue in Ubuntu 14.04. reload rsyslog doesn't write to
new log file but the old one only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940030
Title:
rsyslog stops working after
I'm seeing something similar with 14.04 since upgrading from 12.04 only
in this case, I'm still getting kernel messages written to the logs
however nothing else is until I force a restart of rsyslog. File
permissions look ok though (syslog:adm).
--
You received this bug notification because you
Hi,
I don't know if it can help but I've a similar bug which involves restarting
Rsyslog.
I use Ubuntu 16.04 LTS 64bits with Rsyslog 8.16-0-1ubuntu3 on two kind of
hardware:
- docker-machine
- AWS EC2
I noticed that on servers that don't use systemd -- in this case docker-
machine --
Ubuntu 16.04.1 LTS
Can confirm that invoke-rc.d does not work.
root@server:~# invoke-rc.d rsyslog rotate
initctl: invalid command: rotate
Try `initctl --help' for more information.
invoke-rc.d: initscript rsyslog, action "rotate" failed.
However, service does work.
root@server:~# service
Correction: "But in general postrotate commands don't seem to be executed at
all."
Yes it does work, phew. But the command "invoke-rc.d rsyslog rotate" is wrong
as it doesn't work:
# invoke-rc.d rsyslog rotate
initctl: invalid command: rotate
Try `initctl --help' for more information.
Can confirm the same behavior on Ubuntu 16.04 LTS. Log files are rotated
by logrotate but postrotate command doesn't seem to work.
ls -ltr /var/log | tail
-rw-r- 1 syslog adm 0 Aug 19 06:42 kern.log
-rw-rw 1 root utmp0 Sep 1 06:49 btmp.1
-rw-r--r-- 1 root
I'm seeing the same issue as @Chesler #20.
On Ubuntu 16.04.1 LTS. Log files are created but logging keeps going in
the rotated file. ie: Auth.log.1 until rsyslog is restarted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm also seeing this issue on 14.04.3 LTS and 14.04.4 LTS. In my case,
"/sbin/reload rsyslog" does not cause rsyslog to reopen the file handles
and it instead continues writing to the rotated files, e.g.
/var/log/syslog.1 until explicitly restarted.
--
You received this bug notification because
I can confirm the bug on 14.04.4 LTS using rsyslog and logrotate.
/var/log/syslog and others are not empty and being filled ok, but other
logfiles are empty, e.g. /var/log/samba/*, /var/log/mysql.*,
/var/log/alternatives.log
--
You received this bug notification because you are a member of
** Changed in: rsyslog (Ubuntu)
Assignee: (unassigned) => girish (sajjanarg)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940030
Title:
rsyslog stops working after logrotate until restarted
I also can confirm adding create 640 syslog adm to
/etc/logrotate.d/rsyslog fixes the problem.
@Gustavo, you should change the /etc/logrotate.d/rsyslog file from this:
/var/log/syslog
{
rotate 7
daily
missingok
notifempty
delaycompress
compress
Should create 640 syslog adm be inserted right before the reload
statement?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940030
Title:
rsyslog stops working after logrotate until restarted
To
I can confirm adding create 640 syslog adm to logrotate fixes the
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940030
Title:
rsyslog stops working after logrotate until restarted
To
I can confirm the same bug on precise server. After logrotate
/var/log/syslog is root:root and I syslog does not log anymore. Multiple
restarts fixes the issue.
On the other hand it works just fine on soucy server for me.
--
You received this bug notification because you are a member of Ubuntu
One of the forum mods (and likely of other official roles) over at the
rsyslog.com knowledge-base suggests in this relatively recent thread:
http://kb.monitorware.com/local-file-logging-stopped-t11391.html
.. that this condition is likely reflecting a per-distribution,
implementation-specific
This affects the current development track for Saucy.
I have a minimal server install of 64-bit 13.10 and since logrotate ran
at 0630 there have been no updates to any log files. Restarting rsyslog
hasn't improved things. some log files seem to be owned by
messagebus:adm, rsylog is user syslog
This seems to be caused by the logrotate configuration for rsyslog using
the system dbus-daemon. Here's the representative example for
/var/log/syslog:
/var/log/syslog
{
rotate 7
daily
missingok
notifempty
delaycompress
compress
postrotate
After reading man initctl --reload I wonder if this is caused if for
some reason the 'rsyslogd' process has died/stopped during logrotate and
therefore a new instance is started by dbus-daemon which (initially?)
inherits the dbus-daemon owner credentials?
--
You received this bug notification
Looking back through the rotated syslog I noticed that the PID of
rsyslogd hasn't changed when it was HUPed:
Aug 21 03:57:00 hush rsyslogd: [origin software=rsyslogd swVersion=5.8.11
x-pid=2647 x-info=http://www.rsyslog.com;] start
Aug 21 03:57:00 hush rsyslogd: rsyslogd's groupid changed to
adding a line create 640 syslog adm in /etc/logrotate.d/rsyslog (in
the two blocks) resolves the permission issue for me (Ubuntu 12.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940030
Title:
Noted that the permissions on the syslog and kern,log are changed from
syslog:syslog to root:root. Upon changing the ownership back, the logs
are updated correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
...without a restart of the syslog service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940030
Title:
rsyslog stops working after logrotate until restarted
To manage notifications about this bug
Workaround: open /etc/logrotate.d/rsyslog, and replace this line:
reload rsyslog /dev/null 21 || true
... with this line:
restart rsyslog /dev/null 21 || true
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm also seeing this on a 12.04 minimal install. After logrotate runs,
when syslog stops being written to, here's what my /var/log directory
looks like:
-rw-r--r-- 1 root root 3721 Oct 11 16:11 alternatives.log
drwxr-xr-x 2 root root 4096 Aug 21 22:02 apt
-rw-r--r-- 1 root
Happens on 12.04 VMs, only sometimes. The systems stops logging and
logging only resumes with a restart of rsyslogd.
Rsyslog and logrotate are up to date.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
after restart
root@helen:/var/log# service rsyslog restart
rsyslog stop/waiting
rsyslog start/running, process 3986
root@helen:/var/log# tail -f syslog
Jun 28 08:59:35 helen kernel: imklog 5.8.6, log source = /proc/kmsg started.
Jun 28 08:59:35 helen rsyslogd: [origin software=rsyslogd
# Only check if jobs are disabled if the currently _running_ version of
# Upstart (which may be older than the latest _installed_ version)
# supports such a query.
#
# This check is necessary to handle the scenario when upgrading from a
# release without the 'show-config' command (introduced in
#
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rsyslog (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940030
Title:
37 matches
Mail list logo
