...
Dealing with Known Issues
Confluence's Internal CRON
There is a known performance issue with an internal Confluence feature called BackupJob. Our confluence is too big to run this successfully. It should be disabled. You can use some of these instructions with other background processes if they evidence problems in the future.
- If this is the problem, the catalina.out will contain errors pertaining to "quartz" and "BackupJob" in the same error statement. /opt/sash-server/servers/confluence/logs/catalina.out
- To stop the current process you have to restart the whole confluence container (see above).
- Since this job should be disabled, check to see if it is disable in the web-management console for Confluence.
- MIT
- AMIT and OPS members should all have admin privileges for wikis-stage.mit.edu and wikis.mit.edu.
- Logged Log into the wikis system in question, find the "administration" link at the top of the page.
- From the Admin console, you can "pause" a currently running BackupJob process using the JobManager tool navigate to the Daily Backup Admin panel in the left-and navigation. Find "BackuJob" on that page and click "pause," the status should come back as YES.hand navigation.
- Enter After that, make sure the job is off permanently. It should not have been running in the first place. Navigate to "Daily Backu Admin," enter "Edit" mode, and set "Backup Attachments" to OFF.