Now google that and solve the problem It's got nothing to do with the bot or the installer but with your system / installation.Unable to correct problems, you have held broken packages
Now google that and solve the problem It's got nothing to do with the bot or the installer but with your system / installation.Unable to correct problems, you have held broken packages
apt-get -y install screen x11vnc xvfb libxcursor1 ca-certificates bzip2 psmisc libglib2.0-0 less cron-apt ntp python iproute2 dbus libnss3 libegl1-mesa x11-xkb-utils libasound2 libxcomposite-dev libxi6
Danke, es lag glaube ich einfach an Debian 7. Habe jetzt 8.Das liegt an deinem System, einmal bitte wie es dort steht:
manuell ausführen.Code:apt-get -y install screen x11vnc xvfb libxcursor1 ca-certificates bzip2 psmisc libglib2.0-0 less cron-apt ntp python iproute2 dbus libnss3 libegl1-mesa x11-xkb-utils libasound2 libxcomposite-dev libxi6
Danke, es lag glaube ich einfach an Debian 7. Habe jetzt 8.
Das bietet mein Hoster meines Wissens nach gar nicht an.https://wiki.debian.org/LTS Wäre vermutlich besser gewesen wenn du gleich zu Debian 9 gesprungen wärst
Provide us you complete logsI am getting an error in line 826. https://github.com/Sinusbot/installer-linux/blob/master/sinusbot_installer.sh#L826
Ubuntu 14.04
Provide us you complete logs
Sind die github und live version out of sync? Oder wieso failt da ne empty line?^^Error on line 826. Report this to the author at https://forum.sinusbot.com/threads/sinusbot-installer-script.1200/ only. Not a PN or a bad review, cause this is an error of your system not of the installer script.
Failed command: https://github.com/Sinusbot/installer-linux/blob/master/sinusbot_installer.sh#L826
SinusBot installation done.
Starting systemd installation
Synchronizing state of sinusbot.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable sinusbot
update-rc.d: error: sinusbot Default-Start contains no runlevels, aborting.
Error on line 832. Report this to the author at https://forum.sinusbot.com/threads/sinusbot-installer-script.1200/ only. Not a PN or a bad review, cause this is an error of your system not of the installer script.
Command which failed was: " systemctl enable sinusbot.service". Please try to execute it manually and attach the output to the bug report in the forum thread.
root@madoka:~# systemctl enable sinusbot.service
Synchronizing state of sinusbot.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable sinusbot
update-rc.d: error: sinusbot Default-Start contains no runlevels, aborting.
Hmm, this systemd script was written by @Xuxe maybe he knows an answerHi, i tried full remove and reainstall, but not working.
Linux madoka 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) x86_64 GNU/Linux
Code:SinusBot installation done. Starting systemd installation Synchronizing state of sinusbot.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable sinusbot update-rc.d: error: sinusbot Default-Start contains no runlevels, aborting. Error on line 832. Report this to the author at https://forum.sinusbot.com/threads/sinusbot-installer-script.1200/ only. Not a PN or a bad review, cause this is an error of your system not of the installer script. Command which failed was: " systemctl enable sinusbot.service". Please try to execute it manually and attach the output to the bug report in the forum thread.
If I run manually, than I get this:
Code:root@madoka:~# systemctl enable sinusbot.service Synchronizing state of sinusbot.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable sinusbot update-rc.d: error: sinusbot Default-Start contains no runlevels, aborting.
Hi, i tried full remove and reainstall, but not working.
Its a simple installed linux, not virtualized. Yes, debian 9, and I tried to install a fresh linux in virtualbox, thats worked, but I don't know why on the prod server not work at the moment. 2 days ago its worked. Than when i stoped the instance and than tried to start, the teamspeak client failed to connect too. Do you have any idea, how can I correct the system, to handle the script as normal systemd script?What kind of virtualization is it? As far as i See it's Debian 9; correct me if i'm wrong.
The issue comes from your System, it tries to Wrap this Script and handle it as legacy init Script. But we only provide the systemd file.
2018-04-04T00:22:56+02:00 TSClient quit.
2018-04-04T00:22:56+02:00 Closed.
2018-04-04T00:22:56+02:00 TS>libpng warning: iCCP: known incorrect sRGB profile
2018-04-04T00:22:56+02:00 TS>QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled
2018-04-04T00:22:56+02:00 TS>QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled
2018-04-04T00:22:56+02:00 TS>QCoreApplication::applicationDirPath: Please instantiate the QApplication object first
2018-04-04T00:22:55+02:00 New connection status 0; Error 1797
2018-04-04T00:22:55+02:00 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 the server does not allow the version of the client you are using. See our Wiki / Forums for more help.
2018-04-04T00:22:55+02:00 TS |INFO |ClientUI |1 |Failed to connect to server, want autoreconnect = 0
2018-04-04T00:22:55+02:00 TS |INFO |ClientUI |1 |Connect status: Disconnected
2018-04-04T00:22:52+02:00 Storing configuration.
2018-04-04T00:22:50+02:00 TS |DEVELOP |PktHandler | |Puzzle solve time: 6
2018-04-04T00:22:50+02:00 TS |INFO | | |Statistics report: Setting next report date to: Tue Apr 24 00:22:50 2018
2018-04-04T00:22:50+02:00 TS |INFO | | |Statistics report: First run, report later in 1-30 days
2018-04-04T00:22:50+02:00 TS |INFO |ClientUI | |Last update check was: Tue Jan 1 00:00:01 2019
2018-04-04T00:22:50+02:00 TS |INFO |Bookmarks | |Collecting autoconnect bookmarks
2018-04-04T00:22:50+02:00 New connection status 1; Error 0
2018-04-04T00:22:50+02:00 TS |INFO |ClientUI |1 |Connect status: Connecting
2018-04-04T00:22:49+02:00 TS |INFO |PreProSpeex |1 |Speex version: 1.2rc1
2018-04-04T00:22:47+02:00 TS |INFO |ClientUI |1 |Initiating connection: 127.0.0.1:9987
2018-04-04T00:22:47+02:00 TS |INFO |ClientUI |1 |Connect to server: 127.0.0.1
2018-04-04T00:22:47+02:00 TS |INFO |ClientUI | |ts3server: 127.0.0.1?port=9987&nickname=KURVAGECIBOT&password=&channel=&channelpassword=
2018-04-04T00:22:47+02:00 TS |INFO |ClientUI | |Using configuration location: /opt/sinusbot/data/ts3/977be823-569c-462b-af9d-7bf7c8c003dc/6ba9934d-9acf-43da-9ccf-82698b2cbbf4/settings.db
2018-04-04T00:22:47+02:00 TS |INFO |ClientUI | |Qt version: 5.6.1
2018-04-04T00:22:47+02:00 TS |INFO |ClientUI | |Failed to init text to speech engine
2018-04-04T00:22:47+02:00 TS |DEVELOP |ClientUI | |Notifications init: Soundpack path: /opt/sinusbot/teamspeak3-client/sound/nosounds
2018-04-04T00:22:47+02:00 TS |INFO | | |*** Time [INIT]: 196
2018-04-04T00:22:47+02:00 TS |INFO | | |*** Time [MAINWINDOW]: 195
2018-04-04T00:22:47+02:00 TS>ClientQueryPlugin: currentServerConnectionChanged 1 (0)
2018-04-04T00:22:46+02:00 TS |INFO |Plugins | |Loading plugin: libsoundbot_plugin.so
2018-04-04T00:22:46+02:00 TS |INFO |Query | |listening on 127.0.0.1:25639
2018-04-04T00:22:46+02:00 TS |INFO | | |successfully downloaded revocation list
2018-04-04T00:22:46+02:00 TS |INFO |Plugins | |Loading plugin: libclientquery_plugin_linux_amd64.so
2018-04-04T00:22:46+02:00 TS |INFO |Addons | |Checking for addon updates...
2018-04-04T00:22:46+02:00 TS |INFO |ClientUI | |Unable to create an Open GL context.
2018-04-04T00:22:46+02:00 TS |ERROR |SoundBckndIntf| |/opt/sinusbot/teamspeak3-client/soundbackends/libpulseaudio_linux_amd64.so error: INIT_PA_IMPL
2018-04-04T00:22:46+02:00 TS |ERROR |PulseAudio | |pa_context_connect failed -
2018-04-04T00:22:46+02:00 TS |ERROR |PulseAudio | |failed to connect to pulse audio server -
2018-04-04T00:22:46+02:00 TS |INFO | | |SystemInformation: Linux 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) x86_64 Binary: 64bit
2018-04-04T00:22:46+02:00 TS |INFO | | |TeamSpeak 3 Client 3.1.8 (2018-01-22 09:50:07)
2018-04-04T00:22:46+02:00 TS>DUMP defined! Dumpdir is: /opt/sinusbot/data/ts3/977be823-569c-462b-af9d-7bf7c8c003dc/6ba9934d-9acf-43da-9ccf-82698b2cbbf4/crashdumps
2018-04-04T00:22:46+02:00 TS>Crashdump ENABLED, directory is: /opt/sinusbot/data/ts3/977be823-569c-462b-af9d-7bf7c8c003dc/6ba9934d-9acf-43da-9ccf-82698b2cbbf4/crashdumps
2018-04-04T00:22:46+02:00 Starting instance ts3server://127.0.0.1?port=9987&nickname=KURVAGECIBOT&password=&channel=&channelpassword=
2018-04-04T00:22:45+02:00 Could not insert into FileTransfer-Tableno such table: FileTransfer
2018-04-04T00:22:45+02:00 Could not delete from FileTransferno such table: FileTransfer
2018-04-04T00:22:45+02:00 Could not insert into FileTransfer-Tableno such table: FileTransfer
2018-04-04T00:22:45+02:00 Could not delete from FileTransferno such table: FileTransfer
2018-04-04T00:22:45+02:00 Could not insert into FileTransfer-Tableno such table: FileTransfer
2018-04-04T00:22:45+02:00 Could not delete from FileTransferno such table: FileTransfer
2018-04-04T00:22:45+02:00 Could not insert into FileTransfer-Tableno such table: FileTransfer
2018-04-04T00:22:45+02:00 Could not delete from FileTransferno such table: FileTransfer
2018-04-04T00:22:45+02:00 Could not insert into FileTransfer-Tableno such table: FileTransfer
2018-04-04T00:22:45+02:00 Could not delete from FileTransferno such table: FileTransfer
2018-04-04T00:22:45+02:00 Could not insert into FileTransfer-Tableno such table: FileTransfer
2018-04-04T00:22:45+02:00 Could not delete from FileTransferno such table: FileTransfer
2018-04-04T00:22:45+02:00 About to run.
2018-04-04T00:22:45+02:00 Prespawn.
Searching latest TS3-Client build for hardware type x86_64 with arch amd64.
Detected latest TS3-Client version as 3.1.8
Installing necessary packages. Please wait...
E: Unable to locate package iproute2
Error on line 629. Report this to the author at https://forum.sinusbot.com/threads/sinusbot-installer-script.1200/ only. Not a PN or a bad review, cause this is an error of your system not of the installer script.
Command which failed was: " apt-get -y install screen x11vnc xvfb libxcursor1 ca-certificates bzip2 psmisc libglib2.0-0 less cron-apt ntp python iproute2 dbus libnss3 libegl1-mesa x11-xkb-utils libasound2 libxcomposite-dev libxi6". Please try to execute it manually and attach the output to the bug report in the forum thread.
~# apt-get -y install screen x11vnc xvfb libxcursor1 ca-certificates bzip2 psmisc libglib2.0-0 less cron-apt ntp python iproute2 dbus libnss3 libegl1-mesa x11-xkb-utils libasound2 libxcomposite-dev libxi6
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package iproute2
What should the Installer do?
1) Install
2) Update
3) Remove
4) PW Reset
5) Quit
#? 1
Check if lsb-release and debconf-utils is installed...
E: The repository 'http://de.archive.ubuntu.com/ubuntu zesty Release' does no longer have a Release file.
E: The repository 'http://de.archive.ubuntu.com/ubuntu zesty-updates Release' does no longer have a Release file.
W: GPG error: http://ppa.launchpad.net/webupd8team/java/ubuntu trusty InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C2518248EEA14886
W: The repository 'http://ppa.launchpad.net/webupd8team/java/ubuntu trusty InRelease' is not signed.
E: The repository 'http://security.ubuntu.com/ubuntu zesty-security Release' does no longer have a Release file.
Error on line 266. Report this to the author at https://forum.sinusbot.com/threads/sinusbot-installer-script.1200/ only. Not a PN or a bad review, cause this is an error of your system not of the installer script.
Command which failed was: " apt-get update". Please try to execute it manually and attach the output to the bug report in the forum thread.