| Author |
Message
|
| mhubbard |
 Posted: Wed May 02, 2007 9:19 am Post subject: AMQ7047 with dspmqver after install of 6.0 |
 |
|
Acolyte
Joined: 25 Aug 2004
Posts: 54
|
Hello - My setup is a little different, but please hear me out. I am running on debian linux with their newest stable release called etch. I have a great deal of MQ 5.3 in house now and I wanted to test out MQ 6.0 on these new servers. I initially downloaded the trial version and got it installed. (I convert the rpm's to debian packages with a tool called alien). This worked beautifully. I was connected to the rest of my MQ stuff within an hour. It was the easiest install I had ever done with MQ.
Next it came time to get the real licensed version. This doesn't seem to come in a "all in one chunk" version. (The trial version came with a set of packages that were 6.0.2). With the "real" software, it seems you have to get the base 6.0.0 package and then the 6.0.2 fixpack.
The problem I am having is that after installing the 6.0.0 package that I created in exactly the same way I had done it from the trial, I get this contact admin message when /opt/mqm/bin/dspmqver is run:
etch:/opt/mqm/bin# ./dspmqver
AMQ7047: An unexpected error was encountered by a command.
AMQ6090: WebSphere MQ was unable to display an error message 40806106.
Usage: dspmqver [-p Components] [-f Fields] [-b] [-v]
I discovered this because my fix pack package refused to install saying that it did not match the current version of MQ on the machine. Research into the installation procedure led me to see that the install script was trying to run this dspmqver program and it could not.
All my permissions look good as far as I can tell. /var/mqm is owned by mqm:mqm
Any ideas?
_________________
Michael J. Hubbard |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed May 02, 2007 9:25 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| mhubbard |
| Posted: Wed May 02, 2007 10:16 am Post subject: |
|
|
Acolyte
Joined: 25 Aug 2004
Posts: 54
|
Well - we have been running debian in production (and Websphere MQ 5.3 on it) for coming up on 2 years now. I have had no complaints.
Even the 6.0 client code ran perfectly (from the trial version).
_________________
Michael J. Hubbard |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed May 02, 2007 11:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Well, you've been running on an unsupported platform for coming up on 2 years now. That's your choice, but it's one I wouldn't make.
Unless v5.x was supported on Debian - which I don't remember it being.
The symptoms you are describing seem to indicate that the base MQ install has issues (read, is incompatible with) the version of glibc or the thread library you're using (NLTP, usually).
You may or may not be able to get around this. I don't know if you can do something to force the RPMs to install or not. One hack you could do is temporarily replace dspmqver with something that returned what was expected, or otherwise succeeded.
The RP2 of v6 included better support for different levels of glibc - or something like that - such that it works on newer levels. So if you *could* get it to install, it would likely do something useful.
Or you could look for the FDC that was likely thrown when dspmqver crashed, and try and troubleshoot that.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mhubbard |
| Posted: Wed May 02, 2007 11:50 am Post subject: |
|
|
Acolyte
Joined: 25 Aug 2004
Posts: 54
|
I take it the Trial version of the software magically comes statically linked to all the correct versions of the libraries or something? Of course not.
Thanks anyways.
_________________
Michael J. Hubbard |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed May 02, 2007 11:53 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The trial version is, presumably, a patched installer that is at the 6.0.2.0 level.
You might have luck downloading a new set of RPMS from IBM's website - they may have "refreshed" the installer since your disks were cut.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| BenR |
| Posted: Wed May 02, 2007 10:16 pm Post subject: |
|
|
Acolyte
Joined: 31 Jan 2006
Posts: 60
Location: Hursley, UK
|
Do you have any FDCs? If you can post it here (just the top bit) i'll tell you what failed, but threading is a common cause of these problems, see comments here
http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27007477
especially
| Quote: |
SUSE Linux Enterprise Server 9 has a Linux 2.6 kernel. This means the operating system includes the Native Linux Posix Thread Library (NPTL) threading implementation, which is NOT SUPPORTED by WebSphere MQ for Linux for Intel, V5.3. An environment variable is provided by the operating system to enable a LinuxThread threading implementation as required by WebSphere MQ. This environment variable is detailed in the release notes for SLES9, and must be set as follows for WebSphere MQ: LD_ASSUME_KERNEL=2.4.19
|
I know that's 5.3 on SLES, not 6.0 on Debian, but I assume the NPTL issue is the same? I'd expect to see something like
| Quote: |
| Program Name :- dspmq |
| Thread-Process :- 00008946 |
| ThreadingModel :- Unknown |
| Major Errorcode :- MQRC_ENVIRONMENT_ERROR |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ07DC |
| Probe Severity :- 4 |
| Probe Description :- AMQ6090: WebSphere MQ was unable to display an error |
| message 7DC. |
| FDCSequenceNumber :- 0 p |
And I would echo Jeff's comment about running on an unsupported platform. It's great that you've had no problems, but what do you do if your production system goes down and you need to raise a PMR? |
|
| Back to top |
|
|
| mhubbard |
| Posted: Thu May 03, 2007 3:26 am Post subject: |
|
|
Acolyte
Joined: 25 Aug 2004
Posts: 54
|
No FDC's.....but I got it. As we all could of guessed from the start, it was something I screwed up. I forgot to tell alien (the package converter) to include the scripts in the debian package it created. (I don't know why it is not the default behavior to create the scripts).
If we could not run under debian, then we would not have been able to use Websphere MQ. We have over 2000 devices in the field and we would have never tried to swap OS's. We run our MQ Servers on Red Hat so that we will have support there. All that we run on debian is the client side stuff and it has worked fine. As for support - everyone has there share of complaints, including me, but I have to speak up for IBM on this one....I have had to call several times and have never gotten the "We don't support that" answer. I've always done my best to make sure it wasn't an OS related issue before calling, but they have always been very helpful - especially when working with the GSK which gave me great struggles.
I've always gotten great help from this list and I truly appreciate it.
_________________
Michael J. Hubbard |
|
| Back to top |
|
|
|
|
