|
puppetdb was running with no issues for weeks, then hung and now logs the following on startup:
2016-03-15 15:22:15,183 INFO [o.e.j.s.Server] jetty-9.2.z-SNAPSHOT
|
2016-03-15 15:22:15,257 INFO [o.e.j.s.h.ContextHandler] Started o.e.j.s.h.ContextHandler@31cc7610{/pdb,null,AVAILABLE}
|
2016-03-15 15:22:15,283 INFO [o.e.j.s.ServerConnector] Started ServerConnector@456277f5{HTTP/1.1}{localhost:8080}
|
2016-03-15 15:22:15,382 INFO [o.e.j.s.ServerConnector] Started ServerConnector@6ef9942d{SSL-HTTP/1.1}{dev-puppetdb.ucar.edu:8081}
|
2016-03-15 15:22:15,383 INFO [o.e.j.s.Server] Started @30300ms
|
2016-03-15 15:22:15,428 INFO [p.p.c.services] PuppetDB version 3.2.4
|
2016-03-15 15:22:15,589 INFO [p.p.s.migrate] There are no pending migrations
|
2016-03-15 15:22:15,612 INFO [c.j.b.BoneCP] Shutting down connection pool...
|
2016-03-15 15:22:15,616 INFO [c.j.b.BoneCP] Connection pool has been shutdown.
|
2016-03-15 15:22:15,619 INFO [p.p.c.services] Starting broker
|
|
2016-03-15 15:23:35,088 INFO [p.p.pdb-routing] HTTP request received while in maintenance mode
|
2016-03-15 15:23:37,775 INFO [p.p.pdb-routing] HTTP request received while in maintenance mode
|
2016-03-15 15:24:01,838 INFO [p.p.pdb-routing] HTTP request received while in maintenance mode
|
2016-03-15 15:24:01,848 WARN [o.e.j.h.HttpParser] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@7ed11886{r=1,c=false,a=IDLE,uri=-}
|
2016-03-15 15:24:04,072 INFO [p.p.pdb-routing] HTTP request received while in maintenance mode
|
2016-03-15 15:24:29,776 INFO [p.p.pdb-routing] HTTP request received while in maintenance mode
|
2016-03-15 15:24:32,812 INFO [p.p.pdb-routing] HTTP request received while in maintenance mode
|
Puppetdb appears to be permanently stuck in maintenance mode.
I've tried bumping up the memory and restarting, going as high as "-Xmx2048m -Xms1024m", but that doesn't make any difference. Since I'm using virtual and exported resources, this breaks my whole infrastructure.
|
