- Find Answers
- :
- Splunk Administration
- :
- Deployment Architecture
- :
- Re: Why am I getting a 500 Internal Server Error i...
- 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
On a new install, I am getting a 500 Internal Server Error immediately after logging into my external IP address at port 8000 over http. Once that happens, Splunk errors out, and I can't try to log in again until I restart Splunk. But when I check ./splunk status it appears to be fine. This is on a fresh Ubuntu 16 server on a VPS. I have tried all the reasonably applicable solutions posted here with no success. Any suggestions?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi there,
Please look at splunkd.log file (located at $SPLUNK_HOME/var/log/splunk) for errors or warnings and provide some data to further assist you.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nevermind, forgot to restart. That fixed the problem, thanks.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So what was the last change you did before restart to fix the issue?
What goes around comes around. If it helps, hit it with Karma 🙂
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Worth to check mgmtHostPort = <IP:port> in your web.conf. Normally this error happens when your web is not able to connect to splunkd.
What goes around comes around. If it helps, hit it with Karma 🙂
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I changed it from: [mgmtHostPort = 127.0.0.1:8089] to the external IP address, with no change. Is there something special that must be done to access the web interface remotely as opposed to via localhost, which appears to be the default configuration?
Earn a $35 Gift Card for Answering our Splunk Admins & App Developer Survey
Continuing Innovation & New Integrations Unlock Full Stack Observability For Your ...
Monitoring Amazon Elastic Kubernetes Service (EKS)
