| Author |
Message
|
| MaheshPN |
 Posted: Thu Nov 06, 2003 9:46 am Post subject: Admin server is going down |
 |
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Hi Guys,
I am facing a weird problem on AIX box. From today, when I start the workflow server, the admin server will be up and running for 4min. After that it will die!! I don't see any errors in fmcsys.log and fmcerr.log.
All the other servers(execution and scheduling) server are still running!!!
I cannot log in to WF after 4min. If I restart the wf server, it will exist for another 4 min.
Does anybody faced this kind of problem?. I am guessing, is there any security issue?
Thanks in advance,
-Mahesh |
|
| Back to top |
|
 |
| vennela |
| Posted: Thu Nov 06, 2003 10:01 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Did you apply maintenance and did not do the DB rebinds?
It also helps if you tell the versions of MQ and Workflow.
You should also see the MQ error logs... any FDCs cut etc.
Are you shutting down all the servers (exec sch etc) before bringing the server back or are you just starting an fmcamain. If you haven't already tried, shutown workflow completely, run fmcclean and slibclean and restart the server.
Also, if you keep the workflow admin utility running, see if there are any messages when the workflow server dies.
Last edited by vennela on Thu Nov 06, 2003 10:02 am; edited 1 time in total |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Nov 06, 2003 10:02 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Mahesh:
Never seen anything exactly like this... but be sure you fire up fmcautil "Admin Utility" as soon as the admin server startes, and list the contents of the System Log and Error logs (before your 4 minutes is up  )... some messages are not written to the flat files only to the tables, and vice versa... so its always a good idea to look at both places.
GOOD LUCK... keep us posted on this one
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| manoj |
| Posted: Thu Nov 06, 2003 10:27 am Post subject: |
|
|
Master
Joined: 30 Jan 2002
Posts: 237
Location: Virgina
|
Mahesh,
Do u remember u killed the fmcamain unix process?
or was there any unexpected system failure/crash before
u start experiencing this problem ??
_________________
-manoj |
|
| Back to top |
|
|
| MaheshPN |
| Posted: Thu Nov 06, 2003 10:39 am Post subject: |
|
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Thanks guys,
MQ Error log shows,
11/06/03 12:18:50
AMQ9206: Error sending data to host d507839 (172.27.18.208).
EXPLANATION:
An error occurred sending data over TCP/IP to d507839 (172.27.18.208). This may
be due to a communications failure.
ACTION:
The return code from the TCP/IP(write) call was 32 X('20'). Record these values
and tell your systems administrator.
Keeping the Admin utility running, did put some error in fmcsys.
11/06/03 13:30:52 FMC31050E An error has occurred which has terminated processin
g.
11/06/03 13:30:52 FmcAssertionException, Condition=*** Assertion failed in /proj
ects/fmc/drvp/lbld/v340/aix/src/fmckdynp.cxx(149): ptr != 0[o5adw002] fmc /var/f
I have not yet ran fmcclean and slibclean. Does it break the existing stuff?
I am runnin on unix 5.1, wf 3.4 fixpac 2, db2 7.2
all were running till yesterday!!!!
Thanks,
-Mahesh |
|
| Back to top |
|
|
| Ratan |
| Posted: Thu Nov 06, 2003 11:24 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
d507839 (172.27.18.208) is this your Db2 server?
_________________
-Ratan |
|
| Back to top |
|
|
| praveenchhangani |
| Posted: Thu Nov 06, 2003 12:58 pm Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
I had run into the same exact issue recently on our pilot system. However the difference in mycase what that I was upgrading from wf 3.3.2 to wf3.4 on aix and applying the sp2.
Turns out, some of the configurations came up and were running and others would run for approximately the same time that is indicated in your message, and then the configurations would come down. Not only that, but when I tried to sign in using the webclient I kept getting an "Internal error" message.
Here what was done to fix it: Installing WF3.4 with SP2 alone didn't do the job so, the HyperFix was installed and once that was done, the admin server and all configs would stay up.
Certainly your db2 reorgs and rebinds etc would help, but I think the admin server coming down after 4 minutes or so is a fundamental problem and has to do with either a change (ie. upgrade) or like space issues relating to both the hard drives and database instances.
Like I said the above is what we had to go through to fix this, but I can relate to this problem very well because even my fmcsys.log and fmcerr.log files were not populated with any error messages.
What other processes are being affected on this box? Is this something that just started? Have there been any changes that may have affected this? Are you performing daily db maintenance?
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
|
| karthik |
| Posted: Thu Nov 06, 2003 1:07 pm Post subject: |
|
|
Centurion
Joined: 17 Oct 2003
Posts: 114
|
In Between
Can i get the link where i can get this Hyperfix for db2
Thanks in advance
Karthik |
|
| Back to top |
|
|
| Prahasith |
| Posted: Thu Nov 06, 2003 1:41 pm Post subject: |
|
|
Disciple
Joined: 16 May 2003
Posts: 184
Location: Kansas City
|
|
| Back to top |
|
|
| MaheshPN |
| Posted: Thu Nov 06, 2003 1:43 pm Post subject: |
|
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Thanks guys,
It is working!!!!!
Solution : Applied MQ Support Pac 5 and Wofkflow FixPac 3
-Mahesh |
|
| Back to top |
|
|
| praveenchhangani |
| Posted: Thu Nov 06, 2003 2:24 pm Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
Excellent. Glad it worked out!
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
|
|
|
