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 » General IBM MQ Support » Broker stopped

Post new topic  Reply to topic
 Broker stopped « View previous topic :: View next topic » 
Author Message
makgotsophemelo
PostPosted: Wed May 06, 2009 2:08 am    Post subject: Broker stopped Reply with quote

Novice

Joined: 06 May 2009
Posts: 11

Hi ,

I am having a problem with my production Broker on clustered servers,

Yesterday when i checked it appears to be running , with a ps -ef |grep [/b]bip command , and this morning when i check it appears to be stopped , and i also checked the log files , it shows that the broker was down since the 22nd April,

What i want to find out is :

is there a possibility that a ps command can be wrong in any other cases , or what could have happened

Thanking you in advance
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed May 06, 2009 2:13 am    Post subject: Re: Broker stopped Reply with quote

Grand High Poobah

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

makgotsophemelo wrote:
I am having a problem with my production Broker on clustered servers,


Clustered how? WMQ cluster? Or failover cluster?

makgotsophemelo wrote:
is there a possibility that a ps command can be wrong in any other cases , or what could have happened


This is an OS question, but the ps command is fairly reliable. If this is a failover cluster, you could be looking at the standby (non-running) node.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
makgotsophemelo
PostPosted: Wed May 06, 2009 2:15 am    Post subject: Reply with quote

Novice

Joined: 06 May 2009
Posts: 11

failover cluster
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed May 06, 2009 2:20 am    Post subject: Reply with quote

Grand High Poobah

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

makgotsophemelo wrote:
failover cluster


There you go then.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
makgotsophemelo
PostPosted: Wed May 06, 2009 2:26 am    Post subject: Reply with quote

Novice

Joined: 06 May 2009
Posts: 11

i checked on both servers , the other one has the same details of the last stop in the log files,one more question,when is a log file not written to??,and is there a way where we can do an auomatic start-up for the broker in case , during a failover it doesn't start-up automatically??
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed May 06, 2009 2:28 am    Post subject: Reply with quote

Grand High Poobah

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

makgotsophemelo wrote:
when is a log file not written to??


When there's nothing to write.

makgotsophemelo wrote:
is there a way where we can do an auomatic start-up for the broker in case , during a failover it doesn't start-up automatically??


Then your failover script has a fault that needs fixing. The broker should be started on failover like any other software.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
makgotsophemelo
PostPosted: Wed May 06, 2009 2:31 am    Post subject: Reply with quote

Novice

Joined: 06 May 2009
Posts: 11

Thanx Vitor ,

I will check the script and see if there might be something wrong

Till next time

Cheers!!
Back to top
View user's profile Send private message
aditya.aggarwal
PostPosted: Tue May 12, 2009 12:21 am    Post subject: Reply with quote

Master

Joined: 13 Jan 2009
Posts: 252

Quote:
Then your failover script has a fault that needs fixing. The broker should be started on failover like any other software.


If it is a Sun Cluster and broker is not able to start automatically on the other node then "makgotsophemelo" need to ask Sun Team/Unix team to configure the Broker for the failover alon with MQ.

makgotsophemelo also need to ensure whether the Broker queue manager is able to failover successfully on the other node in case of failure?

If queue manager is not able to failover on other node then this is the problem due to wong failover cluster setup of MQ.

[makgotsophemelo write] i also checked the log files , it shows that the broker was down since the 22nd April[/makgotsophemelo write]

Which log files have you checked for Broker? Have you checked the queue manager was running on the same node or the other node?



Best Regarrds,
Aditya A
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 » General IBM MQ Support » Broker stopped
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.