This was a major fail on my part: There seems to be a difference between a full system restart and a cprestart, one reboots the box and the other seems to fully start the process again (I can only assume some form of state is written to disk and therefore persists at reboot whilst a cprestart starts from scratch). There is a properties file where you can make the debugging more verbose:
Edit:
vi $VSECDIR/lib/log4j.properties
Add entries
log4j.logger.com.cp.dcrepository = TRACE
log4j.logger.com.cp.cms_proxydcrepository=TRACE
log4j.logger.com.cp.cms=TRACE
Restart vsec controller:
vsec_controller_stop
Then you can tail the cloud_proxy.elg file i.e. (I like to follow the file in real time):
tail -f /var/log/opt/CPsuite-R80/fw1/log/cloud_proxy.elg
If you are lookng for something specific, then pipe the tail into grep of something useful (obviously replace some_useful_object with whatever is of interest to you)
tail -f /var/log/opt/CPsuite-R80/fw1/log/cloud_proxy.elg | grep some_useful_object
Loving the gaia linux effect (yeah I know the kernel is different), but this is handy for a less seasoned checkpoint debugger like me
. Interesting mash up to java, bash and python going on in R80.x
This is verbose - therefore consumes disk space - don't forget to remove the entries in the properties file and restart the controller when you are done!!