| Author |
Message
|
| Gideon |
 Posted: Fri Apr 15, 2011 12:28 pm Post subject: Cant start listener |
 |
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
I am running WMQ 9.0.1 and WMB 7.0.0.0 on RHEL 5.6
I went to start the listener, and find the 'resource temporarily unavailable" basically forever,
when I try to perform a 'su mqm' from another session, that also says the resource is temporarily unavailable
| Code: |
[root@ex5b ~]# su mqm
MQSI 7.0.0.2
/opt/ibm/mqsi/7.0
bash-4.1$ mqsilist
BIP1285I: Broker 'LQM3' on queue manager 'LQM3' is stopped.
BIP8071I: Successful command completion.
bash-4.1$ mqsistart LQM3
WebSphere MQ queue manager 'LQM3' starting.
50 log records accessed on queue manager 'LQM3' during the log replay phase.
Log replay for queue manager 'LQM3' complete.
Transaction manager state recovered for queue manager 'LQM3'.
WebSphere MQ queue manager 'LQM3' 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.
bash-4.1$
bash-4.1$
bash-4.1$ runmqlsr -m LQM3 -t tcp -p 1414 &
bash: fork: retry: Resource temporarily unavailable
bash: fork: retry: Resource temporarily unavailable
bash: fork: retry: Resource temporarily unavailable
bash: fork: retry: Resource temporarily unavailable
bash: fork: Resource temporarily unavailable
bash-4.1$ mqsistop LQM3
bash: fork: retry: Resource temporarily unavailable
bash: fork: retry: Resource temporarily unavailable
bash: fork: retry: Resource temporarily unavailable
bash: fork: retry: Resource temporarily unavailable
bash: fork: Resource temporarily unavailable
bash-4.1$ |
Any ideas |
|
| Back to top |
|
 |
| shashivarungupta |
| Posted: Fri Apr 15, 2011 12:35 pm Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
WMQ 9.0.1 ? 
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Fri Apr 15, 2011 12:49 pm Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
whats the o/p of following command, of your qmgr ?
| Code: |
display lsstatus(*) all |
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Apr 15, 2011 12:50 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I wonder if the listener object has already started up?
I wonder how one would check? |
|
| Back to top |
|
|
| Gideon |
| Posted: Fri Apr 15, 2011 2:33 pm Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
I can not check status, becuase all commands by the OS now result in
| Code: |
| resource temporarily unavailable |
I could not even perform a shutdown -r now
So I rebooted, and got the same issue, after I did a start of the listener, qmgr and broker
Kind of looks like the system ran out of memory or something |
|
| Back to top |
|
|
| Gideon |
| Posted: Fri Apr 15, 2011 2:56 pm Post subject: |
|
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
I rebooted and ran the following
| Code: |
bash-4.1$ strmqm LQM3
WebSphere MQ queue manager 'LQM3' starting.
5 log records accessed on queue manager 'LQM3' during the log replay phase.
Log replay for queue manager 'LQM3' complete.
Transaction manager state recovered for queue manager 'LQM3'.
WebSphere MQ queue manager 'LQM3' started.
bash-4.1$
bash-4.1$ runmqlsr -m LQM3 -t tcp -p 1414 &
[1] 5964
bash-4.1$ 5724-H72 (C) Copyright IBM Corp. 1994, 2009. ALL RIGHTS RESERVED.
bash-4.1$
bash-4.1$ runmqsc LQM3
5724-H72 (C) Copyright IBM Corp. 1994, 2009. ALL RIGHTS RESERVED.
Starting MQSC for queue manager LQM3.
display lsstatus(*) all
1 : display lsstatus(*) all
AMQ8631: Display listener status details.
LISTENER(SYSTEM.LISTENER.TCP.1) STATUS(RUNNING)
PID(5964) STARTDA(2011-04-15)
STARTTI(14.51.33) DESCR( )
TRPTYPE(TCP) CONTROL(MANUAL)
IPADDR(*) PORT(1414)
BACKLOG(100)
:
end
2 : end
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.
bash-4.1$ |
However, the problem does not appear to start until after the WMB broker is started
| Code: |
bash-4.1$
bash-4.1$ mqsistart LQM3
BIP8096I: Successful command initiation, check the system log to ensure that the component started without problem and that it continues to run without problem.
bash-4.1$
bash-4.1$
bash-4.1$
bash-4.1$ ls
bash: fork: retry: Resource temporarily unavailable
bash: fork: retry: Resource temporarily unavailable
bash: fork: retry: Resource temporarily unavailable |
Should I report in the WMB forum,
Any ideas |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Apr 15, 2011 3:53 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Are you issuing a command line start for a listener that exists as an object which is under queue manager control?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Sat Apr 16, 2011 12:11 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| Quote: |
display lsstatus(*) all
1 : display lsstatus(*) all
AMQ8631: Display listener status details.
LISTENER(SYSTEM.LISTENER.TCP.1) STATUS(RUNNING)
PID(5964) STARTDA(2011-04-15)
STARTTI(14.51.33) DESCR( )
TRPTYPE(TCP) CONTROL(MANUAL)
IPADDR(*) PORT(1414)
BACKLOG(100)
|
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| exerk |
| Posted: Sat Apr 16, 2011 1:31 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| shashivarungupta wrote: |
| Quote: |
display lsstatus(*) all
1 : display lsstatus(*) all
AMQ8631: Display listener status details.
LISTENER(SYSTEM.LISTENER.TCP.1) STATUS(RUNNING)
PID(5964) STARTDA(2011-04-15)
STARTTI(14.51.33) DESCR( )
TRPTYPE(TCP) CONTROL(MANUAL)
IPADDR(*) PORT(1414)
BACKLOG(100)
|
|
Good spot! It was late for me last night  ...
...but then, why not issue a START LISTENER command?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Sat Apr 16, 2011 4:00 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| exerk wrote: |
| shashivarungupta wrote: |
| Quote: |
display lsstatus(*) all
1 : display lsstatus(*) all
AMQ8631: Display listener status details.
LISTENER(SYSTEM.LISTENER.TCP.1) STATUS(RUNNING)
PID(5964) STARTDA(2011-04-15)
STARTTI(14.51.33) DESCR( )
TRPTYPE(TCP) CONTROL(MANUAL)
IPADDR(*) PORT(1414)
BACKLOG(100)
|
|
Good spot! It was late for me last night ... |
 A cup of coffee could have energized your nuron ! 
On my RHEL setup, I tried to do the same thing as Gideon was trying to do, to run the listener using runmqlsr as a background process..it worked for me. 
@Gideon :
Do you see any errors in the logs ?
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Apr 16, 2011 4:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It sounds like the system is running out of memory or out of file space.
I think you should troubleshoot those rather than ask for more help in the broker forum.
If you don't know how to troubleshoot for these, please don't ask for help in doing that task. Please try to figure it out for yourself. |
|
| Back to top |
|
|
|
|
