CDA Server Serious Error

[dresdn]

I'm running RHEL4 with Scalix 10.0.1, and CDA Server is throwing some nasty errors when it tries to start.

If I do a:

Code: Select all

omoff -s cda
omon -s cda


I get the following from omshowlog:

Code: Select all

SERIOUS ERROR                  CDA Server    (CDA Server    ) 05.30.06 09:46:51
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 6207
Procedure trace follows:
  -> 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


SERIOUS ERROR                  CDA Server    (CDA Server    ) 05.30.06 09:46:51
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x18cf06]
/opt/scalix/lib/libom_er.so[0x18d1d6]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x18d37f]
/lib/tls/libpthread.so.0[0x4bd888]
/lib/tls/libc.so.6(__strtol_internal+0x3f)[0x5719ef]
/lib/tls/libc.so.6(atoi+0x26)[0x56f046]
cda.server[0x804df8b]
/opt/scalix/lib/libom_cl.so(cl_CallProc+0x85)[0x6f41e5]
cda.server[0x80519c6]
/lib/tls/libc.so.6(__libc_start_main+0xd3)[0x55ae23]
cda.server[0x804a8ad]


Any ideas? Also, what's the proper way to report problems like this, just on the forums?

Thanks!

-Mike

[ScalixSupport]

If you have support agreement with us then you can report problems to support at scalix.com, otherwise this is your avenue for reporting problems.

I believe you will find that if you use the search feature on the forum you will find answers to many questions you may have.

For this issue it has been covered before. I know it is difficult to know what to search on to get a match but your error has been posted before.

Delete /var/opt/scalix/sys/omcda.lock and try starting cda again.

Regards,
Don

[dresdn]

My apologies. Doing a better search using the AND, rather than the OR found the problem.

Sorry for creating the additional noise.