| Author |
Message
|
| elikatz |
 Posted: Sun Feb 21, 2010 8:08 pm Post subject: listener didn't start after cluster failover |
 |
|
Voyager
Joined: 24 Feb 2009
Posts: 86
|
all,
we have MQ 6.0.2.8 installed on windows 2003 SP2 server cluster.
we are doing a weekly fail over but this weekend we encountered a serious issue - the listener didn't start after the fail over.
i see this error in the logs:
AM,9218,None,The TCP/IP listener program could not bind to port number 1415. An attempt to bind the TCP/IP socket to the listener port was unsuccessful. The failure could be due to another program using the same port number. The return code from the 'bind' call for port 1415 was 10013. Record these values and tell the systems administrator.
there is nothing else but MQ server running on those servers - any idea what can cause this issue?
thanks... |
|
| Back to top |
|
 |
| Vitor |
| Posted: Sun Feb 21, 2010 8:20 pm Post subject: Re: listener didn't start after cluster failover |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| elikatz wrote: |
| there is nothing else but MQ server running on those servers - any idea what can cause this issue? |
Sounds like the listener on the active node didn't close, didn't close cleanly or didn't close in a way the OS (or failover software) liked.
Is the failover with MCSC or some other software?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| elikatz |
| Posted: Mon Feb 22, 2010 5:07 am Post subject: |
|
|
Voyager
Joined: 24 Feb 2009
Posts: 86
|
| MCSC, the fail over was done with the cluster administrator tool. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Feb 22, 2010 5:36 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I see this once or twice every 100 failovers. No, we don't have MSCS clusters failing over 100s of times a week! Over the course of a year, for planned failovers due to maintenance, I would say that's about as often as it happens for us.
I suspect that some other process grabs the MQ port temporarily. Personally, I wish MQ Listeners had retry logic to auto recover from this.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| nathanw |
| Posted: Mon Feb 22, 2010 7:52 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
| PeterPotkay wrote: |
I suspect that some other process grabs the MQ port temporarily. Personally, I wish MQ Listeners had retry logic to auto recover from this. |
Or at least reported quite quickly that it had not started up at system restart so that we are not waiting for problems to tell us etc
_________________
Who is General Failure and why is he reading my hard drive?
Artificial Intelligence stands no chance against Natural Stupidity.
Only the User Trace Speaks The Truth  |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Feb 22, 2010 10:25 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| nathanw wrote: |
| PeterPotkay wrote: |
I suspect that some other process grabs the MQ port temporarily. Personally, I wish MQ Listeners had retry logic to auto recover from this. |
Or at least reported quite quickly that it had not started up at system restart so that we are not waiting for problems to tell us etc |
An event message would be nice. Yeah, yeah, we could be parsing the MQ error log looking for this error messages and alert on it that way. Just would be nice to have an "MQ way" of knowing.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| BBM |
| Posted: Mon Feb 22, 2010 8:18 pm Post subject: |
|
|
Master
Joined: 10 Nov 2005
Posts: 217
Location: London, UK
|
| I too have seen this from time to time... I just thank my lucky stars the other spurious MSCS related errors we used to get with earlier versions have disappeared..! |
|
| Back to top |
|
|
| Crille76 |
| Posted: Mon Mar 08, 2010 5:02 am Post subject: |
|
|
Newbie
Joined: 15 Aug 2008
Posts: 9
|
This is probably caused by the ports being taken by another app.
Verify the error message, and if this is the case i suggest reserving the ports.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ReservedPorts |
|
| Back to top |
|
|
|
|
