It's all about the answers!

Ask a question

[closed] RTC-CC Synchronizer fails through cleartool error

Simon Eickel (1.1k75457) | asked Jun 05 '13, 4:30 a.m.
closed Mar 20 '14, 6:10 a.m.
Hi there,

again it's me with a synchronizer problem.
I do often have the problem that the synchronizer fails through those cleartool errors:
Stacktrace Part1
Stacktrace Part2

This message describes that the clearcase process could not be contacted ... but why?
When I just rerun the synchronization process than everything works.

The clearcase log just gives me this:
ClearCase log

I think WINSOCK errors can mean everything or nothing ...

But this is really annoying as if the synchronizer shall be running automatically and you get often such an error you have to run it manually ... :(

Any ideas?


Georg Kellner commented Jun 05 '13, 8:48 a.m. | edited Mar 20 '14, 1:50 p.m.

It seems to be a ClearCase problem.

On which host is the synchronizer running?
Is it MU714723?

Simon Eickel commented Jun 05 '13, 9:42 a.m.

Hi Georg ,
I think both assumptions are correct.
The host is MU714723 and when I restart the sync everything is fine again.

The question has been closed for the following reason: "problem is solved - I gave the solution myself" by eickel Mar 20 '14, 6:10 a.m.

One answer

permanent link
Geoffrey Clemm (30.0k23035) | answered Jun 13 '13, 2:32 p.m.
This means that periodically, the sync host (the machine where you are running the synchronization engine) is having trouble talking to the albd_server.   Are there other processes running on this machine that might make the albd_server unresponsive?   One approach would be to try using a different machine as the sync host.

Simon Eickel commented Jun 17 '13, 1:59 a.m.

Hi Geoff,
nothing else is running on this PC but the synchronization engine and the Eclipse client to attach it.
Have to check if I'm able to get another PC for that but at the moment we do not have so much free PCs for testings :(

Geoffrey Clemm commented Jun 17 '13, 2:39 p.m. | edited Jun 17 '13, 2:41 p.m.

Then the next thing to investigate is whether there is a network load at that time (i.e. why the sync engine cannot talk to the registry server).  If the sync engine cannot talk to ClearCase, there's no real work it can do.  If you cannot get a sync host that has reliable access to ClearCase, you could add a few  automated "retry" requests to your Synchronization schedule (e.g., one at midnight, one at 12:15am, and another at 12:30am).

Simon Eickel commented Mar 20 '14, 6:10 a.m. | edited Mar 20 '14, 1:51 p.m.

After moving to a new host this error didn't reappear again.