MQSeries.net :: View topic - Can't create execution group: WMB 7002 on Centos under LXC

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Can't create execution group: WMB 7002 on Centos under LXC

Goto page 1, 2 Next

Can't create execution group: WMB 7002 on Centos under LXC

« View previous topic :: View next topic »

Author

Message

Cliff

Posted: Thu May 12, 2011 9:31 am Post subject: Can't create execution group: WMB 7002 on Centos under LXC

Centurion

Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire

Hi folks,

I have a Ubuntu 10.04 host and a Centos 5 LXC container. MQ 7013 installs and runs happily, WMB 7002 installs happily and I can create and start a broker with no errors reported anywhere. However I can't create an execution group (tried the broker explorer first then the command line) - the logs show the eg repeatedly shutting down and eventually there's a BIP2066E message and an abend. There's nothing helpful that I can see in the logs, service trace or abend files that gives me any inkling as to what's wrong.

I suspect that this is a peculiarity related to LXC ... not as mature as OpenVZ yet ...

Has anybody out there come across this and can share some experience?

mqjeff

Posted: Thu May 12, 2011 9:56 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

can you post the header block and the first bit of the stack trace of the abend file here?

In a [c o d e] block, please.

Cliff

Posted: Thu May 12, 2011 10:35 am Post subject:

Centurion

Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire

Hi Jeff,

thanks for the very fast response! There are two abend files, both small so here's the entirety:

Code:

Code:

+-----------------------------------------------------------------------------+
| |
| |
| First Failure Symptom Report |
| ======================== |
| |
| Proc start time (GMT) :- Thu May 12 16:05:11 2011 |
| |
| Product Details |
| +++++++++++++++ |
| |
| Vendor :- IBM |
| Product Name :- WebSphere Message Broker |
| Program ID :- 5724-J05 |
| Version :- 7002 |
| |
| OS Information |
| ++++++++++++++ |
| |
| Operating System :- Linux |
| Version :- #61-Ubuntu SMP Fri Apr 8 18:25:51 UTC 2011 |
| Release :- 2.6.32-31-generic |
| Node Name :- ve101 |
| Machine ID :- x86_64 |
| |
| Environment |
| +++++++++++ |
| |
| Service User ID :- UID 500 |
| Executable Name :- bipbroker |
| Process ID :- 5124 |
| |
| Deployment |
| ++++++++++ |
| |
| |
| Build Information |
| +++++++++++++++++ |
| |
| Backing build :- |
| Sandbox :- /build/S700_P |
| CMVC Level :- S700-FP02 |
| Build type :- Production |
| 64 Bit Build :- no |
| |
| Failure Location |
| ++++++++++++++++ |
| |
| Time of Report (GMT) :- secs since 1/1/1970: 1305202818 |
| Thread ID :- 0x00000012 |
| |
+-----------------------------------------------------------------------------+

