Nach voller RAM-disc startet Apache nicht mehr. Ist backup über SSH möglich ?

Einklappen
X
 
  • Zeit
  • Anzeigen
Alles löschen
neue Beiträge
  • asenden
    Smart Home'r
    • 03.02.2021
    • 33

    #1

    Nach voller RAM-disc startet Apache nicht mehr. Ist backup über SSH möglich ?

    Hallo zusammen,

    habe gerade festgestellt, dass mein loxberry RAM disc vollgelaufen ist. Leider konnte ich den Übeltäter nicht finden und habe daraufhin über SSH den rasberry neu gestartet

    Leider startet nun aber Apache2 nicht mehr ... bzw. nur kurz nach dem start command. D.h. ich komme nicht auf das webinterface, sondern erhalte dort nur "connection refused"

    Wenn ich den status erneut abfrage, erhalte ich diese Fehler

    Code:
    root@loxberry:~# sudo systemctl status apache2.service
    apache2.service - The Apache HTTP Server
    Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
      > privatetemp.conf
    Active: failed (Result: signal) since Wed 2021-02-03 12:57:24 CET; 48min ago
    Docs: https://httpd.apache.org/docs/2.4/
    Main PID: 4288 (code=killed, signal=SEGV)
    Feb 03 12:57:24 loxberry systemd[1]: apache2.service: Service RestartSec=100ms expired, scheduling restart.
    Feb 03 12:57:24 loxberry systemd[1]: apache2.service: Scheduled restart job, restart counter is at 5.
    Feb 03 12:57:24 loxberry systemd[1]: Stopped The Apache HTTP Server.
    Feb 03 12:57:25 loxberry systemd[1]: apache2.service: Start request repeated too quickly.
    Feb 03 12:57:25 loxberry systemd[1]: apache2.service: Failed with result 'signal'.
    Feb 03 12:57:25 loxberry systemd[1]: Failed to start The Apache HTTP Server.
    Ich kann nicht sagen, ob ich Apache noch reparieren kann oder die SD Karte zerschossen ist

    Wäre auch natürlich dankbar wenn Ihr mir bei der Rettung meines Apaches helfen könntet

    Wenn nein würde ich gerne ein manuelles backup (bspw. über SSH) meiner Einstellung und Configs machen. Ist das möglich ?

    Ich habe zwar das backup plugin installiert aber nie zum Laufen bekommen und nun habe ich das Schlamassel

    Ein Neuaufsetzen wäre ein Horror

    Danke im Voraus
  • Christian Fenzl
    Lebende Foren Legende
    • 31.08.2015
    • 11232

    #2
    Führ bitte mal
    /opt/loxberry/sbin/healthcheck.pl
    aus, dann sieht man schon mal besser, ob was Bestimmtes kaputt ist.
    lg, Christian
    Hilfe für die Menschen der Ukraine: https://www.loxforum.com/forum/proje...Cr-die-ukraine

    Kommentar

    • asenden
      Smart Home'r
      • 03.02.2021
      • 33

      #3
      Vielen Dank für die schnelle Antwort, Christian !

      Hier das Ergebnis


      root@loxberry:~# /opt/loxberry/sbin/healthcheck.pl
      Login
      Topic: loxberry/mqttgateway/keepaliveepoch
      Sub: check_lbversion
      Title: LoxBerry Version
      Status: OK (code 5)
      Desc: Checks the LoxBerry Version
      Result: Current Version: 2.2.0.4 / No newer Release available.
      Logfile:
      URL: https://www.loxwiki.eu/x/b4WdAQ

      Sub: check_kernel
      Title: Linux Kernel
      Status: Info (code 6)
      Desc: Checks the current installed Linux Kernel
      Result: Linux loxberry 4.19.118-v7+ #1311 SMP Mon Apr 27 14:21:24 BST 2020 armv7l GNU/Linux
      Logfile:
      URL:

      Sub: check_arch
      Title: System Architecture
      Status: Info (code 6)
      Desc: Checks the system architecture
      Result: ARM / Raspberry Pi 2 Model B Rev 1.1
      Logfile:
      URL:

      Sub: check_cputemp
      Title: CPU Temperature
      Status: OK (code 5)
      Desc: Checks maximum CPU Temperature
      Result: Current CPU Temperature is 46.5°C. Since last reboot the cpu never reached Raspberry's soft or critical temperature limit. This is fine.
      Logfile: /opt/loxberry/log/system/watchdogdata.log
      URL:

      Sub: check_voltage
      Title: Voltage
      Status: OK (code 5)
      Desc: Checks the voltage of the power supply
      Result: No under-voltage nor system throttling nor capped ARM frequency detected. This is fine.
      Logfile:
      URL: https://www.loxwiki.eu/display/LOXBE...dware-Netzteil

      Sub: check_readonlyrootfs
      Title: RootFS
      Status: OK (code 5)
      Desc: Checks if the RootFS is mounted correctly
      Result: RootFS is mounted ReadWrite. This is fine.
      Logfile:
      URL:

      Sub: check_rootfssize
      Title: RootFS free space
      Status: OK (code 5)
      Desc: Checks the rootfs for available space
      Result: LoxBerry's RootFS has more than 10% free discspace (AVAL 8.1GB/SIZE 14.2GB).
      Logfile:
      URL:

      Sub: check_tmpfssize
      Title: RAMDiscs free space
      Status: OK (code 5)
      Desc: Checks the ramdiscs for available space
      Result: All ramdiscs have more than 25% free discspace.
      Logfile:
      URL: https://www.loxwiki.eu/x/QINYAg

      Sub: check_logdb
      Title: Log Database
      Status: OK (code 5)
      Desc: Checks the consistence of the Logfile Database
      Result: Init logfile database is ok. 69 log sessions with 1378 attributes stored. 53 logfiles are managed. Database size is 200.0KB.
      Logfile:
      URL: https://www.loxwiki.eu/x/oIMKAw

      Sub: check_notifydb
      Title: Notification Database
      Status: OK (code 5)
      Desc: Checks the consistence of the Notification Database
      Result: Init notification database is ok. 81 notifications with 178 attributes stored. It contains 15 info and 65 error notifications.Database size is 60.0KB.
      Logfile:
      URL:

      Sub: check_miniservers
      Title: Miniserver Access
      Status: ERROR (code 3)
      Desc: Checks access to your Miniservers
      Result: Error executing the test: Could not query data (stopped at MS Starnberg: 500 Can't connect to localhost:80 (Connection refused) at /opt/loxberry/sbin/healthcheck.pl line 1303.

      Logfile:
      URL: https://www.loxwiki.eu/x/QYgKAw

      Sub: check_reboot_required
      Title: Reboot required
      Status: OK (code 5)
      Desc: Checks if LoxBerry or a plugin requests a reboot
      Result: LoxBerry and plugins do not require a reboot of your LoxBerry.
      Logfile:
      URL: https://www.loxwiki.eu/x/fogKAw

      Sub: check_loglevels
      Title: Plugin Loglevels
      Status: OK (code 5)
      Desc: Checks for debug loglevel
      Result: No plugin is configured for loglevel DEBUG. (Some plugins may have it's own setting)
      Logfile:
      URL:

      Sub: plugincheck_lbbackup
      Title: Plugin LoxBerry Backup
      Status: ERROR (code 3)
      Desc: Warns if LoxBerry Backup failed running backups.
      Result: You have 24 pending error notifications. Last notification: *** ERROR: LoxBerry Backup finished with error. See the logfile for details.
      Backup started at 01.02.2021 04:00:02 and finished at 01.02.2021 04:00:09
      Disk space info on /backup
      /dev/root (/) | Size: 14.16 GB | Used: 5.42 GB | Free: 8.14 GB *** You have 2 backups scheduled.
      Logfile:
      URL:

      Sub: plugincheck_mqttgateway
      Title: Plugin MQTT Gateway
      Status: OK (code 5)
      Desc: Checks the status of broker and MQTT Gateway
      Result: MQTT Gateway running (PID 1017). Current status: Broker state: Connected and subscribed to broker. Config state: Configfile present. UDPIN state: UDP-IN socket connected. Your keepaliveepoch is current.
      Logfile:
      URL:

      Sub: plugincheck_nukismartlock
      Title: Plugin NUKI SmartLock
      Status: UNKNOWN
      Desc:
      Result:
      Logfile:
      URL:

      Kommentar

      Lädt...