| Author |
Message
|
| marcin.kasinski |
 Posted: Thu Feb 11, 2010 1:23 am Post subject: Problem with starting confgmanager |
 |
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
HP-UX
Broker 6.0.0.5
Hello.
I have problem with starting configmanager
With mqsistart command I receive error
BIP8018E: Component running.
This component is running, the command issued cannot be run against a running component.
Stop the component and reissue the command.
Problem is that I know that this component is stopped and there is no processes of this configmanager.
Is there any lock or something ?
Should I check and release something to get this component running ?
Regards
_________________
Marcin |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Feb 11, 2010 3:08 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Hey Marcin -
you know the configmgr is stopped because there is no bipconfigmgr process?
There's a number of reasons why it could be reporting this falsely. Are there messages in system log that give you more idea of what configmgr is doing when you try to start it?
Look for a db.lck file in configmgr's file system repository. |
|
| Back to top |
|
|
| marcin.kasinski |
| Posted: Thu Feb 11, 2010 3:36 am Post subject: |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
| mqjeff wrote: |
Hey Marcin -
you know the configmgr is stopped because there is no bipconfigmgr process?
There's a number of reasons why it could be reporting this falsely. Are there messages in system log that give you more idea of what configmgr is doing when you try to start it?
Look for a db.lck file in configmgr's file system repository. |
Hi,
Thanks for reply.
What I found:
SYSTEM.BROKER.CONFIG.QUEUE - 14 messages
SYSTEM.BROKER.TIMEOUT.QUEUE – 18 messages
SYSTEM.BROKER.ADMIN.REPLY – 25 messages
db.lck
/var/mqsi/components/CFG_WCESB_T/BERNARD/db.lck
/var/mqsi/components/CFG_WCESB/BERNARD/db.lck
/var/mqsi/components/CFG_WCESB_W/BERNARD/db.lck
Configmanager CFG_WCESB_T is that which doesn’t work, but can con be started.
What should I do? Delete /var/mqsi/components/CFG_WCESB_T/BERNARD/db.lck file ?
_________________
Marcin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Feb 11, 2010 4:13 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| marcin.kasinski wrote: |
| What should I do? Delete /var/mqsi/components/CFG_WCESB_T/BERNARD/db.lck file ? |
Uh, not, not immediately. Perhaps eventually, but not immediately.
There is no bipconfigmgr process running for CFG_WCESB_T? You're sure?
There is no process you've set up to do bad things like try and read configmgr repository - not even some wacky developer thinking they know better and "it's a derby db! it can host multiple connections just fine!"... ?
Again, what does system log show when you issue mqsistart on configmgr? Does it show that the configmgr fails because it thinks the repository is in use? Or for some other reason? |
|
| Back to top |
|
|
| marcin.kasinski |
| Posted: Thu Feb 11, 2010 5:23 am Post subject: |
|
|
Sentinel
Joined: 21 Dec 2004
Posts: 850
Location: Poland / Warsaw
|
| mqjeff wrote: |
| marcin.kasinski wrote: |
| What should I do? Delete /var/mqsi/components/CFG_WCESB_T/BERNARD/db.lck file ? |
Uh, not, not immediately. Perhaps eventually, but not immediately.
There is no bipconfigmgr process running for CFG_WCESB_T? You're sure?
There is no process you've set up to do bad things like try and read configmgr repository - not even some wacky developer thinking they know better and "it's a derby db! it can host multiple connections just fine!"... ?
Again, what does system log show when you issue mqsistart on configmgr? Does it show that the configmgr fails because it thinks the repository is in use? Or for some other reason? |
I’m sure there is no bipconfigmgr process running for CFG_WCESB_T.
There is no messages in syslog refers to mqsistart command.
There is no bad processes ?
It’s not first time in our environment.
In the past we experienced this situation every ~2 months.
Now it happened every week or more often.
What is the difference:
-more execution group
-sometimes there is problem with insufficient memory
-deployment more often.
Now I’m not sure that in the past we had this problem only with configmanager.
Perhaps the same problem we had with broker (can not start stopped component).
I know that server restart helps but I’m looking for beter solution.
_________________
Marcin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Feb 11, 2010 5:30 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Hi Marcin -
I do not expect that the syslog will show mqsistart at all, but it should show several messages from the ConfigMgr itself as it starts up.
At least one of these should include information about why the ConfigMgr fails to start up.
If it is failing because the db.lck file is there, then you should look at why it is still there. Perhaps you are doing something like issuing mqsistart as one user and mqsistop as another user, and the lock file can't be cleaned up. Perhaps the configmgr is crashing.
This shouldn't happen regularly at all!
Again, please issue mqsistart on the confimgr and see what the system log says about what the configmgr did.
Then you can try deleting the db.lck file and see if configmgr will start. You can also look at the owner of the db.lck file and see if this is the right user (it should be the configmgr service user and not one of your admin users). |
|
| Back to top |
|
|
|
|
