• If you need help or want to discuss things, you now can also join us on our Discord Server!
  • A first preview of the unlimited version of SinusBot can be found in the Upcoming Changes thread. A version for Windows will follow, but we don't have a release date, yet.

Bug Respond have to restart bot

Status
Not open for further replies.

lukasjanra

Member
Code:
==========================================================
SINUSBOT RELATED
SYSTEM INFORMATION
- Operating System: Debian GNU/Linux 8.3 (jessie)
- OS x64 check: OK
- Kernel: Linux 3.16.0-4-amd64 x86_64
- Load Average: 0.10 0.08 0.05
- Uptime: 6 days, 19 hours, 48 minutes, 39 seconds
- OS Updates: 20 (updates available!)
- OS Missing Packages: None (v1)
- OS APT Last Update: 01.04.2016 09:16:12 CEST +02:00:00
- Bot Start Script: not found
- DNS resolution check: google.com -> OK
- CPU:
    Architecture:          x86_64
    CPU(s):                1
    Thread(s) per core:    1
    Core(s) per socket:    1
    Socket(s):             1
    Model name:            Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz
    CPU MHz:               2299.998
    Hypervisor vendor:     VMware
    Virtualization type:   full
- RAM: 231.59 MB/1000.41 MB in use (23%)
- SWAP: 53.35 MB/1.85 GB in use (2%)
- DISK: 6.98 GB/9.92 GB in use (70%)
- Report date: 12.04.2016 16:40:42 CEST +02:00:00 (timezone: Europe/Rome)

BOT INFORMATION
- Status: running (PIDs: 15972 15971, User: root)
- Webinterface: port locally not reachable (Port: 8087)
- Binary: /opt/musicbot/sinusbot (Hash: 09876610d75f55d2a133013f5a06937d)
- Version: 0.9.11-ee30ef7
- TS3 Plugin: installed (plugin in bot directory not found)
   - Bot Plugin: unknown
   - TS3 Client: unknown
- Config:
   - LogLevel = 10 (debug log active)
   - TS3Path = /opt/musicbot/TeamSpeak3-Client-linux_amd64/ts3client_linux_amd64 (Version 3.0.19)
   - YoutubeDLPath = /usr/local/bin/youtube-dl (does exist, version: 2015.12.23)
- Installed scripts: advertising.js; aloneMode.js; badchan.js; bookmark.js; covatar.js; dev.js; followme.js; idle.js; metadata.js; norecording.js; rememberChannel.js; showcase.js; sound.js; stickyChannel.js; welcometext.js

OTHER INFORMATION
- TeamSpeak 3 Version: 3.0.19
- DiagScript version: v0.4.1
==========================================================

And here is already github bugtracker. https://github.com/flyth/ts3soundbot/issues/429

Well thats pretty weird there are 2 options.

  1. Bot will stop responding to user chat commands but he still plays his playlist. That happens in like 3-4 hours after I start bot.

  2. Same as before but also sometimes bot stop to transmit into channel sound. I can try to play from website and it seems like playing but no sound no chat command respond. Same solution is I have to restart bot. This happens in like 12hours - 1 day after I start bot.
Since my teamspeak is non profit and this musicbot is made for people and Im not online everyday this is little bit bad that I have to restart bot like every 6 hours.

loglevel10 LOG
 

Seph29

Donor
is awesome!
I'm experiencing this too

tried with ts client 3.0.18.2 / 3.0.19 / 3.0.19.1 / 3.0.19.2 / 3.0.19.3
tried a fresh install of sinusbot + ts client

always the same problem, after serveral hours my 5 bots stops listen to TeamSpeak chat messages.



