| Author |
Message
|
| sgb |
 Posted: Thu Jul 08, 2010 6:09 pm Post subject: Error code 2101 for file 'SYSTEM.DEF.SVRCONN' |
 |
|
Newbie
Joined: 10 Mar 2010
Posts: 7
|
Having got MQ running on our development server, I'm now trying to set it up on our production system. I'm using the same channel configuration with just some of the names changed from TEST to PROD, but either I've forgotten some important installation step, or something has changed from 7.0.0 to 7.0.1.
Installation seemed to go fairly smoothly, and the new prod server can open an outgoing channel to its partner, but the partner trying to connect to it was getting 2035 errors. Log snippet:
----- amqrmrsa.c : 525 --------------------------------------------------------
09/07/10 10:23:50 - Process(2641.75) User(root) Program(amqrmppa)
Host(crimcheck.org.au)
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager 'CCHECKPR' failed with reason code
2035.
ACTION:
Ensure that the queue manager is available and operational.
Not being quite sure what the problem there was, I gave root some permissions via setmqaut. Now I now longer get a 2035, but I get:
----- amqrmrsa.c : 525 --------------------------------------------------------
09/07/10 11:58:23 - Process(2641.83) User(root) Program(amqrmppa)
Host(crimcheck.org.au)
AMQ9516: File error occurred.
EXPLANATION:
The filesystem returned error code 2101 for file 'SYSTEM.DEF.SVRCONN'.
ACTION:
Record the name of the file 'SYSTEM.DEF.SVRCONN' and tell the systems
administrator, who should ensure that file 'SYSTEM.DEF.SVRCONN' is correct and
available.
Is there something I'm missing or doing wrong? Has there been a fatal change between 7.0.0 and 7.0.1? I'm happy to dig up whatever extra info might help in working out what is broken here...
Thanks,
Steve. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Jul 08, 2010 6:43 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have you check group and ownership of the MQ file system?
Seems to me this would be the only reason why you would see something like this... Unless your file system is really way to underdimensioned...
PS if you want to play God in MQ land don't use root use mqm 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sgb |
| Posted: Thu Jul 08, 2010 6:51 pm Post subject: |
|
|
Newbie
Joined: 10 Mar 2010
Posts: 7
|
Everything under /var/mqm and /opt/mqm belongs to mqm:mqm (well, except for /var/mqm/tivoli, which is root:mqm, and which I'm not using).
df reports the particular volume has a bit over 3Gb available.
And I would prefer to avoid using root as well, but was running out of ideas, and the 2035 error did say that User(root) was at fault. |
|
| Back to top |
|
|
| sgb |
| Posted: Thu Jul 08, 2010 7:01 pm Post subject: |
|
|
Newbie
Joined: 10 Mar 2010
Posts: 7
|
| ...ctually, a deeper probe of /opt/mqm shows that /opt/mqm/lib/iconv contains a bunch of files belonging to bin:bin, and /opt/mqm/bin/isa.xml belongs to bin:mqm. Are those of significance? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jul 08, 2010 8:34 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
----- amqrmrsa.c : 525 --------------------------------------------------------
09/07/10 11:58:23 - Process(2641.83) User(root) Program(amqrmppa)
Host(crimcheck.org.au)
AMQ9516: File error occurred.
|
This might well be your cause. Did you start the qmgr as root?
Shut the qmgr down and restart it as user mqm, then try again.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sgb |
| Posted: Thu Jul 08, 2010 10:21 pm Post subject: |
|
|
Newbie
Joined: 10 Mar 2010
Posts: 7
|
Hooray!
That does seem to have done the trick.
The odd thing is that both before and after restarting, 'ps -ef | grep mq' reported all the listed processes as belonging to mqm.
Thank you!  |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Fri Jul 09, 2010 9:57 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
| sgb wrote: |
| The odd thing is that both before and after restarting, 'ps -ef | grep mq' reported all the listed processes as belonging to mqm. |
That's because the "sticky" bit was set for the MQ processes.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
|
|
