1 |
On Tuesday 02 February 2010 04:06:14 Iain Buchanan wrote: |
2 |
> On Fri, 2010-01-29 at 17:29 +0200, Alan McKinnon wrote: |
3 |
> > On Friday 29 January 2010 16:26:42 Iain Buchanan wrote: |
4 |
> > > I don't really care about any killswitch operation, but I'm interested |
5 |
> > > in why I'm getting a "." message. NetworkManager bug or |
6 |
> > > misconfiguration error? |
7 |
> > |
8 |
> > |
9 |
> > Run syslog-ng with the -d switch to enable it's debug output (normally |
10 |
> > to messages), or use -dd to get even more debug output. |
11 |
> > |
12 |
> > Beware, this adds up real quick, so don't run it for long like that. The |
13 |
> > output may give you more of a clue as to what syslog-ng thinks the |
14 |
> > incoming messages are. |
15 |
> |
16 |
> Holy Debug Messages, Batman! Sure does add up real quick. |
17 |
> |
18 |
> 56,599 messages all with the same timestamp Feb 2 11:13:00; 100% cpu |
19 |
> usage, and 200+Mb before I killed it. |
20 |
> |
21 |
> Shirley that's not right? |
22 |
> |
23 |
> The 50k of messages all look like this: |
24 |
> |
25 |
> Feb 2 11:12:59 orpheus syslog-ng[3739]: Filter rule evaluation begins; |
26 |
> filter_rule='f_networkmanager' Feb 2 11:12:59 orpheus syslog-ng[3739]: |
27 |
> Filter node evaluation result; filter_result='not-match' Feb 2 11:12:59 |
28 |
> orpheus syslog-ng[3739]: Filter rule evaluation result; |
29 |
> filter_result='not-match', filter_rule='f_networkmanager' |
30 |
|
31 |
That's definitely not right. Even with full debugging enabled no app should |
32 |
emit that amount of logs. |
33 |
|
34 |
Seeing as we are dealing with networkmanager with it's long history of being |
35 |
hard to deal with, I recommend you |
36 |
|
37 |
a. recognize the truth - that it is a piece of shit |
38 |
b. use wicd instead, which is decidedly not a piece of shit |
39 |
|
40 |
:-) |
41 |
|
42 |
|
43 |
-- |
44 |
alan dot mckinnon at gmail dot com |