This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
** Branch linked: lp:ubuntu/lucid/rsyslog
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This bug was fixed in the package linux - 2.6.31-17.54
---
linux (2.6.31-17.54) karmic-proposed; urgency=low
[ John Johansen ]
* SAUCE: AppArmor: Fix oops after profile removal
- LP: #475619
* SAUCE: AppArmor: Fix Oops when in apparmor_bprm_set_creds
- LP: #437258
*
Maybe this isn't the place to ask, but is there a bug report or fix for
the underlying CPU throttling problem that is the source of all these
log messages? I can't use Karmic because it throttles my CPU to the
point that of complete unusability.
--
/var/log fills up with all normal messages @
rsyslog message repeat suppression works fine here:
Dec 16 13:03:30 tick rtkit-daemon[1644]: last message repeated 3 times
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because
This bug was fixed in the package rsyslog - 4.2.0-2ubuntu5.1
---
rsyslog (4.2.0-2ubuntu5.1) karmic-proposed; urgency=low
* debian/rsyslog.conf:
- enable $RepeatedMsgReduction to avoid bloating the syslog
file (LP: #453444)
-- Michael Vogt michael.v...@ubuntu.com Fri,
This bug was fixed in the package rsyslog - 4.2.0-2ubuntu5.1
---
rsyslog (4.2.0-2ubuntu5.1) karmic-proposed; urgency=low
* debian/rsyslog.conf:
- enable $RepeatedMsgReduction to avoid bloating the syslog
file (LP: #453444)
-- Michael Vogt michael.v...@ubuntu.com Fri,
Copied to lucid, should be tested there a little first.
** Changed in: rsyslog (Ubuntu)
Status: In Progress = Fix Released
** Changed in: rsyslog (Ubuntu Karmic)
Status: Fix Released = Fix Committed
--
/var/log fills up with all normal messages @ about 575/sec fill up the
** Tags added: verification-done
** Tags removed: verification-needed
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The I noticed effect of this bug this morning for the first time and
after screwing up the bug reporting process a few times I note this bug
is apparently fixed in -17, but my version is -16, and I can see no
upgrade to -17 in the update manager, nor do I see any version beyond
-16 in the
The I noticed effect of this bug this morning for the first time and
after screwing up the bug reporting process a few times I note this bug
is apparently fixed in -17, but my version is -16, and I can see no
upgrade to -17 in the update manager, nor do I see any version beyond
-16 in the
-17 is in proposed, not in the official repo yet.
To install it you would need to add karmic-proposed to your list of
supported repositories.
You can do it either via a GUI (e.g. synaptic) or by directly adding the
following line to your /etc/apt/sources.list
deb
Seems fixed in 2.6.31-17
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Accepted linux into karmic-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: linux (Ubuntu Karmic)
I installed the kernels from comment #39 by Osagawara and it does solve
the problem. However, when Karmic installs updated kernels from the
repository the problem resurfaces. Any idea if and when these fixes
will make it into the mainstream kernel? I would have thought this
would have already
I have the same problem. The log files are huge. I do not receive messages on
the cpu but normal messages but that is repeated every second and increase the
use of just the cpu and hd space.
CRON[2730]: pam_unix(cron:session): session opened for user brain by (uid=0)
My / etc / syslog.conf
I could not put the other because I had to log excui them to reactivate
the system
** Attachment added: log
http://launchpadlibrarian.net/36534136/dmesg.1.gz
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You
I could not put the other because I had to log excui them to reactivate
the system
** Attachment added: log
http://launchpadlibrarian.net/36534165/dmesg.2.gz
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You
I'm sad to report that the latest Ubuntu's kernel update broke Ogasawara's
package.
We've just ran the update manager in some machines, and all of them asked to
update the kernel. After that, many modules stopped being loaded, including
snd-hda-intel.
All these machines used a custom Ubuntu
for all unhappy people who reinstalled their loved operating system only
because of this bug:
there exists a very simple temporal solution!!!
1) stop rsyslog service (#service rsyslog stop)
2) (backup and) delete all huge files in /var/log
3) copy the file 10-temperature.conf attached in the
Does anyone know when Osagawaras' fix will make into into the mainline
kernels for ubuntu 9.10? It seems like the answer should be
straightforward but no one seems to want to comment on it.
Juan
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
** Branch linked: lp:ubuntu/linux-mvl-dove
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Branch linked: lp:ubuntu/linux-fsl-imx51
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Is this fixed in Karmic?
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
No it isnt and its really annoying.. It also tends to just generally
flood the screen with those messages during boot.
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you
In the heading of this page I see Fix Committed... when should it
become Released?
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a member of Ubuntu
Bugs, which
I think this problem has affected me, bigtime. I recently tried to
hibernate running Karmic, and got this message, over and over again.
Here is an example:
Dec 1 08:02:42 compname kernel: [35031.545470] CPU0: Temperature/speed normal
Dec 1 08:02:42 compname kernel: [35031.545638] CPU0:
The fix above in comment #57 helped right away, no reboot required. In
my case, the syslogd process itself was actually stopping the
temperature from coming down in this fanless unit..
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
To clarify: when I said the new kernel solves the problem for me I meant
the kernel that was pre-released by Leann (see comment #39) - not the
one in the repositories.
My kernel is:
2.6.31-16-generic #51~lp453444 SMP Wed Nov 11 07:45:32 UTC 2009 x86_64
GNU/Linux
And it definitely solves the
Looks like, that primary P4 systems have the problem
(I've not registered this issue before karmic and the syslog replacement called
rsyslog).
My P4 3.0 GHz is running since the first day with a temperature 70...75°C, its
not a fan issue or cooling problem.. its designed by Intel.
I've
Confirming that the new kernel totally solves the problem for me. I'm
using the 64-bit one.
I see an occasional CPU1: Temperature above threshold, cpu clock
throttled and then CPU1: Temperature/speed normal but no flooding of
the logs occurs. Instead the number of occurrences appears as in
Bug still present for me on ubuntu server with kernel 2.6.31-15-generic-
pae (package linux-image-2.6.31-15-generic-pae, version 2.6.31-15.50).
If the CPU is under high load and over heating message is repeated very often
(100 times/second).
The trick from embecka to discard these messages works
Thanks embecka, your conf file fix worked for me too.
everything now is ok!
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The issue with the kernel side is definitely fixed by:
3967684006f30c253bc6d4a6604d1bad4a7fc672 - cleanup commit first and
b417c9fd8690637f0c91479435ab3e2bf450c038 - for the actual storm.
Tested on Intel(R) Celeron(R) CPU 2.80GHz on 2.6.31-14-generic.
Re: kernel posted earlier - looks like I
Thanks embecka, your conf file fix worked for me.
The messages stopped cold after writing the new conf file and restarting
rsyslog (they had been streaming in at the usual alarming rate just
prior to the fix). Just to be sure, I ran a disk scan of a 40 GB
partition that took about 5 minutes. So
I had this issue when transfering a Sony Vaio laptop with a P4 processor from
XP to Ubuntu. Starting Ubuntu with noapic option solve the problem but I don't
thing log file should be allowed to grow to more than 150Mo.
It is of no use and it is possible to lock the computer. Size limit should be
I wrote a file /etc/rsyslog.d/10-temperature.conf with the following
content:
:msg,contains,Temperature/speed normal ~
:msg,contains,Temperature above threshold ~
All messages containing Temperature/speed normal and Temperature above
threshold are discarded.
I restarted rsyslog and it looks
Ariel, I suggest you to put all (IIRC) three packages in the same folder and
run # dpkg -i *
The nVidia module may be missing the kernel headers.
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this
Thanks so much Raphael,
My installation issue is gone after following your helpful suggestion.
Sorry for the false alarm.
I've not yet verified that this new kernel has solved the logging problem for
me,
but I can confirm at this point that there's no issue with 64-bit and/or nvidia
drivers
I was hopeful that MarkJBobak's suggestion to filter out CPU Temperature
messages before passing them to rsyslog would work, but it actually made
my system unbootable. On boot, my computer would halt after mounting and
checking the disk partitions, even in recovery mode. I found the
following
I had the same symptoms as Matt, I haven't had a chance to check the
syslog messages yet to see if it is exactly the same.
To cheekily repeat my question on the forum thread for this bug
it says that the milestone for this is Ubuntu karmic-updates which has an
expected date of 2011-04-09!
Does
Ubername, I don't belive it will take that long, as Ogasawara already
pre-released the required patched kernel images that fixes this bug.
Those who are still trying to workaround this bug (and flooding the bug
report, I must say), should try installing the kernel that Leann
uploaded. I've been
Installed the kernel Leann uploaded and it's working fine. Thanks
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ogasawara -
I finally got around to installing the patched kernel and headers you
provided and they appear to be working. My Fujitsu N5010 P4 laptop is
no longer being bogged down by excessive cpu temperature messages to
/var/log/messages. I tried taxing the system by running a full file
system
FWIW:
Tried to install the test kernels from Leann, and it looks like they are not
playing nice with the nvidia drivers
(I know, they are not free, but they did work with all officials kernels so far)
If I'm doing anything wrong, please let me know.
Here's my session:
$ sudo dpkg -i
I have been bothered by this problem repeatedly so I finally took the
following steps:
ln -s /dev/null syslog
ln -s /dev/null kern.log
That should take care of most of the problem. Why is it taking so long
to fix this and why did it happen in the first place?
ARRRG!!
--
/var/log
I've got a friend with the same bug on Ubuntu karmic (toshiba satellite M167)
CPU0: Temperature above threshold, cpu clock throttled (total events = 4220841)
Either with kernel 2.6.31.14 or 2.6.32.4
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
Hi all,
This bug has been a real pain in my backside. I think I have a
reasonable, short-term workaround. I'm *not* suggesting this is a
permanent fix for anyone, nor should this be applied to any source trees
anywhere.
This is strictly for someone who, like me, is suffering because of this,
After my last rebooting the problem seemed to be taken out ...
That means that neither dd or rsylogd 'destroy' the system .
In the /var/log directory I found that kern.log , messages , syslog files
appear double :
ls -s command lists :
0 kern.log 4 messages 4 syslog
I find a solution with my laptop that have this problem and a very long
boot time (about 15 minutes) : sony vaio pcg-grt716s
I edit /boot/grub/grub.cfg and i add noapic nomce options to line :
linux /boot/vmlinuz-2.6.31-15-generic root=UUID= ro splash quiet
noapic nomce
I find that
When can we hope a fix ?
use karmic with this bug is impossible !
Nico
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Again, I think the core problem the problem is not intrinsically with
rsyslogd.
While I agree that there ought to be a flooding failsafe in rsyslogd,
the base problem here is the CPU temperature sensors algorithm in the
kernel and the reporting of errant messages.
I earlier thought this was due
Test kernels (amd64 and i386) are available at the following. Please
let us know your results. Thanks.
http://people.canonical.com/~ogasawara/lp453444/
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You
Thanks, Ogasawara. I'll be testing it in few minutes.
Those who for some reason do not want to install the test kernel above can just
disable syslog from running on system startup. You can do this by commenting
the uncommented lines in /etc/init/syslog.conf.
Note that it will prevent syslog
Thanks Ogasawara,
I have the same problem than others in the list with my Quad core Q6600
processor.
I tested your kernel patch for i386 given above in #39 post. It refuses
to launch GDM to login on. The login screen is the console one. And the
display of login screen in text mode was
Ogasawara -
I will your test kernels a try when I get home tonight and post the
results here.
Cheers,
Juan
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a
my nomination for jaunty was an error, soory
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I was getting these messages filling up my root hard drive very quickly.
I discovered that my heat sink was all clogged up with dust and cleaning
it fixed the errors, but it shouldn't be doing this anyway. Eventually
my heat sink is going to get gunked up again and the only way I'm going
to know
Please excuse me if I'm wrong, but libsensors4 was mentioned before in this
page.
I don't think this bug has any relationship with libsensors4 or 3. I tried
purging libsensors3 and rebooting, but the problem persists.
Also, it seems that this bug is triggered only when the temperature goes
up -
I agree with Raphael Campos. I do not see the symptoms from a cold
boot. In my case if I do a find for example and search for a file in
my entire file system the cpu temperature starts to go up rapidly and
then this starts triggering the dd and rsyslogd load spikes. The
problem is that it's a
Interesting. I applied all the updates from the ubuntu site just
nowapparently there were some new ones today and now I cannot
reproduce the problem on my Fujitsu N5010. In fact I am composing this
message from that laptop after heaving searched my entire file system
several times trying to
Scratch that last comment :-). It took a while for the machine to
heat up (from a cold boot) but I can now see the cpu load spike at 100%
for dd and rsyslogd. It looks like the problem persists.
Juan
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available
** Tags added: 2.6.31.6
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Here you go. This was triggered when I went to www.adobe.com using
firefox and the flash videos started playing on their site...
Nov 10 15:40:03 bonsai kernel: [ 1560.857817] CPU0: Temperature/speed normal
Nov 10 15:40:03 bonsai kernel: [ 1560.857822] CPU1: Temperature/speed normal
Nov 10
The patch for the kernel side of things to quit spamming the logs should
be coming in the next 2.6.31.6 upstream stable patch set that we'll pull
into Karmic . I'll try to put together a test kernel with this patch
for people to test. Thanks.
ogasaw...@emiko:~/linux-2.6$ git show
Just want to note that I am experiencing this also, to near-disastrous
results.
Symptoms: log spew seen in 'dmesg' quickly filling up logs in '/var/log';
top shows a 'dd' process pegging a CPU, running as root, which I believe
is doing the writing. This has caused my system to lock up hard, and
Same here. Pentium 4 1,5GHz, some old HP motherboard. I'm laic in hardware, but
I don't know it has any sensors at all.
The repeated line in var/log/syslog is:
Nov 9 12:19:10 Rencznie-Inkrustowany-Kartofel kernel: [ 2527.403083] CPU0:
Temperature above threshold, cpu clock throttled (total
** Changed in: linux (Ubuntu Karmic)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug
I get the same errors that taka jedna gets. The exact same messages
about Temperature above threshold, cpu clock throttled, etc. I mean
thousands of these messages per minute. This machine has always run
like this. I has always run hot and when it gets too hot the cpu is
throttled down and the
I have the same problem. I'm using ubuntu 9.10 on a fujitsu N5010
laptop with a P4 at 3.2 Ghz. Normal temperature swings generate
thousands of messages in /var/log/messages about the CPU
temperaturelike so
Nov 8 15:48:10 bonsai kernel: [ 4428.945041] CPU0: Temperature/speed
normal
The
Enabled karmic-proposed yesterday, and made an update. I saw that it
added the new rsyslog package, but I am still getting all these lines in
three logs, kern.log, syslog as well as messages.
Mind you, I'm a bit of a noob when it comes to this, so please tell me
if you want me to issue some
There are three problems:
1) the libsensors4 package does not contain the drivers for certain
motherboard sensors. The bug is that It returns an out of range error
repeatedly (many times per minute) instead of a no sensors found
error, which ought to trigger completely different behavior vis a
As a temporary fix I can suggest setting up a separate partition for
/var/log. Say about 300 megs to a gig depending on the hdd size. Now
this will probably require non-primary partitions to be setup, but at
least it will keep the logs at bay until the patch is out.
The other solution is more
Hello,
just a useful hint on how to get into the system: After some time of
working with the quite slow Karmic version (now I know why) and a
regular shutdown, the next day I couldn't run Ubuntu any more. After
entering the password and some minutes of intensive working, the system
returned to
the same problem to me - no log rotation and I getting CPU messages too
(patch didn't help me)
$ uname -a
Linux ubuntu 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009
x86_64 GNU/Linux
$ lsb_release -a
...
Release:9.10
Codename: karmic
$ df -ha
Filesystem
I had this one affect me. A fun workaround I discovered was to prevent
the CPU from getting hot by placing my laptop on top of a cooling rack.
No heating - no overheating - no excessive logging - no full disk -
program no longer crashes due to lack of tmp file space.
--
/var/log fills up with
Seeing the same problem on my desktop.
Another side effect is 'logcheck' never being able to catch up with the
logs so multiple logcheck processes accumulate over time and the system
becomes overloaded with logcheck processes taking all CPUs at close to
100% utilization.
Seems like pretty high
Sorry to have to add one more piece of info.
The suggested rsyslog.conf duplication mitigation is not very effective
because when you have many CPUs the messages are not identical dups and
so they aren't being suppressed.
e.g. after adding
$RepeatedMsgReduction on
to /etc/rsyslog.conf, and
** Changed in: rsyslog (Ubuntu Karmic)
Milestone: None = karmic-updates
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Steve,
sorry that I have not added more background to the fix. I tested this
change with the attached test program. Before the change each line is
printed, afterwards the behaviour is similar to the old syslog that
prints last message repeated 62 times.
** Attachment added: test program
The upstream documentation for the option is here http://www.rsyslog.com
/doc-rsconf1_repeatedmsgreduction.html
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a
Commit b417c9fd8690637f0c91479435ab3e2bf450c038 in Linus' tree fixes the
problem of the kernel spamming the logs.
This commit is in the ubuntu kernel now.
** Changed in: linux (Ubuntu Karmic)
Status: New = Invalid
--
/var/log fills up with all normal messages @ about 575/sec fill up the
This diff should turn on the duplication detection in rsyslog:
diff -u rsyslog-4.2.0/debian/rsyslog.conf rsyslog-4.2.0/debian/rsyslog.conf
--- rsyslog-4.2.0/debian/rsyslog.conf
+++ rsyslog-4.2.0/debian/rsyslog.conf
@@ -35,6 +35,9 @@
#
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
Looks reasonable. Please push, mvo, and thanks for looking into this
one!
--
/var/log fills up with all normal messages @ about 575/sec fill up the
available space
https://bugs.launchpad.net/bugs/453444
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: rsyslog (Ubuntu Karmic)
Status: Incomplete = In Progress
** Changed in: rsyslog (Ubuntu Karmic)
Importance: Undecided = High
** Changed in: rsyslog (Ubuntu Karmic)
Assignee: (unassigned) = Michael Vogt (mvo)
--
/var/log fills up with all normal messages @ about
Has anyone tested that $RepeatedMsgReduction works sensibly? The actual
change is small and makes sense, but I have no idea about the precise
semantics of this option and what other bugs this might cause.
I think this is best left for an SRU, where we can test it without
rushing.
--
/var/log
86 matches
Mail list logo
