Solved Sinusbot License doesnt have ip/Hostname

[Dimarzio]

Operating System: Windows / Linux
SinusBot Version: 0.10.6-ea49bdc
TS3 Version: 3.0.19.4

Problem Description
I reinstall the bot 3 times and i add my license to have all my instances back and when i try to connect them back it show me this Error
Instance not configured properly. Need at least host/ip, port and nickname.

I try to add the ip or host and i cant because it change my mouse to a / in a circle.

It shows that the licenses have no ip or hostname maybe the license is the problem because the 2 instances by default work fine.

SOLUTION: Update sinusbot version to the latest version in this case: 0.10.7 If someone have troubles like me after installation any startscript shows error delete the user where you run the bot, old startscript, and optional reboot the vps, my error was because in cache memory was stored something about a process of the old bot installation with the startscript.

Thats only
my humble opinion to fix it because it works for me hope the post helps others in case you have a similar problem. Thanks @flyth

 

[Dimarzio]

@flyth should i request a new license ? The bot works fine but only the extra instances are without ip so they cant connect to the server and i cant modify them.

 

[flyth]

Please redownload the latest version (0.10.7), that should fix it.

 

[Dimarzio]

Please redownload the latest version (0.10.7), that should fix it.

Can you leave a link for the latest version, maybe y download a old one

 

[flyth]

https://www.sinusbot.com/dl/sinusbot-beta.tar.bz2

 

[Dimarzio]

I reinstall it and is all okay but when i use a startscript and i run the command service sinusbot start it shows this:

Job for sinusbot.service failed because the control process exited with error code. See "systemctl status sinusbot.service" and "journalctl -xe" for details.

I run the command: systemctl status sinusbot.service and it shows this:

sinusbot.service - LSB: Sinusbot
Loaded: loaded (/etc/init.d/sinusbot; bad; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2017-10-05 20:06:15 EDT; 11min a
Docs: man:systemd-sysv-generator(8)
Process: 1231 ExecStart=/etc/init.d/sinusbot start (code=exited, status=1/FAIL

Oct 05 20:06:13 dim sinusbot[1231]: BOT RUN CMD: ./sinusbot
Oct 05 20:06:15 dim sinusbot[1231]: Starting sinusbot...
Oct 05 20:06:15 dim su[1238]: Successful su for sinusbot by root
Oct 05 20:06:15 dim su[1238]: + ??? root:sinusbot
Oct 05 20:06:15 dim su[1238]: pam_unix(su:session): session opened for user sinu
Oct 05 20:06:15 dim sinusbot[1231]: sinusbot is already running
Oct 05 20:06:15 dim systemd[1]: sinusbot.service: Control process exited, code=e
Oct 05 20:06:15 dim systemd[1]: Failed to start LSB: Sinusbot.
Oct 05 20:06:15 dim systemd[1]: sinusbot.service: Unit entered failed state.
Oct 05 20:06:15 dim systemd[1]: sinusbot.service: Failed with result 'exit-code'

I start the bot with command ./sinusbot i try to play music or use scripts and nothing works all permisions are ok

 

[flyth]

I start the bot with command ./sinusbot i try to play music or use scripts and nothing works all permisions are ok

Please post some logs from the bot itself, logs from the init script won't help here

 

[Dimarzio]

Sure i will post logs, but i need to change the bot log level to number 10 right ? I never use the log because i just reinstall it when i have troubles. If you can give me some tips to make the bot show logs i will post them. Thanks for your time.

 

[Diesmon]

I never use the log because i just reinstall it when i have troubles.

GeGe... WP, no re

 

[Dimarzio]

GeGe... WP, no re

dude if i always did it right, i never use the log i just dont remember how to activate it, i will activate it and post it, or i will try to solve it by my self xD

 

[irgendwr]

i never use the log i just dont remember how to activate it

log messages are available either in the webinterface or in your CLI when you start the sinusbot manually with the correct user.

 

[Dimarzio]

log messages are available either in the webinterface or in your CLI when you start the sinusbot manually with the correct user.

I check all the logs in web interface and on my terminal but i didnt see critical errors or something weird, i will post the log in some hours when i get out of work, maybe the instalation broke with the startscript because it was running with no problems with the version 0.10.6 or maybe is my error i will check all the posibilities and i will leave a log posted