• If you need help or want to discuss things, you now can also join us on our Discord Server!

Sinusbot startet nicht mehr nachdem ich eine lizenz eigenfügt habe

SiniSN

Donor
is awesome!
#1
Seitdem ich meine lizenz eingefügt habe kommt folgender fehler bei systemctl status sinusbot.service

sinusbot.service - Sinusbot, the Teamspeak 3 and Discord music bot.
Loaded: loaded (/lib/systemd/system/sinusbot.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2018-06-11 14:42:57 CEST; 8s ago
Process: 10834 ExecStopPost=/bin/rm -f /tmp/.sinusbot.lock (code=exited, status=1/FAILURE)
Process: 11090 ExecStartPre=/bin/rm -f /tmp/.sinusbot.lock (code=exited, status=1/FAILURE)
Main PID: 6018 (code=killed, signal=INT)
CPU: 3ms

Jun 11 14:42:57 GravityClan systemd[1]: Starting Sinusbot, the Teamspeak 3 and Discord music bot....
Jun 11 14:42:57 GravityClan systemd[1]: sinusbot.service: Control process exited, code=exited status=1
Jun 11 14:42:57 GravityClan systemd[1]: Failed to start Sinusbot, the Teamspeak 3 and Discord music bot..
Jun 11 14:42:57 GravityClan systemd[1]: sinusbot.service: Unit entered failed state.
Jun 11 14:42:57 GravityClan systemd[1]: sinusbot.service: Failed with result 'exit-code'.
 

SiniSN

Donor
is awesome!
#2
Diag Script:
Code:
SINUSBOT RELATED
SYSTEM INFORMATION
- Operating System: Debian GNU/Linux 9.4 (stretch)
- Kernel: Linux 4.9.0-6-amd64 x86_64
- Load Average: 0.22 0.26 0.32
- Uptime: 8 days, 16 hours, 37 minutes, 44 seconds
- OS x64 check: OK
- OS Updates: 0 (well done!)
- OS Missing Packages: None
- OS APT Last Update: 11.06.2018 04:02:45 CEST +02:00:00
- SHELL LOCALE LANG: de_DE.UTF-8
- Bot Start Script: not found
- DNS resolution check: www.sinusbot.com resolved to 104.18.40.220 -> OK
- HTTPS check with IPv4 mode: SUCCESS [Connection was established to www.sinusbot.com, CODE #200]
- HTTPS check with IPv6 mode: IGNORE
- CPU:
    CPU(s):                10
    CPU MHz:               2199.996
    Hypervisor-Anbieter:   KVM
- RAM: 8.84 GB/49.14 GB in use (17%)
- SWAP: 0 B/0 B in use (0%) (SWAP disabled)
- DISK: 53.34 GB/1.15 TB in use (4%)
- Package versions:
   + libglib: 2.50.3-2

BOT INFORMATION
- Status: not running
- Webinterface: port locally not reachable (Port: 8087)
- Binary: /opt/sinusbot/sinusbot
- Binary Info: MD5 Hash: f42a573b7435a8ff04da446d5ccbe754, Perms: 755, User: musikbot
- Version: 0.13.37-9791176
- TS3 Plugin: installed (md5 hash match)
   - Bot Plugin: 26551adc40e47c6d5d02517b8575d375
   - TS3 Client: 26551adc40e47c6d5d02517b8575d375
- Config:
   - LogLevel = 10 (debug log active)
   - TS3Path = /opt/sinusbot/teamspeak3-client/ts3client_linux_amd64 (Version 3.1.9)
   - YoutubeDLPath = /usr/local/bin/youtube-dl (does exist, version: 2018.06.04)
- Installed scripts: advertising.js; alonemode.js; bookmark.js; Digital_Clock.js; followme.js; norecording.js; rememberChannel.js; welcome.js

TIME INFORMATION
- Time (local): 11.06.2018 15:09:44 CEST +02:00:00
- Time (remote): <Failed retrieving remote time!>
- Time (difference): n/a secs
- Timezone: Europe/Berlin

OTHER INFORMATION
- TeamSpeak 3 Version: 3.1.9
- youtube-dl Version: 2018.06.04
- DiagScript Version: 0.7.1
==========================================================
 
Last edited by a moderator:

irgendwr

Advanced AI with blockchain technology (tm)
Staff member
V.I.P.
is awesome!
is uber awesome!
Contributor
Insider
#3
Überprüfe bitte ob:
und versuche es erneut.
Wenn das nicht klappt starte den bot manuell mit dem user sinusbot und schick den output hier rein.
 

SiniSN

Donor
is awesome!
#4
2018/06/11 16:28:58 X [MAIN] Starting up fake x-server...
2018/06/11 16:28:58 Could not open X11 socket. This happens either if the bot is already running or you ran it before using a different user (root?). Please make sure the bot is not running and delete /tmp/.X11-unix/X40 manually.
 

irgendwr

Advanced AI with blockchain technology (tm)
Staff member
V.I.P.
is awesome!
is uber awesome!
Contributor
Insider
#6
Hat auf jeden Fall nichts mit der Lizenz zu tun, irgendwas hast du da verhauen.
Hast du den bot ordner gechowned?
Lösch mal alle temp files: rm -rf /tmp/*