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 » IBM MQ Installation/Configuration Support » MQSeries on Sun Cluster3.1

Post new topic  Reply to topic
 MQSeries on Sun Cluster3.1 « View previous topic :: View next topic » 
Author Message
srguntaka
PostPosted: Tue Jan 31, 2006 11:52 am    Post subject: MQSeries on Sun Cluster3.1 Reply with quote

Newbie

Joined: 31 Jan 2006
Posts: 1
Hi,
I installed MQSeries 5.3 on sun cluster3.1 with one Queue Manager and it is working fine. but at night 2:00AM to 3:00AM I am getting this messages and looks the queue managere is repeatedly restarting, Please let me know is any solution. and really appreciate for your reply.


01/31/06 02:13:58
AMQ9411: Repository manager ended normally.

EXPLANATION:
The repository manager ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
01/31/06 02:13:59
AMQ9542: Queue manager is ending.

EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
----- amqrimna.c : 859 --------------------------------------------------------
01/31/06 02:14:04
AMQ8004: WebSphere MQ queue manager 'GVS108P' ended.

EXPLANATION:
WebSphere MQ queue manager 'GVS108P' ended.
ACTION:
None.
-------------------------------------------------------------------------------
01/31/06 02:20:02
AMQ8003: WebSphere MQ queue manager 'GVS108P' started.

EXPLANATION:
WebSphere MQ queue manager 'GVS108P' started.
ACTION:
None.
-------------------------------------------------------------------------------
01/31/06 02:20:02
AMQ9410: Repository manager started

EXPLANATION:
The repository manager started successfully.
ACTION:
None.
-------------------------------------------------------------------------------
01/31/06 02:20:41
AMQ8024: WebSphere MQ channel initiator started.

EXPLANATION:
The channel initiator for queue SYSTEM.CHANNEL.INITQ has been started.
ACTION:
None.
-------------------------------------------------------------------------------
01/31/06 02:24:05
AMQ9411: Repository manager ended normally.

EXPLANATION:
The repository manager ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
01/31/06 02:24:06
AMQ9542: Queue manager is ending.

EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
----- amqrimna.c : 859 --------------------------------------------------------
01/31/06 02:24:11
AMQ8004: WebSphere MQ queue manager 'GVS108P' ended.

EXPLANATION:
WebSphere MQ queue manager 'GVS108P' ended.
ACTION:
None.
-------------------------------------------------------------------------------
01/31/06 02:28:35
AMQ8003: WebSphere MQ queue manager 'GVS108P' started.

EXPLANATION:
WebSphere MQ queue manager 'GVS108P' started.
ACTION:
None.
-------------------------------------------------------------------------------
01/31/06 02:28:35
AMQ9410: Repository manager started

EXPLANATION:
The repository manager started successfully.
ACTION:
None.
-------------------------------------------------------------------------------
01/31/06 02:29:42
AMQ8024: WebSphere MQ channel initiator started.

EXPLANATION:
The channel initiator for queue SYSTEM.CHANNEL.INITQ has been started.
ACTION:
None.
-------------------------------------------------------------------------------
01/31/06 02:40:55
AMQ9411: Repository manager ended normally.

EXPLANATION:
The repository manager ended normally.
ACTION:
None.
-------------------------------------------------------------------------------
01/31/06 02:40:56
AMQ9542: Queue manager is ending.

EXPLANATION:
The program will end because the queue manager is quiescing.
ACTION:
None.
----- amqrimna.c : 859 --------------------------------------------------------
01/31/06 02:40:59
AMQ8004: WebSphere MQ queue manager 'GVS108P' ended.

EXPLANATION:
WebSphere MQ queue manager 'GVS108P' ended.
ACTION:
None.
-------------------------------------------------------------------------------
01/31/06 02:41:25
AMQ8003: WebSphere MQ queue manager 'GVS108P' started.

EXPLANATION:
WebSphere MQ queue manager 'GVS108P' started.
ACTION:
None.
-------------------------------------------------------------------------------
01/31/06 02:41:25
AMQ9410: Repository manager started

EXPLANATION:
The repository manager started successfully.
ACTION:
None.
-------------------------------------------------------------------------------
01/31/06 02:41:26
AMQ8024: WebSphere MQ channel initiator started.

EXPLANATION:
The channel initiator for queue SYSTEM.CHANNEL.INITQ has been started.
ACTION:
None.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Jan 31, 2006 8:24 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
This night activity sounds somewhat suspicious. Are you running any program on a schedule that would need the qmgr to be down and is dependant on such an event?(offline bakcup?). Could it be that the process is not successfull and tries multiple times ?

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
mvic
PostPosted: Wed Feb 01, 2006 3:20 am    Post subject: Re: MQSeries on Sun Cluster3.1 Reply with quote

Jedi

Joined: 09 Mar 2004
Posts: 2080
I think it's safe to say that something on the machine is calling 'endmqm'. Probably the best step right now is to find out exactly what that something is.

ps -ef taken at the time should show the endmqm process, and - importantly - the pid of its parent.

So I would suggest running ps -ef automatically every 10 seconds for 1/2 hour or so in the affected time period, to try to capture what is going on.
Back to top
View user's profile Send private message
wschutz
PostPosted: Wed Feb 01, 2006 12:28 pm    Post subject: Reply with quote

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
You could also look into your "cron" log to see if there is anything that runs about that time.
_________________
-wayne
Back to top
View user's profile Send private message Send e-mail AIM Address
HubertKleinmanns
PostPosted: Wed Feb 01, 2006 11:48 pm    Post subject: Reply with quote

Shaman

Joined: 24 Feb 2004
Posts: 732
Location: Germany
Another possibility is, that the Sun cluster has some dependencies (e. g. listener) which are defined as critical resources and cannot be started (e. g. because the port is locked). The cluster then could try again and again.
_________________
Regards
Hubert
Back to top
View user's profile Send private message Visit poster's website
malammik
PostPosted: Wed Feb 08, 2006 5:51 pm    Post subject: Reply with quote

Partisan

Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA
Did you use any specific support packs from IBM to get MQ working on Sun Cluster 3.1 or did u just write your own scripts, customize the ones from MC69 which only supports 2.x sun cluster.

Thanks.
_________________
Mikhail Malamud
http://www.netflexity.com
http://groups.google.com/group/qflex
Back to top
View user's profile Send private message Visit poster's website AIM Address
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » MQSeries on Sun Cluster3.1
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.