Am Di, den 13.07.2004 schrieb Michael Yep um 3:37: > >Failed to bind: 0.0.0.0 port 22 (Address already in use) : 1 Time(s) > > This occurs in my LogWatch everyday. I am a little paranoid, but I just > don't want a "man-in-the-middle" process intercepting my ssh data / passwords > Michael Yep I just could create the log entry. It is good to be open eyed but in this case you see something uncritical. To reproduce I did a "service sshd restart" and tailed /var/log/secure: Jul 13 03:50:34 serendipity sshd[2081]: Received signal 15; terminating. Jul 13 03:50:34 serendipity sshd[7124]: Server listening on :: port 22. Jul 13 03:50:34 serendipity sshd[7124]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Can it be that you change your runlevel by hand, maybe booting into init 3 and then changing that by hand to 5? Check the exact times in your secure log file to have an idea what exactly you might do at the times when the message is logged. Alexander -- Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13 Fedora GNU/Linux Core 2 (Tettnang) on Athlon CPU kernel 2.6.6-1.435.2.3.uml Serendipity 03:51:31 up 1:33, 8 users, 0.03, 0.19, 0.32
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
