| Author |
Message
|
| sarathmattam |
 Posted: Fri Jun 25, 2010 11:18 pm Post subject: ERROR: information for "mqsi60" was not found |
 |
|
Voyager
Joined: 05 Sep 2008
Posts: 94
|
Dear All,
I am getting the below exception in "stderr".
2010-06-24 04:46:23.148431 Execution group started. UUID is: '1032d8de-2101-0000-0080-c5b87e01a290'. Broker is: PRD1.GEN.BRK
ERROR: information for "mqsi60" was not found. This results in loosing the Subscription requests registered to this broker.
I searched for the above error description but couldn't find much useful info ..
Regards,
Sarath |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Sat Jun 26, 2010 11:07 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Is that the full and complete text of the message in the syslog?
If so, then you must be running version 5.0 or earlier, as version 6.0 and later always puts the version number in the messages written out to the syslog. |
|
| Back to top |
|
|
| sarathmattam |
| Posted: Sat Jun 26, 2010 9:27 pm Post subject: |
|
|
Voyager
Joined: 05 Sep 2008
Posts: 94
|
Dear Jeff,
I got this log from /var/mqsi/components/PRD1.GEN.BRK/1032d8de-2101-0000-0080-c5b87e01a290/stderr. Similarly, i can find an update in
/var/mqsi/components/PRD1.GEN.BRK/1032d8de-2101-0000-0080-c5b87e01a290/stdout
2010-06-24 04:46:23.148431 Execution group started. UUID is: '1032d8de-2101-0000-0080-c5b87e01a290'. Broker is: PRD1.GEN.BRK
There are no other entries in logs ..
Regards,
sarath |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Jun 27, 2010 3:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
stdout and stderr are not the syslog.
Ignore them unless directed to review them by IBM Support.
Use the syslog. |
|
| Back to top |
|
|
| sarathmattam |
| Posted: Mon Jul 05, 2010 11:00 pm Post subject: |
|
|
Voyager
Joined: 05 Sep 2008
Posts: 94
|
Dear Jeff,
In our environment, the syslog is diverted ti /var/adm/messages. I cant find any updates in this log at the time of EG restarts.
is there any other logs apart from this ??
Regards,
Sarath |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jul 06, 2010 1:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If there are no messages in the syslog when you start the EG, and there are no messages in the syslog when you "lose a subscription request", then you need to do something more to troubleshoot.
Like explain the actual issue.
The message about " information for "mqsi60" was not found" is not anything I've ever seen before, and I don't think it represents an actual problem - but again I've never seen it before so I don't know.
There are bunch of reasons why subscription requests might get lost, but it's hard to tell from what you've said which is likely. |
|
| Back to top |
|
|
| sarathmattam |
| Posted: Tue Jul 06, 2010 1:40 pm Post subject: |
|
|
Voyager
Joined: 05 Sep 2008
Posts: 94
|
Dear Jeff,
Losing subscriptions is the second part. I had posted a query on the same before here, but i didnt get a proper reply for that query ..
Actually i am working in Solaris Env with Sun Cluster. We have 2 servers in place which are acts on a Active - passive mode and the sun cluster takes care of the high availability.
In Production server where i have the cluster, When i register a subscription request, i can find the same in BSUBSCRIPTIONS tables of my Broker DB, but the message flows will work fine. But in other environments where i dont have cluster i can see all the subscriptions in Table and is still available even after the restart of the server itself ..
As i was not able to find out the root cause of that issue, we have developed shell scripts to post subscriptions in case of cluster switch. But, off late the EG restarts also results in losing subscriptions. Now i am trying to find out the root cause of EG restarts.
Kindly let me know what details do you need. Apart from the afore mentioned ones, i dont have any logs
Regards,
Sarath |
|
| Back to top |
|
|
| sarathmattam |
| Posted: Sun Apr 01, 2012 12:29 am Post subject: |
|
|
Voyager
Joined: 05 Sep 2008
Posts: 94
|
Dear All,
Can anybody give a suggestion about the topic mentioned above. Am getting another error and i assume the issue is related to the restart of EG. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Apr 01, 2012 5:22 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sarathmattam wrote: |
| Can anybody give a suggestion about the topic mentioned above. |
If no-one's posted in nearly 2 years, no-one's going to post now.
| sarathmattam wrote: |
| Am getting another error |
Do you mean url]this? Because that doesn't sound like the same situation.
| sarathmattam wrote: |
| i assume the issue is related to the restart of EG. |
How did you arrive at that assumption? And what restart? You don't mention that in either thread.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Apr 01, 2012 10:52 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| sarathmattam wrote: |
Dear All,
Can anybody give a suggestion about the topic mentioned above. Am getting another error and i assume the issue is related to the restart of EG. |
The assumption might be wrong. It may only show up as a side effect of the restart of an e.g... Is there anything in the logs about the broker may be not being able to reconnect to its database? If so, that is the first problem you need to fix...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
