• If you need help or want to discuss things, you now can also join us on our Discord Server!
  • Happy New Year everyone! A new version (1.0.0-beta.16) is out for Linux, fixing an issue that could lock the bot up when using it with TS3. Please visit the resources section or the main page (https://www.sinusbot.com) for the new package.

Solved TS Client startet nicht | xcb

Status
Not open for further replies.

Flybel

Member
Betriebssystem: Linux (debian 8)
(SinusBot Version: Beta 0.9.16-10f0fad)
TS3 Version: 3.0.19.4 (neuste)
HW: 1 vCore (feste Taktrate); 3GB RAM; 300+GB Festplatte frei

Problembeschreibung
Ich habe meinen TS3-Server und Sinusbot von meinem alten debian8-Server auf einen neuen debian8-Server verschoben. Den TeamSpeak-Client habe ich dann neu installiert und den Dateipfad in der Sinusbot-Config angepasst. Der Server läuft bereits. Doch wenn der Bot verbinden will und wenn man ohne Bot
Code:
./TeamSpeak3-Client-linux_amd64/ts3client_runscript.sh start
ausführt, kommt nachfolgender Fehler.
Als dieser Fehler auftauchte habe ich xcb wie in den Sinusbot-Logs mit apt-get installiert. Der Fehler blieb trotzdem. Den TS-Client zu entfernen und neu zu installieren brachte nichts, ebenso wenig ein Reboot.

Code:
[email protected]:~$ ./TeamSpeak3-Client-linux_amd64/ts3client_runscript.sh start
This application failed to start because it could not find or load the Qt platform plugin "xcb".

Available platform plugins are: xcb.

Reinstalling the application may fix this problem.
./TeamSpeak3-Client-linux_amd64/ts3client_runscript.sh: Zeile 17:  1081 Abgebrochen             ./ts3client_linux_amd64 [email protected]

Wie bereits erwähnt habe ich die Anwendung schon erfolglos neu installiert.
 

Xuxe

Containerholic
Staff member
is awesome!
V.I.P.
Contributor
Insider
[email protected]:~$ ./TeamSpeak3-Client-linux_amd64/ts3client_runscript.sh start This application failed to start because it could not find or load the Qt platform plugin "xcb". Available platform plugins are: xcb. Reinstalling the application may fix this problem. ./TeamSpeak3-Client-linux_amd64/ts3client_runscript.sh: Zeile 17: 1081 Abgebrochen ./ts3client_linux_amd64 [email protected]

Ist ganz Normal da der Client ohne dem LD_LIBRARY_PATH nicht läuft:

Code:
export LD_LIBRARY_PATH=/path/ts3client/directory

... und dann Starten. - Da kümmert sich der Bot btw selbst drum das ist nicht das Problem wenn der Client per Console nun startet und es per Bot nach wie vor nicht geht.

Poste bitte Bot Logs und output des Diagnose Scripts hier.
 

Flybel

Member
Ohne dass der Bot läuft:
Code:
==========================================================
SINUSBOT RELATED
SYSTEM INFORMATION
- Operating System: Debian GNU/Linux 8.6 (jessie)
- OS x64 check: OK
- Kernel: Linux 3.16.0-4-amd64 x86_64
- Load Average: 0.04 0.03 0.05
- Uptime: 0 days, 2 hours, 54 minutes, 41 seconds
- OS Updates: 0 (well done!)
- OS Missing Packages: None (v1)
- OS APT Last Update: 04.01.2017 13:24:42 CET +01:00:00
- Bot Start Script: not found
- DNS resolution check: google.com -> OK
- CPU:
    Architecture:          x86_64
    CPU(s):                1
    Thread(s) per core:    1
    Core(s) per socket:    1
    Socket(s):             1
    Model name:            QEMU Virtual CPU version 2.3.0
    CPU MHz:               2397.222
    Hypervisor vendor:     KVM
    Virtualization type:   full
- RAM: 131.08 MB/2.94 GB in use (4%)
- SWAP: 0 B/5.99 GB in use (0%)
- DISK: 12.72 GB/280.49 GB in use (4%)
- Report date: 04.01.2017 17:21:28 CET +01:00:00 (timezone: Europe/Berlin)

BOT INFORMATION
- Status: not running
- Webinterface: port locally not reachable (Port: 8087)
- Binary: /home/ts3/ts3soundboard/sinusbot (Hash: 0005c8c289b99913844c9f761dbb50e9)
- Version: 0.9.16-10f0fad
- TS3 Plugin: installed (md5 hash match)
   - Bot Plugin: 28b54596e19937601df973b709aa0667
   - TS3 Client: 28b54596e19937601df973b709aa0667
- Config:
   - LogLevel = 10 (debug log active)
   - TS3Path = /home/ts3/TeamSpeak3-Client-linux_amd64/ts3client_linux_amd64 (Version 3.0.19.4)
   - YoutubeDLPath = /usr/local/bin/youtube-dl (does not exist!)
- Installed Scripts: advertising.js; ; ; aloneMode.js; Animated; Animated; BackToDefault.js; BackToDefault.js.store; badchan.js; bookmark.js; covatar.js; dev.js; dice.js; dice.js.store; digitalclock.js; Digital; Digital; followme.js; idle.js; ; ; metadata.js; norecording.js; Reconnect.js; Reconnect.js.store; rememberChannel.js; showcase.js; sound.js; WelcomeSound.js; WelcomeSound.js.store; welcometext.js; Youtube; Youtube
==========================================================

Beim Bot-Start in der Konsole:
Code:
2017/01/04 17:25:54 fd6b927b 99d68826 INFO   Starting instance ts3server://localhost?port=9987&nickname=%E2%96%BA%20top100station&password=&cid=798&channelpassword=
2017/01/04 17:25:54 fd6b927b 19257399 INFO   Starting instance ts3server://localhost?port=9987&nickname=%E2%96%BA%20EDM&password=&cid=122&channelpassword=
2017/01/04 17:25:54 fd6b927b 99d68826 DEBUG  TS>This application failed to start because it could not find or load the Qt platform plugin "xcb".
2017/01/04 17:25:54 fd6b927b 99d68826 ERROR  TS3Client reported missing dependencies for xcb. Please install xcb and try again. On Ubuntu / Debian you can usually as root run: apt-get install xcb
2017/01/04 17:25:54 fd6b927b 99d68826 DEBUG  TS>
2017/01/04 17:25:54 fd6b927b 99d68826 DEBUG  TS>Available platform plugins are: xcb.
2017/01/04 17:25:54 fd6b927b 99d68826 DEBUG  TS>
2017/01/04 17:25:54 fd6b927b 99d68826 DEBUG  TS>Reinstalling the application may fix this problem.
2017/01/04 17:25:54 fd6b927b 99d68826 DEBUG  Closed.
2017/01/04 17:25:54 fd6b927b 99d68826 INFO   TSClient quit. LogLevel has been increased, please try to connect again to see more details.
2017/01/04 17:25:54 fd6b927b 19257399 DEBUG  TS>This application failed to start because it could not find or load the Qt platform plugin "xcb".
2017/01/04 17:25:54 fd6b927b 19257399 ERROR  TS3Client reported missing dependencies for xcb. Please install xcb and try again. On Ubuntu / Debian you can usually as root run: apt-get install xcb
2017/01/04 17:25:54 fd6b927b 19257399 DEBUG  TS>
2017/01/04 17:25:54 fd6b927b 19257399 DEBUG  TS>Available platform plugins are: xcb.
2017/01/04 17:25:54 fd6b927b 19257399 DEBUG  TS>
2017/01/04 17:25:54 fd6b927b 19257399 DEBUG  TS>Reinstalling the application may fix this problem.
2017/01/04 17:25:54 fd6b927b 19257399 DEBUG  Closed.
2017/01/04 17:25:54 fd6b927b 19257399 INFO   TSClient quit. LogLevel has been increased, please try to connect again to see more details.
2017/01/04 17:26:05 fd6b927b 19257399 DEBUG  Could not get channels: HTTP returned an error: Timeout; Code: 500; Message: Timeout
2017/01/04 17:26:05 fd6b927b 19257399 WARN   Script not loaded / crashed. Took too long: timeout

Falls es noch interessiert, das diag-Script bei laufendem Bot:
Code:
BOT INFORMATION
- Status: running (PIDs: 2625 2624, User: ts3)
- Webinterface: port locally not reachable (Port: 8087)
- Binary: /home/ts3/ts3soundboard/sinusbot (Hash: 0005c8c289b99913844c9f761dbb50e9)
- Version: 0.9.16-10f0fad
- TS3 Plugin: installed (md5 hash match)
   - Bot Plugin: 28b54596e19937601df973b709aa0667
   - TS3 Client: 28b54596e19937601df973b709aa0667
- Config:
   - LogLevel = 10 (debug log active)
   - TS3Path = /home/ts3/TeamSpeak3-Client-linux_amd64/ts3client_linux_amd64 (Version 3.0.19.4)
   - YoutubeDLPath = /usr/local/bin/youtube-dl (does not exist!)
- Installed Scripts: advertising.js; ; ; aloneMode.js; Animated; Animated; BackToDefault.js; BackToDefault.js.store; badchan.js; bookmark.js; covatar.js; dev.js; dice.js; dice.js.store; digitalclock.js; Digital; Digital; followme.js; idle.js; ; ; metadata.js; norecording.js; Reconnect.js; Reconnect.js.store; rememberChannel.js; showcase.js; sound.js; WelcomeSound.js; WelcomeSound.js.store; welcometext.js; Youtube; Youtube

Webinterface ist übrigens erreichbar von außen. Bot funktionierte auch vorher schon, nur kam nicht auf den Server.
Im diag-Script hat sich hoffentlich länger nichts geändert, habe das genommen, was schon drauf war, habe es auf dem alten Server schonmal benutzt.
 

Flybel

Member
/update

Nach ein paar Stunden im Leerlauf hat sich der Bot vor 5 Minuten entschieden, den Fehler selbst zu beheben, er ist jetzt verbunden.

/closed
 
Status
Not open for further replies.
Top