• 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.

Newest beta not running on Debian 8

DJ_Ironic

Active Member
  • SinusBot version: Latest Alpha (bot will not start, so I have no number)
  • TS client: again, newly updated
  • TS3 server: 3.7.0 NPL, 512 slots
  • OS: Debian 8 64-bit
  • HW: 1 vCPU, 2GB RAM - OVH CLOUD instance

    The Sinus Diag script:


    Code:
    ==========================================================
    SINUSBOT RELATED
    SYSTEM INFORMATION
     - Operating System: Debian GNU/Linux buster/sid
     - Kernel: Linux 3.16.0-4-amd64 x86_64
     - Load Average: 0.18 0.11 0.10
     - Uptime: 172 days, 3 hours, 33 minutes, 1 seconds
     - OS x64 check: OK
     - OS Updates: 368 (updates available!)
     - OS Missing Packages: None
     - OS APT Last Update: 25.03.2019 22:34:18 CET +01:00:00
     - SHELL LOCALE LANG: en_US.UTF-8
     - Bot Start Script: not found
     - DNS resolution check: www.sinusbot.com resolved to 104.28.15.74 -> OK
     - HTTPS check with IPv4 mode: SUCCESS [Connection was established to www.sinusbot.com, CODE #200]
     - HTTPS check with IPv6 mode: IGNORE
     - CPU:
        Architecture:          x86_64
        CPU(s):                1
        Thread(s) per core:    1
        Core(s) per socket:    1
        Socket(s):             1
        Model name:            Intel Core Processor (Haswell, no TSX)
        CPU MHz:               3092.838
        Hypervisor vendor:     KVM
        Virtualization type:   full
     - RAM: 351.19 MB/1.91 GB in use (17%)
     - SWAP: 0 B/0 B in use (0%) (SWAP disabled)
     - DISK: 8.35 GB/24.55 GB in use (34%)
     - Package versions:
       + libglib: 2.58.3-1
    
    BOT INFORMATION
     - Status: not running
     - Webinterface: port locally not reachable (Port: 8087)
     - Binary: /opt/sinusbot/sinusbot
     - Binary Info: MD5 Hash: cc7e9b1c61045377b221302a86be605e, Perms: 750, User: sinusbot
     - Version: 1.0.0-alpha.6-a47ac17
     - TS3 Plugin: installed (md5 hash mismatch!)
       - Bot Plugin: 59c9a688307aa73af9573029a7625fc5
       - TS3 Client: 0cb7720523475e509ea99d101804e5f0
     - Config:
       - LogLevel = 10 (debug log active)
       - TS3Path = /opt/sinusbot/TeamSpeak3-Client-linux_amd64/ts3client_linux_amd64 (Version 3.2.3)
       - YoutubeDLPath = /usr/local/bin/youtube-dl (does exist, version: 2018.12.17)
     - Installed scripts: advertising.js; alonemode.js; BadChannel.js; Bad_Nickname_Check.js; bookmark.js; command.js; followme.js; jukebox.js; norecording.js; rememberChannel.js; Tunakills_Rankingsystem.js; welcome.js
    
    TIME INFORMATION
     - Time (local): 25.03.2019 23:25:41 CET +01:00:00
     - Time (remote): <Failed retrieving remote time!>
     - Time (difference): n/a secs
     - Timezone: Europe/Paris
    
    OTHER INFORMATION
     - TeamSpeak 3 Version: 3.2.3
     - youtube-dl Version: 2018.12.17
     - DiagScript Version: 0.7.1
    ==========================================================
    '

    It looks like tha SinusBot instance is not able to work with libnss on Debian 8 again as nearly the same issue was on the first alpha 1.0 with Sinus.
    Here is the error ouputed when starting the service:

    Code:
    Mar 25 22:07:43 vpsX83XXX.ovh.net rm[31487]: (rm): relocation error: /lib/x86_64-linux-gnu/libnss_files.so.2: symbol __libc_readline_unlocked, version GLIBC_PRIVATE not defined in file libc.so.6 with link time referenceMar 25 22:07:43 vpsX83XXX.ovh.net systemd[1]: sinusbot.service: control process exited, code=exited status=127
    Mar 25 22:07:43 vpsX83XXX.ovh.net systemd[1]: Failed to start Sinusbot, the Teamspeak 3 and Discord music bot..
    Mar 25 22:07:43 vpsX83XXX.ovh.net systemd[1]: Unit sinusbot.service entered failed state.

    Any idea how to fix the issue? :) Thanks!
 
Top