| Author |
Message
|
| syangloo |
 Posted: Sat Nov 09, 2002 6:07 am Post subject: Can't bring up the listener |
 |
|
Centurion
Joined: 01 Oct 2002
Posts: 120
Location: Kuala Lumpur
|
Dear All,
OS HPUX 11i MQSeries 5.2
I can't bring up the listener before, today i just try to stop the Qmgr for some checking. After it i try to bring up the qmgr with below step:
strmqm qmgr
strmqcsv qmgr
ps -ef | grep qmgr
Q mgr is up but the listener is still down
So i try to issue
runmqlsr -t tcp -p 1414 -m qmgr &
I getting the message say can't bind to the port number
So i try other way.
runmqsc qmgr
start listener
it return listener started
i end this command
But the channel for connect to other qmgr is not up, after i issue the start channel command
What should i check?
Why this problem can be occur?
Any advice is appreciated.
Regards |
|
| Back to top |
|
 |
| vmcgloin |
| Posted: Mon Nov 11, 2002 12:40 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
We have this problem sometimes. It is due to listeners not closing the ports straight away when they stop.
Do a grep on the port for the listener causing problems e.g.:
netstat -a|grep 1418
We used this on AIX, there might be a different command on HPUX.
A running listener shows ESTABLISHED or LISTEN. But once it has stopped it goes through FIN_WAIT and FIN_WAIT2 states. You need to wait until this has passed before restarting the listener.
Regards,
Vicky |
|
| Back to top |
|
|
| 2189 |
| Posted: Mon Nov 11, 2002 8:51 am Post subject: |
|
|
Apprentice
Joined: 22 Oct 2002
Posts: 31
|
Sounds like the port is already in use. You could always try using a different port. Not sure what to suggest if you still get the error with other ports though.
_________________
2189 errors make me  |
|
| Back to top |
|
|
| syangloo |
| Posted: Mon Nov 11, 2002 11:39 pm Post subject: |
|
|
Centurion
Joined: 01 Oct 2002
Posts: 120
Location: Kuala Lumpur
|
Yes, the listener is running with the manually command like issue command start listener at runmqsc qmgr.
It l want the listener start at backgroup like run the command runmqlsr?
What is the proper step for me to bring up the listener as the backgroup job?
Regards |
|
| Back to top |
|
|
| 2189 |
| Posted: Tue Nov 12, 2002 4:42 am Post subject: |
|
|
Apprentice
Joined: 22 Oct 2002
Posts: 31
|
You can run runmqlsr in the backgroup by using:
nohup runmqlsr -t tcp -p PORT-NO -m QMGR-NAME &
Or use INETD as follows:
To configure a listener using INETD on an HP-UX machine requires root access and changes to 2 files as follows:
1. Edit the file /etc/services and add a line as follows:
<QMGR-NAME> <PORT-NO>/tcp
2. Edit /etc/inetd.conf file and add a line to call the program amqcrsta as follows:
<QMGR-NAME> stream tcp nowait mqm /opt/mqm/bin/amqcrsta amqcrsta -m <QMGR-NAME>
3. For INETD to read the new configurations use the command:
inetd -c
_________________
2189 errors make me |
|
| Back to top |
|
|
| kriersd |
| Posted: Tue Dec 03, 2002 10:44 am Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Looks like your having the same troubles that we have. I'll bet you still have resources that didn't get cleaned up apon shutdown. I'll bet one of them is still bound to your port.
This will show all shared resrouces running under user mqm. If all the queuemanagers and listeners are down you shouldn't see any resources when running this command.
This will remove the specified resource.
| Code: |
| ipcrm [-m or -s] ##### |
where #### is the id number shown and -m or -s is the type of resource.
Once you remove all the hanging resources, you should be able to startup the queue manager and listeners with out errors.
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| syangloo |
| Posted: Mon Dec 16, 2002 10:19 pm Post subject: |
|
|
Centurion
Joined: 01 Oct 2002
Posts: 120
Location: Kuala Lumpur
|
Thanks 2189, We have set all the port in the services file before and rerun the inetd also.
kriersd,
i'll test it out.
Regards |
|
| Back to top |
|
|
|
|
