| Author |
Message
|
| prat31 |
 Posted: Wed Sep 18, 2013 5:52 am Post subject: StartDataFlowEngine process appears with DataFlowEngine MB8 |
 |
|
Apprentice
Joined: 01 Feb 2013
Posts: 30
|
Hi All,
We recently migrated the brokers from Mb6 to MB 8.0.0.2 in Solaris Environment.
Now we are facing issues in starting/stopping a broker... The broker is currently stopped but still the process for DataFlowEngine and "/opt/IBM/mqsi/8.0.0.2/bin/startDataFlowEngine" is shown as running.
When I start the broker it is getting started..and the message flows are running.. but the flow is not processing the input and the IPPROCS of Queue is 0.
When I am killing the process dataFlowEngine are again getting created and duplicates are getting created...
Request you to help in this regards... |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Wed Sep 18, 2013 6:08 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
What service Id is being used to run the DataFlowEngine ? ps-elf. When you issue mqsistart or mqsistop, do you first sudo to that Id ?
It is not enough to have mqbrkrs group membership. All your Ids that interact with brokers m ust have PRIMARY group mqbrkrs.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| prat31 |
| Posted: Wed Sep 18, 2013 6:19 am Post subject: |
|
|
Apprentice
Joined: 01 Feb 2013
Posts: 30
|
Hi,
Yes the ID is part of mqbrks group and with the same ID the other broker commands are working fine..
Now I had stopped all the broker process and the broker.... butr when I again started the broker there are duplicate DataFlowEngine and /opt/IBM/mqsi/8.0.0.2/bin/startDataFlowEngine for the same EG.... and the flows are shown running but the IPPROCS of Queue is 0.... |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Sep 18, 2013 6:27 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| prat31 wrote: |
Hi,
Yes the ID is part of mqbrks group and with the same ID the other broker commands are working fine..
Now I had stopped all the broker process and the broker.... butr when I again started the broker there are duplicate DataFlowEngine and /opt/IBM/mqsi/8.0.0.2/bin/startDataFlowEngine for the same EG.... and the flows are shown running but the IPPROCS of Queue is 0.... |
This is not what I asked.
Does the Id have PRIMARY group mqbrkrs ? This is not the same as being a member of mqbrkrs.
http://linuxers.org/article/difference-between-primary-and-secondary-groups-linux
The IPC semaphores get confused on Unix/Linux if any id used to stop or start broker is not PRIMARY group mqbrkrs because of the locking ownership of the semaphore. This requires you to sudo to the right id to perform the commands.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| prat31 |
| Posted: Wed Sep 18, 2013 6:36 am Post subject: |
|
|
Apprentice
Joined: 01 Feb 2013
Posts: 30
|
| I will check and get back to u in 2 mins.... |
|
| Back to top |
|
|
| prat31 |
| Posted: Wed Sep 18, 2013 6:39 am Post subject: |
|
|
Apprentice
Joined: 01 Feb 2013
Posts: 30
|
| Yes the Id have PRIMARY group mqbrkrs and the secoundary as mqm... |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Sep 18, 2013 6:41 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| prat31 wrote: |
| Yes the Id have PRIMARY group mqbrkrs and the secoundary as mqm... |
Does the admin person sudo to the service id to execute mqsistart ?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Sep 18, 2013 6:43 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
startDataFlowEngine is a helper process that runs the DFE processes. That's why the DFE keeps starting.
This extra layer was added in v8 for a couple of reasons - support for MI and support to allow you to modify the environment of each EG individually.
stop the broker.
Kill any outstanding bipService processes.
kill any outstanding bipBroker processes.
kill any start* processes being run by the broker service ID.
kill any DFE processes.
Or simply restart the entire system. |
|
| Back to top |
|
|
| prat31 |
| Posted: Wed Sep 18, 2013 6:44 am Post subject: |
|
|
Apprentice
Joined: 01 Feb 2013
Posts: 30
|
| We use a single ID(mbsid) for all the operatrion and it has the PRIMARY group mqbrkrs and the secoundary as mqm... |
|
| Back to top |
|
|
| prat31 |
| Posted: Wed Sep 18, 2013 6:54 am Post subject: |
|
|
Apprentice
Joined: 01 Feb 2013
Posts: 30
|
Mr. mqjeff,
We tried the below steps but after that the DataflowEngines were created as duplicate... And the restart of the entire system will not be possible as it is Production.
Is there any way in which we can disable the StartDataFlowEngine wrapper script .....
Last edited by prat31 on Wed Sep 18, 2013 6:56 am; edited 1 time in total |
|
| Back to top |
|
|
| Tibor |
| Posted: Wed Sep 18, 2013 6:55 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| Have you checked the WMB related syslog entries? |
|
| Back to top |
|
|
| prat31 |
| Posted: Wed Sep 18, 2013 7:02 am Post subject: |
|
|
Apprentice
Joined: 01 Feb 2013
Posts: 30
|
Dear Mr. Tibor,
There are many files with ordinality(ordinality.PRD2.GEN.BRK.eg2) and configStore(configStore.PRD2.GEN.BRKb7d5a557-2701-0000-0080-eb3b7c488022) in /var/mqsi/common/locks.
In syslogs there are no mbid related entries... |
|
| Back to top |
|
|
| prat31 |
| Posted: Wed Sep 18, 2013 7:04 am Post subject: |
|
|
Apprentice
Joined: 01 Feb 2013
Posts: 30
|
Dear All,
Also we have applied the MB 8.0.0.2 Fix pack but still the mqsireportbroker shows the Fixpack capability level = '' (effective level '8.0.0.1').
What can be the reason for this?
Thanks.. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Sep 18, 2013 7:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| prat31 wrote: |
| What can be the reason for this? |
When you applied the fix pack you didn't issue a change broker command to enable the new functionality (hence "effective level").
So you have the fixes but not the new / improved abilities.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Tibor |
| Posted: Wed Sep 18, 2013 7:08 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| prat31 wrote: |
| Also we have applied the MB 8.0.0.2 Fix pack but still the mqsireportbroker shows the Fixpack capability level = '' (effective level '8.0.0.1'). |
Could you display it with pkginfo? |
|
| Back to top |
|
|
|
|
