Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Deployment Architecture
- :
- Re: [rpcstart.py] RPC server has been terminated a...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
DBConnect was working fine, and it stopped working after it crashed once. Getting RPC server not running message. Appreciate any help or pointers on this.
Error logs
09/22/2015 18:24:13 [INFO] [rpcstart.py] protocol=TLS
09/22/2015 18:24:13 [INFO] [rpcstart.py] cipher_suite = none
09/22/2015 18:24:13 [INFO] [rpcstart.py] keystore=/opt/hunk/etc/apps/splunk_app_db_connect/certs/default.jks
09/22/2015 18:24:13 [INFO] [rpcstart.py] proc.pid = 39990
09/22/2015 18:24:34 [CRITICAL] [rpcstart.py] RPC server has been terminated abnormally with error [org.eclipse.jetty.server.Server@3ce1e309 - STARTED].
09/22/2015 18:24:40 [INFO] [rpcstart.py] protocol=TLS
09/22/2015 18:24:40 [INFO] [rpcstart.py] cipher_suite = none
09/22/2015 18:24:40 [INFO] [rpcstart.py] keystore=/opt/hunk/etc/apps/splunk_app_db_connect/certs/default.jks
09/22/2015 18:24:40 [INFO] [rpcstart.py] proc.pid = 40315
I have tried restarting server, killing java processes with no luck.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It happened to be an issue with /etc/hosts file. some one deleted localhost entry and Splunk healthcheck was failing.
What I noticed in the code is that its not consistent that in some places localhost is used and some places 127.0.0.1 is used.
A
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It happened to be an issue with /etc/hosts file. some one deleted localhost entry and Splunk healthcheck was failing.
What I noticed in the code is that its not consistent that in some places localhost is used and some places 127.0.0.1 is used.
A
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you let me know, what exactly you made the changes, as i am facing the same problem.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It happened to be an issue with /etc/hosts file. some one deleted localhost entry and Splunk healthcheck was failing.
What I noticed in the code is that its not consistent that in some places localhost is used and some places 127.0.0.1 is used.
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions
Splunk Community Badges!
[Puzzles] Solve, Learn, Repeat: Matching cron expressions