Code:
==========================================================
SINUSBOT RELATED
SYSTEM INFORMATION
 - Operating System: Ubuntu 14.04.4 LTS
 - OS x64 check: OK
 - Kernel: Linux 3.14.32-xxxx-std-ipv6-64-hz1000 x86_64
 - Load Average: 0.65 0.60 0.59
 - Uptime: 262 days, 16 hours, 12 minutes, 10 seconds
 - OS Updates: 0 (well done!)
 - OS Missing Packages: None (v1)
 - OS APT Last Update: 29.06.2016 18:09:13 CEST +02:00:00
 - Bot Start Script: found at /etc/init.d/sinusbot [perms: 755]
 - DNS resolution check: google.com -> OK
 - CPU:
  Architecture:  x86_64
  CPU(s):  8
  Thread(s) per core:  2
  Core(s) per socket:  4
  Socket(s):  1
  CPU MHz:  2666.687
  Virtualization:  VT-x
 - RAM: 8.87 GB/15.71 GB in use (56%)
 - SWAP: 171.57 MB/510.99 MB in use (33%)
 - DISK: 157.04 GB/1.54 TB in use (9%)
 - Package versions:
  > libglib: 2.40.2-0ubuntu1

BOT INFORMATION
 - Status: running (PIDs: 21266 21264, User: ts3)
 - Webinterface: port locally reachable (Port: 8089)
 - Binary: /opt/sinusbot/sinusbot (Hash: 15b7bbe76f0eed63f13ad2dbcef391f7)
 - Version: 0.9.12-3f21a70
 - TS3 Plugin: installed (md5 hash match)
  - Bot Plugin: 13bef735b24191476df1de7d8dda2cad
  - TS3 Client: 13bef735b24191476df1de7d8dda2cad
 - Config:
  - LogLevel = 10 (debug log active)
  - TS3Path = /opt/sinusbot/TeamSpeak3-Client-linux_amd64/ts3client_linux_amd64 (Version 3.0.18.2)
  - YoutubeDLPath = /usr/local/bin/youtube-dl (does exist, version: 2016.06.27)
 - Installed Scripts: advertising.js; aloneMode.js; badchan.js; bookmark.js; covatar.js; dev.js; followme.js; idle.js; metadata.js; norecording.js; showcase.js; welcometext.js

OTHER INFORMATION
 - Report date: 29.06.2016 18:21:31 CEST +02:00:00 (timezone: Europe/Paris)
 - TeamSpeak 3 Version: 3.0.18.2
 - youtube-dl Version: 2016.06.27
 - DiagScript version: 0.4.5
==========================================================
 

mxschmitt

Moderator
Staff member
is awesome!
V.I.P.
is uber awesome!
Contributor
Insider
Known bug, which we unfortunately can not reproduce. We have a big amount of logs. (We still don´t need mooore). but thanks for the informations. :)
 

kanalumaddela

Insider
Insider
Known bug, which we unfortunately can not reproduce. We have a big amount of logs. (We still don´t need mooore). but thanks for the informations. :)
Same issue happens for me, the bot stops responding to commands after around 6-7 hours. Nothing shows in the logs, but I don't have to restart the entire sinusbot. I just have to restart a single instance (pressing the power on/off button in the web panel). So maybe it's a teamspeak client thing? I haven't check the client logs yet btw, but I probably will.
 

mxschmitt

Moderator
Staff member
is awesome!
V.I.P.
is uber awesome!
Contributor
Insider
Unfortunately you can find nothing in the Logs, but thanks for helping us.
 

Olof

Member
Getting the exact same issue, as said above only restarting the instance works.
The strange thing however is that I have 2 instances running and only one of them has the problem, so it might depend on the ts server.
But i'm not sure as to what level that is possible.

Edit: Seems that I had the problem come up again after reinstalling, but this time I had to reboot the whole server for it to start working again
 
Last edited:

kanalumaddela

Insider
Insider
As a quick fix for this issue, you could create a crontab to have the bots auto restart every 6 hours (since that's where it seems to stop responding). **This only works for those who have sinusbot running as a server**

Login as root/sudo and enter paste these commands.
Code:
crontab -e
Code:
0 0,6,12,18 * * * /etc/init.d/sinusbot restart

This is the script I used to run the bot as a service: https://forum.sinusbot.com/resources/linux-bootscript-for-the-sinusbot.6/
 
Status
Not open for further replies.
Top