topic Re: Queues hung in Operating System - OpenVMS

Queues hung

Swain — Thu, 10 Sep 2009 13:30:22 GMT

Hi

My system is hung
$ sh que
(no result)

$ sh que/manager
Queue manager SYS$QUEUE_MANAGER, running, on ALPHA::

OpenVMS Monitor Utility
+-----+ TIME IN PROCESSOR MODES
| CUR | on node ALPHA
+-----+ 10-SEP-2009 10:05:59.01

0 25 50 75 100
+ - - - - + - - - - + - - - - + - - - - +
Interrupt State |
| | | | |
MP Synchronization |
| | | | |
Kernel Mode 12 |▒▒▒▒
| | | | |
Executive Mode 29 |▒▒▒▒▒▒▒▒▒▒▒
| | | | |
Supervisor Mode 59 |▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
| | | | |
User Mode |
| | | | |
Compatibility Mode |
| | | | |
Idle Time |
+ - - - - + - - - - + - - - - + - - - - +

$ mon sys

Node: ALPHA OpenVMS Monitor Utility 10-SEP-2009 10:02:05
Statistic: CURRENT SYSTEM STATISTICS
Process States
┌ CPU Busy (100) ─┐ LEF: 149 LEFO: 0
│▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ HIB: 20 HIBO: 0
CPU 0 ├──────────────────────────┤ 100 COM: 1 COMO: 0
│▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ │ PFW: 0 CUR: 1
└──────────────────────────┘ MWAIT: 0 Other: 0
Cur Top: TCPIP$RE_BG8142 (97) Total: 171

┌ Page Fault Rate (0) ─┐ ┌ Free List Size (43463) ┐
│| │ │▒▒▒▒▒▒▒ │ 144K
MEMORY 0 ├──────────────────────────┤ 500 0 ├──────────────────────────┤
│ │ │▒▒▒ │ 36K
└──────────────────────────┘ └ Mod List Size (5347) ┘
Cur Top: (0)

┌ Direct I/O Rate (1391) ─┐ ┌ Buffered I/O Rate (28) ─┐
│▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │▒ │
I/O 0 ├──────────────────────────┤ 500 0 ├──────────────────────────┤ 500
│▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒│ │ │
└──────────────────────────┘ └──────────────────────────┘
Cur Top: TCPIP$RE_BG8142 (1380) Cur Top: DECW$TE_D8F2 (4)

Please reply ASAP. It's urgent.

Thanks,
Amaresh

Re: Queues hung

Swain — Thu, 10 Sep 2009 14:01:23 GMT

this may help...

$ sh sys
.
.
00018CF5 QUEUE_MANAGER LEF 10 185486 0 00:10:35.67 290 328
.
.

$ stop/id=00018CF5
$ start que/manager
Interrupt (hung)

$ sh que/manager
Queue manager SYS$QUEUE_MANAGER, starting, on ALPHA::

Re: Queues hung

Mike R Smith — Thu, 10 Sep 2009 14:13:38 GMT

Amaresh, do a

$ reply/enable
and then perform the stop and start steps again and post the output.

Also, check the device where the queue manager files are located to make sure it is not having a problem.

Re: Queues hung

Joseph Huber_1 — Thu, 10 Sep 2009 14:23:26 GMT

Did it hang before or after You brute forced the queue manager by stop/id ?

The right way is stop/queue/manager[/cluster] !

I would not wonder queue manager hangs on restart after stop/id.

Re: Queues hung

Hoff — Thu, 10 Sep 2009 16:01:01 GMT

If this is an urgent support request, then there are folks here that can diagnose this for you. This might be HP or another existing preferred support provider, or one of the various support providers that frequent the forums here in ITRC.

As for a baseline, confirm that you've got the queues and queue logical names and the queue database configured per (OpenVMS V7.2 and later) SYLOGICALS.TEMPLATE file.

If you're operating at the "free support" level (as your use of "ASAP" here in ITRC tends to imply), then apply the ECO kits for this OpenVMS Alpha version or (if you're not already running V8.3) upgrade to OpenVMS Alpha V8.3 and add on the ECO kits, and call us back.

Re: Queues hung

Pramod Kumar M — Fri, 11 Sep 2009 04:02:22 GMT

Hi,

I am not sure whether your problem is resolved.

Some of the suggestion I have is

1. Don't stop queue manager using stop/id
2. Use STOP/QUEUE/MANAGER/CLUSTER to stop
queue manager.
3. Refer "HP OpenVMS System Managerâ s Manual,
Volume 1: Essentials" to check whether your problem matches with any of the problems listed there.
4. Also did you figure out which process causing your system to hang?
5. Did you check whether the disk you have your QMAN database is stil mounted?

Regards,
Pramod.

Re: Queues hung

Swain — Fri, 11 Sep 2009 04:12:14 GMT

Hi
Thanks for all your help and time.

Since it was urgent,I did a system reboot.

Even "sh dev" was producing weird result before reboot. So we were not aware of space isuue. I got some old files removed from system disk. que manager start/stop was not working because of lack of space.

Thanks,
Amaresh