> From: Perry Taylor
>
> Hrm. Good info.
>
> How would one go about finding a "hung" port.status semaphore?
Red Herring:
-----------
One would *expect* smat -s to indicate it, but no.
Toward the bottom of a smat -s it says:
Port status State Netnode Owner Collisions Retries
Semaphore # 1 0 0 0 1 13
but State doesn't get changed to 1, Collisions & Retries are not
predictably incremented.
1st Symptom:
-----------
The culprit who causes the problem gets an error message.
Let's say I'm at a shell prompt, $UVHOME/bin is in my $PATH, I do
port.status and try to grep for "root", but mis-type grep:
$port.status | gerp root
ksh: gerp: not found
Abnormal termination of UniVerse.
Fault type is 13. Layer type is Verb.
$
2nd Symptom:
-----------
Anyone who subsequently tries to run port.status, whether form unix or
tcl prompt, is politely rebuffed:
>PORT.STATUS
PORT.STATUS is currently being run by another user, try again later.
>
(After all of this, my smat -s still looks just like the example above:
Port status State Netnode Owner Collisions Retries
Semaphore # 1 0 0 0 1 13
Not helpful, or I don't know how to read it.)
Solution:
--------
At this point root does:
>UNLOCK PSTATLOCK SEMAPHORE
Please wait, semaphore clear may take as long as 15 seconds.
Semaphore cleared.
>
& everything is back to normal.
(& smat -s still reports the same stats as before).
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
