MQSeries.net :: View topic

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » mqrc 2035

mqrc 2035

« View previous topic :: View next topic »

Author

Message

JPN

Posted: Sun Jun 25, 2017 12:53 am Post subject: mqrc 2035

Novice

Joined: 27 Feb 2015
Posts: 14

MQ Version: 8.0.0.4
OS Version: RHEL 7.1
MQRC: 2035

After migrating from Solaris to Linux server, there were authorisation errors and to disable for server connection channel tried using 'NOAUTH' and getting the below error

----- cmqxrsrv.c : 2321 -------------------------------------------------------
06/25/2017 10:52:13 AM - Process(24548.576641) User(mqm) Program(amqrmppa)
Host(slds302) Installation(Installation1)
VRMF(8.0.0.4) QMgr(QMC.POST.DV)

AMQ9557: Queue Manager User ID initialization failed for 'NOAUTH'.

EXPLANATION:
The call to initialize the User ID 'NOAUTH' failed with CompCode 2 and Reason
2035.
ACTION:
Correct the error and try again.
----- cmqxrsrv.c : 2321 -------------------------------------------------------

hughson

Posted: Sun Jun 25, 2017 3:28 am Post subject: Re: mqrc 2035

Padawan

Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand

Are you certain that the NOAUTH user ID actually exists on your new Linux Server? Was it defined on the old Solaris machine?

If it does exist, are you certain that the NOAUTH user ID is supposed to have authority to anything? If I were to create a user id that had no authority to anything, I might call it something like 'NOAUTH'. Compare the authority it had on the Solaris machine.

Is this NOAUTH user ID in the MCAUSER of your server-connection channel? Was the same configuration present on Solaris?

Could you elaborate on what you expected to happen?

Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software

JPN

Posted: Mon Jun 26, 2017 5:25 am Post subject: 2035

Novice

Joined: 27 Feb 2015
Posts: 14

Hi Morag,

Was trying to follow the article published by you on https://www-01.ibm.com/support/docview.wss?uid=swg21636093.

Have tried changing the user to mqm and still have the error.

----- cmqxrsrv.c : 2321 -------------------------------------------------------
06/26/2017 03:20:01 PM - Process(48674.404213) User(mqm) Program(amqrmppa)
Host(slds302) Installation(Installation1)
VRMF(8.0.0.4) QMgr(QMC.POST.DV)

AMQ9557: Queue Manager User ID initialization failed for 'MQM'.

EXPLANATION:
The call to initialize the User ID 'MQM' failed with CompCode 2 and Reason
2035.
ACTION:
Correct the error and try again.
----- cmqxrsrv.c : 2321 -------------------------------------------------------

Which ever user is passed on the MCAUSER, the same user is passed on the qmgr error logs with the above statement

mqjeff

Posted: Mon Jun 26, 2017 5:50 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

mqm is different than "mqm".

You should be using neither.
_________________
chmod -R ugo-wx /

fjb_saper

Posted: Mon Jun 26, 2017 6:07 am Post subject:

Grand High Poobah

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

case in point:

run the following mqsc command

Code:

dis chlauth(yourchannelname) type(all) match(runcheck) address('originating ip address in doted form') clntuser('mqm')

And now set authorizations up so that you can use a different user...

_________________
MQ & Broker admin

hughson

Posted: Mon Jun 26, 2017 2:19 pm Post subject: Re: 2035

Padawan

Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand

JPN wrote:

Have you tried a lower case mqm?
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software

JPN

Posted: Mon Jun 26, 2017 10:17 pm Post subject: 2035

Novice

Joined: 27 Feb 2015
Posts: 14

dis chlauth(SYSTEM.DEF.SVRCONN) type(all) match(runcheck) ADDRESS('10.194.133.79') clntuser('mqm')
3 : dis chlauth(SYSTEM.DEF.SVRCONN) type(all) match(runcheck) ADDRESS('10.194.133.79') clntuser('mqm')
AMQ9783: Channel will run using MCAUSER('mqm').

Yes, mqm was set in both the cases and currently it is running as lower case 'mqm'

hughson

Posted: Tue Jun 27, 2017 1:50 am Post subject: Re: 2035

Padawan

Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand

JPN wrote:

mqm was set in both the cases and currently it is running as lower case 'mqm'

Does that mean your problem is now solved? If not could you let us know what is left to solve?
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software

fjb_saper

Posted: Tue Jun 27, 2017 5:10 am Post subject: Re: 2035

Grand High Poobah

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

JPN wrote:

If we've said it once, or a hundred times it still seems not to make it... DON'T USE A SYSTEM CHANNEL for this. Create your own channel and use that...

_________________
MQ & Broker admin

JPN

Posted: Tue Jun 27, 2017 5:29 am Post subject: 2035

Novice

Joined: 27 Feb 2015
Posts: 14

The problem is not solved. I am still having the message on the error log as mentioned above.

Is it possible that if I disable the CHLAUTH then I will not have any issue related to channel?

Tried convincing them to use another channel which is defined for them but they have hardcoded and so do not want to change it.

Vitor

Posted: Tue Jun 27, 2017 5:47 am Post subject: Re: 2035

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

JPN wrote:

Is it possible that if I disable the CHLAUTH then I will not have any issue related to channel?

Yes. If you remove all the security, you'll have no security problems logging on. Nor will the Russian mafia or the North Koreans...

JPN wrote:

Tried convincing them to use another channel which is defined for them but they have hardcoded and so do not want to change it.

Try harder. It was a bad idea when they hardcoded it originally, it's a worse idea now with channel authority.

In terms of code change, this is not the most invasive, risky or hard to test change they could make. At least get them to admit the reason they don't want to change it is that they've no idea where the correct version of the source code is....
_________________
Honesty is the best policy.
Insanity is the best defence.

hughson

Posted: Tue Jun 27, 2017 3:32 pm Post subject: Re: 2035

Padawan

Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand

JPN wrote:

The problem is not solved. I am still having the message on the error log as mentioned above.

So you are still have the error message that indicates that the NOAUTH user ID does not exist?

JPN wrote:

Is the above error message that you are still getting, as a result of something connecting over this channel that you say is now running with the user id 'mqm'?

JPN wrote:

Sorry to ask all these questions, but in order to help you specifically, rather than just give general advise such as "don't use SYSTEM.DEF.SVRCONN" and don't use "mqm" as a user id for client connections, we have to be clear on what your problem is. If you want to repeat your question as it currently stands (if my interpretation in this post is not accurate) please do that. It will get us all back on the same page. Please be clear also on what happened that you didn't want to happen, and what you want to happen instead. Provide us with more information such as your CHLAUTH rules if you are using them, and your SVRCONN definition in question. I believe you are setting the MCAUSER on the SVRCONN channel but I'm not sure you ever told us that explicitly.

JPN wrote:

Is it possible that if I disable the CHLAUTH then I will not have any issue related to channel?

Nothing that you have shown us suggests that you have any CHLAUTH interaction here? If you have CHLAUTH rules in place that set MCAUSER ids, you should include that information in the question. It is but a quick check that you could do to answer your own question in this case. But I suspect it has nothing to do with CHLAUTH.

Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software

bruce2359

Posted: Tue Jun 27, 2017 5:00 pm Post subject:

Poobah

Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.

We're you running IMQ 8004 on Solaris, too? With the same CHLAUTH records?

Does the channel work at all for any app?

Any channel exits?

Is the app Java/JMS asserting username/password?

A quick test to exclude CHLAUTH as the issue: disable CHLAUTH briefly, and try the app.

how does the app assert channel name? How is it 'hard coded?'
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » mqrc 2035

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