| Author |
Message
|
| austadbr |
 Posted: Wed May 02, 2012 3:10 pm Post subject: Message Broker v8 on Ubuntu 12.04 64 bit |
 |
|
Newbie
Joined: 02 May 2012
Posts: 1
|
Anyone successfully got Message Broker v8 running on ubuntu 12.04 64 bit?
I've got mq, mb, and the toolkit installed successfully, but I get an error running the Default Configuration wizard.
Collected output from task >
Stdout: [BIP8050E: Unable to create WebSphere MQ Queue Manager 'MB8QMGR'.
This command attempts to create a WebSphere MQ Queue Manager. The Queue Manager could not be created.
Locate and resolve the problem and retry the command.]
Stderr: [There are 90 days left in the trial period for this copy of WebSphere MQ.
AMQ7077: You are not authorized to perform the requested operation.]
the installation is installed with root privileges. I've added my user to the mq and mqbrkrs groups, I've also tried to run the toolkit as root.
I had to install the 32bit libs and ksh shell.
If anyone has had success and could share tks |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed May 02, 2012 6:05 pm Post subject: Re: Message Broker v8 on Ubuntu 12.04 64 bit |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| austadbr wrote: |
Stderr: [There are 90 days left in the trial period for this copy of WebSphere MQ.
AMQ7077: You are not authorized to perform the requested operation.]
I had to install the 32bit libs and ksh shell.
If anyone has had success and could share tks |
So have you tried to see why you are not authorized?
What i the user running the command?
Remember MQ does not much care for the root user.... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed May 02, 2012 10:14 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
At the risk of getting a storm of Ubuntu Fanboi hate thrown at me, why are you even bothering with this? Esepcially with a version of Ubuntu that has just been released. An older version would be a better bet if you really, really must stick with Ubuntu.
Wouldn't it be a whole lot less grief if you installed Virtualbox or KVM etc, dowloaded CentOS and created a proper Linux Environment for your broker?
Not that thing! from Canonical... 
I know from first hand experience that getting Broker to work on Ubuntu is a whole lot harder than even Debian.
AFAIK, most IBM Websphere software assumes that you have a Linux that conforms to the Linux Standard Base. Ubuntu does not.
Let the hate begin...
(Disclaimer, I have been a RHCE since 2001 but don't work for RedHat)
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mapa |
| Posted: Thu May 03, 2012 12:50 am Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
Not sure how you did go about creating user and group for broker and mq.
Here is how I do it on CentOS, should be same on Ubuntu.
This is before I start installing.
| Code: |
#Create user mqm, with homedir /var/mqm and group mqm
sudo useradd mqm -d /var/mqm -m
#Add user mqbrk to mqm group
sudo usermod -a -G mqm mqbrk
#Create group mqbrkrs
sudo groupadd mqbrkrs
#Add user mqbrk to the mqbrkrs group
sudo usermod -a -G mqbrkrs mqbrk
#Logout from CentOS and login again, restarting shell doesn't help
|
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu May 03, 2012 3:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Note the bit about 'log out and log back in'.
IN all cases of authentication issues, this is always a valid thing to try.
I don't care that it's unix, not windows. There are still layered shells that may have cached authentications.
Secondly, if the default configuration wizard doesn't work, don't use it. Just use mqsicreatebroker. it will even create the queue manager for you. |
|
| Back to top |
|
|
| mapa |
| Posted: Thu May 03, 2012 4:52 am Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
Well we agree about the log in/out then 
I have to write such things or people don't do it...
If default configuration fails due to authentication, then using plain mqsicreatebroker will too, won't it?
I pasted the instructions from our internal wiki where I wrote it.
I vaguely remember the same problem when I did it in another way first, before properly reading the installation documentation for WMQ |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu May 03, 2012 4:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| mapa wrote: |
| If default configuration fails due to authentication, then using plain mqsicreatebroker will too, won't it? |
it's easier to ensure you know what user is actually in effect with mqsicreatebroker than with the default configuration wizard. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu May 03, 2012 4:56 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri May 04, 2012 4:00 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| lancelotlinc wrote: |
| System V IPC semaphore. |
Good point. One that and awful lot of people forget. Probably because a simple, lightly loaded QMGR can run on most Linux distros OOTB, i.e. without the need to change them. Then they put some apps/loads on the QMGR and 'strange' things start happening.
I have a set of kernel defs that are good for Oracle 11gR2 AND WMQ + Broker. I try to apply them as standard right after the install or even at system build time in a Kickstart file.
| lancelotlinc wrote: |
| Don't forget to sudo to mqbrkrs. |
At the risk of being shot down in flames, Real Unix/Linux users don't need to use 'sudo'. On all my systems 'sudo' is disabled. If you need elevated privs then 'su' is the way to go.
Then again, this is Ubuntu we are talking about. 
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri May 04, 2012 6:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| smdavies99 wrote: |
| At the risk of being shot down in flames, Real Unix/Linux users don't need to use 'sudo'. On all my systems 'sudo' is disabled. If you need elevated privs then 'su' is the way to go. |
Ack-ack fire incoming.....
Where is your objection to "sudo su - mqbrkrs" as an authorized command?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri May 04, 2012 6:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| smdavies99 wrote: |
| At the risk of being shot down in flames, Real Unix/Linux users don't need to use 'sudo'. On all my systems 'sudo' is disabled. If you need elevated privs then 'su' is the way to go. |
Ack-ack fire incoming.....
Where is your objection to "sudo su - mqbrkrs" as an authorized command? |
Also what's the objection to only allowing *some* people to 'sudo endmqm', rather than allowing anyone who can su.
Sudo provides granular control over individual commands. su does not. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri May 04, 2012 6:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
Also what's the objection to only allowing *some* people to 'sudo endmqm', rather than allowing anyone who can su.
Sudo provides granular control over individual commands. su does not. |
I don't mind developers using such commands or helper scripts via sudo in low level environments if it stops them whining I'm a bottleneck. No way they're su'ing into mqm and making what they think are the right changes to correct the mistakes I made when I set up the WMQ topology.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri May 04, 2012 7:04 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Vitor wrote: |
| mqjeff wrote: |
Also what's the objection to only allowing *some* people to 'sudo endmqm', rather than allowing anyone who can su.
Sudo provides granular control over individual commands. su does not. |
I don't mind developers using such commands or helper scripts via sudo in low level environments if it stops them whining I'm a bottleneck. No way they're su'ing into mqm and making what they think are the right changes to correct the mistakes I made when I set up the WMQ topology. |
Sudo mqm would work for mq commands but not for mqsi commands. sudo to mqm would not work for mqsi commands since the System V IPC semaphore is owned by mqbrkrs group.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri May 04, 2012 7:14 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| Sudo mqm would work for mq commands but not for mqsi commands. sudo to mqm would not work for mqsi commands since the System V IPC semaphore is owned by mqbrkrs group. |
I congratulate you on your command of the obvious. For helper scripts etc on broker I use mqbrkrs rather than mqm for exactly the reason you specify and others. Even on platforms where semaphores are less of an issue.
It doesn't invalidate the use of sudo under discussion.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri May 04, 2012 7:25 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Vitor wrote: |
| lancelotlinc wrote: |
| Sudo mqm would work for mq commands but not for mqsi commands. sudo to mqm would not work for mqsi commands since the System V IPC semaphore is owned by mqbrkrs group. |
I congratulate you on your command of the obvious. For helper scripts etc on broker I use mqbrkrs rather than mqm for exactly the reason you specify and others. Even on platforms where semaphores are less of an issue.
It doesn't invalidate the use of sudo under discussion. |
There is a debate right now of the inaccuracy of the IBM documentation which recommends running WMB under mqm. I believe the IBM documentation is being revisited to rewrite this since it is not recommended to run WMB as mqm. This is the reason I offered the clarification.
Can you run WMB under the mqm user? Yes.
Should you run WMB under the mqm user? No, because the primary group for mqm user is mqm group and not mqbrkrs group.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
