Deployment Architecture
×
Are you a member of the Splunk Community?
Sign in or Register with your Splunk account to get your questions answered, access valuable resources and connect with experts!
- Find Answers
- :
- Splunk Administration
- :
- Deployment Architecture
- :
- [rpcstart.py] RPC server has been terminated abnor...
Options
- 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
kyaparla
Path Finder
09-22-2015
11:40 AM
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.
1 Solution
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
kyaparla
Path Finder
01-08-2016
11:51 AM
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
kyaparla
Path Finder
01-08-2016
11:51 AM
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
sarwshai
Communicator
11-10-2017
05:09 AM
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
kyaparla
Path Finder
01-08-2016
11:51 AM
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.
Get Updates on the Splunk Community!
Splunk Observability Cloud's AI Assistant in Action Series: Auditing Compliance and ...
This is the third post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how to ...
Splunk Community Badges!
Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...
What You Read The Most: Splunk Lantern’s Most Popular Articles!
Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...
