| Author |
Message
|
| Douzi |
 Posted: Fri Dec 14, 2012 12:23 am Post subject: Unable to Start the Queue manager |
 |
|
Newbie
Joined: 13 Dec 2012
Posts: 3
|
Hi All,
I am trying to start the queue manager, but I am getting the below error,
bash-3.00$ strmqm EESO531P
Segmentation Fault
bash-3.00$
bash-3.00$ dspmqver
Name: WebSphere MQ
Version: 7.0.1.7
CMVC level: p701-107-111117
BuildType: IKAP - (Production)
OS: SunOS <hostname> 5.10 Generic_147440-09 sun4u sparc SUNW,SPARC-Enterprise
Please suggest on what would be the problem... |
|
| Back to top |
|
 |
| ramires |
| Posted: Fri Dec 14, 2012 2:49 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
did it work before? Are there any other errors (logs , fdc files)?
_________________
Obrigado / Thanks you |
|
| Back to top |
|
|
| Douzi |
| Posted: Fri Dec 14, 2012 3:34 am Post subject: |
|
|
Newbie
Joined: 13 Dec 2012
Posts: 3
|
Yes it was working fine before. We didn't found any logs or FDC's.
When I try to create one new qmgr in the same machine I got the below error.
crtmqm: fatal: relocation error: file /opt/mqm/bin/crtmqm: symbol zfpPlugProcess: referenced symbol not found
Killed |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Dec 14, 2012 3:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Douzi wrote: |
| Yes it was working fine before. |
So what happened between it working and it not? Why did you need to restart the queue manager?
Maybe because the sys admins were doing maintenance?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ramires |
| Posted: Fri Dec 14, 2012 4:00 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
| are you using a authorized user (mqm) ? the other(s) queue manager runs ok? |
|
| Back to top |
|
|
| nathanw |
| Posted: Fri Dec 14, 2012 5:39 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
or has, like I have seen elsewhere, some over zealous admin has looked and said not need and removed files etc
_________________
Who is General Failure and why is he reading my hard drive?
Artificial Intelligence stands no chance against Natural Stupidity.
Only the User Trace Speaks The Truth  |
|
| Back to top |
|
|
| Douzi |
| Posted: Fri Dec 14, 2012 5:48 am Post subject: |
|
|
Newbie
Joined: 13 Dec 2012
Posts: 3
|
There was some problem at OS level and due to which the file systems /var/mqm got effected and Qmgr went down. Qmgr is not getting started and throwing error even after restoring the file system to the earlier backup by Unix team.
Yes I am trying to start the Qmgr with "mqm" user.... |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Dec 14, 2012 6:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Douzi wrote: |
| There was some problem at OS level and due to which the file systems /var/mqm got effected and Qmgr went down. Qmgr is not getting started and throwing error even after restoring the file system to the earlier backup by Unix team. |
So the restore has not been performed correctly. Some or all of the needed files are missing and/or some of the file permissions are incorrect. Also (or as well) the uid of the mqm user may have changed so it doesn't match the files.
Get your Unix team to have another go, and brace yourself for reinstalling the WMQ system then rebuilding the queue manager from the script.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| nathanw |
| Posted: Fri Dec 14, 2012 6:31 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
what he said 
_________________
Who is General Failure and why is he reading my hard drive?
Artificial Intelligence stands no chance against Natural Stupidity.
Only the User Trace Speaks The Truth |
|
| Back to top |
|
|
| Andyh |
| Posted: Sat Dec 15, 2012 9:33 am Post subject: |
|
|
Master
Joined: 29 Jul 2010
Posts: 239
|
Your appends mention that /var/mqm was corrupted and restored, however the data you've provided suggests that /opt/mqm may have been corrupted.
If you try and start a queue manager with a damaged /var/mqm filesystem I would expect the queue manager restart might fail and that FDC's would be produced. The queue manager should not however end with a segmentation violation.
Similarly, a failure to resolve a symbol when executing crtmqm suggests a problem with the MQ install, rather than the MQ data filesystem.
You could try an uninstall/reinstall sequence, or look for any corruption (including missing files) in /opt/mqm. |
|
| Back to top |
|
|
|
|
