Hi,
I've been experiencing a periodic hang in rsyslog 7.4.7 on a central
logging node that we have.
Everything runs fine for anywhere betwen 6-48 hours, then one thread will
hang at 100% CPU, with strace showing:
select(1, NULL, NULL, NULL, {82024, 797024}^C <unfinished ...>
The selects are always similar. "1, NULL, NULL, NULL" and an increasing
timeout.
The configuration is minimal.. using the old syntax since we just recently
upgraded and I'm lazy.
$DefaultNetstreamDriver gtls
$MainMsgQueueType FixedArray
$MainMsgQueueSize 1000000
$MainMsgQueueWorkerThreads 4
$MainMsgQueueDequeueBatchSize 2000
(then the DriverCAFile/etc defines)
$ModLoad imtcp
$InputTCPMaxSessions 1000
$InputTCPServerStreamDriverMode 1
$InputTCPServerStreamDriverAuthMode anon
$InputTCPServerRun 514
... the rest are just log routing rules and the module imports required to
make the above lines work.
Host is running ubuntu 12.04.
Clients are very similar. Works over TCP, not using RELP. Don't think any
of the clients are hanging but I haven't checked too closely.
Unfortunately the hang isn't frequent enough to do any brute force
debugging. Any ideas what it could be, or what information I could collect
to track it down faster? If I don't figure this out soon I'll have to try
something else, and I don't want to do that :(
Thanks!
-Dormando
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
