Raspberry 4 - Update von 1.3 auf 1.4 funktioniert nicht

Nachdem ich ein Update auf 1.4 gemacht habe hat Repetier Server nicht mehr gestartet

Habe dann mittels
wget https://download3.repetier.com/files/server/debian-armel/Repetier-Server-1.3.0-Linux.deb
sudo dpkg -i Repetier-Server-1.3.0-Linux.deb
ein Downgrade gemacht und ein update erneut mittels
sudo /usr/local/Repetier-Server/bin/RepetierInstaller /usr/local/Repetier-Server/etc/RepetierServer.xml
versuch jedoch auch hier der selbe fehler

Ich bleibe nun vorerst bei 1.3

pi@Repetier-Server:~ $ sudo service RepetierServer status
● RepetierServer.service - Repetier-Server 3D Printer Server
   Loaded: loaded (/lib/systemd/system/RepetierServer.service; enabled; vendor preset: enabled)
   Active: failed (Result: signal) since Mon 2022-07-11 13:03:12 CEST; 1min 9s ago
  Process: 1001 ExecStartPre=/bin/mkdir -p /var/lib/Repetier-Server (code=exited, status=0/SUCCESS)
  Process: 1002 ExecStartPre=/bin/chown -R repetierserver /var/lib/Repetier-Server (code=exited, status=0/SUCCESS)
  Process: 1003 ExecStart=/usr/local/Repetier-Server/bin/RepetierServer -c /usr/local/Repetier-Server/etc/RepetierServer.xml --daemon (code=exit
 Main PID: 1010 (code=killed, signal=ABRT)

Jul 11 13:03:12 Repetier-Server systemd[1]: RepetierServer.service: Failed with result 'signal'.
Jul 11 13:03:12 Repetier-Server systemd[1]: RepetierServer.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Jul 11 13:03:12 Repetier-Server systemd[1]: RepetierServer.service: Scheduled restart job, restart counter is at 5.
Jul 11 13:03:12 Repetier-Server systemd[1]: Stopped Repetier-Server 3D Printer Server.
Jul 11 13:03:12 Repetier-Server systemd[1]: RepetierServer.service: Start request repeated too quickly.
Jul 11 13:03:12 Repetier-Server systemd[1]: RepetierServer.service: Failed with result 'signal'.
Jul 11 13:03:12 Repetier-Server systemd[1]: Failed to start Repetier-Server 3D Printer Server.



Comments

  • Bei mir hat es so weit immer geklappt auch wenn ich armhf getestet habe. Schwer zu sagen was hier das Problem ist, dazu müsste man den start im gdb machen um zu sehen we er stopt und mit "bt" einen backtrace zeigen. Offenbar gibt es bei dir eine Einstellung die zu einem Problem führt beim initialisieren.

    Eventuell kannst du das noch am server.log sehen - da müsste er ja dann mitten drin vermutlich gestoppt haben. Dann weiß ich wenigstens bei welchem Schritt.

  • Ich weiß leider nicht wie ich die server.log finde habe aber hier die /var/log/syslog

    Kann auch gerne denn start im gdb machen wenn es dir hilft
    Bräuchte nur die Befehle welche in in der shell aufführen soll und die entsprechenden pfade

    Jul 11 17:37:47 Repetier-Server systemd[1]: Started udev Kernel Device Manager.
    Jul 11 17:37:47 Repetier-Server systemd[1]: Reloading.
    Jul 11 17:37:47 Repetier-Server systemd[1]: /lib/systemd/system/xrdp.service:8: PIDFile= references path below legacy directory /var/run/, updating /var/run/xrdp/xrdp.pid → /run/xrdp/xrdp.pid; please update the unit file accordingly.
    Jul 11 17:37:47 Repetier-Server systemd[1]: /lib/systemd/system/xrdp-sesman.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/xrdp/xrdp-sesman.pid → /run/xrdp/xrdp-sesman.pid; please update the unit file accordingly.
    Jul 11 17:37:47 Repetier-Server systemd[1]: getty.target: Wants dependency dropin /etc/systemd/system/getty.target.wants/getty@tty1.service target /etc/systemd/system/autologin@.service has different name
    Jul 11 17:37:47 Repetier-Server systemd[1]: Reloading.
    Jul 11 17:37:48 Repetier-Server systemd[1]: /lib/systemd/system/xrdp.service:8: PIDFile= references path below legacy directory /var/run/, updating /var/run/xrdp/xrdp.pid → /run/xrdp/xrdp.pid; please update the unit file accordingly.
    Jul 11 17:37:48 Repetier-Server systemd[1]: /lib/systemd/system/xrdp-sesman.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/xrdp/xrdp-sesman.pid → /run/xrdp/xrdp-sesman.pid; please update the unit file accordingly.
    Jul 11 17:37:48 Repetier-Server systemd[1]: getty.target: Wants dependency dropin /etc/systemd/system/getty.target.wants/getty@tty1.service target /etc/systemd/system/autologin@.service has different name
    Jul 11 17:37:48 Repetier-Server lircd[736]: lircd-0.10.1[736]: Error: could not get file information for /dev/lirc/0
    Jul 11 17:37:48 Repetier-Server lircd[736]: lircd-0.10.1[736]: default_init(): No such file or directory
    Jul 11 17:37:48 Repetier-Server lircd-0.10.1[736]: Error: could not get file information for /dev/lirc/0
    Jul 11 17:37:48 Repetier-Server lircd-0.10.1[736]: default_init(): No such file or directory
    Jul 11 17:37:49 Repetier-Server lircd[736]: lircd-0.10.1[736]: Error: could not get file information for /dev/lirc/0
    Jul 11 17:37:49 Repetier-Server lircd[736]: lircd-0.10.1[736]: default_init(): No such file or directory
    Jul 11 17:37:49 Repetier-Server lircd-0.10.1[736]: Error: could not get file information for /dev/lirc/0
    Jul 11 17:37:49 Repetier-Server lircd-0.10.1[736]: default_init(): No such file or directory
    Jul 11 17:37:50 Repetier-Server lircd[736]: lircd-0.10.1[736]: Error: could not get file information for /dev/lirc/0
    Jul 11 17:37:50 Repetier-Server lircd[736]: lircd-0.10.1[736]: default_init(): No such file or directory
    Jul 11 17:37:50 Repetier-Server lircd-0.10.1[736]: Error: could not get file information for /dev/lirc/0
    Jul 11 17:37:50 Repetier-Server lircd-0.10.1[736]: default_init(): No such file or directory
    Jul 11 17:37:50 Repetier-Server systemd[1]: Starting Repetier-Server 3D Printer Server...
    Jul 11 17:37:50 Repetier-Server systemd[1]: Started Repetier-Server 3D Printer Server.
    Jul 11 17:37:51 Repetier-Server systemd[1]: Reloading.
    Jul 11 17:37:51 Repetier-Server systemd[1]: /lib/systemd/system/xrdp.service:8: PIDFile= references path below legacy directory /var/run/, updating /var/run/xrdp/xrdp.pid → /run/xrdp/xrdp.pid; please update the unit file accordingly.
    Jul 11 17:37:51 Repetier-Server systemd[1]: /lib/systemd/system/xrdp-sesman.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/xrdp/xrdp-sesman.pid → /run/xrdp/xrdp-sesman.pid; please update the unit file accordingly.
    Jul 11 17:37:51 Repetier-Server systemd[1]: getty.target: Wants dependency dropin /etc/systemd/system/getty.target.wants/getty@tty1.service target /etc/systemd/system/autologin@.service has different name
    Jul 11 17:37:51 Repetier-Server lircd[736]: lircd-0.10.1[736]: Error: could not get file information for /dev/lirc/0
    Jul 11 17:37:51 Repetier-Server lircd[736]: lircd-0.10.1[736]: default_init(): No such file or directory
    Jul 11 17:37:51 Repetier-Server lircd-0.10.1[736]: Error: could not get file information for /dev/lirc/0
    Jul 11 17:37:51 Repetier-Server lircd-0.10.1[736]: default_init(): No such file or directory
    Jul 11 17:37:51 Repetier-Server systemd[1]: RepetierServer.service: Main process exited, code=killed, status=6/ABRT
    Jul 11 17:37:51 Repetier-Server systemd[1]: RepetierServer.service: Failed with result 'signal'.
    Jul 11 17:37:51 Repetier-Server systemd[1]: RepetierServer.service: Service has no hold-off time (RestartSec=0), scheduling restart.
    Jul 11 17:37:51 Repetier-Server systemd[1]: RepetierServer.service: Scheduled restart job, restart counter is at 1.
    Jul 11 17:37:51 Repetier-Server systemd[1]: Stopped Repetier-Server 3D Printer Server.
    Jul 11 17:37:51 Repetier-Server systemd[1]: Starting Repetier-Server 3D Printer Server...
    Jul 11 17:37:51 Repetier-Server RepetierInstaller[24189]: (Reading database ... 67935 files and directories currently installed.)#012Preparing to unpack .../Repetier-Server-1.4.0-Linux.deb ...#012Uninstall Repetier-Server#012Removed /etc/systemd/system/multi-user.targe$
    Jul 11 17:37:51 Repetier-Server RepetierInstaller[24189]: Update finished with code 0
    Jul 11 17:37:51 Repetier-Server systemd[1]: Started Repetier-Server 3D Printer Server.
    Jul 11 17:37:52 Repetier-Server systemd[1]: RepetierServer.service: Main process exited, code=killed, status=6/ABRT
    Jul 11 17:37:52 Repetier-Server systemd[1]: RepetierServer.service: Failed with result 'signal'.
    Jul 11 17:37:52 Repetier-Server systemd[1]: RepetierServer.service: Service has no hold-off time (RestartSec=0), scheduling restart.
    Jul 11 17:37:52 Repetier-Server systemd[1]: RepetierServer.service: Scheduled restart job, restart counter is at 2.
    Jul 11 17:37:52 Repetier-Server systemd[1]: Stopped Repetier-Server 3D Printer Server.
    Jul 11 17:37:52 Repetier-Server systemd[1]: Starting Repetier-Server 3D Printer Server...
    Jul 11 17:37:52 Repetier-Server lircd[736]: lircd-0.10.1[736]: Error: could not get file information for /dev/lirc/0
    Jul 11 17:37:52 Repetier-Server lircd[736]: lircd-0.10.1[736]: default_init(): No such file or directory
    Jul 11 17:37:52 Repetier-Server lircd-0.10.1[736]: Error: could not get file information for /dev/lirc/0
    Jul 11 17:37:52 Repetier-Server lircd-0.10.1[736]: default_init(): No such file or directory
    Jul 11 17:37:52 Repetier-Server systemd[1]: Started Repetier-Server 3D Printer Server.
    Jul 11 17:37:52 Repetier-Server systemd[1]: RepetierServer.service: Main process exited, code=killed, status=6/ABRT
    Jul 11 17:37:52 Repetier-Server systemd[1]: RepetierServer.service: Failed with result 'signal'.
    Jul 11 17:37:52 Repetier-Server systemd[1]: RepetierServer.service: Service has no hold-off time (RestartSec=0), scheduling restart.
    Jul 11 17:37:52 Repetier-Server systemd[1]: RepetierServer.service: Scheduled restart job, restart counter is at 3.
    Jul 11 17:37:52 Repetier-Server systemd[1]: Stopped Repetier-Server 3D Printer Server.
    Jul 11 17:37:52 Repetier-Server systemd[1]: Starting Repetier-Server 3D Printer Server...
    Jul 11 17:37:52 Repetier-Server systemd[1]: Started Repetier-Server 3D Printer Server.
    Jul 11 17:37:53 Repetier-Server systemd[1]: RepetierServer.service: Main process exited, code=killed, status=6/ABRT
    Jul 11 17:37:53 Repetier-Server systemd[1]: RepetierServer.service: Failed with result 'signal'.
    Jul 11 17:37:53 Repetier-Server systemd[1]: RepetierServer.service: Service has no hold-off time (RestartSec=0), scheduling restart.
    Jul 11 17:37:53 Repetier-Server systemd[1]: RepetierServer.service: Scheduled restart job, restart counter is at 4.
    Jul 11 17:37:53 Repetier-Server systemd[1]: Stopped Repetier-Server 3D Printer Server.
    .....




  • Haber gerade noch den server.log gefunden.

    2022-07-11 17:37:51: Start logging...
    2022-07-11 17:37:51: Imported external command Shutdown Server
    2022-07-11 17:37:51: Imported external command Reboot Server
    2022-07-11 17:37:51: Imported allowed execute command shutdown
    2022-07-11 17:37:51: Webdirectory: /usr/local/Repetier-Server/www/
    2022-07-11 17:37:51: Storage directory: /var/lib/Repetier-Server/
    2022-07-11 17:37:51: Configuration file: /usr/local/Repetier-Server/etc/RepetierServer.xml
    2022-07-11 17:37:51: Directory for temporary files: /tmp/
    2022-07-11 17:37:51: Reading firmware data ...
    2022-07-11 17:37:51: Starting Network ...
    2022-07-11 17:37:51: Active features:4095
    2022-07-11 17:37:51: Reading printer configurations ...
    2022-07-11 17:37:51: Reading printer config /var/lib/Repetier-Server/configs/AnyCubic.xml
    2022-07-11 17:37:51: Set webcam url:http://127.0.0.1:8080/?action=stream
    2022-07-11 17:37:51: Reloading Timelapse Entries...
    2022-07-11 17:37:51: Start logging...
    2022-07-11 17:37:51: Imported external command Shutdown Server
    2022-07-11 17:37:51: Imported external command Reboot Server
    2022-07-11 17:37:51: Imported allowed execute command shutdown
    2022-07-11 17:37:51: Webdirectory: /usr/local/Repetier-Server/www/
    2022-07-11 17:37:51: Storage directory: /var/lib/Repetier-Server/
    2022-07-11 17:37:51: Configuration file: /usr/local/Repetier-Server/etc/RepetierServer.xml
    2022-07-11 17:37:51: Directory for temporary files: /tmp/
    2022-07-11 17:37:51: Reading firmware data ...
    2022-07-11 17:37:52: Starting Network ...
    2022-07-11 17:37:52: Active features:4095
    2022-07-11 17:37:52: Reading printer configurations ...
    2022-07-11 17:37:52: Reading printer config /var/lib/Repetier-Server/configs/AnyCubic.xml
    2022-07-11 17:37:52: Set webcam url:http://127.0.0.1:8080/?action=stream
    2022-07-11 17:37:52: Reloading Timelapse Entries...
    2022-07-11 17:37:52: Start logging...
    2022-07-11 17:37:52: Imported external command Shutdown Server
    2022-07-11 17:37:52: Imported external command Reboot Server
    2022-07-11 17:37:52: Imported allowed execute command shutdown
    2022-07-11 17:37:52: Webdirectory: /usr/local/Repetier-Server/www/
    2022-07-11 17:37:52: Storage directory: /var/lib/Repetier-Server/
    2022-07-11 17:37:52: Configuration file: /usr/local/Repetier-Server/etc/RepetierServer.xml
    2022-07-11 17:37:52: Directory for temporary files: /tmp/
    2022-07-11 17:37:52: Reading firmware data ...
    2022-07-11 17:37:52: Starting Network ...
    2022-07-11 17:37:52: Active features:4095
    2022-07-11 17:37:52: Reading printer configurations ...
    2022-07-11 17:37:52: Reading printer config /var/lib/Repetier-Server/configs/AnyCubic.xml
    2022-07-11 17:37:52: Set webcam url:http://127.0.0.1:8080/?action=stream
    2022-07-11 17:37:52: Reloading Timelapse Entries...
    2022-07-11 17:37:53: Start logging...

  • Die Reihenfolge ist

    18:09:40.091: Reloading Timelapse Entries...

    18:09:40.098: Starting printjob manager thread for Prusa_Mini

    bei dir kommt er nur bis timelapse. Also hat er ein Problem mit einer Zeitrafferaufnahme oder mit dem ersten Drucker.

    Wie viele Drucker hast? Jeder Drucker hat unter /var/lib/Repetier-Server/printer/<slug> einen ordner timelapse. Wenn du den testweise mit
    cd /var/lib/Repetier-Server/printer/<slug>
    sudo mv timelapse timelapse_alt

    umbenennst sollte der Server starten. Wenn das der Fall ist wäre die Frage welcher Timelapse den Absturz verursacht und ob du ihn zur analyse schicken könntest. Meinetwegen auch der ganze Timelapse Ordner, auch wenn der evtl groß ist.
  • edited July 11
    Danke für die hilfe jetzt funktioniert es.
    Habe leider vorhin alles timelapse über das webinterface gelöscht daher ging es jetzt ohne umbenennen des Ordners

  • Ok, immerhin weiß ich wo was stören könnte. Werd mir fürs update das noch mal ansehen und potentielle Fehler absichern also z.b. wenn dateien defekt sind. Meist ist das der Grund wenn Server nicht mehr startet. IN 1.3.0 wurden sie  beim start nicht gelesen denke ich.
Sign In or Register to comment.