@Qhiliqq erstmal großes Lob an deine Arbeit hier, scheinst echt aktiv drin zu stecken und den Leuten zu helfen.
Installieren tut er alles richtig keine Fehlermeldungen, habe trotzdem ein kleines Problem.
Habe im Wiki oder im Internet nichts zu der Meldung gefunden :
Installing Sinusbot update cronjob successful.
YouTube-DL already installed. Checking for updates.
Starting the Sinusbot. For first time.
Failed to read password, try a reinstall again.
Habe 4 mal versucht das ganze zu reinstallieren (auch mit Server-Restarts) und weiß nicht wo ich sonst ansetzen soll.
Wäre dankbar über jede Hilfe, das Problem muss ja irgendwie zu beheben sein (Wenn es geht ohne OS-Neuinstallation --> Meine Lösung für alles ^^)
PS: Habe Debian 8
Wenn Update ausgewählt wird, wird die Passwort generation garnicht erst gestartet, somit könnt ihr rein theoretisch und eben auch praktisch getestet garnicht auf den Bot zugreifen, dazu müsste dann ein PW-Reset ausgeführt werden.@Qhilliqq hab das Installscript manuell über deinen Link runtergeladen und als root ausgeführt. Beim installieren kam eben der Error den @hendrick Koch auch hat, habe das Script dann nochmals ausgeführt aber statt Install habe ich Update gewählt und dann hats komischerweise funktioniert und der Bot lief. Also auch an dich @hendrick Koch probier nach dem Install nochmal das Update aus eventuell löst es ja auch dein Problem.
@Xuxe weiss da evtl. mehr@Qhiliqq
brauche ein wenig Hilfe. Ich verstehe nicht wieso der Sinusbot nicht startet
Ich hab keine Ahnung, wieso es an dem User liegen sollte... habe den normalen user "sinusbot" genommen.Job for sinusbot.service failed. See 'systemctl status sinusbot.service' and 'journalctl -xn' for details.root@debian:~# systemctl status sinusbot.service
● sinusbot.service - Sinusbot, the Teamspeak 3 and Discord music bot.
Loaded: loaded (/lib/systemd/system/sinusbot.service; enabled)
Active: failed (Result: exit-code) since Sat 2017-04-29 19:33:41 EDT; 1min 54s ago
Process: 4623 ExecStartPre=/bin/rm -f /tmp/.sinusbot.lock (code=exited, status=217/USER)
Apr 29 19:33:41 debian systemd[1]: sinusbot.service: control process exited, code=exited status=217
Apr 29 19:33:41 debian systemd[1]: Failed to start Sinusbot, the Teamspeak 3 and Discord music bot..
Apr 29 19:33:41 debian systemd[1]: Unit sinusbot.service entered failed state.
Und wo ist das Problem?Ich habe das Problem dass, das Script nacher den Sinusbot nicht downloaden will: Meldung:
Error while downloading with cURL. Trying it with wget.
Ne Idee jemand?
surri xDDa ist der Fehler, welcher soeben im Installer gefixt wurde @irgendwer ist hierbei der teufelsmeister
Leider nein. Bei mir beendet sich das Script einfach ohne irgendwelche Meldung . Ein erneutes Starten des Scripts hat leider auch nichts gebracht
Ich bin eben dran, kann es aber noch nicht nachvollziehen warum.Hier einmal die Fehlermeldung bzw. der Ablauf View attachment 1158
At the moment I'll try to fix this but there is no eta for centos. Also is this and sinsubot an hobby project give it the time it needsPLEASE FIX THE ERRORS! i've waited too long!!
You're using Installer 1.3.4
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...
Done!
Which start script should be used? system.d is prefered since Debian 8.
1) system.d
2) init.d
#? 1
Automatic usage or own directories?
1) Automatic
2) Own path
3) Quit
#? 1
Sinusbot isn't installed yet. Installer goes on.
This Sinusbot version is only for private use! Accept?
1) No
2) Yes
#? 2
Update the system packages to the latest version? Recommended, as otherwise dependencies might break! Option "No" = Exit
1) Yes
2) Try without
3) No
#? 1
Start installer now!
Updating the system in a few seconds silently (no optical output)!
This could take a while. Please give it up to 10 minutes!
Installing necessary packages! Please wait...
Packages installed!
Please enter the name of the sinusbot user. Typically "sinusbot". If it does not exists, the installer will create it.
Username [sinusbot]: Dragon
Your sinusbot user is: Dragon
Downloading TS3 client files.
Installing the TS3 client.
Read the eula!
Do the following: Press "ENTER" then press "q" after that press "y" and accept it with another "ENTER".
Welcome to the TeamSpeak 3 Client for Linux on amd64 installer
In order to install this software you are required to accept the license
agreement, please press return to view the license.
You can scroll with the arrow keys and quit the viewer by pressing 'q'.
[RETURN]
Please type y to accept, n otherwise: y
Creating directory TeamSpeak3-Client-linux_amd64
Verifying archive integrity... All good.
Uncompressing TeamSpeak 3 Client for Linux on amd64 100%
TS3 client install done.
Downloading latest Sinusbot.
Extracting Sinusbot files.
Sinusbot installation done.
Installed systemd file to start the Sinusbot with "service sinusbot {start|stop|status|restart}"
Config.ini created successfully.
Installing Cronjob for automatic Sinusbot update...
Installing Sinusbot update cronjob successful.
Should YT-DL be installed?
1) Yes
2) No
#? 1
Installing YT-Downloader now!
Installing Cronjob for automatic YT-DL update...
Installing successful.
Starting the Sinusbot. For first time.
2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin advertising.js
2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin aloneMode.js
2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin badchan.js
2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin bookmark.js
2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin covatar.js
2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin dev.js
2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin followme.js
2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin idle.js
2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin metadata.js
2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin norecording.js
2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin rememberChannel.js
2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin showcase.js
2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin sound.js
2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin welcometext.js
2017/05/03 15:43:39 X [MAIN] Starting up fake x-server...
Failed to read password, try a reinstall again.
Is there an output if you only type "export" in ssh?Hi..... is error for this installer.
I using debian 8 , latest updates.... apt-get update,upgrade.. i reinstalled...Code:You're using Installer 1.3.4 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... Done! Which start script should be used? system.d is prefered since Debian 8. 1) system.d 2) init.d #? 1 Automatic usage or own directories? 1) Automatic 2) Own path 3) Quit #? 1 Sinusbot isn't installed yet. Installer goes on. This Sinusbot version is only for private use! Accept? 1) No 2) Yes #? 2 Update the system packages to the latest version? Recommended, as otherwise dependencies might break! Option "No" = Exit 1) Yes 2) Try without 3) No #? 1 Start installer now! Updating the system in a few seconds silently (no optical output)! This could take a while. Please give it up to 10 minutes! Installing necessary packages! Please wait... Packages installed! Please enter the name of the sinusbot user. Typically "sinusbot". If it does not exists, the installer will create it. Username [sinusbot]: Dragon Your sinusbot user is: Dragon Downloading TS3 client files. Installing the TS3 client. Read the eula! Do the following: Press "ENTER" then press "q" after that press "y" and accept it with another "ENTER". Welcome to the TeamSpeak 3 Client for Linux on amd64 installer In order to install this software you are required to accept the license agreement, please press return to view the license. You can scroll with the arrow keys and quit the viewer by pressing 'q'. [RETURN] Please type y to accept, n otherwise: y Creating directory TeamSpeak3-Client-linux_amd64 Verifying archive integrity... All good. Uncompressing TeamSpeak 3 Client for Linux on amd64 100% TS3 client install done. Downloading latest Sinusbot. Extracting Sinusbot files. Sinusbot installation done. Installed systemd file to start the Sinusbot with "service sinusbot {start|stop|status|restart}" Config.ini created successfully. Installing Cronjob for automatic Sinusbot update... Installing Sinusbot update cronjob successful. Should YT-DL be installed? 1) Yes 2) No #? 1 Installing YT-Downloader now! Installing Cronjob for automatic YT-DL update... Installing successful. Starting the Sinusbot. For first time. 2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin advertising.js 2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin aloneMode.js 2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin badchan.js 2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin bookmark.js 2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin covatar.js 2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin dev.js 2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin followme.js 2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin idle.js 2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin metadata.js 2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin norecording.js 2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin rememberChannel.js 2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin showcase.js 2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin sound.js 2017/05/03 15:43:39 [GENERAL/SCRIPTS] INFO Loading ScriptPlugin welcometext.js 2017/05/03 15:43:39 X [MAIN] Starting up fake x-server... Failed to read password, try a reinstall again.
Is VPS, no vitrual box... Can help me for fix installer?Is there an output if you only type "export" in ssh?
I can't reproduce this error, neither in virtualbox nor on a normal vserver.
root@rpgonlyplayro:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@rpgonlyplayro:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@rpgonlyplayro:~# lsb_release -da
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.2 (jessie)
Release: 8.2
Codename: jessie
root@rpgonlyplayro:~# hostnamectl
Static hostname: rpgonlyplayro
Icon name: computer-vm
Chassis: vm
Machine ID: cdb7f92199c748a7a20d33ab52974cbb
Boot ID: 137b8e441256431083347f469a9907fc
Virtualization: kvm
Operating System: Debian GNU/Linux 8 (jessie)
Kernel: Linux 3.16.0-4-amd64
Architecture: x86-64
root@rpgonlyplayro:~#
What you have is not the questionIs VPS, no vitrual box... Can help me for fix installer?
Informations
Im not expert of linux, please help to fix, and can help for informations for youCode:root@rpgonlyplayro:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@rpgonlyplayro:~# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@rpgonlyplayro:~# lsb_release -da No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.2 (jessie) Release: 8.2 Codename: jessie root@rpgonlyplayro:~# hostnamectl Static hostname: rpgonlyplayro Icon name: computer-vm Chassis: vm Machine ID: cdb7f92199c748a7a20d33ab52974cbb Boot ID: 137b8e441256431083347f469a9907fc Virtualization: kvm Operating System: Debian GNU/Linux 8 (jessie) Kernel: Linux 3.16.0-4-amd64 Architecture: x86-64 root@rpgonlyplayro:~#
interesting what host i have, give me pm.
Sieht sehr gut aus, funktioniert allerdings nicht:
1. Diese Zeile kommt mir etwas komisch vor:
2. Und das Ende sieht auch nicht so passend aus:
Würde mich freuen wenn mir jemand helfen könnte
Ja das stimmt, schaut beides etwas leer aus^^
Okay, command export :What you have is not the question
I just tested it on vps and virtualbox
I also asked for an output of "export" command.
I actually don't know whats the error... This is my last path to fix that.
root@rpgonlyplayro:~# export
declare -x HOME="/root"
declare -x LANG="en_US.UTF-8"
declare -x LOGNAME="root"
declare -x MAIL="/var/mail/root"
declare -x OLDPWD
declare -x PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
declare -x PWD="/root"
declare -x SHELL="/bin/bash"
declare -x SHLVL="1"
declare -x SSH_CLIENT="94.176.**.** 49742 22"
declare -x SSH_CONNECTION="94.176.64.56 49742 185.62.***.*** 22"
declare -x SSH_TTY="/dev/pts/2"
declare -x TERM="xterm"
declare -x USER="root"
declare -x XDG_RUNTIME_DIR="/run/user/0"
declare -x XDG_SESSION_ID="72"
declare -x sinusbot
edit 04
Job for sinusbot.service failed. See 'systemctl status sinusbot.service' and 'journalctl -xn' for details.
root@rpgonlyplayro:~# systemctl status sinusbot.service
● sinusbot.service - Sinusbot, the Teamspeak 3 and Discord music bot.
Loaded: loaded (/lib/systemd/system/sinusbot.service; enabled)
Active: failed (Result: exit-code) since Thu 2017-05-04 14:03:44 UTC; 34s ago
Process: 18325 ExecStartPre=/bin/rm -f /tmp/.sinusbot.lock (code=exited, status=1/FAILURE)
May 04 14:03:44 rpgonlyplayro rm[18325]: /bin/rm: cannot remove ‘/tmp/.sinusbot.lock’: Operation not permitted
May 04 14:03:44 rpgonlyplayro systemd[1]: sinusbot.service: control process exited, code=exited status=1
May 04 14:03:44 rpgonlyplayro systemd[1]: Failed to start Sinusbot, the Teamspeak 3 and Discord music bot..
May 04 14:03:44 rpgonlyplayro systemd[1]: Unit sinusbot.service entered failed state.
root@rpgonlyplayro:~# journalctl -xn
-- Logs begin at Wed 2017-05-03 22:21:16 UTC, end at Thu 2017-05-04 14:04:26 UTC. --
May 04 14:04:12 rpgonlyplayro sshd[18331]: Failed password for root from 61.177.172.24 port 14000 ssh2
May 04 14:04:14 rpgonlyplayro sshd[18331]: Failed password for root from 61.177.172.24 port 14000 ssh2
May 04 14:04:16 rpgonlyplayro sshd[18331]: Failed password for root from 61.177.172.24 port 14000 ssh2
May 04 14:04:16 rpgonlyplayro sshd[18331]: Disconnecting: Too many authentication failures for root from 61.177.172.24 port 14000 ssh2 [preauth]
May 04 14:04:16 rpgonlyplayro sshd[18331]: PAM 5 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.24 user=root
May 04 14:04:16 rpgonlyplayro sshd[18331]: PAM service(sshd) ignoring max retries; 6 > 3
May 04 14:04:19 rpgonlyplayro sshd[18333]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.172.24 user=root
May 04 14:04:21 rpgonlyplayro sshd[18333]: Failed password for root from 61.177.172.24 port 1502 ssh2
May 04 14:04:24 rpgonlyplayro sshd[18333]: Failed password for root from 61.177.172.24 port 1502 ssh2
May 04 14:04:26 rpgonlyplayro sshd[18333]: Failed password for root from 61.177.172.24 port 1502 ssh2
### German ###
Neue Version verfügbar.
Changelog:
Bei Fehlern und Problemen bitte erst in dem Reiter Diskussion das Problem schildern und nicht gleich eine schlechte Bewertung geben, denn so kann ich euch nicht helfen.
- CentOS 7 funktioniert nun wieder
- PW Problem sollte behoben sein
### English ###
New version available.
Changelog:
If you have bugs or problems use first the discuss tab and write down...
- CentOS 7 works again
- PW problem should be solved
Vielen lieben dankIch muss mich hier einfach nochmal bedanken, du leistest super arbeit, hilfst schnell und setzt Dinge 1a durch.
Bin begeistert. Die PW Probleme welche manche hier haben kann ich nicht nachvollziehen, auch auf der alten Version lief die Installation reibungslos.
Vielen lieben Dank für diesen Installer, er macht was er soll und das sehr schnell!
Ich habe mir jetzt auch bei dir einen vServer geholt, da ich dies im Installer gelesen habe.
Wäre schön, wenn du den Sinusbot statt den *** anbieten könntest, aber das muss denke ich mit dem "Kopf der Sinusbotsache" geklärt werden.
Wie dem auch sei, ich bin sehr zufrieden und musste hier einfach nochmals schreiben, Rezension ist schon raus.
Super!