Installation

Request to remove Splunkforwarder9.X version force request tty env restriction

ShawnC
Observer

When I doing splunkforwarder version upgrade to 9.X which always failed due to below error

- Migration information is being logged to '/opt/splunkforwarder/var/log/splunk/migration.log.2024-03-25.18-09-26' --
Error calling execve(): No such file or directory
Error launching  command: No such file or directory

 

As per the discussion on the link:   https://community.splunk.com/t5/Installation/Upgrading-Universal-Forwarder-8-x-x-to-9-x-x-does-not-w...  who said we have to enable the tty env option on the docker runtime to successfully bring up Splunkforward9.X

Indeed I added the tty config on my docker compose file and it works. But I would say it is werse, bad workaround way to bring up splunkforwarder9.X. 

Why the forwarder9.X version force ask for the tty terminal env to run up?  Can we remove this restriction? In many case, we have to bring up splunkforwarder instance within a background program but not in a terminal, and for some case we have to use process manager to control splunkforwarder start resume...

Anyway, can we remove the tty restriction for newer splunkforwarder9.X just like what it did on 8.X and 7.X

 

0 Karma

splunkuser23409
New Member

Did you ever find an answer or a solution other than adding tty?

0 Karma

ShawnC
Observer

@isoutamo any one could help to take a look

0 Karma
Get Updates on the Splunk Community!

CX Day is Coming!

Customer Experience (CX) Day is on October 7th!! We're so excited to bring back another day full of wonderful ...

Strengthen Your Future: A Look Back at Splunk 10 Innovations and .conf25 Highlights!

The Big One: Splunk 10 is Here!  The moment many of you have been waiting for has arrived! We are thrilled to ...

Now Offering the AI Assistant Usage Dashboard in Cloud Monitoring Console

Today, we’re excited to announce the release of a brand new AI assistant usage dashboard in Cloud Monitoring ...