*** This bug is a duplicate of bug 940030 ***
https://bugs.launchpad.net/bugs/940030
Agree that this does seem to be a uplicate of 940030, marking it as
such.
** Tags added: precise
** This bug has been marked a duplicate of bug 940030
rsyslog stops working after logrotate until restarted
Workaround: open /etc/logrotate.d/rsyslog, and replace this line:
reload rsyslog >/dev/null 2>&1 || true
... with this line:
restart rsyslog >/dev/null 2>&1 || true
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Is this perhaps a duplicate of
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/940030 ?
I'm seeing the same thing, though I noticed it with /var/log/syslog
rather than /var/log/auth.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
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/1059854
Title:
au
Well it's a nice theory, but I can't seem to make it happen by deleting
the log files and forcing a rotation.
I see that logrotate.d/rsyslog does specify the "missingok" option for
these logs files. If that inhibts the "create" option for a missing log
file, then my theory above theory #5 is proba
Ok, I have a theory as to what is causing this bug and why it is hard to
reproduce.
The /etc/logrotate.conf specifies "create" and later the
logrotate.d/rsyslog lists a bunch of log files.
The behavior of "create" is that it creates the new file copying the
owner etc. from the existing file. Howe
Ok, I've written a short Checkbox style test -- that much I could figure
out. I'm hoping someone with permission to submit new checkbox tests can
wrap this up as a checkbox job. It would be interesting to run it after
each install/upgrade cycle as I suspect that's when this bug happens.
#!/bin/bas
Thanks for looking in to it Peter. Sorry for the confusion, but I did
not install syslog-ng. I left the machine with the default. Digging
around, I now see that rsyslogd is the default. Syslog-ng is what
poppped up in the package auto-complete when I typed "syslog" so I
thought, incorrectly, that's
I did a fresh install of 12.04, installed syslog-ng, updated the
machine, but I could not reproduce this problem. Permissions were
always correct and logs collected. It does not seem to be a syslog-ng
package bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Following up on my own bug:
The logging of sudo sessions is another example of data that was not
being written to auth.log
I see that the older auth.log.1 files have the messagebus/adm
permissions, but do have content in them, running up to July 27th 2012.
I assume these were written when the sys
10 matches
Mail list logo
