Search results

So I have 2 music bots set to this radio station, one of them works all the time the other stops every 24 hours and I have to start it, anyway to prevent that?

NVM i guess you mean teamspeak version, will do.

Well it should be easy for you to find what you changed and exclude probabilities till you find what's causing it and change it? even if that means another pre-release before v1.0 as this is really a killer bug.

bump

this is output of Diagnostic script: ========================================================== SINUSBOT RELATED SYSTEM INFORMATION - Operating System: Ubuntu 14.04.4 LTS (OpenVZ) - OS x64 check: OK - Kernel: Linux 2.6.32-042stab115.2 x86_64 - Load Average: 1.22 1.25 1.38 - Uptime: 0...

This is what I see interesting in logs In bot log: 2016-07-16T14:42:24+03:00 Added EVListener 2016-07-16T14:03:27+03:00 Server seems broken or unreachable. Maybe ICY? Trying GET 2016-07-16T14:03:26+03:00 Server seems broken, doesn't understand us. Hopefully it's a stream...

How to detect what is wrong?

Not working, It's currently present and I won't restart cause mabe you want to see.

UPDATE: I tried to look at the console when !sub wasn't working, by that time the console is actually dead, anythig I do doesn't appear even tho the bots are working and streaming in channels/playing youtube links/using scripts.

It's quite old, friend gave it to me when I first downloaded sinusbot but works fine

Ok @Xuxe 's start script could somehow start it and it also worked, dunno dafuq it was tho.

100% clean reinstall again, it worked without license so i closed, added private.dat and added license and changed licensekey in config and then i get this mess when starting (didnt use start script this time)

Hello, I have 7 instances, one of them works perfectly the rest don't work even tho all are licensed and same and first time on server ( did clean reinstall of sinusbot cause !sub was being bugged ) example instance log of one unable to connect: Sometime they can connect but they have...

!sub doesn't work most of the time and if I restart it works then it's bugged again, also !subchan would be nice to see enabled in bot channel by default as I could've just crontabbed restart sinusbot and that would've fixed the issue.

>Yes I have a license >This RAM racking issue still exists. >I have to restart sinusbot every 24 hours.

Of course i do, this still happening by the way, restarting every 24 hours,

nothing man, just a plain ubuntu vps and latest sinusbot/ts3 client

3.0.19.1

still happening, forgot to restart for 48 hours due to exams and ended up with mysql crashed, 2 instances crashed, !sub not working and ram as seen

Happened 2 more times, it happens when the bot racks up ram for an unknown reason (created a thread for that) and is fixed by restart, i'm assuming whatever detects !sub is being closed down by the high ram usage.