I thought we had a major network problem when servers started seeing
"dropped packets" as shown on the query vswitch and lost putty sessions
and http timeouts.  We had migrated to LACP vswitch, 5.4, and put in a
new LPAR all around the same time so it was hard to narrow down.  Turns
out Class A had been lost on the ID that ran the set srm storbuff
command.

Maybe I should have let them stare at the dumps for a few more weeks ;)

What a nice (albeit exasperating) feeling when a simple commands makes
problems vanish immediately!
You get that satisfaction all the time I bet!  I would think that IBM
would want to change it for that reason alone :)


Marcy  
"This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation."


-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Barton Robinson
Sent: Thursday, October 30, 2008 11:19 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Linux VM intermittently goes non-responsive

Marcy, we don't want them to fix it, it is more fun being a hero and
fixing problems with secret commands.


Marcy Cortes wrote:

> IBM, have you thought about changing that default?
> I bet everyone hits it eventually.
>
>
> Marcy
>
> "This message may contain confidential and/or privileged information.
If you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation."
>
>
> -----Original Message-----
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of 
> Mike Hammock
> Sent: Thursday, October 30, 2008 9:34 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: [LINUX-390] Linux VM intermittently goes non-responsive
>
> You need to find out who supports/administers your zVM system and have
them check for your Linux system being in Queue-3.  If it is, the best
fix for this is to set new SRM STORBUFF parameters.  If you don't have
access to MAINT, you probably do not have the authority to set the SRM
STORBUFF parameters yourself anyway.
>
> Mike
>
> C. M. (Mike) Hammock
> Sr. Technical Support
> zFrame & IBM zSeries Solutions
> (404) 643-3258
> [EMAIL PROTECTED]
>
>
>
>              "Warren Taylor"
>              <[EMAIL PROTECTED]
>              global.net>
To
>              Sent by: Linux on         "LINUX-390@VM.MARIST.EDU"
>              390 Port                  <LINUX-390@VM.MARIST.EDU>
>              <[EMAIL PROTECTED]
cc
>              IST.EDU>
>
Subject
>                                        Re: [LINUX-390] Linux VM
>              10/30/2008 12:14          intermittently goes
non-responsive
>              PM
>
>
>              Please respond to
>              Linux on 390 Port
>              <[EMAIL PROTECTED]
>                  IST.EDU>
>
>
>
>
>
>
> I don't have access to MAINT VM id
>
>
>
> ----- Original Message ----
> From: "Chambers, David W." <[EMAIL PROTECTED]>
> To: LINUX-390@VM.MARIST.EDU
> Sent: Thursday, October 30, 2008 8:59:09 AM
> Subject: Re: Linux VM intermittently goes non-responsive
>
> First thing to look at, an IND LOAD command (on MAINT) will probably
show a value other than zero in the E3 counter. There should be several
hits in the list archives on dispatching, over-committing, SRM, etc. You
will probably need to modify STORBUF and/or LDUBUF. Check Q SRM output.
>
> -----Original Message-----
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of 
> Warren Taylor
> Sent: Thursday, October 30, 2008 11:45 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Linux VM intermittently goes non-responsive
>
> Hi,
>
> I've got LinuxVM (RHEL4) going non responsive once in a while. Don't
know what it is and don't know how to diagnose it. Being a real newb I
could use some help. We just use this system to maintain another system
so know very little about linux. I got it running a couple of years ago
and that was fun but had to get back to my real job so have spent very
little time with it.
>
> Thanks
> Warren Taylor
>
>
> ----------------------------------------------------------------------


----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send
email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to