| Author |
Message
|
| Jarno |
 Posted: Fri Nov 14, 2003 6:19 am Post subject: Continuous recovery/error messages in Windows eventlog |
 |
|
Newbie
Joined: 14 Nov 2003
Posts: 4
|
Running MQSeries v5.2 on w2k(sp3) adv server(cluster). Looks like our system is working but there's a lot of error messages in event log:
Here are the event descriptions from eventlog:
*********************************************
"Time: 14:57:02 Event ID: 7883
MY_SYSTEM_NAME/Listener MQSeries service started from recovery.
The MQSeries service has successfully recovered MY_SYSTEM_NAME/Listener.
No Action Required.
Time: 14:57:39 Event ID: 9218
The TCP/IP listener program could not bind to port number 1414.
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. Record the return code 0 from the bind and tell the systems administrator.
Time: 14:57:39 Event ID: 8062
Unexpected return code, '20', from command 'RUNMQLSR -mMY_SYSTEM_NAME -t"TCP" -p 1414 '.
An unexpected return code, '20', was returned by command 'RUNMQLSR -mMY_SYSTEM_NAME -t"TCP" -p 1414 '. This command was issued by the MQSeries service for queue manager 'MY_SYSTEM_NAME'. Verify that the command and parameters are correct.
Time: 14:58:48 Event ID: 7882
Attempting to recover MY_SYSTEM_NAME/Listener MQSeries service.
The MQSeries service has detected that MY_SYSTEM_NAME/Listener has failed, and is attempting to restart it. No Action Required. "
****************************************
I checked usage of port 1414 and its only used by mqseries itself.
Is the syntax of start command : "RUNMQLSR -mMY_SYSTEM_NAME -t"TCP" -p 1414 " really correct ? Shouldn't there be spaces after -m and -t parameters ?
-What could cause this and how to fix it ?
Thanks in advance, Jarno |
|
| Back to top |
|
 |
| JasonE |
| Posted: Fri Nov 14, 2003 6:25 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| Your error is a bind failure - You have something already listening on port 1414 (netstat -a will show it). If you really, really think you havent (ie no other qmgrs nor listeners), ensure you have a recent ver and fixpack level as there were problems fixed which can lead to duplicate launches of services. |
|
| Back to top |
|
|
| Jarno |
| Posted: Fri Nov 14, 2003 6:51 am Post subject: |
|
|
Newbie
Joined: 14 Nov 2003
Posts: 4
|
I've checked port usage and _only_ single instance if runmqlsr.exe process is using 1414 port on our server. Could it be that for some reason server is trying to start another instance of runmqlsr.exe ?
Do you think that syntax of this command is correct ?
'RUNMQLSR -mMY_SYSTEM_NAME -t"TCP" -p 1414 '. I cound not find this command configured anywhere in mqseries files or registry entries. Is there any way to edit it ? Or is it just parsed internally somewhere ? |
|
| Back to top |
|
|
| JasonE |
| Posted: Fri Nov 14, 2003 6:58 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Its parsed internally.
Dont forget if a single instance is *running* (in task mgr) then a 2nd instance will fail. It is quite possible we tried to launch two by accident - What version and csd are you at? |
|
| Back to top |
|
|
| Jarno |
| Posted: Tue Nov 18, 2003 11:24 pm Post subject: |
|
|
Newbie
Joined: 14 Nov 2003
Posts: 4
|
| We are running v5.2 and latest installed cds is 'CDS04'. |
|
| Back to top |
|
|
| JasonE |
| Posted: Wed Nov 19, 2003 2:26 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| Try csd06 or higher to pick up IC34382 (MULTIPLE COPIES OF LISTENER AND TRIGGER MONITOR ON REBOOT OF THE MACHINE: ONLY ONE QUEUE MANAGER WAS RUNNING.) |
|
| Back to top |
|
|
|
|
