Betriebssystem: Linux Debian 8
SinusBot Version: 0.9.18
TS3 Version: 3.0.19.4
Problembeschreibung
Hallo Community,
ich habe meinen SInusbot gerade erst installiert doch leider joint der Sinusbot keinem TS3Server
SinusBot Version: 0.9.18
TS3 Version: 3.0.19.4
Problembeschreibung
Hallo Community,
ich habe meinen SInusbot gerade erst installiert doch leider joint der Sinusbot keinem TS3Server
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.03 0.09 0.04
- Uptime: 0 days, 0 hours, 33 minutes, 10 seconds
- OS Updates: 0 (well done!)
- OS Missing Packages: None (v1)
- OS APT Last Update: 25.04.2017 18:17:29 CEST +02:00:00
- Bot Start Script: not found
- 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): 2
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
Model name: Common KVM processor
CPU MHz: 3199.998
Hypervisor vendor: KVM
Virtualization type: full
- RAM: 281.21 MB/3.77 GB in use (7%)
- SWAP: 0 B/3.08 GB in use (0%)
- DISK: 3.24 GB/63.80 GB in use (5%)
- Package versions:
> libglib: 2.42.1-1+b1
BOT INFORMATION
- Status: not running
- Webinterface: port locally reachable (Port: 8087)
- Binary: /opt/ts3soundboard/sinusbot (MD5 Hash: aa67b784b83f5a7e66c60496f58d4a92)
- Version: 0.9.18-8499d2c
- TS3 Plugin: installed (md5 hash match)
- Bot Plugin: d53693319c8922b95257ad4c6eacff69
- TS3 Client: d53693319c8922b95257ad4c6eacff69
- Config:
- LogLevel = 3
- TS3Path = /opt/ts3soundboard/TeamSpeak3-Client-linux_amd64/ts3client_linux_amd64 (Version 3.0.19.4)
- YoutubeDLPath = not set (does exist anyway, version: 2017.04.17)
- Installed scripts: advertising.js; aloneMode.js; Animated Nickname.js; badchan.js; bookmark.js; covatar.js; dev.js; followme.js; idle.js; metadata.js; norecording.js; rememberChannel.js; showcase.js; sound.js; verify.js; welcometext.js
OTHER INFORMATION
- Report date: 25.04.2017 19:16:29 CEST +02:00:00 (timezone: Europe/Berlin)
- TeamSpeak 3 Version: 3.0.19.4
- youtube-dl Version: 2017.04.17
- DiagScript version: 0.5.1
==========================================================
Code:
2017/04/25 19:21:29 df1a96b1 371d8397 INFO Starting instance ts3server://blackdzn.eu?port=9987&nickname=I%20%E2%99%A5%20Radio%20%C4%B1l%C4%B1l&password=&cid=399&channelpassword=
2017/04/25 19:21:29 X [MAIN] New connection
2017/04/25 19:21:29 df1a96b1 371d8397 INFO TS |INFO | | |TeamSpeak 3 Client 3.0.19.4 (2016-07-14 10:16:58)
2017/04/25 19:21:29 df1a96b1 371d8397 INFO TS |INFO | | |SystemInformation: Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 Binary: 64bit
2017/04/25 19:21:29 X [MAIN] New connection
2017/04/25 19:21:29 df1a96b1 371d8397 INFO TS |ERROR |PulseAudio | |pa_context_connect failed
2017/04/25 19:21:29 df1a96b1 371d8397 INFO TS |ERROR |SoundBckndIntf| |/opt/ts3soundboard/TeamSpeak3-Client-linux_amd64/soundbackends/libpulseaudio_linux_amd64.so error: INIT_PA_IMPL
2017/04/25 19:21:29 df1a96b1 371d8397 INFO TS |INFO | | |Loading plugin: libclientquery_plugin
2017/04/25 19:21:29 df1a96b1 371d8397 INFO TS |INFO | | |Loading plugin: liblua_plugin
2017/04/25 19:21:29 df1a96b1 371d8397 INFO TS |INFO | | |Loading plugin: libsoundbot_plugin
2017/04/25 19:21:29 df1a96b1 371d8397 INFO TS |INFO | | |Loading plugin: libtest_plugin
2017/04/25 19:21:29 df1a96b1 371d8397 INFO TS |INFO |Query | |listening on 127.0.0.1:25639
2017/04/25 19:21:30 X [MAIN] New connection
2017/04/25 19:21:30 df1a96b1 371d8397 INFO TS |INFO |ClientUI | |Failed to init text to speech engine
2017/04/25 19:21:30 df1a96b1 371d8397 INFO TS |INFO |ClientUI | |Qt version: 5.5.1
2017/04/25 19:21:30 df1a96b1 371d8397 INFO TS |INFO |ClientUI | |Using configuration location: /opt/ts3soundboard/data/ts3/df1a96b1-bb6f-4a69-833b-fffa12159362/371d8397-7909-4f46-8b97-eef7b2842406/settings.db
2017/04/25 19:21:30 df1a96b1 371d8397 INFO TS |INFO |ClientUI | |ts3server: blackdzn.eu?port=9987&nickname=I%20%E2%99%A5%20Radio%20%C4%B1l%C4%B1l&password=&cid=399&channelpassword=
2017/04/25 19:21:30 df1a96b1 371d8397 INFO TS |INFO |ClientUI |1 |Connect to server: blackdzn.eu
2017/04/25 19:21:30 df1a96b1 371d8397 INFO TS |INFO |ClientUI |1 |Trying to resolve blackdzn.eu
2017/04/25 19:21:30 df1a96b1 371d8397 INFO TS |INFO |TSDNS | |DNS resolve successful, "blackdzn.eu"=104.31.75.78
2017/04/25 19:21:30 df1a96b1 371d8397 INFO TS |INFO |TSDNS | |SRV DNS resolve successful, "_ts3._udp.blackdzn.eu"=>"dc-a65d81e33bc0.blackdzn.eu:9988" = 149.202.157.178:9988
2017/04/25 19:21:30 df1a96b1 371d8397 INFO TS |INFO |ClientUI |1 |Lookup finished: 149.202.157.178 9988 blackdzn.eu 0 0
2017/04/25 19:21:30 df1a96b1 371d8397 INFO TS |INFO |ClientUI |1 |Resolve successful: 149.202.157.178:9988
2017/04/25 19:21:30 df1a96b1 371d8397 INFO TS |INFO |ClientUI |1 |Blacklist check ok
2017/04/25 19:21:30 df1a96b1 371d8397 INFO TS |INFO |ClientUI |1 |Initiating connection: 149.202.157.178:9988 blackdzn.eu
2017/04/25 19:21:30 df1a96b1 371d8397 INFO TS |INFO |PreProSpeex |1 |Speex version: 1.2rc1
2017/04/25 19:21:31 df1a96b1 371d8397 INFO TS |INFO |ClientUI |1 |Connect status: Connecting
2017/04/25 19:21:31 df1a96b1 371d8397 INFO TS |INFO |ClientUI | |Last update check was: Di. Jan. 1 00:00:01 2019
2017/04/25 19:21:31 df1a96b1 371d8397 INFO TS |INFO |ClientUI | |Checking for update
2017/04/25 19:21:31 df1a96b1 371d8397 INFO New connection status 1; Error 0
2017/04/25 19:21:31 df1a96b1 371d8397 INFO TS |DEVELOP |PktHandler | |Puzzle solve time: 3
2017/04/25 19:21:31 df1a96b1 371d8397 INFO TS |INFO |Update | |Checking for updates...
2017/04/25 19:21:31 df1a96b1 371d8397 INFO TS |INFO |ClientUI |1 |Connect status: Disconnected
2017/04/25 19:21:31 df1a96b1 371d8397 INFO TS |INFO |ClientUI |1 |Disconnected or forced to leave, want autoreconnect = 0
2017/04/25 19:21:31 df1a96b1 371d8397 INFO The bot could not connect. This might have several reasons: the server doesn't exist at that address, the server password is wrong, the default channel doesn't exist, the bot has been banned, the server is an illegal installation or the password is wrong , the security level of your identity is too low or your client version is outdated (the server doesn't allow it anymore).
2017/04/25 19:21:31 df1a96b1 371d8397 INFO New connection status 0; Error 0
2017/04/25 19:21:31 df1a96b1 371d8397 INFO TS |INFO |Update | |Check license version: 1
2017/04/25 19:21:31 df1a96b1 371d8397 INFO TS |INFO |LicenseViewer | |License language: en
2017/04/25 19:21:31 df1a96b1 371d8397 INFO TS |INFO |LicenseViewer | |Found cached license for version 1 and language en
2017/04/25 19:21:32 df1a96b1 371d8397 INFO TSClient quit.