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

"could not contact update server" / Raspberry Pi 3

luk4s

Member
Hi,

ich habe versucht den Bot auf meinem Raspberry Pi 3 zu installieren.
Ich habe eine 64 bit debian version installiert und simuliere mithilfe von Exagear eine x86_64 Umgebung.

Wenn ich den Bot starte bekomme ich die Fehlermeldung "could not contact update server".
Kann mir jemand sagen wodurch der Fehler verursacht wird ?

SInusbot version: SinusBot Beta 0.13.37-f7e9ece
Ts3 Client: 3.1.8

Code:
sinusbot@raspberrypi:/opt/sinusbot$ ./sinusbot
2018/02/10 21:56:13 X [MAIN] Starting up fake x-server...
___ ___ _  _ _   _ ___ ___  ___ _____  BETA
/ __|_ _| \| | | | / __| _ )/ _ \_   _|
\__ \| || .` | |_| \__ \ _ \ (_) || |
|___/___|_|\_|\___/|___/___/\___/ |_|

Version: 0.13.37-f7e9ece
(C) 2013-2017 Michael Friese. All rights reserved.

2018/02/10 21:56:15 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin AFK_Mover_(AwayMuteDeafIdle).js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin Advanced_Display_Playback_Information.js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin Animated_Nickname.js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin BackToDefault.js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin Channel_Description_Changer.js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin Default-Channel.js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin Jail.js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin Now_Playing_[Cleans_Bad_Tags]_[Custom_Display_Formats]_[TTS_Announce].js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin Simple_Custom_Commands.js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin Youtube_Search.js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin advertising.js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin alonemode.js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin bookmark.js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin come.js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin followme.js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin norecording.js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin rememberChannel.js
2018/02/10 21:56:16 [GENERAL/SCRIPTS] INFO   Loading ScriptPlugin welcome.js
could not contact update server
 
Last edited:

mxschmitt

Moderator
Staff member
is awesome!
V.I.P.
is uber awesome!
Contributor
Insider
Das bedeutet, dass deine Uhrzeit auf dem Server nicht passend ist. Versuche die mithilfe eines Zeitservers genau einzustellen. :)
 

luk4s

Member
Das bedeutet, dass deine Uhrzeit auf dem Server nicht passend ist. Versuche die mithilfe eines Zeitservers genau einzustellen. :)

Die Zeit auf meinem Server ist wie folgt:
Local time is now: Sat Feb 10 22:30:46 CET 2018.
Universal Time is now: Sat Feb 10 21:30:46 UTC 2018.

Was muss ich ändern ? Ist doch eigentlich richtig oder ? :confused:

Edit: Diagnoseskript

Code:
==========================================================
SINUSBOT RELATED
SYSTEM INFORMATION
 - Operating System: Ubuntu 16.04.3 LTS
 - Kernel: Linux 4.11.12-pi64+ x86_64
 - Load Average: 0.76 0.43 0.25
 - Uptime: 0 days, 2 hours, 51 minutes, 2 seconds
 - OS x64 check: OK
 - OS Updates: 0 (well done!)
 - OS Missing Packages: None
 - OS APT Last Update: 10.02.2018 20:44:10 CET +01:00:00
 - SHELL LOCALE LANG: (not set)
 - Bot Start Script: not found
 - DNS resolution check: www.sinusbot.com resolved to 104.18.41.220 -> 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):                4
    Thread(s) per core:    1
    Core(s) per socket:    4
    Socket(s):             1
    Model name:            Exagear Virtual x86-64-compatible CPU @ 1.00GHz
    CPU MHz:               1000.00
    Hypervisor vendor:     vertical
    Virtualization type:   full
 - RAM: 174.45 MB/919.33 MB in use (18%)
 - SWAP: 0 B/0 B in use (0%) (SWAP disabled)
 - DISK: 2.73 GB/10.80 GB in use (25%)
 - Package versions:
   + libglib: 2.48.2-0ubuntu1

BOT INFORMATION
 - Status: not running
 - Webinterface: port locally not reachable (Port: 8087)
 - Binary: /opt/sinusbot/sinusbot
 - Binary Info: MD5 Hash: 9e74167de6a4b9931e381cc86bf05b3e, Perms: 755, User: sinusbot
 - Version: 0.13.37-f7e9ece
 - TS3 Plugin: installed (md5 hash match)
   - Bot Plugin: 26551adc40e47c6d5d02517b8575d375
   - TS3 Client: 26551adc40e47c6d5d02517b8575d375
 - Config:
   - LogLevel = 10 (debug log active)
   - TS3Path = /opt/sinusbot/TeamSpeak3-Client-linux_amd64/ts3client_linux_amd64 (Version 3.1.8)
   - YoutubeDLPath = not set
 - Installed scripts: AFK_Mover_(AwayMuteDeafIdle).js; Advanced_Display_Playback_Information.js; Animated_Nickname.js; BackToDefault.js; Channel_De         scription_Changer.js; Default-Channel.js; Jail.js; Now_Playing_[Cleans_Bad_Tags]_[Custom_Display_Formats]_[TTS_Announce].js; Simple_Custom_Commands         .js; Youtube_Search.js; advertising.js; alonemode.js; bookmark.js; come.js; followme.js; norecording.js; rememberChannel.js; welcome.js

TIME INFORMATION
 - Time (local): 11.02.2018 00:37:51 CET +01:00:00
 - Time (remote): 11.02.2018 00:37:52 CET +01:00:00
 - Time (difference): 1 secs (Time diff less than 2 secs. Good.)
 - Timezone: Europe/Berlin

OTHER INFORMATION
 - TeamSpeak 3 Version: 3.1.8
 - youtube-dl Version: unknown
 - DiagScript Version: 0.7.0
==========================================================
 
Last edited:

Multivitamin

Well-Known Member
Tier III
is awesome!
V.I.P.
is uber awesome!
Contributor
Insider
Schau halt ob die mit der Atomuhr übereinstimmt, notfalls installier dir einen ntp client um ganz sicher zu gehen
was deine Zeit aussagt ist so ziemlich doof da wir nicht wissen wann du das geprüft hast
 

luk4s

Member
Schau halt ob die mit der Atomuhr übereinstimmt, notfalls installier dir einen ntp client um ganz sicher zu gehen
was deine Zeit aussagt ist so ziemlich doof da wir nicht wissen wann du das geprüft hast


An der Zeit scheint es wohl nicht zu liegen.
Das Diagnoseskript gab aus:
Code:
TIME INFORMATION
- Time (local): 11.02.2018 00:37:51 CET +01:00:00
- Time (remote): 11.02.2018 00:37:52 CET +01:00:00
- Time (difference): 1 secs (Time diff less than 2 secs. Good.)
- Timezone: Europe/Berlin
 

irgendwr

no longer active, "retired" staff member
is awesome!
V.I.P.
is uber awesome!
Contributor
Insider
Wie Xuxe bereits erwähnt hat bieten wir keinen Support für die Verwendung von Emulationssoftware.
 
Top