| Author |
Message
|
| thejacka1 |
 Posted: Thu Apr 14, 2005 1:52 am Post subject: TCP responder subsystem not working on HPUX 11 |
 |
|
Newbie
Joined: 14 Apr 2005
Posts: 5
Location: London
|
Hi
We have an HPUX version 11.0.0 development server, our Unix admins have applied the 2004 patches yesterday and since then we have been unable to get the MQ managers on the server to respond to Client calls.
MQ version is 5.3 CSD04, we are in the throws of installing the CSD09 patch.
I have tried various ways to isolate the problem, the MQ managers all start up OK and I can run the listener either through the inetd.conf or running the runmqlsr command.
Either way I can't make a client connection to the queue manager and the remote admin MMC will not connect.
The error message we get is AMQ9228 "The TCP/IP responder program could not be started". I get a 2059 error if I try to do an amqsput.
I have done a search of the site but couldn't find a similar problem. So I guess my question is, will appying the CSD09 patch fix the problem or is it something else. I think it may be something to do with Shared Memory, but my knowledge of HP/UX isn't strong enough to diagnose.
Thanks for any help you can give me.
Scott |
|
| Back to top |
|
 |
| sjensen |
| Posted: Thu Apr 14, 2005 3:05 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Hi
Is it possible something is holding the port you are trying to use?
Cheers
Stefan |
|
| Back to top |
|
|
| thejacka1 |
| Posted: Thu Apr 14, 2005 3:33 am Post subject: |
|
|
Newbie
Joined: 14 Apr 2005
Posts: 5
Location: London
|
Hi
Is it possible something is holding the port you are trying to use?
Cheers
Stefan
It's not reporting any conflicts, "netstat -a" shows that the port is listening correctly. If I try to start a listener whilst the port is running then it doesn't allow me. I've tried it with the listener program running and running it from the inetd.conf.
We have now applied CSD09 but the problem still exists. I will raise the problem with IBM and report back what they say.
thanks
Scott |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 14, 2005 4:00 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Is there a firewall on the HP server, or between the HP server and your client?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| thejacka1 |
| Posted: Thu Apr 14, 2005 4:20 am Post subject: |
|
|
Newbie
Joined: 14 Apr 2005
Posts: 5
Location: London
|
"Is there a firewall on the HP server, or between the HP server and your client?"
Hi
No, no firewalls involved, I can telnet directly to the server, I can even bring the queue manager up and ping a receiver channel from a remote machine. The problem seems to be sending a transmission from another manager, using amqsputc from a client, or trying to connect to the manager from a remote MMC. The problem is I'm not getting any meaningful error logs or FDC files because the MQ manager seems to be untouched.
I think the problem lies either with the HP/UX comms subsystem or with trying to allocate shared memory segments, but I'm being asked to prove it |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 14, 2005 4:44 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Can you use amqsputc on the server machine? (You will have to install the client if you haven't)
Have you tried enabling trace on MQ on the server?
Can you ask your HP sys admin to prove that the connection is getting to the MQ server?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| thejacka1 |
| Posted: Thu Apr 14, 2005 5:18 am Post subject: |
|
|
Newbie
Joined: 14 Apr 2005
Posts: 5
Location: London
|
I've tried to use amqsputc on the server but it's unable to make a connection out.
I can start a trace, what do you suggest I capture, should I just choose "all"?
I just created a Remote definition on another development server pointing to a test queue and a receiver channel on the server. It managed to send through to the test queue OK, which makes things really strange. So Receiver channels can be contacted but SVRCONN channels and Sender channels are not working.
thanks
Scott |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 14, 2005 5:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I actually meant try to use amsputc to talk to the local server on the machine...
But if you can't create outbound connections, then there's some sort of networking limitations in effect.
But a SVRCONN uses the same listener port as the Receiver does. Maybe you have host specific filters enabled on the network - so the sender qmgr is allowed to connection, but your other client machines aren't.
Can you make a client connection from the machine that hosts that sender qmgr?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Thu Apr 14, 2005 8:13 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Why raise it with IBM?
You put on HP maintenance, and it breaks WMQ.
Why not raise it with HP? |
|
| Back to top |
|
|
| clindsey |
| Posted: Thu Apr 14, 2005 9:17 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
From one of your client machines, enter telnet hphost 1414
assuming the listerner is on port 1414. Either you will get a message that you are connected or you will get connection refused. If connection fails, WMQ is completely out of the picture and you can report that to your HP admin. The problem is with the HP box or in the network.
Also, try the telnet from a shell on the hp machine with telnet localhost 1414. If that fails, the problem is completely isolated to the HP box.
Charlie |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 14, 2005 9:22 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| clindsey wrote: |
From one of your client machines, enter telnet hphost 1414
assuming the listerner is on port 1414. |
| thejacka1 wrote: |
| I can telnet directly to the server, I can even bring the queue manager up and ping a receiver channel from a remote machine. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 14, 2005 7:14 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If everything seems to be configured right and just does not work check following
a) make sure the listnener is not running under root authority
b) make sure the userid the listener is running under is in the mqm group.
We had the case once where root was running the listener. Everything seemed to work but the communication just did not happen. Note that root is not in the mqm group on our servers.
Enjoy  |
|
| Back to top |
|
|
| thejacka1 |
| Posted: Fri Apr 15, 2005 1:14 am Post subject: |
|
|
Newbie
Joined: 14 Apr 2005
Posts: 5
Location: London
|
Thanks for all the help on this one.
In the end we reverted back to the 2002 patches on HP/UX 11.0.0, everything is working OK with no changes required for MQ.
Looks like there are serious compatibility problems with the 2004 patches, it's a shame that the managers here couldn't live with the down time whilst I tried to fix it with IBM.
The symptoms of the problem were we were unable to start client processes (amqcrsta) from client connections or remote MMC. The Sender/Receiver channels were working but they are owned by the amqrmppa process, so the listeners were working. I think the problems were related to allocating shared memory when an amqcrsta process was spawned.
So it is more likely to be an HPUX issue rather than IBM, but as I said earlier, sometimes we have to prove that the product we support is working properly before the sys admins will step up to the mark!
Anyway, I will feed back this to IBM on our PMR and see if they can come up with anything.
One for the knowledge base anyway
thanks
Scott |
|
| Back to top |
|
|
|
|
