@Moses, from what I could see, rsyslog is unable to get the "kernel"
syslog facility regardless of the imklog module presence, even in 10.04.
I think the OpenVZ kernel blocks access to this syslog facility for
guests.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Upgraded from 10.04 LTS to 12.04 LTS, and I was surprised to see my load
average at >= 2.00 for days.
OpenVZ virtual private server
`lsb_release -a |grep Desc`:Ubuntu 12.04.1 LTS
`uname -a`: Linux 2.6.32-042stab057.1 x86_64
`dpkg -l rsyslog`: 5.8.6-1ubuntu8
I used the solution suggested in co
same problem here :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523610
Title:
rsyslogd spins CPU on some kernels
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
I am still experiencing this on 12.04 (rackspace hosting)
$lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.04.1 LTS
Release:12.04
Codename: precise
$uname -a
Linux ex-test 2.6.32.1-rscloud #15 SMP Mon Feb 22 13:22:15 UTC 2010 x86_64
x86
For those running OpenVZ/Proxmox containers, one simple workaround is to
disable the imklog module using this :
sed -i -e 's/^\$ModLoad imklog/#\$ModLoad imklog/g' /etc/rsyslog.conf
This fixes the 100% CPU usage of rsyslog in Natty, Oneiric and Precise
containers.
--
You received this bug not
I had what I believe to be the same issue on 12.04 Precise 2.6.32-12-pve
x86_64 running in a Proxmox container. I downloaded
http://archive.ubuntu.com/ubuntu/pool/main/r/rsyslog/rsyslog_4.2.0-2ubuntu8_amd64.deb,
installed, and now the error messages are no longer appearing.
Does this bug need to b
I just upgraded from 10.04 to 12.04 and encountered this problem. As it
turns out I was still using the 10.04 kernel and my Grub menu was
woefully out of date and so was my kernel. I ran
apt-get install grub2
and that fixed my loader problems and also fixed the rsyslogd issue. I
assume that th
Still happens when running 11.10 on Proxmox VE 2.0-beta1 in an OpenVZ container:
Linux lorentz-s19 2.6.32-7-pve #1 SMP Thu Feb 16 09:00:32 CET 2012 i686 athlon
i386 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
same problem under debian squeeze 64bit xen kernel:
Linux oneiric 2.6.32-5-xen-amd64 #1 SMP Thu Nov 3 05:42:31 UTC 2011 x86_64
x86_64 x86_64 GNU/Linux
fixed with:
wget
http://mirror.netcologne.de/ubuntu/pool/main/r/rsyslog/rsyslog_4.2.0-2ubuntu8_amd64.deb
-O /tmp/rsyslog_4.2.0-2ubuntu8_amd64.de
it happens to me on a VPS with :
Linux x.santrex.net 2.6.31.6 #3 SMP Mon May 3 19:58:57 UTC 2010 i686 i686 i386
GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523610
Title:
rsyslogd spins
I see this issue running 11.10; kernel 2.6.32.33-kvm-i386-20110317-dirty.
Temporary workaround was to downgrade to maverick's rsyslogd via: apt-get
install rsyslog=4.2.0-2ubuntu8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
This is still active in 11.04. I am running this under a VPS, running
kernel 2.6.32.19-0.2.99.17.22250fd-xen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523610
Title:
rsyslogd spins CPU on some k
the -rt kernel is still based on 2.6.33. a natty-based system with the
-rt kernel is still prone to this issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/523610
Title:
rsyslogd spins CPU on some
Just to add another option in the spirit of #39. I couldn't find a
simple solution and ended up solving this issue by removing rsyslog
entirely and now use syslog-ng which does everything I need (only issue
when installing was to chown a few logs to root.adm).
--
You received this bug notificatio
I solved this issue for me (no kernel hacker) with going back to the
last Version 4.2.0-2ubuntu5.
(Just want to mention this for other newbies like my)
--
rsyslogd spins CPU on some kernels
https://bugs.launchpad.net/bugs/523610
You received this bug notification because you are a member of Ubu
Right, that's my understanding as well
The design of rsyslog made it very hard to "fall back" to not de-rooting
in the case of an unpatched kernel
--
rsyslogd spins CPU on some kernels
https://bugs.launchpad.net/bugs/523610
You received this bug notification because you are a member of Ubuntu
Bu
Just to correct an earlier comment I made: that patch in bug #515623
(comment 1) ISN'T in 2.6.33.2. I applied it to 2.6.33.2 and kernel
logging now works again. It looks like the patch will be in the vanilla
2.6.34, though. So hopefully 2.6.33 will be the only newer kernel that
doesn't allow kernel
** Changed in: rsyslog (Ubuntu Lucid)
Status: Confirmed => Fix Released
--
rsyslogd spins CPU on some kernels
https://bugs.launchpad.net/bugs/523610
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
Apologies, I'll report it as another bug then.
Is it also the intention that rsyslog won't read kmsg on newer kernels?
(2.6.33 is a newer kernel, not an older kernel).
--
rsyslogd spins CPU on some kernels
https://bugs.launchpad.net/bugs/523610
You received this bug notification because you are
On Sat, 2010-04-17 at 06:18 +, Rocko wrote:
> I confirm Gianvito's findings with 2.6.33.2, ie that the problem is NOT
> resolved. rsyslog isn't using up CPU cycles, but it is failing to read
> kmsg.
>
Then this isn't the reported bug!
status fixreleased
Note that the fact it doesn't read k
I confirm Gianvito's findings with 2.6.33.2, ie that the problem is NOT
resolved. rsyslog isn't using up CPU cycles, but it is failing to read
kmsg.
What I suspect is happening is that attempting a zero-byte read from
ksmg always succeeds, so rsyslog is using the wrong test, eg:
sudo python
>>> i
** Changed in: rsyslog (Ubuntu Lucid)
Status: Fix Released => Confirmed
--
rsyslogd spins CPU on some kernels
https://bugs.launchpad.net/bugs/523610
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
This bug still persist on Lucid:
"localhost kernel: imklog: Cannot read proc file system, 1."
I have a kernel vanilla 2.6.33.2 without patches and rsyslog
4.2.0-2ubuntu8.
--
rsyslogd spins CPU on some kernels
https://bugs.launchpad.net/bugs/523610
You received this bug notification because you
@Scott
Just to check --- is there a risk that the patch to rsyslog will in
effect disable kernel logging on any final lucid release, bearing in
mind that not all the kernels are in sync (particularly armel imx51)
That would surely be bad, but I've probably misunderstood here...
--
rsyslogd spin
** Tags added: iso-testing
--
rsyslogd spins CPU on some kernels
https://bugs.launchpad.net/bugs/523610
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://lists.ubuntu.com/ma
This bug was fixed in the package rsyslog - 4.2.0-2ubuntu8
---
rsyslog (4.2.0-2ubuntu8) lucid; urgency=low
* debian/patches/deroot.patch:
- After opening /proc/kmsg, set the effective user to an unprivileged
one and attempt a zero-byte read from the file. If this succeeds
Gary: because upgrading doesn't actually fix the problem - if you use
Debian's package, your rsyslog is running as *root* - the whole point of
this exercise is to make it not need to. If we were to merge rsyslog,
we'd still use our deroot.patch, so would still hit the same bug
--
rsyslogd spins
Better version of the patch
** Attachment added: "deroot.patchpatch"
http://launchpadlibrarian.net/39737922/deroot.patchpatch
--
rsyslogd spins CPU on some kernels
https://bugs.launchpad.net/bugs/523610
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
why not upgrade rsyslogd? Using debian testing's 4.4.2 package fixed it
for me.
On Wed, Feb 24, 2010 at 12:41 PM, Scott James Remnant
wrote:
> Something like this seems the sanest approach.
>
> After opening /proc/kmsg, attempt a zero-byte read from it - if that
> fails with EPERM then we don't
That patch isn't right, needs to seteuid() around the read() call, but
the module doesn't know what the uid is going to be; wondering whether
hard-coding some number in there will upset pitti
--
rsyslogd spins CPU on some kernels
https://bugs.launchpad.net/bugs/523610
You received this bug notifi
Something like this seems the sanest approach.
After opening /proc/kmsg, attempt a zero-byte read from it - if that
fails with EPERM then we don't load the klog module
** Attachment added: "deroot.patchpatch"
http://launchpadlibrarian.net/39737237/deroot.patchpatch
--
rsyslogd spins CPU on s
Yeah, same here. I have the problem with 2.6.33 as well.
--
rsyslogd spins CPU on some kernels
https://bugs.launchpad.net/bugs/523610
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.
Same here on 2.6.33-020633rc8-generic; downgrading to 4.2.0-2ubuntu5
fixes it. I'd say 2.6.33 isn't an "older" kernel...
** Summary changed:
- rsyslogd spins CPU on older kernels
+ rsyslogd spins CPU on some kernels
--
rsyslogd spins CPU on some kernels
https://bugs.launchpad.net/bugs/523610
Y
33 matches
Mail list logo
