Register - Outages and performance degradations
- Cintia Del Rio
- chagara casanova
This page hasn't been updated as much as it should :/
Service | Date/time UTC | Resolution | Cause | Comments |
|---|---|---|---|---|
Confluence | Sep 21, 2016 |
|
| |
Sonar | Sep 22, 2016 ~11am | Restart service | Sonar is not on status page Builds failed due to outage | |
Jira | Sep 22, 2016 22:44 | restart service | Out of memory | 2016-09-22 21:10:15,849 ajp-bio-8041-exec-560 WARN anonymous 1266x78860x6 - 50.23.94.74 /secure/Dashboard.jspa [renderer.internal.local.LocalGadgetSpecFactory$Parser] Could not retrieve gadget spec https://issues.openmrs.org/rest/gadgets/1.0/g/com.atlassian.jira.gadgets:filter-results-gadget/gadgets/filter-results-gadget.xml from plugin-provided gadget spec store: java.lang.OutOfMemoryError: Java heap space |
Confluence | Sep 22, 2016 23:26 | Restart Service | Added new profiling flag |
|
Jira | Sep 23, 2016 23:38 | Restart Service | Crashed |
|
Bamboo | Sep 27, 2016 ~00:00 | Kill old service and start again | Crashed? | For some reason, Bamboo server was printing some very weird error messages to the logs: Sep 26, 2016 9:33:20 PM com.sun.jersey.spi.container.ContainerResponse write SEVERE: A message body writer for Java class com.atlassian.bamboo.plugins.rest.model.server.RestServerStatusInfo, and Java type class com.atlassian.bamboo.plugins.rest.model.server.RestServerStatusInfo, and MIME media type application/xml was not found Sep 26, 2016 9:33:20 PM com.sun.jersey.spi.container.ContainerResponse write SEVERE: The registered message body writers compatible with the MIME media type are: application/xml -> com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$App com.sun.jersey.core.impl.provider.entity.DocumentProvider com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$App com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App */* -> com.sun.jersey.core.impl.provider.entity.FormProvider com.sun.jersey.core.impl.provider.entity.StringProvider com.sun.jersey.core.impl.provider.entity.ByteArrayProvider com.sun.jersey.core.impl.provider.entity.FileProvider com.sun.jersey.core.impl.provider.entity.InputStreamProvider com.sun.jersey.core.impl.provider.entity.DataSourceProvider com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General com.sun.jersey.core.impl.provider.entity.ReaderProvider com.sun.jersey.core.impl.provider.entity.DocumentProvider com.sun.jersey.core.impl.provider.entity.StreamingOutputProvider com.sun.jersey.core.impl.provider.entity.SourceProvider$SourceWriter com.sun.jersey.server.impl.template.ViewableMessageBodyWriter com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General com.sun.jersey.json.impl.provider.entity.JSONWithPaddingProvider com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General com.sun.jersey.json.impl.provider.entity.JacksonProviderProxy It appears to be some sort of red herring, because this error appears on the logs every so often.
Also, service stop didn't work, I had to use kill -9. I forgot to reenable the agents, bringing the outage to pretty much a day. |
jira | Oct 30, 2016 | restart service | crashed |
|
Bamboo | Nov 15, 2016 | Re-authorise agents in bamboo | ? | Nov 16, 2016 11:55:37 AM Remote agent 'gw107.iu.xsede.org (1)' was unresponsive and has gone offline. |