Problems with Sync between CS and RME in LMS 3.2

Unanswered Question
Oct 27th, 2009

Hello there,

with LMS 3.2 we do not use the autodiscovery feature (because of network-topology) so new devices are manually added in CS-DeviceManagement.

Several times we discover that after adding devices the new devices won't be sync'd with the RME-DB. Devices in RME-State pending (for ever).

Only performing a restart of CW2000-Deamons puts them in Normal state.

Resubmitting doesn't help.

Any advices how to further troubleshoot.

This problem occours after an undefined application running time?

Credentials are checked and set correctly.

Best Regards


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Joe Clarke Tue, 10/27/2009 - 05:46

This could be an issue with either EssentialsDM or ICServer. Typically, when something in a process hangs, I would want to look at the Java thread dump of that process. On Solaris, getting this is as simple as sending a SIGQUIT to the process then looking in daemons.log for the dump. On Windows, the process is much more complicated. If you contact TAC, they can walk you through the process.

lo.mueller Tue, 10/27/2009 - 06:33

Hi Joe,

thanks for your fast response.

As we are running solaris SIGQUIT is our tool.

Can the output be interpreted by my/our own, or do we need TAC help?

Best Regards


Joe Clarke Tue, 10/27/2009 - 06:36

You would need TAC help. The output will be a set of Java stack traces. Someone knowledgeable with the code would have to analyze the output to determine why the thread is stuck.


This Discussion