|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Generation of the fmcerr.log file |
« View previous topic :: View next topic » |
Author |
Message
|
praveenchhangani |
Posted: Wed Jun 11, 2003 12:50 pm Post subject: Generation of the fmcerr.log file |
|
|
 Disciple
Joined: 20 Sep 2002 Posts: 192 Location: Chicago, IL
|
Folks,
Have any of you ever ran into a situation whereby the your execution servers were stopping and starting every few minutes for like say a 30 minute interval.
I recently ran into the above issue, but when I thought of checking the log files, I only saw an fmcsys.log. There was no fmcerr.log surprisingly even despite the fact that the fmcsys.log file was reporting stopping and starting of execution servers (abnormally 3 times, and the 4th time they came down "with an error").
How am I supposed to diagnose this problem when there is nothing to work with. I was wondering if anyone here had ever experienced this issue and/or if they might know what;s going on here...
Thanks, Praveen _________________ Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
Back to top |
|
 |
vennela |
Posted: Wed Jun 11, 2003 12:59 pm Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
I am sure there are some error messages in fmcsys.log. They should be enough to start with. But usually fmcerr.log messages are more verbose and more detailed. But fmcsys.log messages should serve the purpose as well
-------
Venny |
|
Back to top |
|
 |
praveenchhangani |
Posted: Wed Jun 11, 2003 1:14 pm Post subject: |
|
|
 Disciple
Joined: 20 Sep 2002 Posts: 192 Location: Chicago, IL
|
Usually that's the case. One is able to gather a rather sufficient amnt if info, but in this case, I'm not sure how I am where exactly the problem lies....
Here's a snippet
Code: |
06/09/03 13:42:17 FMC12240E Execution server instance(s) stopped with an error.
06/09/03 13:42:18 FMC10500I Execution server instance started.
06/09/03 13:42:18 FMC10500I Execution server instance started.
06/09/03 13:42:18 FMC10500I Execution server instance started.
06/09/03 13:42:18 FMC10500I Execution server instance started.
06/09/03 13:42:18 FMC10500I Execution server instance started.
06/09/03 13:42:18 FMC10500I Execution server instance started.
06/09/03 13:42:18 FMC10500I Execution server instance started.
06/09/03 13:42:18 FMC10500I Execution server instance started. |
Code: |
06/09/03 13:44:17 FMC12250E The execution server for system FMCSYS2 stopped abnormally.
06/09/03 13:44:18 FMC10500I Execution server instance started.
06/09/03 13:44:18 FMC10500I Execution server instance started.
06/09/03 13:44:18 FMC10500I Execution server instance started.
06/09/03 13:44:18 FMC10500I Execution server instance started.
06/09/03 13:44:18 FMC10500I Execution server instance started.
06/09/03 13:44:19 FMC10500I Execution server instance started.
06/09/03 13:44:19 FMC10500I Execution server instance started.
06/09/03 13:44:19 FMC10500I Execution server instance started.
06/09/03 13:44:19 FMC10500I Execution server instance started.
06/09/03 13:44:19 FMC10500I Execution server instance started. |
I will say that what else that is contained in the sys file is a WHOLE bunch of system messages such as ...
activity afsdf sfkasfd not set...
connector afasfasffs not set...
Could this be our problem? _________________ Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
Back to top |
|
 |
vennela |
Posted: Wed Jun 11, 2003 1:24 pm Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
I think your admin server is running OK but for some reason, the execution server is failing as soon as it is started. admin server finds that there is no execution server and it is trying to restart it. That's the reason you are getting those messages. But why there are no errors, I am not sure.
If you try to login using fmcautil, it will keep spitting those messages, but you can stop the two instances of the exec server, then admin server will not restart them. Then try to see if there are error messages that admin utility can show you.
Any FDCs ?
Anything from db2diag.log? |
|
Back to top |
|
 |
Andy |
Posted: Sun Jun 15, 2003 2:24 am Post subject: |
|
|
 Centurion
Joined: 14 May 2003 Posts: 122
|
vennela wrote: |
If you try to login using fmcautil, it will keep spitting those messages, but you can stop the two instances of the exec server, then admin server will not restart them. |
You mean to say that we can keep Execution Server running and can stop all the instances. I just tried to see what happens in this case, it gives error:
"FMC12390E Request ignored because at least one instance must remain running."
Did I understand something wrong?  _________________
Andy |
|
Back to top |
|
 |
jmac |
Posted: Sun Jun 15, 2003 4:48 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
Andy wrote: |
You mean to say that we can keep Execution Server running and can stop all the instances. I just tried to see what happens in this case, it gives error:
"FMC12390E Request ignored because at least one instance must remain running."
Did I understand something wrong?  |
It is my opinion that you can never stop the last Execution Server with fmcautil. So what you are seeing is normal behaviour _________________ John McDonald
RETIRED |
|
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
|
|
|
|