-
Notifications
You must be signed in to change notification settings - Fork 55
MumbleDJ will not take commands or read configs (intel based system) #187
Description
Before submitting this issue, please acknowledge that you have done the following:
- I've at least skimmed through the README
- I have checked that I am running the latest version of MumbleDJ (use
mumbledj --versionwhen starting the bot or use the MumbleDJ version command in Mumble) - I have searched through the existing issues to see if my issue has been answered already
What type of issue is this?
- Bug report (encountered problems with MumbleDJ)
- Feature request (request for a new functionality)
- Question
- Other:
Log output of bot with --debug flag (likely only for bug reports):
INFO[0000] Checking for duplicate aliases...
INFO[0000] Performing startup checks...
INFO[0000] Checking for availability of services... num_services=3
WARN[0000] A startup check discovered an issue. The service will be disabled. error=No YouTube API key has been provided service=YouTube
WARN[0000] A startup check discovered an issue. The service will be disabled. error=No SoundCloud API key has been provided service=SoundCloud
INFO[0000] Checking YouTubeDL installation...
INFO[0000] Checking ffmpeg installation...
INFO[0000] Checking aria2c installation...
WARN[0000] aria2 is not installed or is not discoverable in $PATH. The bot will still partially work, but some services will not work properly.
INFO[0000] Checking openssl installation...
INFO[0000] Attempting connection to server... address=127.0.0.1 port=64738
FATA[0000] An error occurred while connecting to the server. error="x509: cannot validate certificate for 127.0.0.1 because it doesn't contain any IP SANs"
Description of your issue:
Bot failing to read config or take command line arguments. I compiled it from git. If I delete the config file, it will recognize that the config file is not there and will make a new one, but no values that I change are reflected in the bot nor will it take arguments from flags.
Running CentOS 6.5 (legacy is a bitch) x86_64
Bug is a possible duplicate of #171 but I thought I'd make a new thread as I'm not on ARM and the other issue was blamed on ARM derpery.