** Branch linked: lp:~davewalker/ubuntu/lucid/logrotate/lp387189
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/387189
Title:
logrotate incorrectly rotates /dev/null to /dev/null.1
--
ubuntu-bugs m
** Changed in: logrotate (Ubuntu)
Assignee: (unassigned) => Canonical Server Team (canonical-server)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/387189
Title:
/dev/null corrupted (/dev/null.1
OK. Do we have a test case for which my patch fails?
If the remaining issue is that my patch contains a closing '}', that is
easily "solved", because the {} around the variable name are only there
for style reasons, and are not required.
Here is a modified patch without the {} . Is there a test
This is a logrotate issue and happens if the specified logfile directory
(in this case /var/log/apache2) does not exist and the postrotate script
contains a closing '}'. Therefore I don't think Jonathan's patch would
fix the issue completely.
The full info is at http://bugs.debian.org/cgi-
bin/bug
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/387189
Title:
/dev/null corrupted (/dev/null.1)
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com
It seems to me a patch to /etc/logrotate.d/apache2 is the simplest
solution.
The attached diff tries to solve the issue and also be more readable,
breaking the one complex line involving backticks into three shorter
simpler lines, no backticks needed.
There are a lot of cases to test this with,
Based on comments #24 and #25 it looks like this is an Apache issue, so
I've added apache2 - apache2 maintainers please have a look because it's
got quite an impact.
Dave
** Also affects: apache2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
Marking High status. This breaks software that is unrelated to it's
self. libc will fail if this is not a character block device, and even
can deny remote login ( such as on servers, in some cases ). This is an
important issue to address.
** Changed in: logrotate (Ubuntu)
Importance: Undecided
The problem is within /etc/logrotate.d/apache2 - when
/etc/apache2/envvars does not exist:
# logrotate -d /etc/logrotate.conf:
[...]
error: apache2:11 lines must begin with a keyword or a filename (possibly in
double quotes)
error: apache2:12 missing end of line
reading config info for /etc/init
I think I tracked this down to a syntax thinko in
/etc/logrotate.d/apache2 (installed by apache2.2-common), when
/etc/apache2/envvars doesn't exist - which can happen easily, e.g., when
you do not really need apache2 but only something from the -common
package:
logrotate -d /etc/logrotate.conf 2>&
Architecture: i386
DistroRelease: Ubuntu 10.04
NonfreeKernelModules: nvidia
Package: logrotate 3.7.8-4ubuntu2
PackageArchitecture: i386
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Tags: lucid
Uname: Linux 2.6.32-24-generic i686
UserGroups: adm admin audio cdrom dialout fuse
when the reported files are attached you can mark as confirmed.
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Hello pberndt
Can you please run in a terminal:
apport-collect -p logrotate 387189
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
** Package changed: ubuntu => logrotate (Ubuntu)
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
https://wiki.ubuntu.com/Bugs
I'm pretty sure this bug is related to logrotate. When Mészáros Balázs
suggested that it might be, I disabled logrotate on both my systems and
did not have any problems ever since.
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received this bug notification becau
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: ubuntu
Status: New
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
https://wiki.ubuntu.com/Bugs
** Changed in: ubuntu
Status: New => Incomplete
** Changed in: ubuntu
Status: Incomplete => New
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Same bug under Lucid.
I had started to audit /dev/null and recognized that logrotate simply
rotated it.
The output of ausearch -i -f /dev/null is included. It was a character
device and became a regular file. I've checked every logrotate rules,
but I can't guess why it happend. I will continue de
same bug
/dev/null - is ordinal file
/dev/null.1 - is original /dev/null device file
same problem to unlock gnome-screensaver without /dev/null fix
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received this bug notification because you are a member of Ubuntu
atop isn't the reason
I have currently 5 installations (2 fresh karmic installations) with this
problem.
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
The problem still occurs 2 machines
fuser -av /dev/null
shows always atop in the process list
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
Can't confirm.
I'm not using syslog-ng.
The problem occurs also under karmic with rsyslogd on a netbook.
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
I think it might be related to syslog-ng, i removed it 5 days ago and
still no sign of the bug
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
Happens also to me every 2-3 days.
Upgrading to Karmic 9.10 didn't resolve the issue .
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Problem occurred again.
The output of fuser -av /dev/null* is attached.
** Attachment added: "fuser -av /dev/null*"
http://launchpadlibrarian.net/34844990/null
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received this bug notification because you are a mem
The process/package moving the file isn't determined in the moment.
** Changed in: ubuntu
Status: Incomplete => New
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
The problem is not depending on a reboot.
After some time the /dev/null device is moved to /dev/null.1 and a new **file**
is created for /dev/null.
This triggers https://bugs.launchpad.net/ubuntu/+source/pam/+bug/270781, if the
screensaver locks the screen.
Some "older" processes still using the
I'm marking the udev task as invalid, because this is not a udev bug.
Something else on the system is overwriting /dev/null (removing the
device node udev creates), and obviously is also creating those .1, .2,
etc. files
This will be quite difficult to debug, you'll need to first establish
whethe
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
https://wiki.ubuntu.com/Bug
** Changed in: ubuntu
Status: New => Confirmed
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
same here on a laptop that I rarely reboot (I just suspend to ram);
after a while, /dev/null is replaced with a blank file, and /dev/null.1
appears; if /dev/null.1 exists, /dev/null.2 is created and so on
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received thi
Second desktop shows the problem (also 9.04/amd-64) after being
hibernated 4 or 5 times.
--
/dev/null corrupted (/dev/null.1)
https://bugs.launchpad.net/bugs/387189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
34 matches
Mail list logo
