You have twins? Are they physically close to each other? Can you swap hardware from the good server to the bad server?
Mike M. On Tuesday 19 February 2002 11:58 am, you wrote: > I have two servers that are consistently reporting what appears to be a > SCSI timeout error. I have two other servers with the same model > hardware (one of which is literally a copy of the one below) that are > not reporting this problem. The error that I am looking at (AAC:SCSI > Channel[0]: Timeout Detected On 1 Command(s)) always occurrs after the > "su(pam_unix)[12432]: session closed for user nobody" but as you can see > there is no time relationship. I'm not sure what is going on here and > anything to point me in the right direction would be appreciated. The > hardware is Dell PowerEdge 2400. The OS is RH 7.2. The BIOS and PERC2 > are up-to-date. I guess one of my main questions is: Is this a kernel > issue or a hardware issue? > > > Feb 17 11:06:58 betaserver su(pam_unix)[12422]: session opened for user > nobody by (uid=0) > Feb 17 11:06:58 betaserver su(pam_unix)[12422]: session closed for user > nobody > Feb 17 11:18:30 betaserver su(pam_unix)[12432]: session opened for user > nobody by (uid=0) > Feb 17 11:18:30 betaserver su(pam_unix)[12432]: session closed for user > nobody > Feb 17 21:50:11 betaserver kernel: AAC:ID(0:02:0) Timeout detected on > cmd[0x2a] > Feb 17 21:50:11 betaserver kernel: > Feb 17 21:50:11 betaserver kernel: AAC:SCSI Channel[0]: Timeout Detected > On 1 Command(s) > Feb 17 21:50:11 betaserver kernel: > Feb 17 22:30:08 betaserver kernel: AAC:ID(0:01:0) Timeout detected on > cmd[0x2a] > Feb 17 22:30:08 betaserver kernel: > Feb 17 22:30:08 betaserver kernel: AAC:SCSI Channel[0]: Timeout Detected > On 1 Command(s) > Feb 17 22:30:08 betaserver kernel:
