| Author |
Message
|
| roni |
 Posted: Wed Jan 23, 2002 2:46 pm Post subject: |
 |
|
Newbie
Joined: 22 Jan 2002
Posts: 8
|
I can successfully start a listener with:
runmqlsr -t tcp -p 1415 -m [qmgr name]
I cannot start the listener by using /etc/inetd.conf & /etc/services. I ran "refresh -s inetd" after the file changes.
/etc/inetd.conf:
MQSeries stream tcp nowait mqm /usr/mqm/bin/amqcrsta amqcrsta
/etc/services:
MQSeries 1415/tcp
I also checked that I did not have the wrong directory in /etc/inetd.conf:
lrwxrwxrwx 1 root system 24 Jan 30 2001 /usr/mqm/bin/amqcrsta -> /usr/mqm/bin/amqcrsta_nd
Am I overlooking a typo or is this a known problem?
Thanks.
|
|
| Back to top |
|
 |
| StefanSievert |
| Posted: Wed Jan 23, 2002 3:26 pm Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
Hi Roni,
this is taken from the MQSeries Intercommunication Guide:
MQSeries stream tcp nowait root /usr/mqm/bin/amqcrsta amqcrsta
You did specify 'mqm' as the user.
Hope that helps,
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
| tony@work |
| Posted: Wed Jan 23, 2002 3:29 pm Post subject: |
|
|
Newbie
Joined: 12 Nov 2001
Posts: 9
Location: Australia
|
It looks to me like you are making configuration entries for a second QMGR on the AIX System, indicated by the 1415 port. If this is so, then I believe that you entry into the /etc/inetd.conf file is missing the QMGR name. Without the QMGR name it will associate the process with the 'default' QMGR.
ie/
you have:
MQSeries stream tcp nowait mqm /usr/mqm/bin/amqcrsta amqcrsta
you should have:
MQSeries stream tcp nowait mqm /usr/mqm/bin/amqcrsta amqcrsta -m <QMGR-Name>
|
|
| Back to top |
|
|
| roni |
| Posted: Thu Jan 24, 2002 7:39 am Post subject: |
|
|
Newbie
Joined: 22 Jan 2002
Posts: 8
|
|
| Back to top |
|
|
| StefanSievert |
| Posted: Thu Jan 24, 2002 11:43 am Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
Roni,
back to your original question, what exactly do you mean when you say you can't start the listener? I just want to make sure that you understand that in your configuration inetd is the 'listener' and you have to test it by trying to start a channel targeting this machine and port. This should then cause inetd to spawn a new amqcrsta process, which you should be able to see using the 'ps -ef | grep amq' command.
Just a shot in the dark, following a gut feeling... 
Cheers,
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
| roni |
| Posted: Thu Jan 24, 2002 11:59 am Post subject: |
|
|
Newbie
Joined: 22 Jan 2002
Posts: 8
|
I believe you're right. I was probably checking incorrectly to see if it was working. If I do a remote connect with MQSeries Explorer to the port I've listed in /etc/services -- will that also test that it's working? That is what I have been trying as a quick test -- and the MQSeries Explorer cannot connect. It will connect if I do runmqlsr with that port.
Thanks for your help.
Roni |
|
| Back to top |
|
|
| StefanSievert |
| Posted: Thu Jan 24, 2002 1:19 pm Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
Roni,
hmm, that's strange. Do you get any error messages on the server side (AMQERR01.LOG)? What return code do you get from MQExplorer?
If you do a netstat -a on the unix side, do you see an entry for port 1415 with the status 'LISTENING'?
In your /etc/services file, is the entry MQSeries tcp/1415 the last line in the file or did you put it somewhere in the middle (try creating an empty line after it, if it is the last line)?
Anyway, you should get some return codes either on the sending side (NT Event Viewer or AMQERR01.LOG) or on the receiving i.e. Unix side (AMQERR01.LOG, inetd log??).
Can you check for any of these error messages?
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
| roni |
| Posted: Wed Jan 30, 2002 9:30 am Post subject: |
|
|
Newbie
Joined: 22 Jan 2002
Posts: 8
|
There were no messages on the server side -- either system or qmgr.
The return code from MQExplorer was that the host at the specified port was not available:
Try the connection again later. If the failure persists, record the error values and contact your systems administrator. The return code from TCP/IP is 10061 (X'274D'). The reason for the failure may be that this host cannot reach the destination host. It may also be possible that the listening program at host 'hostname(xx.xx.xx.xx) (1416)' was not running. If this is the case, perform the relevant operations to start the TCP/IP listening program, and try again.
A netstat -a didn't show the port number at all. I could see 2 other ports started with runmqlsr -- they listed "established" connections and "listening".
In /etc/services the entry is in the middle of the file and was a modified copy of an existing line in /etc/services.
Sorry it took a while to get back to your questions -- thanks alot for your help. Unfortunately, my systems haven't given any clues as to what may be wrong.
Roni
|
|
| Back to top |
|
|
| StefanSievert |
| Posted: Wed Jan 30, 2002 4:42 pm Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
Roni,
if you are using inetd to start your channel programs, you should not see ANY runmqlsr processes running at all. Is it possible that you still start those runmqlsr's from a startup script?
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
| roni |
| Posted: Thu Jan 31, 2002 6:44 am Post subject: |
|
|
Newbie
Joined: 22 Jan 2002
Posts: 8
|
| Yes I had forgotten to take them out. I did run another test without any listeners running. When I tried to connect via MQ Explorer I got the same qmgr unavailable message. When I did a ps there were no amqcrsta. Also, just to clarify, there were no messages in the syslog output from inetd. |
|
| Back to top |
|
|
| StefanSievert |
| Posted: Thu Jan 31, 2002 11:33 am Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
Roni,
you won't see any amqcrsta processes as output from a ps command unless a channel is actually running.
However, and I have to defer to the AIX experts here for the correct command because I can't recall, netstat -a (that's for Windows) should give you a line for your configured MQ port(s) (1414, 1415?) which shows a status of LISTENING for these ports. If they don't show up, I would suspect that your inetd configuration is not correct. This usually works without problems, so I guess we have overlooked something really obvious...
Anybody else with ideas?
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
| anderson |
| Posted: Thu Feb 07, 2002 4:10 am Post subject: |
|
|
Newbie
Joined: 06 Feb 2002
Posts: 1
|
Two things you could try:--
1. To establish if the inetd.conf configuration is working try:
telnet yourhost 1415
If you get a "connected" message then your basic inetd.conf setup is OK.
2. Just a wild guess but you need to define a "SYSTEM.ADMIN.SVRCONN" channel before you can connect with MQExplorer.
|
|
| Back to top |
|
|
| roni |
| Posted: Thu Feb 07, 2002 6:24 am Post subject: |
|
|
Newbie
Joined: 22 Jan 2002
Posts: 8
|
I've just installed a brand new server with MQSeries 5.2 and I'm having similar problems. Since noone else is on it I can do a little more experimenting.
I added 1414 to the /etc/services and the MQSeries line in /etc/inetd.conf. Did a refresh and could connect with MQ Explorer. Netstat reported it had an established connection against 1414 and was also listening.
MQSeries stream tcp nowait mqm /opt/mqm/bin/amqcrsta amqcrsta -m MQSIHUB
MQSeries 1414/tcp # MQSeries
I copied and modified the 1414 line and ADDED 1415. Did a refresh and all I had listening (from netstat) was 1414.
MQSeries stream tcp nowait mqm /opt/mqm/bin/amqcrsta amqcrsta -m MQSIHUB
MQSeries 1414/tcp # MQSeries
MQSeries 1415/tcp # MQSeries
Then I tried two entries:
MQSeries1 stream tcp nowait mqm /opt/mqm/bin/amqcrsta amqcrsta -m MQSIHUB
MQSeries2 stream tcp nowait mqm /opt/mqm/bin/amqcrsta amqcrsta -m MQSIHUB
MQSeries1 1414/tcp # MQSeries
MQSeries2 1415/tcp # MQSeries
This resulted in listening only on 1415 -- I'd lost 1414.
Maybe if you want to run more than one port for the same qmgr you have to do runmqlsr for the additional ports? I have only one qmgr running but I need multiple ports.
|
|
| Back to top |
|
|
| roni |
| Posted: Thu Feb 07, 2002 8:31 am Post subject: |
|
|
Newbie
Joined: 22 Jan 2002
Posts: 8
|
| After reading other posts, it looks like my best bet is to use runmqlsr anyway. But it's still annoying that it won't work with inetd. |
|
| Back to top |
|
|
|
|
