Nach deinstallation von Plugin keine Web Zugriff

[Gast]

Hallo zusammen,

ich erreiche die Website Loxberry nicht mehr nach dem ich das 1-Wire-NG Plugin installiert habe.
Zunächst habe ich einen Loxberry neu aufgesetzt (2.0.0.3), dann upgegradet auf 2.0.1.3 und dann das 1-Wire-NG Plugin installiert. Alles lief ohne Probleme. Nach dem Neustart, der nach der Installation gefordert wurde, ist die Website nicht mehr erreichbar.
Ich habe daraufhin Loxberry wieder neu aufgesetzt usw. -> gleiches Verhalten.
Ich habe die o.g. Befehle ausgeführt

• /opt/loxberry/sbin/loxberryupdatecheck.pl querytype=prerelease update=1 nofork=1

root@loxberry:~# /opt/loxberry/sbin/loxberryupdatecheck.pl querytype=prerelease update=1 nofork=1
Subroutine vers_tag redefined at /opt/loxberry/sbin/loxberryupdatecheck.pl line 1157.
================================================== ==============================
<LOGSTART> 23.04.2020 13:47:51 TASK STARTED
<LOGSTART> LoxBerry Update Check
<INFO> LoxBerry Version 2.0.1.3 ( is_raspberry.cfg )
<INFO> Loglevel: 7
<INFO> Version of loxberryupdatecheck.pl is 2.0.0.3
<INFO> Executing user of loxberryupdatecheck is root
<INFO> Locking lbupdate to check if an update is running...
<OK> No update seems to be running currently
<OK> Parameters/settings of this update:
<INFO> querytype: prerelease
Use of uninitialized value $cron in concatenation (.) or string at /opt/loxberry/sbin/loxberryupdatecheck.pl line 200.
<INFO> cron:
Use of uninitialized value in concatenation (.) or string at /opt/loxberry/sbin/loxberryupdatecheck.pl line 201.
<INFO> keepupdatefiles:
Use of uninitialized value in concatenation (.) or string at /opt/loxberry/sbin/loxberryupdatecheck.pl line 202.
<INFO> dryrun:
Use of uninitialized value $formatjson in concatenation (.) or string at /opt/loxberry/sbin/loxberryupdatecheck.pl line 203.
<INFO> output:
<INFO> Current LoxBerry version: v2.0.1.3
<INFO> max_version v2.99.99 calculated from current version
<INFO> Updates limited from : v0.3.0
<INFO> Updates limited to : v2.99.99
<INFO> Start checking releases...
<INFO> Checking for releases from https://api.github.com/repos/mschlen...berry/releases
<INFO> Requesting release list from GitHub...
<INFO> Try 1: Getting release list... (23.04.2020 13:47:53)
<OK> Release list fetched.
<INFO> Parsing release list...
<INFO> Release version : v2.0.1.3
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v2.0.1.3
<OK> Skipping - this is the same version.
<INFO> Release version : v2.0.1.2
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v2.0.1.2
<OK> Skipping - the release is older than current version.
<INFO> Release version : v2.0.1.1
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v2.0.1.1
<OK> Skipping - the release is older than current version.
<INFO> Release version : v2.0.1
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v2.0.1
<OK> Skipping - the release is older than current version.
<INFO> Release version : v2.0.0.4
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v2.0.0.4
<OK> Skipping - the release is older than current version.
<INFO> Release version : v2.0.0.3
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v2.0.0.3
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.4.3
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.4.3
<OK> Skipping - the release is older than current version.
<INFO> Release version : v2.0.0.2
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v2.0.0.2
<OK> Skipping - the release is older than current version.
<INFO> Release version : v2.0.0.1
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v2.0.0.1
<OK> Skipping - the release is older than current version.
<INFO> Release version : v2.0.0.0
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v2.0.0.0
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.4.2.2
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.4.2.2
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.4.2.1
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.4.2.1
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.4.2
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.4.2
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.4.1.1
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.4.1.1
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.4.1
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.4.1
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.4.0.3
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.4.0.3
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.4.0.2
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.4.0.2
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.4.0.1
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.4.0.1
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.4.0
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.4.0
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.2.5.5
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.2.5.5
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.2.5.4
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.2.5.4
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.2.5.3
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.2.5.3
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.2.5.1
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.2.5.1
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.2.5
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.2.5
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.2.4.6
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.2.4.6
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.2.4.5
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.2.4.5
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.2.4.4
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.2.4.4
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.2.4.3
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.2.4.3
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.2.4.2
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.2.4.2
<OK> Skipping - the release is older than current version.
<INFO> Release version : v1.2.4.1
<OK> Filter check passed.
<INFO> Current Version: v2.0.1.3 <--> Release Version: v1.2.4.1
<OK> Skipping - the release is older than current version.
<OK> No new version found: Latest version is v2.0.1.3
<INFO> Keine neue Version gefunden.
<OK> Keine neue Version gefunden.
<LOGEND> 23.04.2020 13:48:04 TASK FINISHED

• systemctl start apache2

root@loxberry:~# systemctl start apache2
Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.

• systemctl status apache2

