• 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.
Sinusbot Installer Script

EN Sinusbot Installer Script 1.5

No permission to download

Qhiliqq

Donor
is awesome!
Contributor
Insider
Licensed Partner
Hallo.
habe leider auch das Problem, dass man Bot über den sinusbot Nutzer nicht starten will. Über root funktioniert es zwar, will es aber hinsichtlich schlechter Erfahrungen nicht machen.
bekomme das als Output:

sinusbot@vmd10630:/opt/sinusbot$ ./sinusbot
Could not open /tmp/.sinusbot.lock. Is SinusBot already running?
Sicher dass der Bot nicht schon läuft?
Mach mal "service sinusbot stop" (als root) oder "/etc/init.d/sinusbot stop"
 
Operating System: Linux
SinusBot Version: 0.9.x
TS3 Version: 3.x.x

Problem Description
hello dear users i cant enter sinusbot web interface via http://myip:8087/ error is : error connection timed out for google chrome and Opera. im using vps and i tried open port 8087 tcp and udp. 80 and 22 are also open. i tried many thing like that i cant remember exactly. im working 4 hour for solve this error.and im also newbie with linux. i used https://sinusbot-installer.de/ for install. please help for the solition. im not connect my server ts3 server yet .please help me :8

Code:
==========================================================
SINUSBOT RELATED
SYSTEM INFORMATION
- Operating System: Ubuntu 16.04.2 LTS
- OS x64 check: OK
- Kernel: Linux 4.4.0-66-generic x86_64
- Load Average: 0.23 0.12 0.04
- Uptime: 0 days, 1 hours, 3 minutes, 5 seconds
- OS Updates: 7 (updates available!)
- OS Missing Packages: None (v1)
- OS APT Last Update: 27.03.2017 17:08:33 UTC +00:00:00
- Bot Start Script: found at /etc/init.d/sinusbot [perms: 755]
- DNS resolution check: sinusbot.com resolved to 104.18.41.220 -> OK
- HTTPS check with IPv4 mode: SUCCESS [Connection was established to sinusbot.com]
- HTTPS check with IPv6 mode: FAILED  [Failed connecting to sinusbot.com]
- 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 @ 2.30GHz
    CPU MHz:               2300.000
    Hypervisor vendor:     KVM
    Virtualization type:   full
- RAM: 361.53 MB/3.61 GB in use (9%)
- SWAP: 0 B/0 B in use (0%) (SWAP disabled)
- DISK: 1.37 GB/8.23 GB in use (16%)
- Package versions:
   > libglib: 2.48.2-0ubuntu1

BOT INFORMATION
- Status: running (PIDs: 2944 2943, User: ...
sinusbot)
- Webinterface: port locally reachable (Port: 8087)
- Binary: /opt/sinusbot/sinusbot (MD5 Hash: aa67b784b83f5a7e66c60496f58d4a92)
- Version: 0.9.18-8499d2c
- TS3 Plugin: installed (md5 hash match)
   - Bot Plugin: d53693319c8922b95257ad4c6eacff69
   - TS3 Client: d53693319c8922b95257ad4c6eacff69
- Config:
   - LogLevel = 10 (debug log active)
   - TS3Path = /opt/sinusbot/teamspeak3-client/ts3client_linux_amd64 (Version 3.0.19.4)
   - YoutubeDLPath = /usr/local/bin/youtube-dl (does exist, version: 2017.03.26)
- 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; welcometext.js

