/var/log/cce growing rapidly

[acw]

One of our appliance has it's /var/log/cce growing rapidly, filled with the following :

[Tue Apr 29 00:13:53 -0400 2008][2108] Failed receiving signal information from CCE core. Using default values. Error code [510]
[Tue Apr 29 00:13:56 -0400 2008][2099] Failed to get the init info. Error code [510]
[Tue Apr 29 00:13:56 -0400 2008][2098] Failed receiving signal information from CCE core. Using default values. Error code [510]
[Tue Apr 29 00:14:02 -0400 2008][2109] Failed to get the init info. Error code [510]
[Tue Apr 29 00:14:02 -0400 2008][2102] Failed to get the init info. Error code [510]


Any idea what is this, and what should be done?

Thanks!

[PeterNic]

Albert,

Which version of AppLogic is that on? (use 'grid info') I recall a similar problem with the 2.0.2 beta but it is possible there is a condition in which this happens in 2.1.x.

Can you provide more info -- which appliance does that, is its mon output connected; if yes, is MON running?

(A quick solution would be to branch the offending appliances and symlink /var/log/cce to /dev/null, or simply disable the applogic_cce service; an alternative is to connect the appliance's mon terminal to a MON instance and have it running)

Regards,
-- Peter

[acw]

Hi Peter,

2.1.0 hf2061 hf2057 hf1960 hf2069 hf2192

it's a custom appliance. Mon output is connected, but MON is not running.

Thanks for the tips. Just tried starting up mon, and the logs stopped immediately. Then brought the Mon down again, and the logs continued to be ok without the errors. So, something somehow triggered it earlier. Have another appliance that's exactly the same, and that one has been ok without the same problem.

[acw]

Peter - FYI - this problem occurs in 2.3.9 hf2425 also when MON is left disabled.

[PeterNic]

Albert -- thanks. We missed it in 2.3.9 :mad: , will be fixed in 2.4. The fix is the same -- one of: delete the logs periodically, keep MON running or disconnect the mon terminal.