| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQCTL on MQv7.0.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| George Carey |
 Posted: Thu Dec 10, 2009 9:16 am Post subject: Whew |
 |
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
Really back pedalling to come to understanding of filesystem issues.
Have recreated on my sandbox system whole new contact admin volumes for /var/mqm and /opt/mqm and attempted to reinstall MQv7.0.1.
Now some new media related issues show up ?
================================
I have determined that the IBM rpm tarball now (didn't need this before) needs to be untared with:
tar xvof MQv7.0.1_linux86-64_CZ4VEML.tar
notice the 'o' option !!! Previously I was able to untar this file and then install the rpms without the 'o' option and no problems.
Now I must use the 'o' option or the uid, gid are screwed up on the untarred rpm files.(using original IBM values likely)
However, doing my rpm -ivh {packagename} all works fine except for:
rpm -ivh MQSeriesKeyMan-7.0.1-0.x86_64.rpm
The install seems to go fine [100%] shows up but then I get a screen full of errors like:
/bin/tar: jre/lib/{filename} : Cannot change ownership to uid 123, gid 2345: Invalid argument
Something has changed in my environment to cause this but don't have a clue as to what at this time.
Any feedback on likely cause ... MOST appreciated at this time!!!!!!
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
 |
| mvic |
| Posted: Thu Dec 10, 2009 12:30 pm Post subject: Re: Whew |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| Quote: |
| /bin/tar: jre/lib/{filename} : Cannot change ownership to uid 123, gid 2345: Invalid argument |
Is the install running as root?
Is root allowed to change file ownership on that filesystem? |
|
| Back to top |
|
|
| George Carey |
| Posted: Fri Dec 11, 2009 5:38 am Post subject: NFSv4 and NFSv3 |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
Yes, install was running as root. Not the issue.
The issue(s) at least most appear to be related to the behavior differences between NFSv3 and NFSv4. The uids and gids for mqm across MQ servers and on NIS server, the idmapd.conf Domain setting needing to sync with what contact admin NetApp device, the yada, yada for all things NFS and all things NetApp need to be sync properly for NFSv4. Not so for NFSv3 it appears.
Mounts of /var/mqm volume for NFSv3 would for example show the acl's on a qmgr named FOO as
drwxrwsr-x 20 mqm mqm 4096 Dec 10 08:25 /var/mqm/qmgrs/FOO
and when mounted as NFSv4 would show
drwxrwsr-x 20 mqm nobody 4096 Dec 10 08:30 /var/mqm/qmgrs/FOO
resolving why that occurred required the above mentioned (tedious and involved) configuration changes.
My original problem relating to a contrained resource problem for MQCTL(send) etc. may occur again, I don't know but the issues relating to NFSv4 mounted volumes
which I believe were a red herring in relation to my original problem are likely not needing to be chased further.
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| 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
|
|
|
|
