• 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 start/stop

Status
Not open for further replies.

asdf1414

Donor
is awesome!
Betriebssystem: Linux
SinusBot Version: 0.9.16-10f0fad
TS3 Version: 3.1.1.1

Ich habe den Sinusbot mittels des Sinusbot-Installers installiert und das ganze läuft auch. Danach wollte ich den Sinusbot stoppen um die lizenz datei hochzuladen, die mir 4 weitere Sinusbots gibt. Das ganze habe ich mit den Commands "service sinusbot stop" bzw "service sinusbot start" gemacht und es kam der Fehler, ich solle hier nachschauen: "systemctl status sinusbot.service"
Code:
● sinusbot.service - LSB: Sinusbot
   Loaded: loaded (/etc/init.d/sinusbot)
   Active: failed (Result: exit-code) since Sat 2017-03-04 16:16:25 CET; 9s ago
  Process: 5748 ExecStart=/etc/init.d/sinusbot start (code=exited, status=1/FAILURE)

Mar 04 16:16:23 sinusbot[5748]: BOT RUN CMD: ./sinusbot
Mar 04 16:16:25 sinusbot[5748]: Starting sinusbot...
Mar 04 16:16:25 su[5753]: Successful su for sinusbot by root
Mar 04 16:16:25 su[5753]: + ??? root:sinusbot
Mar 04 16:16:25 su[5753]: pam_unix(su:session): session opened for user sinusbot by (uid=0)
Mar 04 16:16:25 su[5753]: pam_unix(su:session): session closed for user sinusbot
Mar 04 16:16:25 sinusbot[5748]: sinusbot is already running
Mar 04 16:16:25 systemd[1]: sinusbot.service: control process exited, code=exited status=1
Mar 04 16:16:25 systemd[1]: Failed to start LSB: Sinusbot.
Mar 04 16:16:25 systemd[1]: Unit sinusbot.service entered failed state.


Fehlerbehebungs-Script Output
Code:
==========================================================
SINUSBOT RELATED
SYSTEM INFORMATION
- Operating System: Debian GNU/Linux 8.7 (jessie)
- OS x64 check: OK
- Kernel: Linux 3.16.0-4-amd64 x86_64
- Load Average: 0.38 0.25 0.20
- Uptime: 1 days, 20 hours, 43 minutes, 12 seconds
- OS Updates: 0 (well done!)
- OS Missing Packages: None (v1)
- OS APT Last Update: 04.03.2017 15:48:09 CET +01:00:00
- Bot Start Script: found at /etc/init.d/sinusbot [perms: 755]
- DNS resolution check: sinusbot.com resolved to 104.18.40.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):                16
    Thread(s) per core:    2
    Core(s) per socket:    8
    Socket(s):             1
    Model name:            Intel(R) Xeon(R) CPU D-1540 @ 2.00GHz
    CPU MHz:               1576.093
    Virtualization:        VT-x
- RAM: 1.55 GB/62.95 GB in use (2%)
- SWAP: 0 B/15.25 GB in use (0%)
- DISK: 1.87 GB/1.69 TB in use (0%)
- Package versions:
   > libglib: 2.42.1-1+b1

BOT INFORMATION
- Status: running (PIDs: 5581 5579, User: sinusbot)
- Webinterface: port locally reachable (Port: 8087)
- Binary: /opt/sinusbot/sinusbot (MD5 Hash: 0005c8c289b99913844c9f761dbb50e9)
- Version: 0.9.16-10f0fad
- TS3 Plugin: installed (md5 hash match)
   - Bot Plugin: 28b54596e19937601df973b709aa0667
   - TS3 Client: 28b54596e19937601df973b709aa0667
- Config:
   - LogLevel = 3
   - TS3Path = /opt/sinusbot/teamspeak3-client/ts3client_linux_amd64 (Version 3.0.19.4)
   - YoutubeDLPath = /usr/local/bin/youtube-dl (does exist, version: 2017.03.02)
- 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: 04.03.2017 16:19:45 CET +01:00:00 (timezone: Europe/Berlin)
- TeamSpeak 3 Version: 3.0.19.4
- youtube-dl Version: 2017.03.02
- DiagScript version: 0.5.0
==========================================================
 
Status
Not open for further replies.
Top