Restarted Server now Sinusbot wont turn on?

[Neejrow]

Hello,

VPS: CentOS 7
Version: Sinusbot 0.9.8
Installed using: https://forum.sinusbot.com/resources/sinusbot-installer-script.58/

I have been running Sinusbot for over a month and have had no issues when restarting my VPS. However today I restarted my VPS and Sinusbot will not start up. In terminal it says it starts, but then when I check it's status it says it is not running.
Here is a log

[username@ts data]$ /etc/init.d/sinusbot status
sinusbot is DOWN
[username@ts data]$ /etc/init.d/sinusbot start
Using following data:
USER: username
DIR ROOT: /opt/ts3soundboard/
BOT RUN CMD: ./sinusbot

Starting sinusbot...
sinusbot started successfully
[username@ts data]$ /etc/init.d/sinusbot status
sinusbot is DOWN

I'm not familiar enough with Linux on how to troubleshoot this. I looked around for some sort of log that sinusbot might spit out but was unable to find anything.

Anyone able to help me out with this? Thanks.

 

[mxschmitt]

Please update to the latest beta

 

[Neejrow]

Please update to the latest beta

I have updated and both of the bots connected, but both of them had the no speakers symbol in Teamspeak. so I restarted Sinusbot via command line and now only 1 of the bots will connect but it is functioning.

Any idea why I can only get 1 bot connected now?

Also my Sinusbot version number says 0.9.16-10f0fad now so I assume thats the latest version?

 

[Xuxe]

Run ./sinusbot instead of ts3bot since you have Upgraded.

 

[Neejrow]

Run ./sinusbot instead of ts3bot since you have Upgraded.

I have always been using ./sinusbot ?

Still every time I restart the bot only 1 instance comes online. the 2nd one says it's turned on but is not joining Teamspeak.
Is there a way to view logs?

Edit: just viewing the instance logs on the bot that wont connect and it says this

2017-01-10T14:23:20+11:00 Ping failed.
2017-01-10T14:23:05+11:00 Starting instance ts3server://127.0.0.1?port=9987&nickname=SOCA%20Music%20%28music.soc-aus.net%29&password=&channel=&channelpassword=
2017-01-10T14:22:40+11:00 TSClient quit.
2017-01-10T14:22:40+11:00 KILL [admin] OK
2017-01-10T14:22:39+11:00 Could not request shutdown. Please make sure that the loopback interface is not firewalled; HTTP returned an error: Timeout; Code: 500; Message: Timeout
2017-01-10T14:22:25+11:00 SAMPLEX 3840 60
2017-01-10T14:22:24+11:00 BOT-CONFIG [admin] CHAN CHANPW ANNOUNCE DESCRIPTION ANNOUNCESTR TTSURL CC OK
2017-01-10T14:20:58+11:00 STOP [admin] OK
2017-01-10T14:16:13+11:00 Ping failed.
2017-01-10T14:16:13+11:00 Ping failed.
2017-01-10T14:16:04+11:00 Could not send description command: HTTP returned an error: Timeout; Code: 500; Message: Timeout
2017-01-10T14:16:02+11:00 Could not send description command: HTTP returned an error: Timeout; Code: 500; Message: Timeout
2017-01-10T14:15:58+11:00 Starting instance ts3server://127.0.0.1?port=9987&nickname=SOCA%20Music%20%28music.soc-aus.net%29&password=&channel=&channelpassword=

 

[Neejrow]

So I take it nobody else has any experience with this issue?

It's very strange. Even if I turn off the main bot instance, this second instance still will not connect and gives that error log in my post above.

Not exactly sure what to do now. Could this be a potential issue with the latest beta version?

 

[kanalumaddela]

It's very strange. Even if I turn off the main bot instance, this second instance still will not connect and gives that error log in my post above.

2017-01-10T14:15:58+11:00 Starting instance ts3server://127.0.0.1?port=9987&nickname=SOCA%20Music%20%28music.soc-aus.net%29&password=&channel=&channelpassword=

Is the bot on the same machine as the VPS, if not, then you didn't enter the IP/hostname

 

[Neejrow]

Is the bot on the same machine as the VPS, if not, then you didn't enter the IP/hostname

Yes the Bot is on the same server. And has worked flawlessly up until the other day when I did a VPS reset. However I had reset the VPS many times prior with Sinusbot on and it worked fine. Nothing had been changed on the VPS so I'm curious as to what has caused this issue.
Is there some sort of license that Sinusbot checks with a master server every time it starts, to force updates etc?

Going to get my mate who works with Linux for his job to have a look tonight, but it's really weird that 1 bot instance can connect but the other is timing out.

 

[krawol]

having the same issue but from the beggining.
i've never started a sinusbot yet.
any1 got some ideas?

 

[Neejrow]

having the same issue but from the beggining.
i've never started a sinusbot yet.
any1 got some ideas?

Hey mate. I still have not found a solution to this.

Going to try a full clean reinstall I guess. See if that works. I'll get back to you in a week or so when I get around to doing it.