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
Get Updates on the Splunk Community!

Shape the Future of Splunk: Join the Product Research Lab!

Join the Splunk Product Research Lab and connect with us in the Slack channel #product-research-lab to get ...

Auto-Injector for Everything Else: Making OpenTelemetry Truly Universal

You might have seen Splunk’s recent announcement about donating the OpenTelemetry Injector to the ...

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...