| Author |
Message
|
| sethryan |
 Posted: Fri Mar 16, 2007 7:45 am Post subject: Urgent - Trouble with BlockIP2 on Linux MQ 6.0.2 |
 |
|
Novice
Joined: 21 Apr 2005
Posts: 10
|
Hi all,
We have some new systems that are migrating to Linux, and I am trying to get BlockIP2 installed and working. The servers are HP DL360 G5 Woodcrest running Redhat AS4 64 bit install. I installed the 32bit version of MQ6 refresh pack 2.
I downloaded version 2.60 of the exit and copied the 32bit exit to /var/mqm/exits. I altered my channel SCYEXIT('BlockIP2(BlockExit)') and SCYDATA('*;-d') just to test it. This is the error I'm getting in the debug log:
2007-03-16|10:37:55|Looking for BlockIP2.ini processing
2007-03-16|10:37:55|ProcessMQSiniFile() Invoked.
2007-03-16|10:37:55|Line read 1 AllQueueManagers:
2007-03-16|10:37:55|Line read 1 DefaultPrefix=/var/mqm
2007-03-16|10:37:55|Line read 0 ClientExitPath:
2007-03-16|10:37:55|Line read 0 ExitsDefaultPath=/var/mqm/exits
2007-03-16|10:37:55|Line read 0 LogDefaults:
2007-03-16|10:37:55|Line read 0 LogPrimaryFiles=3
2007-03-16|10:37:55|Line read 0 LogSecondaryFiles=2
2007-03-16|10:37:55|Line read 0 LogFilePages=1024
2007-03-16|10:37:55|Line read 0 LogType=CIRCULAR
2007-03-16|10:37:55|Line read 0 LogBufferPages=0
2007-03-16|10:37:55|Line read 0 LogDefaultPath=/var/mqm/log
2007-03-16|10:37:55|Line read 4 QueueManager:
2007-03-16|10:37:55|Line read 4 Name=FECPERF2.QUEUE.MANAGER
2007-03-16|10:37:55|Now we have the queueManager token...
2007-03-16|10:37:55|Wanted qmgr found
2007-03-16|10:37:55|Line read 4 Prefix=/var/mqm
2007-03-16|10:37:55|Wanted QmgrPrefix found
2007-03-16|10:37:55|Now we have the queueManager token...
2007-03-16|10:37:55|Line read 4 Directory=FECPERF2!QUEUE!MANAGER
2007-03-16|10:37:55|Wanted QmgrDirectory found
2007-03-16|10:37:55|Now we have the queueManager token...
2007-03-16|10:37:55|Line read 4 QueueManager:
2007-03-16|10:37:55|Line read 4 Name=RDPERF2
2007-03-16|10:37:55|Now we have the queueManager token...
2007-03-16|10:37:55|Line read 4 Prefix=/var/mqm
2007-03-16|10:37:55|Now we have the queueManager token...
2007-03-16|10:37:55|Line read 4 Directory=RDPERF2
2007-03-16|10:37:55|Now we have the queueManager token...
2007-03-16|10:37:55|resulting path: /var/mqm/qmgrs/FECPERF2!QUEUE!MANAGER
2007-03-16|10:37:55|ProcessMQSiniFile_qm_ini() Invoked.
2007-03-16|10:37:55|Line read 1 ExitPath:
2007-03-16|10:37:55|Line read 1 ExitsDefaultPath=/var/mqm/exits/
2007-03-16|10:37:55|Wanted ExitPath found
2007-03-16|10:37:55|Line read 1 ExitsDefaultPath64=/var/mqm/exits64/
2007-03-16|10:37:55|Wanted ExitsDefaultPath64 found
2007-03-16|10:37:55|Line read 0 Log:
2007-03-16|10:37:55|Line read 0 LogPrimaryFiles=3
2007-03-16|10:37:55|Line read 0 LogSecondaryFiles=2
2007-03-16|10:37:55|Line read 0 LogFilePages=16384
2007-03-16|10:37:55|Line read 0 LogType=CIRCULAR
2007-03-16|10:37:55|Line read 0 LogBufferPages=0
2007-03-16|10:37:55|Line read 0 LogPath=/var/mqm/log/FECPERF2!QUEUE!MANAGER/
2007-03-16|10:37:55|Line read 0 LogWriteIntegrity=SingleWrite
2007-03-16|10:37:55|Line read 0 Service:
2007-03-16|10:37:55|Line read 0 Name=AuthorizationService
2007-03-16|10:37:55|Line read 0 EntryPoints=13
2007-03-16|10:37:55|Line read 0 ServiceComponent:
2007-03-16|10:37:55|Line read 0 Service=AuthorizationService
2007-03-16|10:37:55|Line read 0 Name=MQSeries.UNIX.auth.service
2007-03-16|10:37:55|Line read 0 Module=/opt/mqm/lib/amqzfu
2007-03-16|10:37:55|Line read 0 ComponentDataSize=0
2007-03-16|10:37:55|Line read 0 Channels:
2007-03-16|10:37:55|Line read 0 MaxChannels=500
2007-03-16|10:37:55|resulting ExitPath paths: /var/mqm/exits/ 64: /var/mqm/exits64/
2007-03-16|10:37:55|ProcessMQSiniFile_qm_ini() requested connection broken.
2007-03-16|10:37:55|Free success
2007-03-16|10:37:55|ProcessMQSiniFile() Invoked.
2007-03-16|10:37:55|ProcessMQSiniFile_qm_ini() Invoked.
2007-03-16|10:37:55|Deduct status Q entered....
2007-03-16|10:37:55|UpdateShrMem() - generate shm shmem [/var/mqm/qmgrs/FECPERF2!QUEUE!MANAGER/shmem/BlockIP2.2]
2007-03-16|10:37:55|UpdateShrMem() Working
2007-03-16|10:37:55|UpdateShrMem() Channel [SETH.TEST] located at 0
2007-03-16|10:37:55|UpdateShrMem() Channel [SETH.TEST] max lim was reached -1
2007-03-16|10:37:55|LockChannelSem() entered
2007-03-16|10:37:55|LockSpecSem() entered
2007-03-16|10:37:55|LockAllSem() - generate sem shmem [/var/mqm/qmgrs/FECPERF2!QUEUE!MANAGER/shmem/BlockIP2.1]
2007-03-16|10:37:55|ftok1 -141303744 ok
2007-03-16|10:37:55|LockSpecSem() leaved
2007-03-16|10:37:55|UpdateShrMem() Decrement counter
2007-03-16|10:37:55|FreeChannelSem() entered
2007-03-16|10:37:55|FreeSpecSem() entered
2007-03-16|10:37:55|FreeSpecSem() leaved
2007-03-16|10:37:55|UpdateShrMem() status return -1 (0=below limit)
2007-03-16|10:37:55|======= TERM ======
Can anyone shed some light on what is going on?
Regards,
Seth |
|
| Back to top |
|
 |
