| Author |
Message
|
| apohorai |
 Posted: Fri Aug 04, 2006 12:55 am Post subject: Reason code 2195 (AMQ4048) |
 |
|
Apprentice
Joined: 15 Mar 2006
Posts: 26
Location: Budapest/Munich
|
Hi,
I'm getting crazy about this problem:
Actually 7 queue managers (5.3) working fine on an AIX 5.2ML5 machine.
I've created two new ones, but I can't connect to them using MQ explorer.
All firewall ports open, everything looks OK, but I still receiving the error message above when I try to connect.
Any Idea?
Cheers
$ ps -ef |grep HPI
mqm 21432 23288 0 09:06:45 - 0:00 /usr/mqm/bin/amqrrmfa -t2332800 -s2592000 -p2592000 -g5184000 -c3600 -m SHPING01
mqm 23288 1 0 09:06:44 - 0:00 amqzxma0 -m SHPING01
mqm 24504 23288 0 09:06:45 - 0:00 /usr/mqm/bin/amqzdmaa -m SHPING01
mqm 27974 23288 0 09:06:44 - 0:00 /usr/mqm/bin/amqzfuma -m SHPING01
mqm 34130 23288 0 09:06:45 - 0:00 amqzllp0 -mSHPING01 ?
mqm 60550 23288 0 09:06:44 - 0:00 amqhasmx SHPING01 /var/mqm
mqm 60890 23288 0 09:06:45 - 0:00 amqzlaa0 -mSHPING01 -fip0
mqm 61290 23288 0 09:06:45 - 0:00 /usr/mqm/bin/runmqchi -m SHPING01
mqm 66870 1 0 09:13:19 - 0:00 amqpcsea SHPING01
$ cat /etc/services |grep hpi
shping01 12515/tcp
shping01 12515/udp
$ cat /etc/inetd.conf |grep HPI
shping01 stream tcp nowait root /usr/mqm/bin/amqcrsta amqcrsta -m SHPING01 |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Aug 04, 2006 1:04 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
In theory at least, a 2195 should be associated with an FDC file - are you getting one and what does it say? Can you post the relevant bits? Also, what CSD level of 5.3 are you on?
Moving to the realm of speculation here, have you tried shutting down some of the existing queue managers & then connecting to the new ones? It's a remote but measurable possibiity you've got resource issues.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| apohorai |
| Posted: Fri Aug 04, 2006 1:17 am Post subject: |
|
|
Apprentice
Joined: 15 Mar 2006
Posts: 26
Location: Budapest/Munich
|
Ufortunately there's no any PDC for this, and the last one is generated 2 days ago. Nothing in the AMQERR as well.
I just realized that only CSD4 installed. Can this be a problem? The other queue managers are working fine.
I haven't stopped them yet. I'll try shortly. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Aug 04, 2006 1:24 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Never mind a PDC, is there the FDC I asked about.....  
I did say in theory. Odd though...
It is IMHO worth updating the CSD level just on spec. That level is way old (the latest is CSD 12) and there's been a lot of fixes in the intervening 8 CSDs.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| apohorai |
| Posted: Fri Aug 04, 2006 2:04 am Post subject: |
|
|
Apprentice
Joined: 15 Mar 2006
Posts: 26
Location: Budapest/Munich
|
Sorry, that was a typo, of course I spoke about FDC ... :DDD
-rw-r--r-- 1 mqm mqm 27033 Aug 02 16:53 AMQ13524.0.FDC
drwxrwsrwx 2 mqm mqm 13824 Aug 02 16:53 .
drwxrwxr-x 8 mqm mqm 512 Aug 03 15:45 ..
-rw-rw-rw- 1 mqm mqm 78591 Aug 04 10:28 AMQERR01.LOG
I stopped all qm's, and started the newly created one, but the problem is the same.
root@dublin:/var/mqm/errors# ps -ef |grep mqm
mqm 21436 60902 0 10:28:18 - 0:00 /usr/mqm/bin/amqzfuma -m SHPING01
mqm 24506 60902 0 10:28:18 - 0:00 /usr/mqm/bin/amqrrmfa -t2332800 -s2592000 -p2592000 -g5184000 -c3600 -m SHPING01
root 26504 27088 0 11:02:13 pts/2 0:00 grep mqm
mqm 27976 60902 0 10:28:18 - 0:00 /usr/mqm/bin/amqzdmaa -m SHPING01
mqm 34132 60902 0 10:28:18 - 0:00 amqzllp0 -mSHPING01 ?
mqm 52130 60902 0 10:28:18 - 0:00 amqzlaa0 -mSHPING01 -fip0
mqm 60552 60902 0 10:28:18 - 0:00 amqhasmx SHPING01 /var/mqm
mqm 60902 1 0 10:28:18 - 0:00 amqzxma0 -m SHPING01
mqm 66876 60902 0 10:28:18 - 0:00 /usr/mqm/bin/runmqchi -m SHPING01
I'm going to apply the CSD ... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Aug 04, 2006 2:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Definitely apply the CSD/FP.
Also, what does the header block of the FDC file show? Or just run ffstsummary.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| tleichen |
| Posted: Fri Aug 04, 2006 12:22 pm Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
In my experience, this has usually meant something is way out of kilter, such as using the wrong version of the core dll's or libraries with the product, or the installation did not complete properly. That is why it is called "Unexpected Error". Some condition has occurred that really is not supposed to happen. 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| apohorai |
| Posted: Fri Aug 11, 2006 7:27 am Post subject: |
|
|
Apprentice
Joined: 15 Mar 2006
Posts: 26
Location: Budapest/Munich
|
Guys,
I solved this problem. Here's the "solution" if someone has the same.
I not copied here, but there was a # after the inetd.conf entry like (#requested by me)
This is not permitted.
I removed, now everything working fine ...
Cheers, |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Aug 11, 2006 2:24 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| apohorai wrote: |
Guys,
I solved this problem. Here's the "solution" if someone has the same.
I not copied here, but there was a # after the inetd.conf entry like (#requested by me)
This is not permitted.
I removed, now everything working fine ...
Cheers, |
If you are at 5.3 or above don't use inetd anymore. Use runmqlsr... and search the forum for the reason why...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
