Hi
Version: SinusBot 0.11.0-8e5f1a2
OS: Debian Jessie (8.10)- Sinusbot installer script used. (will test debian 9 later on again)
After some time online the bot stops responding to commands like !next.
I don't see anything in the logs.
If the bot have not yet stopped playing music i still see the the yt-dl processing urls, but does not register the !next command i.e.
Restarting the bot from the webinterface does not change this, only restarting the service does.
Loglevel is now set to 10 and a logfile is set in config.ini
I had a "stable version" bot earlier on debian 9 stretch, which had the same issues.
I have tried to check the forum but without any luck.
Can i do something about this or is this a buglike thing maybe ?
/Cromag
Version: SinusBot 0.11.0-8e5f1a2
OS: Debian Jessie (8.10)- Sinusbot installer script used. (will test debian 9 later on again)
After some time online the bot stops responding to commands like !next.
I don't see anything in the logs.
If the bot have not yet stopped playing music i still see the the yt-dl processing urls, but does not register the !next command i.e.
Restarting the bot from the webinterface does not change this, only restarting the service does.
Loglevel is now set to 10 and a logfile is set in config.ini
I had a "stable version" bot earlier on debian 9 stretch, which had the same issues.
I have tried to check the forum but without any luck.
Can i do something about this or is this a buglike thing maybe ?
/Cromag