root@loxberry:~# systemctl status apache2
● apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/apache2.service.d
└─privatetmp.conf
Active: failed (Result: exit-code) since Thu 2020-04-23 13:53:51 CEST; 1min 32s ago
Docs: https://httpd.apache.org/docs/2.4/
Process: 3698 ExecStart=/usr/sbin/apachectl start (code=exited, status=132)

Apr 23 13:53:51 loxberry systemd[1]: Starting The Apache HTTP Server...
Apr 23 13:53:51 loxberry apachectl[3698]: Illegal instruction
Apr 23 13:53:51 loxberry apachectl[3698]: Action 'start' failed.
Apr 23 13:53:51 loxberry apachectl[3698]: The Apache error log may have more information.
Apr 23 13:53:51 loxberry systemd[1]: apache2.service: Control process exited, code=exited, status=132/n/a
Apr 23 13:53:51 loxberry systemd[1]: apache2.service: Failed with result 'exit-code'.
Apr 23 13:53:51 loxberry systemd[1]: Failed to start The Apache HTTP Server.

jetzt weiß ich nicht mehr weiter ... kann mir bitte jemand helfen?
Danke, Daniel

[Gast]

Hier noch ein Nachtrag:

• journalctl -xe

root@loxberry:~# journalctl -xe
-- Subject: Automatic restarting of a unit has been scheduled
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Automatic restarting of the unit systemd-logind.service has been scheduled, as the result for
-- the configured Restart= setting for the unit.
Apr 23 14:02:46 loxberry systemd[1]: Started D-Bus System Message Bus.
-- Subject: A start job for unit dbus.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit dbus.service has finished successfully.
--
-- The job identifier is 13460.
Apr 23 14:02:46 loxberry systemd[1]: Stopped Login Service.
-- Subject: A stop job for unit systemd-logind.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A stop job for unit systemd-logind.service has finished.
--
-- The job identifier is 13396 and the job result is done.
Apr 23 14:02:46 loxberry systemd[1]: Starting Login Service...
-- Subject: A start job for unit systemd-logind.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit systemd-logind.service has begun execution.
--
-- The job identifier is 13396.
Apr 23 14:02:46 loxberry systemd[1]: dbus.service: Main process exited, code=killed, status=4/ILL
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit dbus.service has exited.
--
-- The process' exit code is 'killed' and its exit status is 4.
Apr 23 14:02:46 loxberry systemd[1]: dbus.service: Failed with result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit dbus.service has entered the 'failed' state with result 'signal'.
Apr 23 14:02:46 loxberry systemd[1]: Started D-Bus System Message Bus.
-- Subject: A start job for unit dbus.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit dbus.service has finished successfully.
--
-- The job identifier is 13523.
Apr 23 14:02:46 loxberry systemd-logind[4240]: New seat seat0.
-- Subject: A new seat seat0 is now available
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- Documentation: https://www.freedesktop.org/wiki/Sof...temd/multiseat
--
-- A new seat seat0 has been configured and is now available.
Apr 23 14:03:01 loxberry CRON[4243]: pam_unix(cron:session): session opened for user loxberry by (uid=0)
Apr 23 14:03:01 loxberry CRON[4242]: pam_unix(cron:session): session opened for user loxberry by (uid=0)
Apr 23 14:03:01 loxberry CRON[4250]: (loxberry) CMD (cd / && run-parts --arg=cron=03min /opt/loxberry/system/cron/cron.03min > /dev/null 2>&1)
Apr 23 14:03:01 loxberry CRON[4251]: (loxberry) CMD (cd / && run-parts --arg=cron=01min /opt/loxberry/system/cron/cron.01min > /dev/null 2>&1)
ESCOC

[Christian Fenzl]

Schau mal, ob es den Ordner /opt/loxberry/log/system_tmpfs/apache2/ gibt und ob es dort ein Log gibt.
Evt. fehlt das Verzeichnis, dann startet Apache nicht.

lg, Christian

[Gast]

Danke für deine Antwort Christian,

Ergebnis:

root@loxberry:/opt/loxberry/log/system_tmpfs/apache2# ls -all
total 0
drwxr-xr-x 2 loxberry loxberry 40 Apr 23 13:10 .
drwxr-xr-x 5 loxberry loxberry 160 Apr 23 15:00 ..

kein Log, aber das Verzeichnis existiert.
lG Daniel

[svethi]

Teils gibt es Probleme bei Neuaufgesetzten Loxberrys bezgl. der Systemupdates. Setze den Loxberry nochmal neu auf. Lasse ihn 1 Stunde in Ruhe. Richte ihn ein und starte ihn neu. Führe das Update auf 2.0.1.3 durch. Warte wieder. Starte dann neu und installiere dann das Plugin.

[Gast]

Hey svethi,
ich habs jetzt über Nacht ganz langsam gemacht aber es ist genau der gleiche Fehler. Keine Website erreichbar nach Installation des 1-Wire Plugins.

[Gast]

ich hab hier noch den Install Log:

[Gast]

Ich bin mit meinem Problem umgezogen nachdem ich festgestellt habe, dass es eigentlich zum Thread des Plugins gehört:
Sorry dafür.

https://www.loxforum.com/forum/projektforen/loxberry/plugins/227489-plugin-1-wire-ng/page3