[syslog-ng] syslog-ng crashes
Balazs Scheidler
bazsi@balabit.hu
Mon, 24 Jun 2002 10:44:10 +0200
- Previous message: [syslog-ng]Well, I use the last version of Syslog-ng (1.5.18). Well it looks
as if syslog-ng was crashing itself and then all programsthat are usually
logged via syslog-ng are unable to perform their ownactions (that's why ssh
doesn't work anymore)... In some words, it looks like syslog-ng was
becoming blocking for allapplications.On Fri, 2002-06-21 at 10:28, Balazs
Scheidler wrote:> On Fri, Jun 21, 2002 at 10:23:24AM +0200, Yan DENET
wrote:> > Hi all,> > > > Some quite strange things have happened in my
network since i set up my> > syslog-ng as a log centralizer...> > Actually,
when launched, my syslog-ng ends up to grab all resources of> > the machine
on which it's installed. Then, no way to ssh to it...> > It's really
strange cause normally, syslog-ng should use only very few> > resources...
like syslog !> > Whereas with syslog, everything goes well..> > > > Don't
know what's happening. Could somebody help me ?> > we can't help you unless
you provide more information. which version are you> using, and what do you
mean it ate up all resources?> > does it eat memory, or use all cpu cycles
or?> > -- > Bazsi> PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944
9CFD 804E C82C 8EB1
- Next message: [syslog-ng]io.c:263: failed assertion `i == nfds'
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On Mon, Jun 24, 2002 at 10:24:20AM +0200, Yan DENET wrote:
> Well, I use the last version of Syslog-ng (1.5.18).
> Well it looks as if syslog-ng was crashing itself and then all programs
> that are usually logged via syslog-ng are unable to perform their own
> actions (that's why ssh doesn't work anymore)...
> In some words, it looks like syslog-ng was becoming blocking for all
> applications.
Hmm.. nobody else reported such problems on syslog-ng 1.5.18. I'd need
an strace of the syslog-ng process, or something that leads me to the
solution.
syslog-ng seems to be blocking on something which it shouldn't have. The
only possibility I see right now is DNS. Try use_dns(no) in your global
options, or limit access to your syslog port.
--
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
- Previous message: [syslog-ng]Well, I use the last version of Syslog-ng (1.5.18). Well it looks
as if syslog-ng was crashing itself and then all programsthat are usually
logged via syslog-ng are unable to perform their ownactions (that's why ssh
doesn't work anymore)... In some words, it looks like syslog-ng was
becoming blocking for allapplications.On Fri, 2002-06-21 at 10:28, Balazs
Scheidler wrote:> On Fri, Jun 21, 2002 at 10:23:24AM +0200, Yan DENET
wrote:> > Hi all,> > > > Some quite strange things have happened in my
network since i set up my> > syslog-ng as a log centralizer...> > Actually,
when launched, my syslog-ng ends up to grab all resources of> > the machine
on which it's installed. Then, no way to ssh to it...> > It's really
strange cause normally, syslog-ng should use only very few> > resources...
like syslog !> > Whereas with syslog, everything goes well..> > > > Don't
know what's happening. Could somebody help me ?> > we can't help you unless
you provide more information. which version are you> using, and what do you
mean it ate up all resources?> > does it eat memory, or use all cpu cycles
or?> > -- > Bazsi> PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944
9CFD 804E C82C 8EB1
- Next message: [syslog-ng]io.c:263: failed assertion `i == nfds'
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]