abend record for pid 5124 tid 18 time in seconds since 01/01/1970: 1305202818
File: /build/S700_P/src/CommonServices/Unix/ImbAbend.cpp
Line: 1044
Function: signal received
---- Inserts ----
6
@(#) 1.33.9.3 CommonServices/Unix/ImbAbend.cpp, CommonServices, S700, S700-L100922 10/06/29 10:58:52 [9/22/10 22:00:39]
0
-----------------
----------------------------- Stack dump for current thread ( 18)
/opt/ibm/mqsi/7.0/lib/libCommonServices.so[0xf714b383]
/opt/ibm/mqsi/7.0/lib/libCommonServices.so(_ZN8ImbAbend23dumpCurrentStacksToFileEPKvi+0x128)[0xf6f2bce8]
/opt/ibm/mqsi/7.0/lib/libCommonServices.so(_ZN8ImbAbend10dumpToFileEPcPKciS2_RKNS_6InsertES5_S5_S5_S5_S5_PKv+0x8ad)[0xf6f2d12d]
/opt/ibm/mqsi/7.0/lib/libCommonServices.so(_ZN8ImbAbend22logSystemErrorInternalEPKciS1_RKNS_6InsertES4_S4_S4_S4_S4_PKvb+0x260)[0xf6f2d8c0]
/opt/ibm/mqsi/7.0/lib/libCommonServices.so(_ZN8ImbAbend41logSystemErrorAndTerminateProcessInternalEPKciS1_RKNS_6InsertES4_S4_S4_S4_S4_PKvb+0x89)[0xf6f2e369]

Hope this means more to you than it does to me ...

mqjeff

Posted: Thu May 12, 2011 10:40 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Signal 6 on linux is SIGABORT...

Take a startup trace
http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg21177044

and review the agent trace output to see if it provides more information about why the sigabort.

lancelotlinc

Posted: Thu May 12, 2011 11:48 am Post subject:

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

I have seen this before, when the broker is running under a user id other than mqbrkrs. You may like to check that your broker process is owned by mqbrkrs user.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER

Cliff

Posted: Thu May 12, 2011 12:06 pm Post subject:

Centurion

Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire

Well, I ran the trace as suggested but there was no output available from the execution group (mqsireadlog B101A -t -e EG01 -f -o EG01trace.xml gave "The execution group could not be found...". I'm still poring over the service trace but no lightbulb moments yet.

The broker process is started by a user wmbadmin whose group membership is wmbadmin mqm mqbrkrs. Do you think that wmbadmin's PRIMARY group should be mqbrkrs? Lancelot, is that what you meant?

I also have the debug output from creating the execution group (mqsicreateexecutiongroup B101A -e EG01 -v /var/mqsi/log/B101A_EG01.log) that I'm looking at but again, nothing stands out. I can see that the broker didn't respond but not why.

<sigh>

lancelotlinc

Posted: Thu May 12, 2011 12:17 pm Post subject:

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Yes, I believe you will see this problem if the primary group is not mqbrkrs for the user that is running mqsistart. This is because the bar files cannot explode properly under the $MQSI_WORKPATH directory since the user's primary group is different than the file permissions in that directory. (ie. /var/mqsi/components/<brokername>)
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER

Cliff

Posted: Thu May 12, 2011 12:51 pm Post subject:

Centurion

Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire

I blew the broker away, usermodded wmbadmin to set the primary group to mqbrkrs, shut everything down and restarted the container. Then I started up afresh, recreated the broker, ran mqsicreateexecutiongroup, and the same thing happened again. Damn.

I'm not a happy chappie, it's late and I'll have another stab tomorrow. Thank you for your suggestions and if you can think of anything else then I'm all ears! Well, I will be tomorrow.

Cheers ...

lancelotlinc

Posted: Thu May 12, 2011 1:22 pm Post subject:

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Please post a directory listing (ls -l) of /var/mqsi or $MQSI_WORKPATH if you differ from the default.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER

Cliff

Posted: Thu May 12, 2011 11:31 pm Post subject:

Centurion

Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire

This is my playpen environment, so the install used all the defaults and there is no security. Selinux is disabled of course. And yes, I was root when I did the install! It's all I've ever been when installing ...

However I reread the install guide which is a bit ambiguous about group membership for the install, so I did the belt-and-braces thing and uninstalled, added root to mqbrkrs and mqm, reinstalled, recreated the broker, same problem. So it wasn't that then.

I have other stuff to do for a few hours, I'll return to poring over traces later ...

mqjeff

Posted: Fri May 13, 2011 2:18 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

If you can identify the UUID of the EG, you can pass that to mqsireadlog.

Again, however, it was the agent trace that might tell you more about why the EG is failing to start.

Also double-check the file permissions on the broker workpath - $MQSI_WORKPATH as lancelotlinc mentions - (/var/mqsi).

lancelotlinc

Posted: Fri May 13, 2011 4:45 am Post subject:

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

Also post a df -h along with your ls -l.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER

Cliff

Posted: Fri May 13, 2011 7:24 am Post subject:

Centurion

Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire

OK gents, back on the case ...

I couldn't run mqsireadlog against the execution group's uuid:

Code:

[wmbadmin@ve101 ~]$ mqsireadlog B101A -t -x 7bcc7e4-2f01-0000-0080-848d390601c0 -f -o egtrace.xml
Failed to open trace file /var/mqsi/common/log/B101A.7bcc7e4-2f01-0000-0080-848d390601c0.trace.bin.0 with error No such file or directory
BIP8041E: Unable to open the selected file '/var/mqsi/common/log/B101A.7bcc7e4-2f01-0000-0080-848d390601c0.trace.bin.*'.
A

Here's the permissions and df output:

Code:

[wmbadmin@ve101 ~]$ cd/var
-bash: cd/var: No such file or directory
[wmbadmin@ve101 ~]$ cd /var
[wmbadmin@ve101 var]$ ls -al
total 88
drwxr-xr-x 21 root root 4096 Apr 27 13:44 .
drwxr-xr-x 27 root root 4096 May 13 10:34 ..
drwxr-xr-x 6 root root 4096 Jul 8 2010 cache
-rwxrwxrwx 1 root root 2022 May 12 15:19 .com.zerog.registry.xml
drwxr-xr-x 3 root root 4096 Jul 8 2010 db
drwxr-xr-x 3 root root 4096 Jul 8 2010 empty
drwxr-xr-x 2 root root 4096 Jan 27 2010 games
drwxr-xr-x 15 root root 4096 Jan 6 01:31 lib
drwxr-xr-x 2 root root 4096 Jan 27 2010 local
drwxrwxr-x 6 root lock 4096 Jul 8 2010 lock
drwxr-xr-x 5 root root 4096 May 4 04:02 log
lrwxrwxrwx 1 root root 10 Sep 17 2010 mail -> spool/mail
drwxrwsr-x 12 mqm mqm 4096 May 4 06:23 mqm
drwxrwxr-x 10 mqm mqbrkrs 4096 May 12 20:27 mqsi
drwxr-x--- 5 root named 4096 Jul 8 2010 named
drwxr-xr-x 2 root root 4096 Jan 27 2010 nis
drwxr-xr-x 2 root root 4096 Jan 27 2010 opt
drwxr-xr-x 2 root root 4096 Jan 27 2010 preserve
drwxr-xr-x 13 root root 4096 May 13 10:37 run
drwxr-xr-x 9 root root 4096 Jul 8 2010 spool
drwxrwxrwt 2 root root 4096 May 12 13:19 tmp
drwxr-xr-x 6 root root 4096 Jul 8 2010 www
drwxr-xr-x 2 root root 4096 Jan 27 2010 yp
[wmbadmin@ve101 var]$ cd mqsi
[wmbadmin@ve101 mqsi]$ ls -al
total 44
drwxrwxr-x 10 mqm mqbrkrs 4096 May 12 20:27 .
drwxr-xr-x 21 root root 4096 Apr 27 13:44 ..
drwxrwxr-x 7 mqm mqbrkrs 4096 Mar 16 14:42 common
drwxrwsr-x 3 mqm mqbrkrs 4096 May 12 20:26 components
-rw-r--r-- 1 root root 26 May 12 15:08 install.properties
drwxrwxrw- 2 mqm mqbrkrs 4096 May 12 20:45 log
drwxrwxr-x 2 mqm mqbrkrs 4096 Mar 16 14:42 odbc
drwxrws--- 3 mqm mqbrkrs 4096 May 12 20:26 registry
drwxrwxr-x 2 mqm mqbrkrs 4096 Mar 16 14:42 shared-classes
drwxrwxr-x 3 mqm mqbrkrs 4096 Mar 16 14:42 XML
drwxrwxr-x 3 mqm mqbrkrs 4096 Mar 16 14:42 XSL
[wmbadmin@ve101 mqsi]$ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 440G 93G 326G 23% /
/dev/disk/by-uuid/d2b48586-669c-4a7b-bf49-dba84098aea3
440G 93G 326G 23% /
/dev/disk/by-uuid/d2b48586-669c-4a7b-bf49-dba84098aea3
440G 93G 326G 23% /library
[wmbadmin@ve101 mqsi]$

I'll return to studying the trace logs.

mqjeff

Posted: Fri May 13, 2011 7:26 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Cliff wrote:

OK gents, back on the case ...

I couldn't run mqsireadlog against the execution group's uuid:

Code:

Okay then, didn't even get that far.

Nothing in the agent trace file?

can we see ls -al /var/mqsi/common/log?

Cliff

Posted: Fri May 13, 2011 7:39 am Post subject:

Centurion

Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire

I'm still looking at the agent traces. The startup trace doesn't refer to the eg except for one line where a 'stop execution group' message is retrieved. The regular service trace is large and taking some time to digest!

Here's the content of /var/mqsi/common/log:

Code:

[wmbadmin@ve101 log]$ ls -al
total 4604
drwxrwsrwx 2 mqm mqbrkrs 4096 May 12 20:26 .
drwxrwxr-x 7 mqm mqbrkrs 4096 Mar 16 14:42 ..
-rw-rw---- 1 wmbadmin mqbrkrs 1572506 May 12 19:24 B101A.agent.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 1572559 May 12 19:25 B101A.agent.trace.bin.1
-rw-rw---- 1 wmbadmin mqbrkrs 32336 May 12 19:25 B101A.agent.trace.bin.2
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:36 B101A.agent.trace.bin.3
-rw-rw---- 1 wmbadmin mqbrkrs 1400 May 12 16:18 B101A.agent.userTrace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 1400 May 12 19:22 B101A.agent.userTrace.bin.1
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:36 B101A.agent.userTrace.bin.2
-rw-rw---- 1 wmbadmin mqbrkrs 818799 May 12 16:20 B101A.httplistener.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 586882 May 12 19:24 B101A.httplistener.trace.bin.1
-rw-rw---- 1 wmbadmin mqbrkrs 84136 May 12 19:24 B101A.httplistener.trace.bin.2
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:36 B101A.httplistener.trace.bin.3
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:36 B101A.httplistener.userTrace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:27 B101A.mqsichangebroker.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:27 B101A.mqsichangebroker.userTrace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 16:24 B101A.mqsichangetrace.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 16:24 B101A.mqsichangetrace.userTrace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:26 B101A.mqsicreatebroker.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:26 B101A.mqsicreatebroker.userTrace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:24 B101A.mqsideletebroker.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:24 B101A.mqsideletebroker.userTrace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:29 B101A.mqsilist.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:29 B101A.mqsilist.userTrace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 13 10:43 B101A.mqsireadlog.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 13 10:43 B101A.mqsireadlog.userTrace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 19:33 B101A.mqsiservice.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 19:33 B101A.mqsiservice.userTrace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:27 B101A.mqsistart.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:27 B101A.mqsistart.userTrace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:52 B101A.mqsistop.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:52 B101A.mqsistop.userTrace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 24387 May 12 19:25 B101A.service.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:27 B101A.service.trace.bin.1
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:27 B101A.service.userTrace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:26 utility.mqsichangebroker.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 20:26 utility.mqsichangebroker.userTrace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 19:31 utility.mqsiformatlog.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 19:31 utility.mqsiformatlog.userTrace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 15:50 utility.mqsilist.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 15:50 utility.mqsilist.userTrace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 17:17 utility.mqsiservice.trace.bin.0
-rw-rw---- 1 wmbadmin mqbrkrs 0 May 12 17:17 utility.mqsiservice.userTrace.bin.0
[wmbadmin@ve101 log]$

Thanks again for your help. Bit of a head scratcher this one eh?

Display posts from previous:

Goto page 1, 2 Next

Page 1 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Can't create execution group: WMB 7002 on Centos under LXC

Jump to:

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

Protected by Anti-Spam ACP