Versions Compared

Old Version 1

changes.mady.by.user Stephen M Landry

Saved on

compared with

New Version 2

changes.mady.by.user Stephen M Landry

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Operating Confluence

If there is a problem with wikis, obviously this document would not be accessible to you from here. Please copy this content to a location where you store support information. 

Starting and Stopping the Service

  • The service can be safely Like most ISDA-run application services, the service can be non-invasely restarted with /etc/init.d/web restart. This restarts apache, tomcat, and other dependent components.
  • To restart just the servlet container (just confluence), run /opt/sash-server/bin/sashctl confluence restart
  • Wikis uses a multi-container tomcat derivative called sashserver, /opt/sash-server. Therefore, you will see multiple java processes running on a system. You can identify confluence doing an "lsof" on the java or jsvc processes to see which is grabbing up confluence jars in the path to the confluence servlet container (somewhere under /opt/sash-server/servers/confluence). 
  • Confluence is a resource-intensive application. It can take several minutes for the service to start.

Dealing with Known Issues

  • 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.
    • AMIT and OPS members should all have admin privileges for wikis-stage.mit.edu and wikis.mit.edu.
    • Logged 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 in the left-and navigation. Find "BackuJob" on that page and click "pause," the status should come back as YES.
    • 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.