|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Translate Execution Group GUUID to Actual Name |
« View previous topic :: View next topic » |
Author |
Message
|
neWMBGuy |
Posted: Wed Dec 12, 2012 8:36 am Post subject: Translate Execution Group GUUID to Actual Name |
|
|
Novice
Joined: 01 Aug 2012 Posts: 19
|
hey All,
WMB 8.0.0.1 on linux.
under execution logs folder i see several folders with long gUIID.
1022b251-3b01-0000-0080-9007ac9f5b4a
ae00622c-3a01-0000-0080-b451f4334b66
is there a way to easy translate what GUIID corresponds to the correct Execution group which are defined in readable english like
EAI1,SERVICES1 etc etc
any help is appreciated.
K |
|
Back to top |
|
 |
JosephGramig |
Posted: Wed Dec 12, 2012 8:50 am Post subject: |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
Well,
ps -ef|grep Data
Will give you a list of the DFEs and their UIDs. Then you can figure it out. |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Dec 12, 2012 9:07 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
There is no folder called 'execution logs'.
There are a few different places where Broker stores *internal* *binary* log files that are ONLY to be processed using MQSIREADLOG.
Broker will use either console.txt or stdout and stderr files on a per execution group basis. But you should really only be looking at these if it is *strictly* necessary, you should not be treating them as a source of general purpose information.
You should be looking at the SYSTEM LOG for all relevant Broker data about the general purpose state of the Broker and each EG.
This will, among other things, usually provide you with information about what EG is having the problem and what the UUID of that EG is.
OR if you have specific troubleshooting requirements, you should be using MQSIREADLOG to extract the TRACE data. This will also tell you the UUID of a given EG and allow you to find the relevant other files if you *absolutely* need them.
Don't just randomly decide to monitor files under the Broker file system. It will only distract and can impede or impact your troubleshooting or production environment. |
|
Back to top |
|
 |
JosephGramig |
Posted: Wed Dec 12, 2012 12:01 pm Post subject: |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
@neWMBGuy
Well, I did jump to the conclusion you were looking for stderr and stdout in /var/mqsi/components/<BrokerName>/<UUID>
You could also read this.
In the past, I've found this very valuable. |
|
Back to top |
|
 |
neWMBGuy |
Posted: Wed Dec 12, 2012 12:37 pm Post subject: |
|
|
Novice
Joined: 01 Aug 2012 Posts: 19
|
Thanks JosephGramig. thats exactly what i was looking for. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|