| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Installing MQ with drbd/nfs4 for data and log |
« View previous topic :: View next topic » |
| Author |
Message
|
| PascalLap |
 Posted: Tue Apr 24, 2012 6:37 pm Post subject: Installing MQ with drbd/nfs4 for data and log |
 |
|
Newbie
Joined: 24 Apr 2012
Posts: 5
|
Hi,
We are trying to install MQ with this configuration.
-A server running MQ.
-The Data and Log for Q manager is installed on a NFS4 mount point.
-The Nfs4 mount point is actually a DRBD partition on a different server.
We have propagated the proper user and group to each server (with same UID).
We fail to create the Qmanager (crtmqm).
If we do a «amqmfsck» on the location for the data and log, we get an error: «AMQ6242: Incorrect ownership for 'xxxxx/amqmfsck.lck'.
Current(65534) Expected(1100)»
But the user and group are the proper one (mqm:mqm / 1100).
Do you have any idea of where/what could be our problem?
Does anybody have a similar setup?
Thanks for your help |
|
| Back to top |
|
 |
| JasonE |
| Posted: Wed Apr 25, 2012 12:51 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
At a low level, I believe this is coming out because amqmfsck calls fstat on the xxxx/amqmfsck.lck file and verifies what is coming back, specifically the st_uid field. It expects it to be user mqm (which I assume is 1100) but is finding it as 65534. I dont know much about this configuration, but I assume mqm is a local id on the server running mq (with id 1100).
A little google implies that NFS servers can map to nfsnobody which is -2, or 65534, so perhaps this is going on here... However I've no idea if this is actually the case and if it is what you can do about it! |
|
| Back to top |
|
|
| PascalLap |
| Posted: Wed Apr 25, 2012 5:54 am Post subject: |
|
|
Newbie
Joined: 24 Apr 2012
Posts: 5
|
Thanks Jason.
There was indeed a misconfiguration in our nfs4 client.
In the /etc/idmapd.conf file the domain parameter was different on the nfs4 server and client. Change it for the same value. It is working fine now! |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
