| Author |
Message
|
| integra |
 Posted: Wed Jan 25, 2006 3:13 am Post subject: File error occurred (AMQ9516) |
 |
|
Newbie
Joined: 25 Jan 2006
Posts: 8
Location: Hannover, Germany
|
Hi,
I have installed MQ V5.3.0.2 plus CSD11 on a pSeries running AIX V5.3.
Everything looked fine.
Then I created a queue manager and started it:
crtmqm -q bcg.queue.manager
strmqm bcg.queue.manager
But when I try to define a channel I get the following error:
AMQ9516: File error occurred.
Here is the command I issued:
runmqsc bcg.queue.manager
5724-B41 (C) Copyright IBM Corp. 1994, 2002. ALL RIGHTS RESERVED.
Starting MQSC for queue manager bcg.queue.manager.
DEFINE CHANNEL(TEST) CHLTYPE(SVRCONN)
1 : DEFINE CHANNEL(TEST) CHLTYPE(SVRCONN)
AMQ9516: File error occurred.
And here is the content of the error log:
----- amquopra.c : 3906 -------------------------------------------------------
01/25/06 11:53:13
AMQ9516: File error occurred.
EXPLANATION:
The filesystem returned error code 1000 for file 'TEST'.
ACTION:
Record the name of the file 'TEST' and tell the systems administrator, who
should ensure that file 'TEST' is correct and available.
----- amquopra.c : 3906 -------------------------------------------------------
Does anyone have an idea what's the problem here ?
Any help is much appreciated !
Regards,
Ruediger |
|
| Back to top |
|
 |
