| Author |
Message
|
| andrey.vasilevskiy |
 Posted: Tue Sep 20, 2011 2:09 am Post subject: |
 |
|
Newbie
Joined: 14 Sep 2011
Posts: 4
|
| mqjeff wrote: |
Are you sure it's the *same* problem, where the broker is unable to create a UUID?
Your RedHat is *broken* somehow. You need to *fix* your *RedHat*. And then *reinstall* both MQ and Broker, just to be sure. |
yes. It the same problem. But.
uuidget command (RED HAT related) exec successfully. here is an example
| Code: |
uuidgen
1ae71bc1-a322-4593-ad3d-2c50e29417d2
|
is this command use for uuid generating ? |
|
| Back to top |
|
 |
| andrey.vasilevskiy |
| Posted: Tue Sep 20, 2011 3:29 am Post subject: |
|
|
Newbie
Joined: 14 Sep 2011
Posts: 4
|
| I determine that i use 32-bit MQ on my 64 RHEL. can be a problem with this? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 20, 2011 4:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| andrey.vasilevskiy wrote: |
| I determine that i use 32-bit MQ on my 64 RHEL. can be a problem with this? |
Yes.
Use the 64bit version. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Sep 20, 2011 4:24 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Remember to follow explicitly the step-by-step instructions in Chapter 6 of the installation guide **before** you copy any files to your server. If you don't you will have more problems.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Qadeer_824 |
| Posted: Sun May 13, 2012 6:08 am Post subject: |
|
|
Acolyte
Joined: 04 Oct 2007
Posts: 59
|
I had the same problem and resolved it by installing the MQ Global Security kit which i believe contains the cryptography packages required for generating UUID..
I also edited the /etc/hosts file at the same time before rebooting the server. Its' one of the above 2 changes that resolved the issue. My bet is on the first part.. I will check by back-tracking one by one to see what happens..! 
Thanks,
Qadeer |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Sun May 13, 2012 10:09 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Qadeer_824 wrote: |
I had the same problem and resolved it by installing the MQ Global Security kit which i believe contains the cryptography packages required for generating UUID..
I also edited the /etc/hosts file at the same time before rebooting the server. Its' one of the above 2 changes that resolved the issue. My bet is on the first part.. I will check by back-tracking one by one to see what happens..!
Thanks,
Qadeer |
Not and not.
UUID is a standard Java runtime extension and has nothing to do with MGS.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| sgies |
| Posted: Fri Dec 13, 2013 1:20 pm Post subject: |
|
|
Newbie
Joined: 30 Jan 2009
Posts: 3
Location: Seattle
|
| I just ran into this same issue on a newly create RHEL 6 linux install in our lab environment. I was unable to use an broker commands that required connecting to the queue manager (e.g. mqsilist, mqsicreateexecutiongroup). Updating the \etc\hosts file resolved the issue. (The linux admin forgot to do this.) We did reboot the server after the update. Don't know if that was required. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Dec 13, 2013 10:41 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Would you care to share the change you made to your hosts file with the rest of us?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| sgies |
| Posted: Mon Dec 16, 2013 10:35 am Post subject: |
|
|
Newbie
Joined: 30 Jan 2009
Posts: 3
Location: Seattle
|
I just added the server's ip into the host file. For example:
111.22.33.44 myservername
You can also get this error if you have a mis-match between the hostname (as set in /etc/sysconfig/network) and the name specified in the /etc/hosts file.
A simple test to determine if your configuration is incorrect is to run the commands:
hostname - this should return the expected hostname
ping $(hostname) - this should start pinging the local interface
If the ping fails, double-check your settings.
** edited to add a few more details to help others in need ** |
|
| Back to top |
|
|
|
|
