karlt
Member
Operating System: Windows / Linux
SinusBot Version: 0.9.15-b20cc30
TS3 Version: 3.0.18.2
Problem Description
The bot ran fine for 3-4 days since installation. !play command included. We used the AloneMode Script from the start. At some point users left the channel and now, despite killing the process and rerunning the bot and various combinations of stopping/starting the bot, it no longer responds to play commands. We use the playlist listing script, which provides output. We can start playback manually on the admin panel.
When trying to just !play something, the console outputs:
When trying to play a playlist:
The only major 'change' we made was instantiating a second instance of the bot in another channel on the same server.
SinusBot Version: 0.9.15-b20cc30
TS3 Version: 3.0.18.2
Problem Description
The bot ran fine for 3-4 days since installation. !play command included. We used the AloneMode Script from the start. At some point users left the channel and now, despite killing the process and rerunning the bot and various combinations of stopping/starting the bot, it no longer responds to play commands. We use the playlist listing script, which provides output. We can start playback manually on the admin panel.
When trying to just !play something, the console outputs:
Code:
2016/12/29 03:08:13 e7cf5b5f 967463be INFO CHAT 2 [admin @ XXX] < !play > / NOTFOUND/NOPRIVWhen trying to play a playlist:
Code:
2016/12/29 03:08:18 e7cf5b5f 967463be INFO CHAT 2 [admin @ XXX] < !playlist PLAYLISTNAME > / OK
2016/12/29 03:08:18 e7cf5b5f 967463be DEBUG New channel
2016/12/29 03:08:18 e7cf5b5f 967463be DEBUG Deleting channel
2016/12/29 03:08:21 e7cf5b5f 967463be DEBUG Storing configuration.
2016/12/29 03:11:06 e7cf5b5f d840a89f INFO SAMPLEX 3840 60
2016/12/29 03:11:06 e7cf5b5f d840a89f DEBUG Deleting channel
2016/12/29 03:11:06 e7cf5b5f d840a89f DEBUG Channels now zero
2016/12/29 03:11:06 e7cf5b5f d840a89f DEBUG Done playingThe only major 'change' we made was instantiating a second instance of the bot in another channel on the same server.
On our server, we enforce push-to-talk. By creating a special group for the bot without this requirement, and doing some minor stuff like ensuring it had server group list viewing power, it seems to be fine now!