| Author |
Message
|
| vijaya |
 Posted: Thu Sep 13, 2007 7:41 pm Post subject: Not able to restart the qmgr |
 |
|
Newbie
Joined: 13 Sep 2007
Posts: 7
|
Hi all,
OS:
$ uname -a
SunOS dev-db2 5.9 Generic_122300-11 sun4u sparc SUNW,Sun-Fire-V440
MQ: 6.0
Its a new server where we installed MQ and created all the required objects.
We used circular logging and the log paths are set to defaults.
We need to send the message to a mainframe qmgr and when we sent the test messages, all the
messages are sitting in the XMITQ.
All the definitions were correct from my side but I am not able to see the failed activity in the logs.
I had all the logs available just before doing a put. I waited few more mins...but no use..so I bounced
the QMGR using the endmqm -i( biggest mistake)....thinking my logs would be updated on a restart.And now
when I try to do a restart, I get the error like this..
$ sudo -u mqm strmqm SPEX.SUN.DEV_MQ_ORA.DEV
WebSphere MQ queue manager 'SPEX.SUN.DEV_MQ_ORA.DEV' starting.
Log path not valid or inaccessible.
I don't know how to proceed ahead. Am I only left with recreating my QMGR and all the definitions??.. 
If that's th only option left...please let me know if this is the right order of cleanup.
1. delete the /var/mqm/qmgrs sub directory.
2. delete logs at /var/mqm/logs
and let me know the other areas to look up.
I sincerely appreciate any of your help.
Thanks,
vijaya |
|
| Back to top |
|
 |
| sidharth_bora |
| Posted: Thu Sep 13, 2007 9:27 pm Post subject: |
|
|
Voyager
Joined: 24 Nov 2005
Posts: 87
|
can you send the output of the following command to be run with the same id you are using to administer the QM
touch /var/mqm/log/<QMname>/active/abc.dummy
ls -lrt /var/mqm/log/QMname/active
thx
Sid |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 14, 2007 12:02 am Post subject: Re: Not able to restart the qmgr |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vijaya wrote: |
We need to send the message to a mainframe qmgr and when we sent the test messages, all the
messages are sitting in the XMITQ.
All the definitions were correct from my side but I am not able to see the failed activity in the logs.
|
For what it's worth, if the problem reoccurs when you've made it back out of the hole this indicates a channel problem which bouncing the queue manager is not very likely to fix. Verify the sender channel definitions & especially that you have network connectivity to the target.
Then look for messages in the error log, in /var/mqm/<QMname>/errors. The files in /var/mqm/<QMname>/logs are the circular logs used to hold messages and have nothing of value to you.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Sep 14, 2007 6:48 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
$ sudo -u mqm strmqm SPEX.SUN.DEV_MQ_ORA.DEV
WebSphere MQ queue manager 'SPEX.SUN.DEV_MQ_ORA.DEV' starting.
Log path not valid or inaccessible. |
Probably a file permission error.Get your unix admin to help.
Make sure the /var/mqm system is owned by mqm:mqm and has rw-rw (ug+rw) permissions for mqm:mqm and ug+rwx on directories
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| vijaya |
| Posted: Fri Sep 14, 2007 6:52 am Post subject: |
|
|
Newbie
Joined: 13 Sep 2007
Posts: 7
|
hi siddharth / Vitor,
My problem was resolved.
The problem is from the mainframe side..where there was a typo in channel definitions and hence my messages are sitting is the queues.
I deleted my entire stuff and recreated things and everything is working fine.
I am new person here and I see all the qmgrs here are set with Circular logging.
Thanks,
viji |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 14, 2007 10:31 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vijaya wrote: |
| The problem is from the mainframe side..where there was a typo in channel definitions and hence my messages are sitting is the queues. |
Told you. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
