Carsten,

The incomplete-ness was the result of syslogd falling over (took me a
while to figure it out).  It was also the reason authentication, sshd
and telnet weren't working properly.  I killed the syslogd process and
restarted syslogd and the server is operational again...

There has been no sense (dasd) messages logged to syslog since then
either...  I'ld be interested to see what is causing the log entries all
the same... It would be great if it was possible to decode the sense
data, but it's not as urgent now...

Regards

Donal

Carsten Otte wrote:
> 
> Hi Donal!
> 
> The message you see recently indicates that the
> problem was recoverable (dasd driver says
> "postprocessing successfull error recovery action".
> The 20:35 message seems to have the same sense
> data (those hex values), but is not complete. There
> should be a third line of sense data and some more
> messages - probably after the mark?
> Since we've got a long weekend in Germany this time,
> I'll try to decode the sense data on Tuesday, stay tuned.
> 
> mit freundlichem Gruß / with kind regards
> Carsten Otte
> 
> IBM Deutschland Entwicklung GmbH
> Linux for eServer development - device driver team
> Phone: +49/07031/16-4076
> IBM internal phone: *120-4076
> --
> We are Linux.
> Resistance indicates that you're missing the point!
> 
> |---------+---------------------------->
> |         |           "Post, Mark K"   |
> |         |           <[EMAIL PROTECTED]|
> |         |           m>               |
> |         |           Sent by: Linux on|
> |         |           390 Port         |
> |         |           <[EMAIL PROTECTED]|
> |         |           IST.EDU>         |
> |         |                            |
> |         |                            |
> |         |           05/18/02 11:30 PM|
> |         |           Please respond to|
> |         |           Linux on 390 Port|
> |         |                            |
> |---------+---------------------------->
>   
>>--------------------------------------------------------------------------------------------------------------|
>   |                                                                                  
>                            |
>   |       To:       [EMAIL PROTECTED]                                          
>                            |
>   |       cc:                                                                        
>                            |
>   |       Subject:  Re: Strange problem [Suse Linux on S390 VM]                      
>                            |
>   |                                                                                  
>                            |
>   |                                                                                  
>                            |
>   
>>--------------------------------------------------------------------------------------------------------------|
> 
> Donal,
> 
> This looks like a possible hardware problem.  I would have your IBM CE look
> at it for you.
> 
> Mark Post
> 
> -----Original Message-----
> From: Donal Hunt [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, May 18, 2002 4:26 PM
> To: [EMAIL PROTECTED]
> Subject: Strange problem [Suse Linux on S390 VM]
> 
> Hi there,
> 
> I was pointed in this direction for advice I'm having with a VM I'm
> using.  I'm using the VM for a project machine running:
> 
>     - Suse Linux 7.0
>     - Proftpd (standalone)
>     - OpenSSH
>     - Apache 1.3.22 (http and https)
>     - Mailman 2.1b2
>     - Postfix as the MTA (replacing the default sendmail install)
>     - Big Brother monitoring client (to try and keep track of problems).
> 
> Recently I've had a problem with ftp (was called from inetd before i
> installed proftpd), telnet, SSH and Postfix dying on the machine.  The
> processes are still running but they aren't usable. eg telnet to port 23
> won't let me login. SSH to the machine fails. Connecting to port 25, I'm
> accepted but no MTA header is shown and anything I type isn't processed.
> 
> A couple of times I've been totally locked out of the machine (no
> possible way to login), but Apache has stayed up and I was able to
> access to request any page I wanted (normal service).  That's the reason
> I installed Proftpd - at least I'll have ftp access to get logs now).
> 
> Anyway - to get to the point of mail.  The same problem occured again
> this evening at 20:35 IST (thanks to BigBrother for the time) and
> /var/log/messages shows:
> 
> May 18 20:35:39 linux28 kernel: dasd(eckd):device 0203 on irq 2: I/O
> status report:
> May 18 20:35:39 linux28 kernel: dasd(eckd):in req: 07f55980 CS: 0x00 DS:
> 0x02
> May 18 20:35:39 linux28 kernel: dasd(eckd):Failing CCW: 07f55a18
> May 18 20:35:39 linux28 kernel: dasd(eckd):Sense:  0:0x00  1:0x10
> 2:0x10  3:0x00  4:0x00 5:0x00 6:0x8f  7:0xe0
> May 18 20:35:39 linux28 kernel: dasd(eckd):Sense:  8:0x62  9:0x70
> 10:0x00 11:0x08 12:0x20 13:0x00 14:0xae 15:0x05
> 
> and after that there is nothing for about 18 minutes (not normal):
> 
> May 18 20:53:48 linux28 -- MARK --
> 
> I notice that every five minutes before the "device status report" above
> there is a similar (but slightly different message):
> 
> May 18 20:30:39 linux28 kernel: dasd(eckd):device 0203 on irq 2: I/O
> status report:
> May 18 20:30:39 linux28 kernel: dasd(eckd):in req: 07f55980 CS: 0x00 DS:
> 0x02
> May 18 20:30:39 linux28 kernel: dasd(eckd):Failing CCW: 07f55a18
> May 18 20:30:39 linux28 kernel: dasd(eckd):Sense:  0:0x00  1:0x10
> 2:0x10  3:0x00  4:0x00  5:0x00 6:0x8f  7:0xe0
> May 18 20:30:39 linux28 kernel: dasd(eckd):Sense:  8:0x62  9:0x70
> 10:0x00 11:0x08 12:0x20 13:0x00 14:0xae 15:0x05
> May 18 20:30:39 linux28 kernel: dasd(eckd):Sense: 16:0x22 17:0x00
> 18:0x70 19:0x88 20:0x00 21:0x1c 22:0x3e 23:0x41
> May 18 20:30:39 linux28 kernel: dasd(eckd):Sense: 24:0x05 25:0x10
> 26:0x4c 27:0x02 28:0xf2 29:0x00 30:0x00 31:0x00
> May 18 20:30:39 linux28 kernel: dasd(eckd):32 Byte: Format: f Exception
> class 3
> May 18 20:30:39 linux28 kernel: dasd: devno 0x0203 on subchannel 2 =
> /dev/dasdb (94:4) postprocessing successful error recovery action using
> 00072fb0
> 
> Is there something wrong with the underlying VM session?? I don't have
> very much experience with using VMs - just using it for a project
> machine at present...  I don't have any control of the VM at present,
> but the local administrator has restarted my VM for me in the past, but
> doesn't have much experience with S390s after that...
> 
> Any help / pointers would be appreciated... Thanks
> 
> Donal
> DCU

Reply via email to