ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Performance Monitoring » Rfhutilc connection problem.

Post new topic  Reply to topic Goto page 1, 2  Next
 Rfhutilc connection problem. « View previous topic :: View next topic » 
Author Message
czaszek
PostPosted: Tue May 30, 2006 5:25 am    Post subject: Rfhutilc connection problem. Reply with quote

Apprentice

Joined: 30 May 2006
Posts: 36
Location: Poland

hi All

I am trying to connect to my remote queue manager (MQ5.3) from my WinXP laptop using rfhutilc.exe.
I do not a direct connection to the linux box so I am connecting via ssh (using putty) and tunneling 1414 port from a linux box to my laptop.
When I test the connection from my laptop (telnet localhost 1414) I works fine, but when I try to connect via rfhutilc, it shows:
"2059 Queue manager not available (Connect) - may not be started"

In the rfhutilc I entered:
in the Queue Manager Name (to connect to):
SYSTEM.DEF.SVRCONN/TCP/localhost(1414)
Queue name:
QUEUE_NAME_TO_BROWSE

Additionally I have tested these settings on one of Windows boxes located in our server room, which has a direct connection to the linux box, instead of "localhost" I have used an IP address and it works fine.
(I tested 127.0.0.1 instead of localhost on my laptop, it does not help).

Have anyone of You faced problems like that?
Thanks in advance for any help.

Lukas
Back to top
View user's profile Send private message
wschutz
PostPosted: Tue May 30, 2006 5:39 am    Post subject: Reply with quote

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)

I've no experience with tunnelling via putty, but have you tried using amqsputc.exe with a MQSERVER variable to see if you can get that to work first?
_________________
-wayne
Back to top
View user's profile Send private message Send e-mail AIM Address
jefflowrey
PostPosted: Tue May 30, 2006 5:40 am    Post subject: Re: Rfhutilc connection problem. Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

czaszek wrote:
in the Queue Manager Name (to connect to):
SYSTEM.DEF.SVRCONN/TCP/localhost(1414)

What part of the documentation for RFHUTILC told you that syntax would function in that field?

Try the following from a windows command prompt.
Code:
c:\>set MQSERVER=SYSTEM.DEF.SVRCONN/TCP/localhost(1414)
c:\>rfhutilc


Also, use netstat to make sure that 1414 is already tunnelled and working.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue May 30, 2006 2:19 pm    Post subject: Re: Rfhutilc connection problem. Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

jefflowrey wrote:
czaszek wrote:
in the Queue Manager Name (to connect to):
SYSTEM.DEF.SVRCONN/TCP/localhost(1414)

What part of the documentation for RFHUTILC told you that syntax would function in that field?

Try the following from a windows command prompt.
Code:
c:\>set MQSERVER=SYSTEM.DEF.SVRCONN/TCP/localhost(1414)
c:\>rfhutilc


Also, use netstat to make sure that 1414 is already tunnelled and working.
Don't know about the part of the documentation. Tool is so intuitive I haven't read it. But this works for me:
in qmgr field
SYSTEM.ADMIN.SVRCONN/TCP/targethost(port)
Although I must say I do not tunnel the port. We have it open in the firewall.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
czaszek
PostPosted: Tue May 30, 2006 11:17 pm    Post subject: Reply with quote

Apprentice

Joined: 30 May 2006
Posts: 36
Location: Poland

I have tested the tunnel using netstat:
TCP 127.0.0.1:1414 0.0.0.0:0 LISTENING

I have also added the server connection:
set MQSERVER=SYSTEM.DEF.SVRCONN/TCP/localhost(1414)

I have chosen this connection in the Queue Manager Name.
Unfortunatelly I still have got:
2059 Queue manager not available (Connect) - may not be started

Any idea?
Back to top
View user's profile Send private message
wschutz
PostPosted: Wed May 31, 2006 2:45 am    Post subject: Reply with quote

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)

Try using amqscnxc and see if you can connect with that:

Quote:
Usage:
amqscnxc [-x ConnName [-c SvrconnChannelName]] [QMgrName]


If that works, then your problem is either with the MQSERVER variable or rhfutilc itself. If it doesn't work, then I'd suspect your putty tunnel.
_________________
-wayne
Back to top
View user's profile Send private message Send e-mail AIM Address
jefflowrey
PostPosted: Wed May 31, 2006 5:22 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

wschutz wrote:
If it doesn't work, then I'd suspect your putty tunnel.

That's only because you've never done an ssh tunnel of the MQ listener port.

If the port shows up as LISTENING in netstat, then the tunnel is working.

amqscnxc is the tool to use to verify.

