Agent not checking in - CSA 4.5.x

Unanswered Question
Oct 12th, 2007

I have a hand full of agents that stopped checking into the console with:

[2007-10-12 12:16:29.630] [PID=388] [Csamanager]: inquire_config_status: Inquiring config status [37] with server, Failure (1), (elapsed_time=107825 ms)

[2007-10-12 13:10:00.735] [PID=388] [Csamanager]: Failed transaction, url=, curlerr=56 (SSL read: error:00000000:lib(0):func(0):reason(0), errno 10054).

[2007-10-12 13:10:00.735] [PID=388] [Csamanager]: inquire_config_status: Inquiring config status [38] with server, Failure (1), (elapsed_time=114064 ms)

These systems stopped checking in at different times...(one two days ago, another 10 days ago)...

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
tsteger1 Fri, 10/12/2007 - 15:23

An SSL read error may indicate a problem with the certificate on the host. Can you resolve the MC in DNS?


dave_schroeder Mon, 10/15/2007 - 07:35

Hi there...

Yes, the MC is fully resolvable in DNS from all of the affected systems... It is strange.. when I first noticed it, there were 2 out of 7 hosts checking into the MC, now there are 4 out of 7 checking in all of a sudden...

tsteger1 Mon, 10/15/2007 - 12:25

Yes that is strange.

Couple of other questions:

How long has this setup been working without error?

Were there any other recent changes that might have affected the hosts or MC?


dave_schroeder Mon, 10/15/2007 - 12:38

The console has been running without any issues for nearly 2 years... the end points experiencing issues have been in place since and reporting into the MC since September 26th... all systems currently not reporting stopped reporting at different times... other than running the prepare migration utility, no configuration changes were made to the system in a long time... I am in the process of migrating endpoints from all sites to version

tsteger1 Thu, 10/18/2007 - 10:24

Sorry, I'm stumped. Have they been slowly coming back on line or are there still some holdouts?

Migration to 5.2 may be your solution in this case.



This Discussion