[rsyslog] URGENT - rsyslog stops sshd
Martin Mielke
martinmie at PartyGaming.com
Thu Oct 8 10:50:13 CEST 2009
Hi all,
odd behavior here...
Today one of our core systems stopped accepting ssh connections.
--
$ telnet sshserver 22
Trying 1.2.3.4...
Connected to sshserver.
Escape character is '^]'.
Connection closed.
--
Using a pre-established session rsyslog was shutdown:
--
# /etc/init.d/rsyslog stop
Shutting down system logger: [ OK
][/quote]
--
..and the system started accepting connections again:
--
$ ssh sshserver
Last login: Thu Oct 8 01:12:59 2009 from foo.bar.tld
--
We are just one step before dropping rsyslog and use syslog-ng again
(which was dismissed some time ago to favor rsyslog) but I would like to
know what's the reason for this and, most important, what's the solution
:-)
Some additional info:
--
# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 32767
max locked memory (kbytes, -l) 32
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 32767
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
--
Thanks!
Martin
This email and any attachments are confidential, and may be legally privileged and protected by copyright. If you are not the intended recipient dissemination or copying of this email is prohibited. If you have received this in error, please notify the sender by replying by email and then delete the email completely from your system.
Any views or opinions are solely those of the sender. This communication is not intended to form a binding contract unless expressly indicated to the contrary and properly authorised. Any actions taken on the basis of this email are at the recipient's own risk.
More information about the rsyslog
mailing list