Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 3434 - metalog random freezes that require restarting it
Summary: metalog random freezes that require restarting it
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GCC Porting (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Matthew Kennedy (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 8607
  Show dependency tree
 
Reported: 2002-06-05 23:26 UTC by tuxisuau
Modified: 2003-02-04 19:42 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tuxisuau 2002-06-05 23:26:46 UTC
I did install gentoo a week ago with gcc3.1 and CFLAGS=-march=athlon -O3 -pipe.

I've managed to make everything work ok, but metalog sometimes freezes and i
have to restart it, cause all programs that write things to syslog (like
postfix, login, etc) freeze with it. It occurs two or three times a day.
Comment 1 Matthew Kennedy (RETIRED) gentoo-dev 2002-07-16 10:24:02 UTC
This is not a bug. What you are seeing is the buffering nature of metalog. (see
metalog(1)). You can turn the buffing off at runtime with SIGUSR1 and turn it
back on with SIGUSR2.

Matt
Comment 2 tuxisuau 2002-07-16 10:54:24 UTC
This IS a bug. Buffering nature of metalog stands for writing the logs in the hard disk, not from accepting data from servers. 
It's serious enough it makes apps freeze, and yes, it gave the same problem with the buffering disabled.
Now i'm using syslog-ng.

Tuxisuau.
Comment 3 Matthew Kennedy (RETIRED) gentoo-dev 2002-07-16 18:44:10 UTC
If you use -march=i686 (instead of athlon) do you get the same problem? 

Never in several months that I have been using metalog w/ gcc3.0.4 and gcc3.1
have I see the behavior you describe.
Comment 4 Matthew Kennedy (RETIRED) gentoo-dev 2002-07-29 05:52:55 UTC
do you get a freeze at all with syslog-ng?
Comment 5 Sascha Silbe 2002-10-08 11:39:33 UTC
I'm hitting the same bug. Occured during the gcc 2.95.x time and is still happening. Had buffering turned off (-s) and tried it with buffering this week, but it seems to only get worse if buffering is turned on (even happened immediatly after one of the reboots).
See the comments on the other bug for details. As soon as it happens again, I'll attach gdb to metalog. Perhaps I can get more info that way.
And please reopen the bug again, it does NOT work.

PS: athlon-xp CPU