Deployment Architecture

[rpcstart.py] RPC server has been terminated abnormally with error [org.eclipse.jetty.server.Server@3ce1e309 - STARTED].

kyaparla
Path Finder

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.

0 Karma
1 Solution

kyaparla
Path Finder

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

View solution in original post

kyaparla
Path Finder

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

sarwshai
Communicator

Can you let me know, what exactly you made the changes, as i am facing the same problem.

0 Karma

kyaparla
Path Finder

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.

0 Karma
Get Updates on the Splunk Community!

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...

Adoption of Infrastructure Monitoring at Splunk

  Splunk's Growth Engineering team showcases one of their first Splunk product adoption-Splunk Infrastructure ...

Modern way of developing distributed application using OTel

Recently, I had the opportunity to work on a complex microservice using Spring boot and Quarkus to develop a ...