OTHER INFORMATION
- Report date: 27.03.2017 18:18:41 UTC +00:00:00 (timezone: Etc/UTC)
- TeamSpeak 3 Version: 3.0.19.4
- youtube-dl Version: 2017.03.26
- DiagScript version: 0.5.1
==========================================================
My config.ini file
Code:
TS3Path = "/opt/sinusbot/teamspeak3-client/ts3client_linux_amd64"
ListenHost = "0.0.0.0"
DataDir = "/opt/sinusbot/data/"
ListenPort = 8087
LocalPlayback = false
EnableLocalFS = false
MaxBulkOperations = 300
LogLevel = 10
EnableProfiler = false
YoutubeDLPath = "/usr/local/bin/youtube-dl"
EnableDebugConsole = false
UploadLimit = 83886080
RunAsUser = 0
RunAsGroup = 0
InstanceActionLimit = 6
UseSSL = false
SSLKeyFile = ""
SSLCertFile = ""
Hostname = ""
SampleInterval = 60
StartVNC = false
EnableWebStream = false
LogFile = ""
LicenseKey = .......
IsProxied = false
DenyStreamURLs = []
Pragma = 0

[YoutubeDL]
  BufferSize = 524288
  MaxDownloadSize = 419430400
  MaxDownloadRate = 104857600
  CacheStreamed = false

[TS3]
  AvatarMaxWidth = 0
  AvatarMaxHeight = 0
  AllowGIF = false

[StreamRewrites]

[Scripts]
  AllowReload = false
  EnableTimer = false

[Themes]
  Default = ""

[SpeechRecognition]
  Enable = false

[FFmpeg]
  UserAgent = "SinusBot (0.9.18-8499d2c)"

[DAV]
  Enable = false

[XServer]
Results of netstat -tulpn
Code:
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:30033           0.0.0.0:*               LISTEN      1561/ts3server
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1609/sshd
tcp        0      0 0.0.0.0:10011           0.0.0.0:*               LISTEN      1561/ts3server
tcp6       0      0 :::30033                :::*                    LISTEN      1561/ts3server
tcp6       0      0 :::22                   :::*                    LISTEN      1609/sshd
tcp6       0      0 :::8087                 :::*                    LISTEN      2944/sinusbot
.
.
.
.
.
and more.
 
Last edited:
i solved the problem the problem is out put of installer installer says sinus bot is up on example.example.example.10:8087 this out put not the right thing to copy past google chrome u must write the adress line ur http://vpsip:8087
 

Koarl3

Member
sinusbot_installer.sh:
if [ "$OS" == "" ]; then
errorExit "Error: Could not detect OS. Currently only Debian, Ubuntu and CentOS are supported. Aborting!"
elif [ ! `cat /etc/debian_version | grep "7"` == "" ]; then
errorExit "Debian 7 isn't supported anymore!"
else
greenMessage "Detected OS $OS"

fi

root@tsbot:~# cat /etc/debian_version
8.7


....
 

Qhiliqq

Donor
is awesome!
Contributor
Insider
Licensed Partner
sinusbot_installer.sh:
if [ "$OS" == "" ]; then
errorExit "Error: Could not detect OS. Currently only Debian, Ubuntu and CentOS are supported. Aborting!"
elif [ ! `cat /etc/debian_version | grep "7"` == "" ]; then
errorExit "Debian 7 isn't supported anymore!"
else
greenMessage "Detected OS $OS"

fi

root@tsbot:~# cat /etc/debian_version
8.7


....
Use the latest installer guy...


/dev/fd/63: line 586: syntax error near unexpected token `fi'
/dev/fd/63: line 586: ` fi'


was ist das?
wurde schon lange gefixt, bitte nutze den neusten installer.

Not working anymore... 403 link expired
Use new link. The link has an expiration time of 15 minutes.
 

Qhiliqq

Donor
is awesome!
Contributor
Insider
Licensed Partner
Ist seit 08:07 Uhr wieder online.
Es gab Rechenzentrum Probleme.

Ich bitte um Entschuldigung.
 

KiurZima123

New Member
Operating System: Windows / Linux
SinusBot Version: 0.9.x
TS3 Version: 3.x.x

Problem Description
Describe your problem in detail. What did you do exactly, what did you expect to happen and what did actually happen?
Hello i've a bug with my sinusbot when i want to start it:

