Closed benheise closed 3 years ago
Hey @benheise, sorry for the delay here. Is the Splunk issue repeatable? Maybe it was a corrupted download or an intermittent issue with Splunk servers at the time?
Also, I can't repro the windows control characters issue (but I'm running this on a Mac):
$ md5sum logger_bootstrap.sh
82fc33098b4f20e55df55561b1056b9e logger_bootstrap.sh
$ dos2unix logger_bootstrap.sh
dos2unix: converting file logger_bootstrap.sh to Unix format...
$ md5sum logger_bootstrap.sh
82fc33098b4f20e55df55561b1056b9e logger_bootstrap.sh
Maybe you opened the file in a Windows text editor at some point which caused Windows control chars to get added?
I didn't think so, but I'm not running into that same issue so that must be the case.
Description of the issue:
While using WSL2 and building the logger host, I'm running into the following error message that causes the build to stop.
The first is that the bash script copied over to the logger host has windows control characters in it for some reason.
Installing and running dos2unix resolved this issue.
The second issue is that the script appears to correctly parse the splunk .deb for installation, however the file downloaded is empty.
Manually running the splunk installer .deb and supplying the default username/password completed this step and allowed Ansible to move on to the next steps.