- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Issued START/QUEUE/MANAGER/NEW a second time ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-09-2012 06:58 PM
08-09-2012 06:58 PM
I have a 2 node cluster running OpenVMS 8.4.
I issued the command START/QUEUE/MANAGER/NEW a second time by mistake, now when I issue SHOW QUEUE/MANAGER I get the message "SYS$QUEUE_MANAGER, failing over" on both nodes (full command output below). I imagine I am not the first one to ever make this goof. Anyone know how to get the queue manager corrected? Thanks in advance for any and all assistance.
$ SHOW QUEUE/MANAGER/FULL
Master file: SYS$SYSROOT:[SYSEXE]QMAN$MASTER.DAT
Queue manager SYS$QUEUE_MANAGER, failing over
/ON=(*)
Database location: SYS$COMMON:[SYSEXE]
$
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-09-2012 09:01 PM
08-09-2012 09:01 PM
Re: Issued START/QUEUE/MANAGER/NEW a second time by mistake
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2012 01:13 AM
08-10-2012 01:13 AM
Re: Issued START/QUEUE/MANAGER/NEW a second time by mistake
I think this may be one of those times where the useful messages get sent to OPCOM. Worth having a look see.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2012 09:22 AM
08-10-2012 09:22 AM
Re: Issued START/QUEUE/MANAGER/NEW a second time by mistake
hi Steven,
Yes, shared SAN for the 2 node cluster.
Note that one node seems to have finally failed over, and the queue manager started again. I rebooted the node that was still failing over, and then both nodes queue managers went into "failing over" state. They have been that way for about 70 minutes and counting, so something is not good.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2012 10:20 AM
08-10-2012 10:20 AM
Re: Issued START/QUEUE/MANAGER/NEW a second time by mistake
Scot,
did you check for error messages in SYS$MANAGER:OPERATOR.LOG ?
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2012 10:43 AM - edited 08-10-2012 07:08 PM
08-10-2012 10:43 AM - edited 08-10-2012 07:08 PM
SolutionEssentially had to delete the QMAN$MASTER.DAT file and recreate the queue database as though it were a new system. I tried renaming the file I created accidentally and rebooting, hoping that the original database file would resume and all would be well. Unfortunately, not so easy. Somewhere during the process, I think I also corrupted the original, as I kept returning to he state where both nodes would have batch queues "failing over". Thanks everyone for helping!