sinusbot.service - Sinusbot the Teamspeak 3 and Discord MusicBot.
Loaded: loaded (/etc/systemd/system/sinusbot.service; enabled)
Active: inactive (dead) since Wed 2017-04-12 20:37:31 CEST; 58s ago
Process: 2555 ExecStart=/opt/sinusbot/sinusbot (code=exited, status=0/SUCCESS)
Main PID: 2555 (code=exited, status=0/SUCCESS)

Apr 12 20:37:31 vps397550.ovh.net systemd[1]: Started Sinusbot the Teamspeak....
Apr 12 20:37:31 vps397550.ovh.net sinusbot[2555]: 2017/04/12 20:37:31 The par...
Hint: Some lines were ellipsized, use -l to show in full.

Code:
Paste output of the diagnostic tool in here, if possible.
 

Nebula

Member
Helft mir bitte, bei mir wurde der Bot support funktioniert es gab keine Fehlermeldung aber wenn ich dann per Firefox/Chrome auf den Bot zugreifen möchte kommt folgende Fehlermeldung: Firefox kann keine Verbindung zu dem Server unter 31.172.80.39:8087 aufbauen.
 

Diesmon

Tuetchen Dominator
is awesome!
Contributor
Insider
Helft mir bitte, bei mir wurde der Bot support funktioniert es gab keine Fehlermeldung
Was auch immer du damit sagen willst...

aber wenn ich dann per Firefox/Chrome auf den Bot zugreifen möchte kommt folgende Fehlermeldung: Firefox kann keine Verbindung zu dem Server unter 31.172.80.39:8087 aufbauen.
Klingt stark danach das der Bot nicht läuft.

Ich nehme mal an das du den Bot unter Linux mit diesem Installer Script installiert hast. Wenn ja geh in das Verzeichnis wo du ihn hin installiert hast und führe dann (in der console) folgendes commando aus "./sinusbot start" ohne die "".

Daraufhin sollte der Bot starten und erreichbar sein. Wenn ja musst du den Bot Prozess nur noch per screen anpinnen und er sollte dauerhaft laufen.

Wenn nein.. tja dann gucken...
 

Kagotza

New Member
Hello,

I'm running into a problem while using the Sinusbot Installscript. It's the first time I've used it. The installation was successful except for the end, when it tried to start sinusbot. The error message was:
sinusbot[16344]: Could not open /tmp/.sinusbot.lock. Is SinusBot already running?

Trying to restart it by hand gives out the same message:
[ root@astra5078 ~ ] service sinusbot status
● sinusbot.service - Sinusbot the Teamspeak 3 and Discord MusicBot.
Loaded: loaded (/etc/systemd/system/sinusbot.service; enabled)
Active: failed (Result: exit-code) since Thu 2017-04-13 19:18:40 CEST; 2min 26s ago
Process: 15859 ExecStart=/opt/sinusbot/sinusbot (code=exited, status=255)
Main PID: 15859 (code=exited, status=255)

Apr 13 19:18:40 astra5078 systemd[1]: Started Sinusbot the Teamspeak 3 and Discord MusicBot..
Apr 13 19:18:40 astra5078 sinusbot[15859]: Could not open /tmp/.sinusbot.lock. Is SinusBot already running?
Apr 13 19:18:40 astra5078 systemd[1]: sinusbot.service: main process exited, code=exited, status=255/n/a
Apr 13 19:18:40 astra5078 systemd[1]: Unit sinusbot.service entered failed state.
[ root@astra5078 ~ ] service sinusbot start
[ root@astra5078 ~ ] service sinusbot status
● sinusbot.service - Sinusbot the Teamspeak 3 and Discord MusicBot.
Loaded: loaded (/etc/systemd/system/sinusbot.service; enabled)
Active: failed (Result: exit-code) since Thu 2017-04-13 19:21:13 CEST; 6s ago
Process: 16344 ExecStart=/opt/sinusbot/sinusbot (code=exited, status=255)
Main PID: 16344 (code=exited, status=255)

