Hi Justin, Confluence is back again. Root cause was an out of memory error while running a critical task.
More specifically, Confluence ran out of heap memory while running the ClusterSafetyJob thread  which likely caused the out of sync error in the cluster safety table. There were no errors prior to that so it's hard to say what exactly in Confluence started using all that memory (but the heap was too small in any case). I've increased the JVM heap space from 1GB to 4GB . Regards, Giovanni 0 - "executeJob Unhandled exception thrown by job QueuedJob[jobId=ClusterSafetyJob,deadline=1523306258345] java.lang.OutOfMemoryError: Java heap space" 1 - https://wiki.fluidproject.org/admin/systeminfo.action On 04/10/2018 08:21 AM, Justin Obara wrote: > > Hi Everyone, > > It appears that the fluid project wiki <https://wiki.fluidproject.org> is > currently down. It seems that confluence couldn’t be started. > > Thanks > Justin _______________________________________________________ fluid-work mailing list - firstname.lastname@example.org To unsubscribe, change settings or access archives, see https://lists.idrc.ocad.ca/mailman/listinfo/fluid-work