| Author |
Message
|
| rax |
 Posted: Sun Nov 12, 2006 8:09 pm Post subject: Neither Broker nor the Configuration Manager is starting! |
 |
|
Novice
Joined: 23 Feb 2004
Posts: 22
|
Hi All,
I have SLES-9 with Service Pack 3, DB2 ES v8.1.2.120, WM6 v6.0.2.0 and WBIMB v6.0.0.3. The installation and working id is root which is member of groups mqm and mqbrkrs.
The installation was successful. I created db for MB and CM, and successfully binded them. Next, set the .odbc.ini and created the user.log log file in /var/log and gave the chmod 640 with ownership to mqm:mqbrkrs. /etc/syslog.conf was also appended with user.* /var/log/user.log entry.
Now, after creation of the CM and Broker when tried to start both of them none of them ran. Interestingly, i am not receiving any msg in the user.log.
Can anybody suggest, what could be the reason of not starting of the Component?
Regards,
Rax
_________________
IBM Certified Solution Developer & System Administrator- WebSphere MQ 5.3
Last edited by rax on Mon Nov 13, 2006 6:09 pm; edited 1 time in total |
|
| Back to top |
|
 |
| jbanoop |
| Posted: Sun Nov 12, 2006 9:57 pm Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
In my understanding V 6 does not need a CM DB to be defined..it is supposed to use cloudscape which is in memory ..
if you change the syslog path .. i think you need to refresh the syslog deamon .. maybe thats why messages may not be showing up .
There should be some exception that happened during startup of the CM and broker ..
Anoop |
|
| Back to top |
|
|
| rax |
| Posted: Sun Nov 12, 2006 10:19 pm Post subject: |
|
|
Novice
Joined: 23 Feb 2004
Posts: 22
|
Hi,
I refreshed the syslogd twice. I even restarted the machine, but in vain. Any Guess what might have gone wrong?
-Rax
_________________
IBM Certified Solution Developer & System Administrator- WebSphere MQ 5.3 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Nov 13, 2006 4:16 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What is the output from mqsistart?
What is the piece of information that tells you that the configmgr and broker haven't started?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rax |
| Posted: Mon Nov 13, 2006 6:06 pm Post subject: |
|
|
Novice
Joined: 23 Feb 2004
Posts: 22
|
The mqsistart generates the following output:
mqsistart BROKER
WebSphere MQ queue manager 'BRQM' starting.
9 log records accessed on queue manager 'BRQM' during the log replay phase.
Log replay for queue manager 'BRQM' complete.
Transaction manager state recovered for queue manager 'BRQM'.
WebSphere MQ queue manager 'BRQM' started.
BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.
After mqsistart, if i give
mqsistop BROKER
BIP8019E: Component stopped.
A previous command was issued to stop this component or it has never been started.
This component may be started, changed or deleted.
Above is one way, i found that BROKER is not working. Other method employed to find that broker is not running are:
1. The ps -aef doesn't return any bip* process.
2. db2 list application for both of the databases CMBD and BRDB don't return any application connected except db2bp.
The size of the user.log is still zero. DB2 instance is running.
Any clue where could be the reason?
Thanks.
Rax
_________________
IBM Certified Solution Developer & System Administrator- WebSphere MQ 5.3 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Nov 13, 2006 7:13 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Does it say that the queue manager is starting every time you issue mqsistart?
Are there errors in /var/mqm/qmgrs/BPQM/errors/AMQERR01.LOG?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| rax |
| Posted: Mon Nov 13, 2006 7:55 pm Post subject: |
|
|
Novice
Joined: 23 Feb 2004
Posts: 22
|
No. It doesn't say each time that QM is starting . Only when QM is not running before using mqsistart, it gives.
So far, only one error log file, namely /var/mqm/qmgrs/BPQM/errors/AMQERR01.LOG, has been created. It doesn't contain any error message, just normal event messages.
_________________
IBM Certified Solution Developer & System Administrator- WebSphere MQ 5.3 |
|
| Back to top |
|
|
|
|