Apparently it's valid syntax to use the MQSERVER values in the rfhutilc queue manager name - I didn't know that!
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
jbanoop
PostPosted: Sat Aug 26, 2006 5:43 am    Post subject: Reply with quote

Chevalier

Joined: 17 Sep 2005
Posts: 401
Location: SC

Anybody got a solution for this ?

I am getting the same problem. Environment is MQ V 6.0 and RFHUTIL 4.0.4.

the QMGR is on AIX and the machine I am trying from is WinXP.
The MQExplorer on the same machine shows the concerned queue manager.
However when i use rfhutilc i get a message saying 2059 Queue manager not available (Connect) - may not be started.

I am able to telnet the qmgr port on AIX successfuly.
the MQSERVER variable is set to SYSTEM.ADMIN.SVRCONN/TCP/10.1.53.112(1415).
any suggestions are really welcome..

Regards,
Anoop
Back to top
View user's profile Send private message Yahoo Messenger
jefflowrey
PostPosted: Sat Aug 26, 2006 5:52 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

does amqscnxc work?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sat Aug 26, 2006 5:53 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

czaszek wrote:
I have tested the tunnel using netstat:
TCP 127.0.0.1:1414 0.0.0.0:0 LISTENING
On which machine? While in the ssh session?
czaszek wrote:

I have also added the server connection:
set MQSERVER=SYSTEM.DEF.SVRCONN/TCP/localhost(1414)

I have chosen this connection in the Queue Manager Name.
Unfortunatelly I still have got:
2059 Queue manager not available (Connect) - may not be started

Any idea?

If you are truely using 127.0.0.1 and or localhost this means you have very little understanding of TCP/IP or the network. You will never get out of your machine with this ip address. So how will you ever connect from your laptop to the foreign host with this address? -- Guess what the answer is NEVER EVER.
Try replacing the localhost with the ip you use for ssh.

Now if your tunnelling really exposes this as a local connection you have a different problem. I have seen this behavior if the user running the mqlistener has no permissions on the qmgr.

Enjoy
_________________
MQ & Broker admin


Last edited by fjb_saper on Sat Aug 26, 2006 6:03 am; edited 2 times in total
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Sat Aug 26, 2006 5:59 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

FJ -
It's perfectly reasonable to use localhost when one has used SSH to tunnell a remote port to a port on the local machine.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sat Aug 26, 2006 6:09 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

I must admit my experience with SSH tunnelling is limited to X11. In this case you still have at each end to notify the destination using the other's IP address and not your own.

Like I said after the edit, if the tunnelling truely exposes it as a local service I strongly suspect that the mqlistener might be running under a user with no mq priviledges: like root but not part of the mqm group... This would explain the behavior. Which ever way you want to connect (sender channel, svrconn, etc) you will get the QMGR not available response...

Thanks for clarifying my poor understanding of TCP/IP
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
jbanoop
PostPosted: Sat Aug 26, 2006 6:33 am    Post subject: Reply with quote

Chevalier

Joined: 17 Sep 2005
Posts: 401
Location: SC

Sorry for not clarifying these points :

In my case I am not using tunnelling. Its a normal connection frm winXP to aix.So i guess the question of problems during tunneling need not be considered.
Also my qmgr is on an aix box listening on 1415 port and all these steps I have discussed are related to connecting frm that winxp box to AIX box using rfhutilc (MQ explorer works).

So I guess my problem is the same as czaszek's but without the issue of tunneling and also that my qmgr is not on the local machine (however the port for the qmgr can be telnetted from the winxp machine).
Just as a note ..the admin server conn channel has a user id set on the MCA.

The is amqscnxc also not working:
>amqscnxc -x 10.1.53.112(1415) -c SYSTEM.ADMIN
.SVRCONN EEAX431P

Sample AMQSCNXC start
Connecting to queue manager EEAX431P
using the server connection channel SYSTEM.ADMIN.SVRCONN
on connection name 10.1.53.112(1415).
MQCONNX ended with reason code 2059


Regards,
Anoop
Back to top
View user's profile Send private message Yahoo Messenger
fjb_saper
PostPosted: Sat Aug 26, 2006 6:37 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

Another reason for unexpected Qmgr Not available is a blip in the network and too many channels open due to the network instability. User's programs reconnect without getting disconnected and you rapidly hit the max channel.

Usually doing a force shutdown and restart of the offending channel(s) solves that problem...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
zpat
PostPosted: Wed Aug 30, 2006 2:11 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5849
Location: UK

I always use the AMQCLCHL.TAB file with RFHUTILC, works fine.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » IBM MQ Performance Monitoring » Rfhutilc connection problem.
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.