On Thu, Jun 10, 2010 at 8:54 AM, Oron Peled wrote:
>
> On Wednesday, 9 בJune 2010 15:14:44 Amit Aronovitch wrote:
> > Recently I stopped getting any messages in /var/log/messages (and probably
> > ...
> > 1) /etc/syslogd.conf is debian's standard, seems to support
> > /var/log/messages (as ever):
On Wednesday, 9 בJune 2010 15:14:44 Amit Aronovitch wrote:
> Recently I stopped getting any messages in /var/log/messages (and probably
> ...
> 1) /etc/syslogd.conf is debian's standard, seems to support
> /var/log/messages (as ever):
>
> *.=info;*.=notice;*.=warn;\
> auth,authpriv.none;\
>
2010/6/9 Amit Aronovitch
> Hi,
>
> Recently I stopped getting any messages in /var/log/messages (and probably
> some other files as well). Basic tests I could think of all check out OK
> (see below). Any ideas what I should check next?
> Using sysklogd+klogd 1.5 on Debian (unstable).
>
>
Permissi
On Wed, Jun 9, 2010 at 3:27 PM, linux.il wrote:
>
> >
> > 5) Google found some similar problem reports, but they all turned out to be
> > either filesize overflow (have plenty of place on the /var/ partition btw),
> > or crashed daemon.
> >
> may be your /var is out of inodes?
nope, I think:
pen
On Wed, Jun 9, 2010 at 3:26 PM, Valery Reznic wrote:
> Connect to syslogd with strace:
>
> strace -p syslogd_pid
>
> And then "provoke" message that should go to /var/log/messages
> strace will show you what syslogd do.
> May be it will reveal cause of the problem.
>
Does not help much. After the
Connect to syslogd with strace:
strace -p syslogd_pid
And then "provoke" message that should go to /var/log/messages strace will show
you what syslogd do.May be it will reveal cause of the problem.
Valery
--- On Wed, 6/9/10, Amit Aronovitch wrote:
From: Amit Aronovitch
Subject: pro
>
> 5) Google found some similar problem reports, but they all turned out to be
> either filesize overflow (have plenty of place on the /var/ partition btw),
> or crashed daemon.
>
may be your /var is out of inodes?
___
Linux-il mailing list
Linux-il@cs.
Hi,
Recently I stopped getting any messages in /var/log/messages (and probably
some other files as well). Basic tests I could think of all check out OK
(see below). Any ideas what I should check next?
Using sysklogd+klogd 1.5 on Debian (unstable).
1) /etc/syslogd.conf is debian's standard, seems