Apr 13 19:21:13 astra5078 systemd[1]: Started Sinusbot the Teamspeak 3 and Discord MusicBot..
Apr 13 19:21:13 astra5078 sinusbot[16344]: Could not open /tmp/.sinusbot.lock. Is SinusBot already running?
Apr 13 19:21:13 astra5078 systemd[1]: sinusbot.service: main process exited, code=exited, status=255/n/a
Apr 13 19:21:13 astra5078 systemd[1]: Unit sinusbot.service entered failed state.

I have checked all my screen sessions and processes. Sinusbot is not already running anywhere.
Anyone got a clue?

//Edit:
I'm running it on Debian 8 if that makes a difference.
 

Qhiliqq

Donor
is awesome!
Contributor
Insider
Licensed Partner
Operating System: Windows / Linux
SinusBot Version: 0.9.x
TS3 Version: 3.x.x

Problem Description
Describe your problem in detail. What did you do exactly, what did you expect to happen and what did actually happen?
Hello i've a bug with my sinusbot when i want to start it:

sinusbot.service - Sinusbot the Teamspeak 3 and Discord MusicBot.
Loaded: loaded (/etc/systemd/system/sinusbot.service; enabled)
Active: inactive (dead) since Wed 2017-04-12 20:37:31 CEST; 58s ago
Process: 2555 ExecStart=/opt/sinusbot/sinusbot (code=exited, status=0/SUCCESS)
Main PID: 2555 (code=exited, status=0/SUCCESS)

Apr 12 20:37:31 vps397550.ovh.net systemd[1]: Started Sinusbot the Teamspeak....
Apr 12 20:37:31 vps397550.ovh.net sinusbot[2555]: 2017/04/12 20:37:31 The par...
Hint: Some lines were ellipsized, use -l to show in full.

Code:
Paste output of the diagnostic tool in here, if possible.
Öhm.
Some more informations please...

Hello,

I'm running into a problem while using the Sinusbot Installscript. It's the first time I've used it. The installation was successful except for the end, when it tried to start sinusbot. The error message was:
sinusbot[16344]: Could not open /tmp/.sinusbot.lock. Is SinusBot already running?

Trying to restart it by hand gives out the same message:
[ root@astra5078 ~ ] service sinusbot status
● sinusbot.service - Sinusbot the Teamspeak 3 and Discord MusicBot.
Loaded: loaded (/etc/systemd/system/sinusbot.service; enabled)
Active: failed (Result: exit-code) since Thu 2017-04-13 19:18:40 CEST; 2min 26s ago
Process: 15859 ExecStart=/opt/sinusbot/sinusbot (code=exited, status=255)
Main PID: 15859 (code=exited, status=255)

Apr 13 19:18:40 astra5078 systemd[1]: Started Sinusbot the Teamspeak 3 and Discord MusicBot..
Apr 13 19:18:40 astra5078 sinusbot[15859]: Could not open /tmp/.sinusbot.lock. Is SinusBot already running?
Apr 13 19:18:40 astra5078 systemd[1]: sinusbot.service: main process exited, code=exited, status=255/n/a
Apr 13 19:18:40 astra5078 systemd[1]: Unit sinusbot.service entered failed state.
[ root@astra5078 ~ ] service sinusbot start
[ root@astra5078 ~ ] service sinusbot status
● sinusbot.service - Sinusbot the Teamspeak 3 and Discord MusicBot.
Loaded: loaded (/etc/systemd/system/sinusbot.service; enabled)
Active: failed (Result: exit-code) since Thu 2017-04-13 19:21:13 CEST; 6s ago
Process: 16344 ExecStart=/opt/sinusbot/sinusbot (code=exited, status=255)
Main PID: 16344 (code=exited, status=255)

Apr 13 19:21:13 astra5078 systemd[1]: Started Sinusbot the Teamspeak 3 and Discord MusicBot..
Apr 13 19:21:13 astra5078 sinusbot[16344]: Could not open /tmp/.sinusbot.lock. Is SinusBot already running?
Apr 13 19:21:13 astra5078 systemd[1]: sinusbot.service: main process exited, code=exited, status=255/n/a
Apr 13 19:21:13 astra5078 systemd[1]: Unit sinusbot.service entered failed state.

