Author |
Message
|
karthik |
Posted: Wed Nov 19, 2003 3:37 pm Post subject: admin utility |
|
|
 Centurion
Joined: 17 Oct 2003 Posts: 114
|
Hi
I am trying to connect to my admin server using
fmcautil -y=FMC -u=fmc -p=password.
But the prompt stays there for a long time and gives a message as "timeout occured " finally.
Please help me in diagnosing what might be the problem in this case.
1)The user and password are already set in the database
2)The admin server is started
Thanks
karthik |
|
Back to top |
|
 |
Ratan |
Posted: Wed Nov 19, 2003 5:20 pm Post subject: |
|
|
 Grand Master
Joined: 18 Jul 2002 Posts: 1245
|
this means it is unable to comminicate with workflow server. Make sure your WF Server is running and your MQ communication fine. _________________ -Ratan |
|
Back to top |
|
 |
karthik |
Posted: Thu Nov 20, 2003 7:04 am Post subject: Thanks |
|
|
 Centurion
Joined: 17 Oct 2003 Posts: 114
|
Thanks ratan
Yup , i guess the workflow was started but i was ctl + c to comeout , which ws killing the server. I did everything right and this time everything is working fine.
Thanks
Karthik |
|
Back to top |
|
 |
karthik |
Posted: Thu Nov 20, 2003 7:45 am Post subject: Problem |
|
|
 Centurion
Joined: 17 Oct 2003 Posts: 114
|
I guess all that worked for the first time , and i could see the commands menu
I came out of the menu tried to connect again , the prompt was blinking and not connecting again.
I killed the processes and tried fresh again , but the next time i got the below messages
- FMC16006I Administration Utility started.
System group name : [FMCGRP] FMCGRP
System name : [FMCSYS] FMCSYS
Userid : [ADMIN] ADMIN
Password : []
- FMC00011E Already logged on to the system
- FMC16302I Not connected to any system.
FMC15010I Main Menu:
s ... System Commands Menu
x ... Exit Main Menu
s
FMC15040I System Commands Menu:
c ... Connect
w ... Wait
x ... Exit System Commands Menu
c
System group name : [FMCGRP]
System name : [FMCSYS]
Userid : [ADMIN] fmc
Password : []
- FMC00010E Unknown user ID
- FMC16302I Not connected to any system.
FMC15040I System Commands Menu:
c ... Connect
w ... Wait
x ... Exit System Commands Menu
c
System group name : [FMCGRP]
System name : [FMCSYS]
Userid : [ADMIN]
Password : []
- FMC00011E Already logged on to the system
- FMC16302I Not connected to any system.
FMC15040I System Commands Menu:
c ... Connect
w ... Wait
x ... Exit System Commands Menu
x
FMC15010I Main Menu:
s ... System Commands Menu
x ... Exit Main Menu
Please explain why its happening like this and what should i do to come out of such situations.
Thanks in advance
Karthik |
|
Back to top |
|
 |
jmac |
Posted: Thu Nov 20, 2003 7:52 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
Run fmcautil from a command prompt with the force option like this:
Code: |
fmcautil -uadmin -ppassword -f -y<configID> |
_________________ John McDonald
RETIRED |
|
Back to top |
|
 |
karthik |
Posted: Thu Nov 20, 2003 7:59 am Post subject: |
|
|
 Centurion
Joined: 17 Oct 2003 Posts: 114
|
I tried that option but did not work, the prompt stays there for a long time
after which i get a timeout error.
- FMC00014E Timeout occurred
- FMC16302I Not connected to any system.
FMC15010I Main Menu:
s ... System Commands Menu
x ... Exit Main Menu
What else could have been wrong.What other options have i got.
Thanks in advance
karthik |
|
Back to top |
|
 |
jmac |
Posted: Thu Nov 20, 2003 8:07 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
Your ADMIN server crashed... Is fmcautil running? OOPS
As vennala says... I MEANT fmcamain _________________ John McDonald
RETIRED
Last edited by jmac on Thu Nov 20, 2003 8:59 am; edited 1 time in total |
|
Back to top |
|
 |
vennela |
Posted: Thu Nov 20, 2003 8:56 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Check if fmcamain process is still running. You should check the workflow logs also. If that doesn't make sense to you post them here. |
|
Back to top |
|
 |
karthik |
Posted: Thu Nov 20, 2003 9:17 am Post subject: |
|
|
 Centurion
Joined: 17 Oct 2003 Posts: 114
|
Thanks all
I talked to the MQ people and they were recycling the queue managers. I guess that was the problem.
Actually i saw the errors in nohup.out file in the home directory ( i tried nohup for running the commands in back ground).Is this where i get the errors , because there were nothing in the fmcsys.log and fmcerr.log.
I donot know if i will see these errors in the QMGRS logs. And probably will not be able to find there because there will be thousands of errors in those logs.
I started the trigger monitor and started the server and everything works fine here.
Thanks again
karthik |
|
Back to top |
|
 |
vennela |
Posted: Thu Nov 20, 2003 9:39 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Quote: |
I talked to the MQ people and they were recycling the queue managers |
Make sure your MQ people know that workflow has to brought down before the workflow QMGR is shutdown. Also, workflow should be started after MQ is started. |
|
Back to top |
|
 |
|