Archive

Splunk DB Connect 1: Why is the Java bridge not running with error "PID file content changed...Forcing shutdown"?

Contributor

Continuously getting the following errors in Splunk DB Connect 1

2016-02-09 20:20:03.716 :ERROR:JavaBridgeServer$ProcessWatcher - PID file content changed: content=31663 current pid=15473 - Forcing shutdown.
2016-02-09 20:20:18.716 :ERROR:JavaBridgeServer$ProcessWatcher - PID file content changed: content=31663 current pid=15473 - Forcing shutdown.
2016-02-09 20:20:33.716 :ERROR:JavaBridgeServer$ProcessWatcher - PID file content changed: content=31663 current pid=15473 - Forcing shutdown.
2016-02-09 20:20:48.717 :ERROR:JavaBridgeServer$ProcessWatcher - PID file content changed: content=31663 current pid=15473 - Forcing shutdown.
2016-02-09 20:21:03.716 :ERROR:JavaBridgeServer$ProcessWatcher - PID file content changed: content=31663 current pid=15473 - Forcing shutdown.
2016-02-09 20:21:10.561 dbx3531:ERROR:Splunkd - Splunkd REST Service keep-alive failed! Session key probably expired. (java.io.IOException: Server returned HTTP response code: 401 for URL: https://127.0.0.1:8089/servicesNS/nobody/-/authentication/current-context/context)
java.io.IOException: Server returned HTTP response code: 401 for URL: https://127.0.0.1:8089/servicesNS/nobody/-/authentication/current-context/context
    at sun.reflect.GeneratedConstructorAccessor42.newInstance(Unknown Source)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
    at java.lang.reflect.Constructor.newInstance(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection$6.run(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection$6.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.net.www.protocol.http.HttpURLConnection.getChainedException(Unknown Source)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
    at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source)
    at com.splunk.rest.Response.getContent(Response.java:54)
    at com.splunk.rest.Response.readXML(Response.java:62)
    at com.splunk.rest.Splunkd$KeepAlive.run(Splunkd.java:144)
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
    at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: Server returned HTTP response code: 401 for URL: https://127.0.0.1:8089/servicesNS/nobody/-/authentication/current-context/context
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
    at java.net.HttpURLConnection.getResponseCode(Unknown Source)
    at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(Unknown Source)
    at com.splunk.rest.Response.<init>(Response.java:31)
    at com.splunk.rest.Splunkd.request(Splunkd.java:217)
    at com.splunk.rest.Splunkd.request(Splunkd.java:102)
    at com.splunk.rest.Splunkd.request(Splunkd.java:94)
    ... 8 more
2016-02-09 20:21:10.561 dbx3531:INFO:ExecutionContext - Execution finished in duration=8 ms
2016-02-09 20:21:18.717 :ERROR:JavaBridgeServer$ProcessWatcher - PID file content changed: content=31663 current pid=15473 - Forcing shutdown.
2016-02-09 20:21:33.717 :ERROR:JavaBridgeServer$ProcessWatcher - PID file content changed: content=31663 current pid=15473 - Forcing shutdown.
2016-02-09 20:21:48.716 :ERROR:JavaBridgeServer$ProcessWatcher - PID file content changed: content=31663 current pid=15473 - Forcing shutdown.

How to fix this error in Splunk 6.2.1

0 Karma

Splunk Employee
Splunk Employee

That sounds like a second copy is altering the PID file, which would be pretty bad. I suspect it's running in an environment that it isn't able to support.

0 Karma