Troubleshooting Job Cleanup

For troubleshooting, we recommend starting Pulse or a Remote Connection Server so that the House Cleaning logs will be collected on to a single computer. We’ll refer to the computer that is running the House Cleaning process as the House Cleaning computer going forward.

To separate the House Cleaning log from the application’s log, in the Monitor under Tools → Configure Repository Options → House Cleaning → House Cleaning enable ‘Run House Cleaning in a Separate Process’ and ‘Write House Cleaning Output to Separate Log File’. Do this and restart the House Cleaning computer or wait approximately 10 minutes for the change to propagate to Pulse or the Remote Connection Server.

With that change in effect in the application log folder of the House Cleaning machine you’ll find a file named in the following format:

housecleaning-[hostname]-[date].log

If the Job Cleanup process never reports how many jobs were cleaned up it may be that there are too many Jobs to be processed and the process cannot complete before the default 30 second timeout.

To resolve that, in the Monitor under Tools → Configure Repository Options → House Cleaning → House Cleaning enable the session Job counts. To do that, enable all the entries under ‘House Cleaning Maximums Per Session’. Use the default settings to begin with, and if the timeouts aren’t resolved, lower the numbers.

If adjusting the session counts doesn’t resolve the issue then please share your House Cleaning log with the support team at awsthinkbox.zendesk.com