Page 1 of 1
CDA Server Process
Posted: Thu Jul 20, 2006 8:57 am
by jillrae
I have the following entry in from the omshowlog command:
WARNING IMAP Server Da(IMAP Server Pr) 07.20.06 08:07:16
[OM.DMON 2108] Maximum IMAP connection rate exceeded, sleeping.
SERIOUS ERROR CDA Server (CDA Server ) 07.20.06 08:30:01
[OM 28664] There is already a CDA server process running
-> aud_GetSetLogConfig
<- aud_GetSetLogConfig
-> cda_DaemonMain
-> ccs_DoInitTables
-> ccs_AttemptSMem
<- ccs_AttemptSMem
<- ccs_DoInitTables
-> cvc_IsMappingAvail2
-> uni_GetCharset
-> cvc_IsMappingAvail3
-> cvc_AttemptSMem
<- cvc_AttemptSMem
<- cvc_IsMappingAvail3
<- uni_GetCharset
<- cvc_IsMappingAvail2
<- /build/10.0.0.175/src/bin/cda/cda_daemon.c:799[205,28664]
What does it means and how do I fix it?
Help
jillrae
Posted: Thu Jul 20, 2006 9:37 am
by ScalixSupport
Because the CDA server aborted, it left a lock file called /var/opt/scalix/sys/omcda.lock.
Remove this file and restart the CDA service.
Cheers
Dave
Posted: Thu Jul 20, 2006 9:49 am
by jillrae
Thank you
jillrae
Posted: Sat Aug 05, 2006 9:38 am
by joaster
Hi, I have the same error.
My question is; how do you restart a seperate Scalix service without restarting all Scalix services?
Regards, Joost.
Posted: Sat Aug 05, 2006 11:59 am
by dkelly
Please look at the man pages for omon and omoff.
Cheers
Dave
Posted: Sat Aug 05, 2006 12:51 pm
by joaster
Thanks for the hint
Joost
Posted: Thu Sep 28, 2006 6:44 pm
by mhtrim
I'm getting this same error. And, sure, if I remove the lock file and restart the service with omon or the admin web interface it will start up again just fine.
But the CDA service is dying at least once a day and I'd rather know why it's crashing all the time instead of scripting something to watch the process, wait for it to die, remove the lock file and restart the service.
How can I tell what's really going on here and what can I do to fix it so the service stays up?
Here are the log snips from today:
---------------------------------------------------------------------------------
REPORT CDA Server (CDA Server ) 09.28.06 07:45:47
[OM 28658] CDA server starting up
REPORT CDA Server (CDA Server ) 09.28.06 07:45:47
[OM 28670] CDA Server using Directory change logs to optimise builds.
SERIOUS ERROR CDA Server (CDA Server ) 09.28.06 15:44:30
[OM 28664] There is already a CDA server process running
-> aud_GetSetLogConfig
<- aud_GetSetLogConfig
-> cda_DaemonMain
-> ccs_DoInitTables
-> ccs_AttemptSMem
<- ccs_AttemptSMem
<- ccs_DoInitTables
-> cvc_IsMappingAvail2
-> uni_GetCharset
-> cvc_IsMappingAvail3
-> cvc_AttemptSMem
<- cvc_AttemptSMem
<- cvc_IsMappingAvail3
<- uni_GetCharset
<- cvc_IsMappingAvail2
<- /build/10.0.1.3/src/bin/cda/cda_daemon.c:799[205,28664]
SERIOUS ERROR CDA Server (CDA Server ) 09.28.06 16:16:11
[OM 28664] There is already a CDA server process running
-> aud_GetSetLogConfig
<- aud_GetSetLogConfig
-> cda_DaemonMain
-> ccs_DoInitTables
-> ccs_AttemptSMem
<- ccs_AttemptSMem
<- ccs_DoInitTables
-> cvc_IsMappingAvail2
-> uni_GetCharset
-> cvc_IsMappingAvail3
-> cvc_AttemptSMem
<- cvc_AttemptSMem
<- cvc_IsMappingAvail3
<- uni_GetCharset
<- cvc_IsMappingAvail2
<- /build/10.0.1.3/src/bin/cda/cda_daemon.c:799[205,28664]
REPORT CDA Server (CDA Server ) 09.28.06 16:29:02
[OM 16144] The character set 'T61BASE,O' was recorded as the interchange character set
for attributes and values.
SERIOUS ERROR CDA Server (CDA Server ) 09.28.06 16:29:02
[OM 28664] There is already a CDA server process running
-> aud_GetSetLogConfig
<- aud_GetSetLogConfig
-> cda_DaemonMain
-> ccs_DoInitTables
-> ccs_AttemptSMem
<- ccs_AttemptSMem
<- ccs_DoInitTables
-> cvc_IsMappingAvail2
-> uni_GetCharset
-> cvc_IsMappingAvail3
-> cvc_AttemptSMem
<- cvc_AttemptSMem
<- cvc_IsMappingAvail3
<- uni_GetCharset
<- cvc_IsMappingAvail2
<- /build/10.0.1.3/src/bin/cda/cda_daemon.c:799[205,28664]
REPORT CDA Server (CDA Server ) 09.28.06 16:30:05
[OM 16144] The character set 'T61BASE,O' was recorded as the interchange character set
for attributes and values.
REPORT CDA Server (CDA Server ) 09.28.06 16:30:05
[OM 28658] CDA server starting up
REPORT CDA Server (CDA Server ) 09.28.06 16:30:05
[OM 28670] CDA Server using Directory change logs to optimise builds.
REPORT CDA Server (CDA Server ) 09.28.06 16:30:05
[OM 28668] CDA Server has enabled the Change Log for Directory: SYSTEM.
REPORT CDA Server (CDA Server ) 09.28.06 16:30:05
[OM 28660] CDA server rebuilding tables for SYSTEM
REPORT CDA Server (CDA Server ) 09.28.06 16:30:05
[OM 28661] CDA server finished rebuilding for SYSTEM
Posted: Fri Sep 29, 2006 2:42 pm
by ScalixSupport
I think you should run consistency checks on the directories.
First cd /var/opt/scalix/dir/1
then run
for f in *; do cd $f; /opt/scalix/diag/dbcheck -s vi_dir; cd ..; done
Regards,
Don
Posted: Fri Sep 29, 2006 3:34 pm
by mhtrim
Thanks for the reply...
for f in *; do cd $f; /opt/scalix/diag/dbcheck -s vi_dir; cd ..; done
Returns "0 errors were detected" in three places. So that doesn't seem to be a problem. Any ideas on where to go from here?