- This topic has 2 replies, 3 voices, and was last updated 19 years, 2 months ago by
.
-
Topic
-
We have a process that will not start. We began having problems with it about a week ago. Anyone that might have seen such an error and has any ideas to resolve it, advice would be appreciated. So far we have rebooted the server, done a site cleanup, and changed the process name. When you try to start it you get the following:
[cmd :cmd :ERR /0:recvfromtest2_cmd] Initialization of DBI failed
07/26/2005 14:55:44
[prod:prod:ERR /0:recvfromtest2_cmd] Unable to initialize the Command Thread.
PANIC: “0”
PANIC: Calling “pti” for thread recvfromtest2_cmd
Scheduler State
Thread Events State Priority Runnable PT Msgs
0 0 SCHED_IDLE 0 0 0,0,0
Thread 0
ti: 0x402feda8
tid : 0
HostPthreadId : 0x00000001
EventList : 0x40075b08
PolledEvents : 0x40075b50
PthreadEvent : 0x40080808
ReadyEvents : 0x40075b68
CtrlMsgs : 0x40075b80
UserCtrlMsgs : 0x40075b98
UserDataMsgs : 0x40075bb0
StartArgs : 0x00000000
SchedState : SCHED_IDLE
SchedPriority : 0
Killed : 0
Registered Events
el: 0x40075b08
elCount : 1
elHead: 0x4007fc70
elTail: 0x4007fc70
ele: 0x4007fc70
event: 0x40080808
prev : 0x0
next : 0x0
ev: 0x40080808
evType : PTHREADS
evStrDesc :
evSocket : 0
evMsgQue : 0
evTid : 0
evState : 0
evPtMsg : 0x0
evUserData : 0x0
evCallBack : 0x0
evCbShutdown : 0x0
evRecurFreq :
Polled Events
el: 0x40075b50
elCount : 0
elHead: 0x00000000
elTail: 0x00000000
Ready Events
el: 0x40075b68
elCount : 0
elHead: 0x00000000
elTail: 0x00000000
Outstanding Pthread Ctrl Msgs
pmq: 0x40075b80
Count : 0
Head : 0x00000000
Tail : 0x00000000
Outstanding Pthread User Ctrl Msgs
pmq: 0x40075b98
Count : 0
Head : 0x00000000
Tail : 0x00000000
Outstanding Pthread User Data Msgs
pmq: 0x40075bb0
Count : 0
Head : 0x00000000
Tail : 0x00000000
PANIC: Process panic—engine going down
PANIC: assertion ‘0’ failed at main.cpp/236
-
Replies
-
-
You may need to run database cleanup including reinitializing your databases for the particular site where this is occurring. Make sure that your recovery database is clear and any errors in the error database have been handled before doing this. You also need to shut down all processes. There may be less drastic measures you can take but in the rare instances I have seen this error I have had to schedule interface downtime, bring all processes in the site down, reinitialize the databases, and restart threads. I additionally clear vista.taf, monitorShmemFile, sem files, etc which are not critical but are good to do. I have steps to do this that I can send you if you want to reply with your e-mail address. -
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