| wschutz |
| Posted: Wed Jan 25, 2006 4:12 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Are there any FDC's in /var/mqm/<qmgr>/errors ??
_________________
-wayne |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Jan 25, 2006 4:15 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| wschutz wrote: |
| Are there any FDC's in /var/mqm/<qmgr>/errors ?? |
FDC files appear under /var/mqm/errors/  |
|
| Back to top |
|
|
| integra |
| Posted: Wed Jan 25, 2006 4:36 am Post subject: |
|
|
Newbie
Joined: 25 Jan 2006
Posts: 8
Location: Hannover, Germany
|
Hi,
thanks for your quick reply.
In /var/mqm/errors are some files with content like this:
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thursday January 19 15:13:41 NFT 2006 |
| Host Name :- sapbt310 (AIX 5.3) |
| PIDS :- 5724B4101 |
| LVLS :- 530.11 CSD11 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- CO052000 |
| Application Name :- MQM |
| Component :- cciTcpReceive |
| Build Date :- Aug 2 2005 |
| CMVC level :- p530-11-L050802 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000008 (mqm) |
| Program Name :- amqrmppa |
| Process :- 00557220 |
| Thread :- 00000008 |
| QueueManager :- bcg!queue!manager |
| Major Errorcode :- rrcE_BAD_DATA_RECEIVED |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9207 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9207: The data received from host 'scanondemand |
| (9.19.123.97)' is not valid. |
| FDCSequenceNumber :- 0 |
| Comment1 :- scanondemand (9.19.123.97) |
| Comment2 :- TCP/IP |
| Comment3 :- |
| |
+-----------------------------------------------------------------------------+
I think this comes from an internal scan service which scans all ports of the system on a regular basis.
Regards,
Ruediger |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jan 25, 2006 4:39 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| integra wrote: |
| I think this comes from an internal scan service which scans all ports of the system on a regular basis. |
Probably it does, if you have such a service. Tell it not to scan the MQ ports, or tell it to scan them using amqscnx or something.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Jan 25, 2006 4:59 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| integra wrote: |
Probe Id :- CO052000
...
Component :- cciTcpReceive
...
Major Errorcode :- rrcE_BAD_DATA_RECEIVED
...
Comment1 :- scanondemand (9.19.123.97)
...
I think this comes from an internal scan service which scans all ports of the system on a regular basis. |
Almost certainly correct, given the data in the FDC file. But the timestamp at the top of it is different from the one in the original error you posted. Please supply output from
| Code: |
cd /var/mqm/errors
/usr/mqm/bin/ffstsummary |
|
|
| Back to top |
|
|
| integra |
| Posted: Wed Jan 25, 2006 5:06 am Post subject: |
|
|
Newbie
Joined: 25 Jan 2006
Posts: 8
Location: Hannover, Germany
|
Hi,
thanks for your quick reply... 
Here is the output:
AMQ13872.0.FDC 2006/01/18 17:21:45 amqzlaa0_nd 413872 7 XY324192 GetSubpoolsLock xecF_E_UNEXPECTED_SYSTEM_RC OK
AMQ42416.0.FDC 2006/01/18 17:21:45 runmqchi 442416 5 XY324192 GetSubpoolsLock xecF_E_UNEXPECTED_SYSTEM_RC OK
AMQ49918.0.FDC 2006/01/18 17:21:45 amqpcsea 249918 1 XY324192 GetSubpoolsLock xecF_E_UNEXPECTED_SYSTEM_RC OK
AMQ22032.0.FDC 2006/01/18 17:24:22 endmqm 422032 2 XC338001 xehAsySignalHandler xecE_W_UNEXPECTED_ASYNC_SIGNAL OK
AMQ56434.0.FDC 2006/01/18 17:25:05 amqzdmaa 356434 4 XY324192 GetSubpoolsLock xecF_E_UNEXPECTED_SYSTEM_RC OK
AMQ64772.0.FDC 2006/01/18 17:25:05 amqrrmfa 364772 1 XY324192 GetSubpoolsLock xecF_E_UNEXPECTED_SYSTEM_RC OK
AMQ42424.0.FDC 2006/01/18 17:26:19 endmqm 442424 2 XC338001 xehAsySignalHandler xecE_W_UNEXPECTED_ASYNC_SIGNAL OK
AMQ01540.0.FDC 2006/01/18 17:28:29 amqzfuma 0 0 XY324192 GetSubpoolsLock
AMQ44126.0.FDC 2006/01/18 17:31:13 amqzxma0_nd 344126 1 AD031001 adiWriteFile xecF_E_UNEXPECTED_SYSTEM_RC OK
AMQ52316.0.FDC 2006/01/18 17:33:06 amqzxma0_nd 352316 1 AD031001 adiWriteFile xecF_E_UNEXPECTED_SYSTEM_RC OK
AMQ44162.0.FDC 2006/01/18 17:35:23 setmqcap 344162 1 XC022003 xcsDisplayMessage xecF_E_UNEXPECTED_SYSTEM_RC OK
AMQ42500.0.FDC 2006/01/18 17:35:29 amqzlaa0_nd 442500 5 AD020000 adiSetFSize xecF_E_UNEXPECTED_SYSTEM_RC OK
AMQ40050.0.FDC 2006/01/18 17:35:40 amqzxma0_nd 340050 1 ZX005025 zxcProcessChildren zrcX_PROCESS_MISSING OK
AMQ74448.0.FDC 2006/01/18 17:35:52 amqzfuma 274448 1 AD020000 adiSetFSize xecF_E_UNEXPECTED_SYSTEM_RC OK
AMQ89286.0.FDC 2006/01/18 17:35:52 amqfcxaa 389286 1 PU202010 fqxCreateInternalQ frcE_UNEXPECTED_ERROR OK
AMQ89300.0.FDC 2006/01/18 17:37:03 runmqsc 389300 0 XC022003 xcsDisplayMessage xecF_E_UNEXPECTED_SYSTEM_RC OK
AMQ81022.0.FDC 2006/01/18 17:37:19 amqpcsea 0 0 XC022003 xcsDisplayMessage
AMQ97382.0.FDC 2006/01/18 17:37:19 runmqchi 0 0 XC022003 xcsDisplayMessage
AMQ40052.0.FDC 2006/01/18 17:38:56 amqzxma0_nd 0 0 AD031001 adiWriteFile
AMQ44166.0.FDC 2006/01/18 17:45:08 runmqlsr_nd 344166 2 XC338001 xehAsySignalHandler xecE_W_UNEXPECTED_ASYNC_SIGNAL OK
AMQ57220.0.FDC 2006/01/19 14:13:41 amqrmppa 557220 8 CO052000 cciTcpReceive rrcE_BAD_DATA_RECEIVED OK
AMQ57220.0.FDC 2006/01/19 14:13:44 amqrmppa 557220 9 CO052000 cciTcpReceive rrcE_BAD_DATA_RECEIVED OK
AMQ57220.0.FDC 2006/01/19 14:13:56 amqrmppa 557220 12 CO052000 cciTcpReceive rrcE_BAD_DATA_RECEIVED OK
AMQ57220.0.FDC 2006/01/19 14:13:58 amqrmppa 557220 13 CO052000 cciTcpReceive rrcE_BAD_DATA_RECEIVED OK
AMQ57220.0.FDC 2006/01/19 14:14:00 amqrmppa 557220 14 CO052000 cciTcpReceive rrcE_BAD_DATA_RECEIVED OK
AMQ57220.0.FDC 2006/01/19 14:14:01 amqrmppa 557220 0 XC130006 xehExceptionHandler STOP OK
AMQ57222.0.FDC 2006/01/19 14:14:02 amqrmppa 557222 0 XC130006 xehExceptionHandler STOP OK
AMQ57224.0.FDC 2006/01/19 14:14:05 amqrmppa 557224 4 CO052000 cciTcpReceive rrcE_BAD_DATA_RECEIVED OK
AMQ57224.0.FDC 2006/01/19 14:14:08 amqrmppa 557224 6 CO052000 cciTcpReceive rrcE_BAD_DATA_RECEIVED OK
AMQ79398.0.FDC 2006/01/23 16:19:29 amqzxma0_nd 479398 1 ZX005022 zxcProcessChildren lrcW_S_FAST_PATH_APP_DEAD OK
AMQ79398.0.FDC 2006/01/23 16:19:29 amqzxma0_nd 479398 1 ZX005022 zxcProcessChildren lrcW_S_FAST_PATH_APP_DEAD OK
AMQ79398.0.FDC 2006/01/23 16:19:29 amqzxma0_nd 479398 1 ZX005022 zxcProcessChildren lrcW_S_FAST_PATH_APP_DEAD OK
AMQ79398.0.FDC 2006/01/23 16:19:29 amqzxma0_nd 479398 1 ZX005022 zxcProcessChildren lrcW_S_FAST_PATH_APP_DEAD OK
AMQ79398.0.FDC 2006/01/23 16:19:29 amqzxma0_nd 479398 1 ZX005022 zxcProcessChildren lrcW_S_FAST_PATH_APP_DEAD OK
AMQ79398.0.FDC 2006/01/23 16:19:29 amqzxma0_nd 479398 1 ZX005022 zxcProcessChildren lrcW_S_FAST_PATH_APP_DEAD OK
AMQ79398.0.FDC 2006/01/23 16:19:29 amqzxma0_nd 479398 1 ZX005022 zxcProcessChildren lrcW_S_FAST_PATH_APP_DEAD OK
AMQ79398.0.FDC 2006/01/23 16:19:29 amqzxma0_nd 479398 1 ZX005022 zxcProcessChildren lrcW_S_FAST_PATH_APP_DEAD OK
AMQ79398.0.FDC 2006/01/23 16:19:29 amqzxma0_nd 479398 1 ZX005022 zxcProcessChildren lrcW_S_FAST_PATH_APP_DEAD OK
AMQ92312.0.FDC 2006/01/24 14:10:27 runmqlsr_nd 692312 2 XC338001 xehAsySignalHandler xecE_W_UNEXPECTED_ASYNC_SIGNAL OK
AMQ03994.0.FDC 2006/01/24 22:27:18 runmqlsr_nd 503994 2 XC338001 xehAsySignalHandler xecE_W_UNEXPECTED_ASYNC_SIGNAL OK
BTW, I'm using MQ with IBM WebSphere Partner Gateway Enterprise Edition V6.
Regard,
Ruediger |
|
| Back to top |
|
|
| LuisFer |
| Posted: Wed Jan 25, 2006 5:15 am Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
If you do a telnet on TCP/IP port 1414 (or MQ port) will have the same FDC.
telnet MQDNS 1414
Review the AMQERRLG files and FDC's created after this probe.
Regards |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Jan 25, 2006 5:59 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
OK I see no FFST for the time 01/25/06 11:53:13 which is when your original problem was noted in the error log you posted.
Apart from this, I have no idea. I recommend taking an MQ trace using the instructions in the System Administration Guide and calling MQ Support.
Unless anyone else has an idea... |
|
| Back to top |
|
|
| gunter |
| Posted: Wed Jan 25, 2006 6:33 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
It looks like a problem with the os, the user couldn't write. Did you check the filesystem /var/mqm and the setuid-bits in /usr/mqm/bin ? Is there enough space and the right permission.
| Quote: |
DEFINE CHANNEL(TEST) CHLTYPE(SVRCONN)
1 : DEFINE CHANNEL(TEST) CHLTYPE(SVRCONN)
AMQ9516: File error occurred.
|
This command changes the file /var/mqm/qmgrs/bcg!queue!manager/@ipcc/AMQCLCHL.TAB ond maybe also other files.
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3 |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Jan 25, 2006 6:45 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| gunter wrote: |
| It looks like a problem with the os, the user couldn't write. Did you check the filesystem /var/mqm and the setuid-bits in /usr/mqm/bin ? |
MQ runtime processes never write to /usr/mqm ... only ever /var/mqm |
|
| Back to top |
|
|
| gunter |
| Posted: Wed Jan 25, 2006 7:25 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
I didn't said someboy writes to /usr/mqm, I said , check the setuid bits, because if somebody removed setuid from binaries, ,the result are really bad problems. I had this problem an I still don't know who or what did it.
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3 |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Jan 25, 2006 7:30 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| gunter wrote: |
| I didn't said someboy writes to /usr/mqm, I said , check the setuid bits |
Sorry, my mistake - you are right. Removing setuid or setgid bits on MQ executables could prevent them from writing to protected MQ directories I guess. |
|
| Back to top |
|
|
| integra |
| Posted: Wed Feb 01, 2006 4:06 am Post subject: |
|
|
Newbie
Joined: 25 Jan 2006
Posts: 8
Location: Hannover, Germany
|
Hi,
finally, I managed to solve this problem....
Here is what I did:
1. Uninstall WebSphere Partner Gateway
2. Manually remove the remaining entries from the ODM using the odmdelete command like this:
odmdelete -q lpp_name=BCGBobcat600 -o product
odmdelete -q lpp_id=2108 -o history
odmdelete -q lpp_id=2108 -o inventory
BTW: the WPG uninstaller sucks - it leaves entries in the ODM...
3. Uninstall MQ using SMIT
4. Manually remove remaining MQ directories
5. Install MQ using SMIT
=> problem solved
Regards,
Ruediger |
|
| Back to top |
|
|
|
|
