Installation

Issues installing Enterprise Addition on EC2

dstrower
Observer

I installed Splunk on an EC2 instance.

I saw the login page on port 8000 but when I tried to login I got a server error.

I am not sure what I should look at.

Labels (1)
Tags (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

t2.micro probably is too small.  I use a t2.medium for my sandbox.  100GB isn't enough, either.  Try 300GB.

The message means Splunk is trying to index a non-text file and is informational.  It should not prevent login.  You can delete that file to clear the log message.  Use less or more rather than vi to view log files.

There should be other log messages explaining why you can't log in.

---
If this reply helps you, Karma would be appreciated.
0 Karma

dstrower
Observer

I used t2.micro instance. I installed version  downloaded version

splunk-8.2.6-a6fe1ee8894b-Linux-x86_64.tgz and I untarred it.

I have a UNIX volume of 100Gb.

Inside the file splunkd.log:

The file '/home/ec2-user/splunk/var/log/splunk/.sp lunkd.log.swp' is invalid. Reason: binary.

 

0 Karma

richgalloway
SplunkTrust
SplunkTrust

What instance type did you use?

What server error did you get? 

Did you check $SPLUNK_HOME/var/log/splunk/splunkd.log?

---
If this reply helps you, Karma would be appreciated.
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Introduction to Splunk AI

How are you using AI in Splunk? Whether you see AI as a threat or opportunity, AI is here to stay. Lucky for ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Maximizing the Value of Splunk ES 8.x

Splunk Enterprise Security (ES) continues to be a leader in the Gartner Magic Quadrant, reflecting its pivotal ...