| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Challenge Question - 04 / 2008 - Week One |
« View previous topic :: View next topic » |
| Author |
Message
|
| fjb_saper |
 Posted: Fri Apr 04, 2008 2:46 pm Post subject: |
 |
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Challenger wrote: |
Sorry, I couldn't find a way to display this any better. Note: /opt/mqm and /var/mqm are local filesysystems, while /home/mqm is a mount from remote storage.
mqm:/home/mqm>df -k
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/bootdg/rootvol 8268461 3753046 4432731 46% /
/proc 0 0 0 0% /proc
mnttab 0 0 0 0% /etc/mnttab
fd 0 0 0 0% /dev/fd
/dev/vx/dsk/bootdg/var 8268461 1620815 6564962 20% /var
swap 41114944 40 41114904 1% /var/run
/dev/vx/dsk/bootdg/export 92365779 6654667 84787455 8% /export
swap 41115736 832 41114904 1% /tmp
/export/optmqm 92365779 6654667 84787455 8% /opt/mqm
/export/varmqm 92365779 6654667 84787455 8% /var/mqm
/export/u01 92365779 6654667 84787455 8% /u01
ieeprodhome:/prodhome/home/mqm 847034984 798291456 48743528 95% /home/mqm
Comparison of kernel settings to Quick Beginnings shows that two settings was missed during upgrade:
--semsys:seminfo_semmnu was 1024
but should have been = 16384
--maxuprc was 800
but should have been = 1024
|
From the look of it your /home/mqm is shared between multiple systems and there is your problem. Not all systems have the same uid/gid for mqm.
Also you are out of resources as they are way lower than the recommanded.
So a) fix the resources
if that does not fix the problem you then need to address b) the problematic mount at /home/mqm
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
 |
| Challenger |
| Posted: Fri Apr 04, 2008 7:11 pm Post subject: |
|
|
Centurion
Joined: 31 Mar 2008
Posts: 115
|
| fjb_saper wrote: |
From the look of it your /home/mqm is shared between multiple systems and there is your problem. Not all systems have the same uid/gid for mqm.
Also you are out of resources as they are way lower than the recommanded.
So a) fix the resources
if that does not fix the problem you then need to address b) the problematic mount at /home/mqm
|
Let me mention the rest of the post that you quote. I stated:
| Challenger wrote: |
Comparison of kernel settings to Quick Beginnings shows that two settings was missed during upgrade:
--semsys:seminfo_semmnu was 1024
but should have been = 16384
--maxuprc was 800
but should have been = 1024
Queue managers were quiesced. Kernel settings were adjusted as above and the server was rebooted. Unlike the original event where queue managers were not started all at once, this time the queue managers were immediately restarted, with CHALLENGE first. It failed to start. The other nine queue managers also failed to start.
All ten queue managers had to be started with a different user ID, changing the presenting problem from one to all ten queue managers failing to start as 'mqm'. |
The kernel settings were, in fact, adjusted and are now as specified by IBM; and, after the adjustment, the problem remained.
On the subject of the shared home directory, I offer the following:
1) On the first go round of starting the ten queue managers after upgrade, nine of them started just fine as 'mqm'; the tenth one, started later in the day, did not.
2) The user ID that is successfully starting the queue managers also has a home directory on shared storage.
3) Our development environment uses shared storage home directories without problem.
4) I've been using shared storage home directories for both MQ and WMB for five years and have never had an issue.
 And, as I know what fixed it, I regret to say that you haven't got it yet.... |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
