imap,pop3 and ssh won't work after reboot

[shantec]

i have rebooted my redhat 7.2, after the system load went very high, at sendmail.
now my imap , pop3 and ssh won't work.although my ports, 110, 143,22 are all open , and all daemons are working

thank you ,
shawn

 

[Morsing]

Maybe a full file system??

Anyhting in the log??

Cheers Henrik Morsing
IBM Certified AIX 4.3 Systems Administration

 

[shantec]

Henrik,

thank you for your reply,


i get these errors st sendmail logs, dics usage is only at 23%

pop3 service init from UNKNOWN
imap service init from UNKNOWN
MAIL/EXPN/VRFY/ETRN during connection
to MTA
DSN: Local configuration error
config error: mail loops back to
me (MX problem?)
DSN: Data format error

Service sshd:
Bind to port 22 on 0.0.0.0 failed: Address already in use.: 2 Time(s)

sshd[12523]: fatal: Cannot bind any address.

thank you

 

[marsd]

Yuck..
You've got problems with your dns and mail config..your sshd cannot bind() due to a process(sshd) already bound and listening(?), and it looks like pop3 and imap might be working.

Post the results of lsof -i -n, and
kill -hup all pids listed in:
lsof -i -n | awk ' {
if ($2 ~ /[0-9]+/) {
print $2
}
}'

Who does your dns?

 

[shantec]

lsof -i -n, produces these results.....



COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
portmap 789 root 3u IPv4 985 UDP *:sunrpc
portmap 789 root 4u IPv4 986 TCP *:sunrpc (LISTEN)
rpc.statd 817 root 4u IPv4 1006 UDP *:imaps
rpc.statd 817 root 5u IPv4 1215 UDP *:32790
rpc.statd 817 root 6u IPv4 1218 TCP *:32768 (LISTEN)
miniserv. 1434 root 4u IPv4 1609 TCP *:20000 (LISTEN)
miniserv. 1434 root 5u IPv4 1610 UDP *:20000
mysqld 1469 root 3u IPv4 1657 TCP *:mysql (LISTEN)
mysqld 1471 root 3u IPv4 1657 TCP *:mysql (LISTEN)
mysqld 1472 root 3u IPv4 1657 TCP *:mysql (LISTEN)
mysqld 1473 root 3u IPv4 1657 TCP *:mysql (LISTEN)
miniserv. 1474 root 4u IPv4 1695 TCP *:10000 (LISTEN)
miniserv. 1474 root 5u IPv4 1696 UDP *:10000
httpd 12355 root 22u IPv4 56829 TCP xxx.xx.xx.xxx:http (LISTEN)
xinetd 13916 root 3u IPv4 68819 TCP *:imap (LISTEN)
xinetd 13916 root 4u IPv4 68820 TCP *:imaps (LISTEN)
xinetd 13916 root 5u IPv4 68821 TCP *op3 (LISTEN)
xinetd 13916 root 8u IPv4 68823 TCP *:ftp (LISTEN)
miniserv. 15825 root 5u IPv4 1696 UDP *:10000
miniserv. 15825 root 8u IPv4 77945 TCP xxx.xx.xx.xxx:10000->xxx.xxx.x.x.:1281 (ESTABLISHED)
sshd 18080 root 3u IPv4 86339 TCP *:ssh (LISTEN)
miniserv. 18696 root 5u IPv4 1696 UDP *:10000
miniserv. 18696 root 8u IPv4 90834 TCP xxx.xx.xx.xxx:10000->xxx.xxx.x.x:2295 (ESTABLISHED)
miniserv. 19352 root 5u IPv4 1696 UDP *:10000
miniserv. 19352 root 8u IPv4 93167 TCP xxx.xx.xx.xxx:10000->xxx.xxx.x.x:4702 (ESTABLISHED)
miniserv. 19361 root 5u IPv4 1696 UDP *:10000
miniserv. 19361 root 8u IPv4 93194 TCP xxx.xx.xx.xxx:10000->195.174.8.6:4720 (ESTABLISHED)
httpd 22889 root 22u IPv4 56829 TCP xxx.xx.xx.xxx:http (LISTEN)
httpd 22890 root 22u IPv4 56829 TCP xxx.xx.xx.xxx:http (LISTEN)
httpd 22891 root 22u IPv4 56829 TCP xxx.xx.xx.xxx:http (LISTEN)
httpd 22892 root 22u IPv4 56829 TCP xxx.xx.xx.xxx:http (LISTEN)
httpd 22893 root 22u IPv4 56829 TCP xxx.xx.xx.xxx:http (LISTEN)
httpd 22894 root 22u IPv4 56829 TCP xxx.xx.xx.xxx:http (LISTEN)
httpd 22900 root 22u IPv4 56829 TCP xxx.xx.xx.xxx:http (LISTEN)
httpd 22901 root 22u IPv4 56829 TCP xxx.xx.xx.xxx:http (LISTEN)
httpd 24393 root 22u IPv4 56829 TCP xxx.xx.xx.xxx:http (LISTEN)
httpd 24400 root 22u IPv4 56829 TCP xxx.xx.xx.xxx:http (LISTEN)
httpd 24401 root 22u IPv4 56829 TCP xxx.xx.xx.xxx:http (LISTEN)
httpd 29364 root 22u IPv4 56829 TCP xxx.xx.xx.xxx:http (LISTEN)
sendmail 30224 root 4u IPv4 135443 TCP *:smtp (LISTEN)
miniserv. 30510 root 5u IPv4 1696 UDP *:10000
miniserv. 30522 root 5u IPv4 1696 UDP *:10000
miniserv. 30859 root 5u IPv4 1696 UDP *:10000
miniserv. 30859 root 8u IPv4 137129 TCP xxx.xx.xx.xxx:10000->xxxxxxxxxx:1767 (ESTABLISHED)

thank you,

shawn

 

[marsd]

Did you mess with any of your configs before the problem?
You are using webmin I notice, does this work?

Otherwise I would just issue a hup to all server and xinetd processes and start trying to figure out what works and what doesn't.
If a server does not respond or errors out, kill it and
then check your logs. You may want to check out man syslog.conf and set up logging for any event right now
instead or warning or critcal entries and add an entry
for your daemon processes.