| Author |
Message
|
| tomsal |
 Posted: Wed Feb 19, 2003 6:01 pm Post subject: Error FMC00014E while running fmcautil |
 |
|
Newbie
Joined: 10 Oct 2002
Posts: 9
|
We are using WorkFlow on Solaris 2.8 and started the fmcamain without problems.
But when atempting to start the fmcautil the response from the server is always the error FMC00014E (Timeout).
This happens in both cases, from the server and from the client!!!!
We've already done the configuration of the mqclient and the workflow client. The mqclient is working fine.
Any toughts????
The actual output in the server is:
$ fmcautil -f -uADMIN -ppassword
- FMC16006I Administration Utility started.
System group name : [FMCGRP] FMCGRP
System name : [FMCSYS] FMCSYS
Userid : [ADMIN] ADMIN
Password : [********] ********
- FMC00014E Timeout occurred
- FMC16302I Not connected to any system.
FMC15010I Main Menu:
s ... System Commands Menu
x ... Exit Main Menu
The workfolw version is 3.3.2 and the Mq version is 5.2.0 on solaris 2.8 with db2 7.2 Fixpack 8.
Thanks in advance!!!! |
|
| Back to top |
|
 |
| vennela |
| Posted: Thu Feb 20, 2003 6:25 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
If you can't get the admin utility to work from the server then I don't think your admin server is started.
Do you see the fmcamain process?
-------
Venny |
|
| Back to top |
|
|
| tomsal |
| Posted: Thu Feb 20, 2003 4:18 pm Post subject: |
|
|
Newbie
Joined: 10 Oct 2002
Posts: 9
|
Thanks Venny.
The detail is teh next one.
When I start the task fmcamain the prompt indicates thet the server is running.
But I've found that a FDC file was generated by the fmcamain and thus killing the process of the fmcamain.
We reported this to IBM because it seems to be a big issue with Solaris and WorkFlow.
This is the actual output from the FDC file.
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Wednesday February 12 12:07:52 CST 2003 |
| Host Name :- gnpdomc (SunOS 5. |
| PIDS :- 5765B75 |
| LVLS :- 520 |
| Product Long Name :- MQSeries for Sun Solaris 2 (Sparc) |
| Vendor :- IBM |
| Probe Id :- XC130003 |
| Application Name :- MQM |
| Component :- xehExceptionHandler |
| Build Date :- Aug 1 2002 |
| CMVC level :- p520-CSD05G |
| Build Type :- IKAP - (Production) |
| UserID :- 00000107 (fmc) |
| Program Name :- fmcamain |
| Process :- 00009576 |
| Thread :- 00000001 |
| QueueManager :- FMCQM |
| Major Errorcode :- STOP |
| Minor Errorcode :- OK |
| Probe Type :- HALT6109 |
| Probe Severity :- 1 |
| Probe Description :- AMQ6109: An internal MQSeries error has occurred. |
| Arith1 :- 11 b |
| |
+-----------------------------------------------------------------------------+
Thanks in advance |
|
| Back to top |
|
|
| clindsey |
| Posted: Fri Feb 21, 2003 7:46 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
I believe you have hit a problem with the signal handler code in Workflow.
A good workaround is to set tracing to simple mode which changes the
behavior of the signal handler and circumvents this problem. A fix will come out soon in a servicepac, but in the meantime, issue this command:
fmczchk -c inst:m,FMC_SIMPLE_TRACE_ONLY,YES -y <configid>
Note: this does not turn trace on so there is no additional overhead.
Hope this helps,
Charlie |
|
| Back to top |
|
|
| tomsal |
| Posted: Tue Feb 25, 2003 8:54 am Post subject: |
|
|
Newbie
Joined: 10 Oct 2002
Posts: 9
|
Thanks a lot Clindsey and Venny!!!
The problem is now solved.
Could you refer more en this trouble so I can explain it to my customer, please.
Thanks again. |
|
| Back to top |
|
|
| clindsey |
| Posted: Wed Feb 26, 2003 6:43 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
Tomsal,
This problem is fixed in ServicePac 4 which is now available. Here is the detail line from the fix list:
17832 - Internal Signal handler problems prevent servers from starting on UNIX platforms |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Jun 11, 2003 10:05 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Charlie:
I am having a similar FDC. The only difference is this FDC is being cut by fmcemain process. I am at the latest maintenance level SP4. The Workflow server runs fine for a while and then crashes?
Is it a bug, do you think?
Do you think we need to open a PMR.
I have posted the FDC in this thread.
I have also tried this on an SP3 box
fmczchk -c inst:m,FMC_SIMPLE_TRACE_ONLY,YES -y <configid>
I don't think it worked.
That's when SP4 was applied but the problem still persists.
Thanks
-------
Venny |
|
| Back to top |
|
|
|
|
