Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Admin Other
- :
- Installation
- :
- Unable to install Splunk Phantom on CentOS
- 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
Unable to install Splunk Phantom on CentOS
I'm trying to install Splunk Phantom on CentOS server but I'm getting the below error.
About to proceed with Phantom install
Do you wish to proceed [y/N]
y
sed: can't read /opt/phantom/bin/stop_phantom.sh: No such file or directory
Enter username: vikram@abc.com
Enter password: **********
./phantom_setup.sh: line 357: python: command not found
./phantom_setup.sh: line 358: python: command not found
21 files removed
Updating phantom repo package
Error updating Phantom Repo package
Errors during downloading metadata for repository 'phantom-base':
- Status code: 404 for https://***@repo.phantom.us/phantom/4.5/base/8/x86_64/repodata/repomd.xml (IP: 54.165.15.205)
Error: Failed to download metadata for repo 'phantom-base': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you installing as root or a privileged user? The /opt directory is owned by root so only one of those two can write there.
An upvote would be appreciated and Accept Solution if it helps!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, @codebuilder I'm installing phantom via root user.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks like the network on your box can't reach the repo, or the repo url itself isn't correct. Try doing an nslookup or ping on the fqdn listed in your url.
An upvote would be appreciated and Accept Solution if it helps!
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Index This | What travels the world but is also stuck in place?
Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data
Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...
