Hi Wally,

Thanks for the suggestion.  Here's what I've currently got configured:

MSGTQL is set to 1024.

ipcstat -qon shows nothing
 
ipcs -qop  shows 5 queues (0-4) all with 0 in the CBYTES and QNUM columns


I ran udtconf & allowed it to autoconf, then rebooted the system.  So far
(knock on wood) we haven't had another hang, BUT I have all of the cron jobs
that start Unidata phantoms temporarily disabled.

Larry Hiscock
Western Computer Services



-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wally Terhune
Sent: Monday, October 23, 2006 10:11 AM
To: [email protected]
Subject: Re: [U2] Help -- UD System hang...

ran out of message headers? kernel MSGTQL
$UDTBIN/ipcstat -qon    will just show message queues with non-zero CBYTES
or QNUM
or 'ipcs -qop' - look at QNUM total and compare to kernel MSGTQL

Wally Terhune
U2 Support Architect
IBM Information Management
4700 South Syracuse Street, Denver, CO   80237
Tel:  303.773.7969
Fax: 303.773.5915
[EMAIL PROTECTED]





             "Larry Hiscock"
             <[EMAIL PROTECTED]
             com>                                                       To
             Sent by:                  <[email protected]>
             [EMAIL PROTECTED]                                          cc
             stserver.u2ug.org
                                                                   Subject
                                       [U2] Help -- UD System hang...
             10/23/2006 10:20
             AM


             Please respond to
             [EMAIL PROTECTED]
                er.u2ug.org






I recently upgraded a client to UniData 6.1.12 running on SCO OpenServer
5.0.7.  The installation (fresh installs of both) went smoothly, and
everything seemed fine after the upgrade.  This morning, however, once all
of the users logged in, they are intermittently experiencing "hangs" (i.e.
no response from their terminals).  Unix is still up and running fine, but
the Unidata sessions can't be killed using stopudt pid.  They CAN be killed
using kill -9, but a 'listuser' shows them as still logged in to Unidata.
The hang affects ALL Unidata users.  If I attempt to begin a new Unidata
session, it starts, but immediately hangs.

I'm not seeing any obvious problems in the Unidata log files.  The hang may
or may not be related to a couple of cron jobs that we have running once
per hour.  After the last two, I noticed that there were PHANTOM users in
the listuser output.  There were no errors in the _PH_ output files or the
log files that the PHANTOM jobs created.

All of the kernel tunable parameters are set at or above recommended
settings (I can provide the config settings if needed).

Any ideas?

Larry Hiscock
Western Computer Services
http://www.wcs-corp.com
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

[demime 1.01d removed an attachment of type image/gif which had a name of
graycol.gif]

[demime 1.01d removed an attachment of type image/gif which had a name of
pic11604.gif]

[demime 1.01d removed an attachment of type image/gif which had a name of
ecblank.gif]
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to