I saw these in /var/log/messages Feb 19 13:45:23 box1 kernel: dpti0: Trying to Abort cmd=835603 Feb 19 13:45:23 box1 kernel: dpti0: Abort cmd not supported Feb 19 13:45:23 box1 kernel: dpti0: Trying to reset device Feb 19 13:45:23 box1 kernel: dpti0: Device reset not supported Feb 19 13:45:23 box1 kernel: dpti0: Bus reset: SCSI Bus 0: tid: 9 Feb 19 13:45:23 box1 kernel: dpti0: Bus reset success. On Saturday 19 February 2005 02:56 pm, Jeffrey Laramie wrote:
On Saturday 19 February 2005 00:20, Alex Daniloff wrote:
Hello SuSE folks, Today I wasn't able to login on my remote server over ssh, although the server was pingable. After about ten minutes I was able to login and I found these records in /var/log/warn Feb 18 16:13:50 box1 kernel: dpti0: Bus reset: SCSI Bus 0: tid: 9 Feb 18 16:13:50 box1 kernel: dpti0: Bus reset success. Feb 18 16:19:00 box1 kernel: dpti0: Bus reset: SCSI Bus 0: tid: 9 Feb 18 16:19:00 box1 kernel: dpti0: Bus reset success. Feb 18 16:23:21 box1 kernel: SFW2-OUT-ERROR IN= OUT=eth0 SRC=xxx.xxx.xxx.xxx DST=xxx.xxx.xxx.xxx LEN=52 TOS=0x10 PREC=0x 00 TTL=64 ID=2147 DF PROTO=TCP SPT=22 DPT=44630 WINDOW=2088 RES=0x00 ACK FIN URGP=0 OPT (0101080A36F612A8927EDD69)
Were there any interesting messages in /var/log/messages at this time or just before it? Unless you did something to change the configuration, this looks like a hardware problem. The firewall message is probably the server trying to respond to a RELATED packet on a broken connection that had been reset.
Jeff