ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Changing Broker and Config manager service id on AIX server

Post new topic  Reply to topic
 Changing Broker and Config manager service id on AIX server « View previous topic :: View next topic » 
Author Message
yugan8055
PostPosted: Tue Jul 20, 2010 7:22 am    Post subject: Changing Broker and Config manager service id on AIX server Reply with quote

Novice

Joined: 19 Aug 2009
Posts: 12

Hi All,

I need to change serviceUserId/servicepassword of a broker and config manager created on AIX server. here the Problem is, ID with which broker was made has been revoked and not available.

Now, i got new ID which has access to mqm & mqbrkrs group, but not able to stop the broker. Getting below error :

Quote:
BIP8016E: Unable to stop component.
A request to stop this component was refused.
Investigate the reason for this failure and reissue the command. The problem may be that the component was in the process of being stopped or started, in this case just reissue the command. It may be that the command could not be issued because of insufficient userid permissions. If you are unable to resolve the problem, contact your IBM support center.


If i can stop the broker then only i can run mqsichangebroker/mqsichangeconfigmgr commands to change component properties.
Is there any way to stop these components or do we need to use any other id which has more access permissions?
Can any one help.. how to stop broker and Config managers in this scenario....?

Thanks in advance...
Back to top
View user's profile Send private message
Vitor
PostPosted: Tue Jul 20, 2010 7:28 am    Post subject: Re: Changing Broker and Config manager service id on AIX ser Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

yugan8055 wrote:
Now, i got new ID which has access to mqm & mqbrkrs group


You're sure about that? What is the new user's principle group? You're sure that the broker is running under the current (revoked) user id?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Amitha
PostPosted: Tue Jul 20, 2010 11:59 am    Post subject: Reply with quote

Voyager

Joined: 20 Nov 2009
Posts: 80
Location: Newyork

I am not sure if this works, can you create the new user id with the same name and same same access as the one which was previously revoked and then try deleting the broker.
Back to top
View user's profile Send private message Send e-mail
yugan8055
PostPosted: Tue Jul 20, 2010 9:06 pm    Post subject: Reply with quote

Novice

Joined: 19 Aug 2009
Posts: 12

Hi Vitor,

Sorry, i am not sure on principle group,New user(ashkoshe) belongs to mqm and mqbrkrs..,

Quote:
# id ashkoshe
uid=328(ashkoshe) gid=1(staff) groups=14(mqm),210(people),216(mqbrkrs)


When i tried to run mqsichangebroker command, getting below message:

Quote:
BIP8018E: Component running.
This component is running, the command issued cannot be run against a running component.
Stop the component and reissue the command.


This says that Component is running ..
Vitor, even i tried to kill this process,, but could not see any change..

Please help..

Amitha,
I guess, creating new user id with same name will not help.... still, i can try.

Thanks...
Back to top
View user's profile Send private message
smdavies99
PostPosted: Tue Jul 20, 2010 11:19 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

yugan8055 wrote:

Quote:
BIP8018E: Component running.
This component is running, the command issued cannot be run against a running component.
Stop the component and reissue the command.



The bit in the error message in Bold (highlighted by me) tells you everything you need to know.
Stop the broker. Don't try to kill it. Do it properly. Then you can try the changebroker command
_________________
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
View user's profile Send private message
zpat
PostPosted: Tue Jul 20, 2010 11:29 pm    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

I hate Unix principal groups on principle.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Jul 21, 2010 4:09 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

smdavies99 wrote:
Stop the broker. Don't try to kill it. Do it properly. Then you can try the changebroker command


I think this is where the OP came in:

yugan8055 wrote:
Now, i got new ID which has access to mqm & mqbrkrs group, but not able to stop the broker. Getting below error :

Quote:
BIP8016E: Unable to stop component.
A request to stop this component was refused.
Investigate the reason for this failure and reissue the command. The problem may be that the component was in the process of being stopped or started, in this case just reissue the command. It may be that the command could not be issued because of insufficient userid permissions. If you are unable to resolve the problem, contact your IBM support center.

_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Jul 21, 2010 4:10 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

yugan8055 wrote:
Vitor, even i tried to kill this process,, but could not see any change..


So get the admins to kill it with root. I suspect that as it's now running under a non-existent id nothing else will do.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
yugan8055
PostPosted: Wed Jul 21, 2010 4:43 am    Post subject: Reply with quote

Novice

Joined: 19 Aug 2009
Posts: 12

Hi Vitor,

thanks for your reply..

I need some more information...
Admin already killed that Broker's process, now flows are not running,
but still i am getting Broker is running message when trying mqsichangebroker command...

So, Rebooting server will solve the problem and after reboot broker will be in STOPPED status?
(Note: Usually, broker get started whenever system restarted .. )

Thanks..
Back to top
View user's profile Send private message
yugan8055
PostPosted: Mon Jul 26, 2010 7:10 am    Post subject: Reply with quote

Novice

Joined: 19 Aug 2009
Posts: 12

Hi..
Restarted server then Brokers got stopped.. i could run mqsichangebroker command

thanks all...
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Changing Broker and Config manager service id on AIX server
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
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.