| HubertKleinmanns |
| Posted: Fri Mar 16, 2007 7:58 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
sethryan,
I do not see an error message  . Were you able, to start the channel?
_________________
Regards
Hubert |
|
| Back to top |
|
|
| sethryan |
| Posted: Fri Mar 16, 2007 8:45 am Post subject: |
|
|
Novice
Joined: 21 Apr 2005
Posts: 10
|
The channel doesn't start. Here is the error in the qmgr error logs
----- amqccita.c : 3094 -------------------------------------------------------
03/16/2007 11:41:33 AM - Process(16578.4) User(mqm) Program(amqrmppa)
AMQ9492: The TCP/IP responder program encountered an error.
EXPLANATION:
The responder program was started but detected an error.
ACTION:
Look at previous error messages in the error files to determine the error
encountered by the responder program.
----- amqrmrsa.c : 459 --------------------------------------------------------
03/16/2007 11:41:33 AM - Process(16578.5) User(mqm) Program(amqrmppa)
AMQ9604: Channel 'SETH.TEST' terminated unexpectedly
EXPLANATION:
The process or thread executing channel 'SETH.TEST' is no longer running. The
check process system call returned 545284357 for process 16573.
ACTION:
No immediate action is required because the channel entry has been removed from
the list of running channels. Inform the system administrator who should
examine the operating system procedures to determine why the channel process
has terminated.
----- amqrcsia.c : 1410 -------------------------------------------------------
This is what I get in Hermes JMS client
I'm thinking it has something to do with 2007-03-16|10:37:55|UpdateShrMem() status return -1 (0=below limit) |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Fri Mar 16, 2007 10:07 am Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
It seems like there a real bug in BlockIP2 (2.60) when dealing with *NIX implementations, and long queue manager names....
| Quote: |
| 2007-03-16|10:37:55|ProcessMQSiniFile_qm_ini() requested connection broken. |
This causes storage a storage overlay. 
I'll see to create a fix to deal with this problem.
Maybe I should add more range checking, to see if there are enought room in the variables before they are used... But it might have a performace impact.
-- Lock it or Lose it .. 
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| sethryan |
| Posted: Fri Mar 16, 2007 11:06 am Post subject: |
|
|
Novice
Joined: 21 Apr 2005
Posts: 10
|
| I can test it on a queue manager with a shorter name. How many characters should I try to stay under? |
|
| Back to top |
|
|
| sethryan |
| Posted: Fri Mar 16, 2007 11:09 am Post subject: |
|
|
Novice
Joined: 21 Apr 2005
Posts: 10
|
| Also, should I try a different version of BlockIP2? I really appreciate the help. |
|
| Back to top |
|
|
| oz1ccg |
| Posted: Fri Mar 16, 2007 12:44 pm Post subject: |
|
|
Yatiri
Joined: 10 Feb 2002
Posts: 628
Location: Denmark
|
You can download the fixed version here 2.62. I'll update the manual soon because of new options.....
And after that change this link.
The problem was introduced in 2.60 becasue of a new function...
So you could try version 2.55.
-- Lock it or Lose it --
_________________
Regards, Jørgen
Home of BlockIP2, the last free MQ Security exit ver. 3.00
Cert. on WMQ, WBIMB, SWIFT. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Mar 16, 2007 5:13 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
But, should you really be trusting your enterprise security to a basically unsupported solution?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sethryan |
| Posted: Sat Mar 17, 2007 8:52 am Post subject: |
|
|
Novice
Joined: 21 Apr 2005
Posts: 10
|
The new version works! I used queue manager name LONG.QUEUE.MANAGER.NAME and it works correctly.
And this solution seems to be supported just fine. As long as it is extensively tested in a prod identical QA environment, whats the big deal? |
|
| Back to top |
|
|
|
|
