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

Error Connection refused

Status
Not open for further replies.

lusu007

Member
Hey Leute,

ich habe seit heute das Problem, dass ich nicht mehr auf das Interface des SinusBot's zugreifen kann.

Ich habe den Port in der Config auf 8080 umgestellt und bekommen jedes mal einen ERR_CONNECTION_REFUSED.

Meine Config:
Code:
TS3Path = "/opt/ts3soundboard/TeamSpeak3-Client-linux_amd64/ts3client_linux_amd64"
ListenHost = "0.0.0.0"
DataDir = "/opt/ts3soundboard/data/"
ListenPort = 8080
LocalPlayback = false
EnableLocalFS = false
MaxBulkOperations = 300
LogLevel = 10
EnableProfiler = true
YoutubeDLPath = "/usr/local/bin/youtube-dl"
EnableDebugConsole = false
UploadLimit = 83886080
RunAsUser = 0
RunAsGroup = 0
InstanceActionLimit = 6
UseSSL = false
SSLKeyFile = ""
SSLCertFile = ""
Hostname = ""
SampleInterval = 100
StartVNC = false
EnableWebStream = false
LogFile = ""
LicenseKey = "LICENSEKEY"
IsProxied = false
DenyStreamURLs = []
Pragma = 0

[YoutubeDL]
  BufferSize = 524288
  MaxDownloadSize = 419430400
  MaxDownloadRate = 104857600
  CacheStreamed = false

[TS3]
  AvatarMaxWidth = 0
  AvatarMaxHeight = 0

[StreamRewrites]

[Scripts]
  AllowReload = false
  EnableTimer = false

[SpeechRecognition]
  Enable = false

[FFmpeg]
  UserAgent = "SinusBot (0.9.11-6e331b1)"

[DAV]
  Enable = false

[XServer]
  Delay = 0
  Debug = false


Was ist falsch?

Gruß,
lusu007
 

Xuxe

Containerholic
Staff member
is awesome!
V.I.P.
Contributor
Insider
Der Bot wurde Neugestartet und läuft auch? ->
Code:
netstat -tulpn
 

lusu007

Member
Der Bot scheint trotz service ts3bot start nicht zu laufen.

//EDIT: Habe den Bot jetzt manuell gestartet. Es kommt derselbe Fehler.
 

lusu007

Member
Ausgabe von diagSinusbot Script:
Code:
==========================================================
SINUSBOT RELATED
SYSTEM INFORMATION
 - Operating System: Debian GNU/Linux 8.4 (jessie)
 - OS x64 check: OK
 - Kernel: Linux 3.16.0-4-amd64 x86_64
 - Load Average: 0.36 0.24 0.18
 - Uptime: 13 days, 0 hours, 46 minutes, 46 seconds
 - OS Updates: 0 (well done!)
 - OS Missing Packages: None (v1)
 - OS APT Last Update: 13.05.2016 15:02:16 CEST +02:00:00
 - Bot Start Script: not found
 - DNS resolution check: google.com -> OK
 - CPU:
    Architecture:          x86_64
    CPU(s):                8
    Thread(s) per core:    1
    Core(s) per socket:    1
    Socket(s):             8
    Model name:            Intel(R) Xeon(R) CPU           L5640  @ 2.27GHz
    CPU MHz:               2266.744
    Hypervisor vendor:     KVM
    Virtualization type:   full
 - RAM: 2.11 GB/4.85 GB in use (43%)
 - SWAP: 0 B/0 B in use (0%) (SWAP disabled)
 - DISK: 7.44 GB/39.23 GB in use (18%)
 - Package versions:
   > libglib: 2.42.1-1+b1
BOT INFORMATION
 - Status: not running
 - Webinterface: port locally not reachable (Port: 8080)
 - Binary: /opt/ts3soundboard/sinusbot (Hash: a48069da6b637c88fceb92244e8df116)
 - Version: 0.9.11-6e331b1
 - TS3 Plugin: installed (md5 hash match)
   - Bot Plugin: d1ddcca9fd7ace3caf85821656b425c2
   - TS3 Client: d1ddcca9fd7ace3caf85821656b425c2
 - Config:
   - LogLevel = 10 (debug log active)
   - TS3Path = /opt/ts3soundboard/TeamSpeak3-Client-linux_amd64/ts3client_linux_amd64 (Version 3.0.19)
   - YoutubeDLPath = /usr/local/bin/youtube-dl (does exist, version: 2016.04.06)
 - 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: 14.05.2016 22:15:31 CEST +02:00:00 (timezone: Europe/Berlin)
 - TeamSpeak 3 Version: 3.0.19
 - youtube-dl Version: 2016.04.06
 - DiagScript version: 0.4.5
==========================================================
 

lusu007

Member
Nach einer Neuinstallation des Bots bekommen ich kein Connection refused mehr, sondern einen Time Out.
 

lusu007

Member
Jetzt komme ich nur auf das Interface, wenn ich den Bot im Ordner per ./sinusbot starte. Wenn ich jedoch den per service starte startet der Bot nicht.

Ich benutze das Start Script vom AutoInstaller.
 

mxschmitt

Moderator
Staff member
is awesome!
V.I.P.
is uber awesome!
Contributor
Insider
versuche es mal mit
Code:
/etc/init.d/sinusbot start
 
Status
Not open for further replies.
Top