I have checked all my screen sessions and processes. Sinusbot is not already running anywhere.
Anyone got a clue?

//Edit:
I'm running it on Debian 8 if that makes a difference.
Maybe @Xuxe knows something... The startscript is made by him...
 

Qhiliqq

Donor
is awesome!
Contributor
Insider
Licensed Partner
Daraufhin sollte der Bot starten und erreichbar sein. Wenn ja musst du den Bot Prozess nur noch per screen anpinnen und er sollte dauerhaft laufen.
Oder einfach Startcommands nutzen ;) Weiss nicht was er installiert hat init.d oder systemd!?

Helft mir bitte, bei mir wurde der Bot support funktioniert es gab keine Fehlermeldung aber wenn ich dann per Firefox/Chrome auf den Bot zugreifen möchte kommt folgende Fehlermeldung: Firefox kann keine Verbindung zu dem Server unter 31.172.80.39:8087 aufbauen.
systemd oder init.d?
 

KiurZima123

New Member
Hello, I have a very big worries with Sinusbot ...
My Sinusbot does not want to start with "service sinusbot start" nor with the update via the script ... When I do "service sinusbot status" I get this error, it's the same after the update --" :

systemd already exists!
● sinusbot.service - Sinusbot the Teamspeak 3 and Discord MusicBot.
Loaded: loaded (/etc/systemd/system/sinusbot.service; enabled)
Active: inactive (dead) since Thu 2017-04-13 12:00:15 CEST; 1min 44s ago
Main PID: 441 (code=exited, status=0/SUCCESS)

Apr 13 12:00:14 vps397550.ovh.net systemd[1]: Started Sinusbot the Teamspeak 3 and Discord MusicBot..
Apr 13 12:00:15 vps397550.ovh.net sinusbot[441]: 2017/04/13 12:00:15 The parameter '-RunningAsRootIsEvilAndI...ons.
Apr 13 12:00:34 vps397550.ovh.net systemd[1]: [/etc/systemd/system/sinusbot.service:7] Executable path is no...lock
Apr 13 12:00:34 vps397550.ovh.net systemd[1]: [/etc/systemd/system/sinusbot.service:8] Executable path is no...lock
Hint: Some lines were ellipsized, use -l to show in full.
Sinusbot already stopped.
Installing Cronjob for automatic Sinusbot update...
Installing Sinusbot update cronjob successful.
YouTube-DL already installed. Checking for updates.
youtube-dl is up-to-date (2017.04.11)
Please wait... This will take some seconds!
Sinusbot could not start! Starting it directly. Look for errors!
2017/04/13 12:02:05 The parameter '-RunningAsRootIsEvilAndIKnowThat' has been disabled for security reasons.


This is problematic for me, I hope you will help me :)

I've a linux Deban 8 Jessie
 

Qhiliqq

Donor
is awesome!
Contributor
Insider
Licensed Partner
I can't reproduce this error.
Seems that the sinusbot.service use the installer instead the sinusbot file.

Please send the sinusbot.service incrediments here...
Located under /etc/systemd/system/
 

KiurZima123

New Member
[Unit]
Description=Sinusbot the Teamspeak 3 and Discord MusicBot.
After=syslog.target network.target
[Service]
User=sinusbot
ExecStartPre=rm -f /tmp/.sinusbot.lock
ExecStopPost=rm -f /tmp/.sinusbot.lock
ExecStart=/opt/sinusbot/sinusbot
WorkingDirectory=/opt/sinusbot
Type=simple
KillSignal=2
SendSIGKILL=yes

[Install]
WantedBy=multi-user.target
 

Nebula

Member
Can you please help me ? It say me :

Failed to start sinusbot.service: Unit sinusbot.service failed to load: Invalid argument. See system logs and 'systemctl status sinusbot.service' for details.
Please wait... This will take some seconds!
Sinusbot could not start! Starting it directly. Look for errors!
Could not open /tmp/.sinusbot.lock. Is SinusBot already running?
 
Top