|
General software and network General OS-independent software and network questions, X11, MTA, routing, etc. |
|
Thread Tools | Display Modes |
|
||||
Thanks for your reply anomie.
I must confess this machine runs Linux Red Hat. It is running OpenSSH version: OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003 Here is the latest log snippet. Code:
Apr 25 19:50:11 log02 sshd[3180]: Received signal 15; terminating. Apr 27 11:28:04 log02 sshd[3155]: Server listening on :: port 22. Apr 27 11:28:04 log02 sshd[3155]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Code:
Nov 19 09:39:03 log02 sshd[3153]: Received signal 15; terminating. Nov 19 09:39:06 log02 sshd[6573]: Server listening on :: port 22. Nov 19 09:39:06 log02 sshd[6573]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Nov 19 09:40:17 log02 sshd[6573]: Received signal 15; terminating. Nov 19 09:40:20 log02 sshd[7597]: Server listening on :: port 22. Nov 19 09:40:20 log02 sshd[7597]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
__________________
"Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." |
|
||||
Quote:
Anyway, let me ask you: are you perchance restarting the iptables service around the same time that you are seeing those sshd restarts? The reason I ask is I've noticed that if you have a default DROP policy for your INPUT chain, then restarting the iptables service may 1) terminate your current ssh connection; 2) generate unusual log messages from sshd similar to what you've posted. If you (or someone) are not restarting iptables, then it looks like some process is trying to kill sshd and then fire up another one too quickly (since it says it can't bind to tcp 22). Maybe logrotate? Although that doesn't explain the seemingly random times you're seeing.
__________________
Kill your t.v. |
|
||||
You are right anomie. I have a script that changes the INPUT chain's policy for some maintenance operations. This might be cause of my worries.
Thank you very much for your answer anomie. That was very helpful. Thanks!
__________________
"Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Basic sshd hardening | anomie | Guides | 12 | 12th September 2008 03:39 AM |
sshd doesn't time out | arch | FreeBSD Security | 4 | 6th September 2008 12:23 PM |
cupsd and sshd slow | mururoa | FreeBSD General | 3 | 27th August 2008 08:36 PM |
High disk activity crashes machine (sudden reboot) | Damien787 | FreeBSD General | 10 | 12th June 2008 03:28 PM |
sshd and timeout | Sunsawe | FreeBSD Security | 6 | 29th May 2008 12:54 PM |