Hallo,

in der log-Datei "graphql-api.txt" sind folgende Fehler aufgeführt:

[07:01:39 ERROR emhttp]: Failed loading state file from "/usr/local/emhttp/state/var.ini" with "Invalid File Path: /usr/local/emhttp/state/var.ini, or Extension: ini" {"apiVersion":"4.29.2+c39b0b26","logger":"emhttp"}

[07:01:39 ERROR emhttp]: Failed loading state file from "/usr/local/emhttp/state/devs.ini" with "Invalid File Path: /usr/local/emhttp/state/devs.ini, or Extension: ini" {"apiVersion":"4.29.2+c39b0b26","logger":"emhttp"}

[07:01:39 ERROR emhttp]: Failed loading state file from "/usr/local/emhttp/state/nginx.ini" with "Invalid File Path: /usr/local/emhttp/state/nginx.ini, or Extension: ini" {"apiVersion":"4.29.2+c39b0b26","logger":"emhttp"}

[07:01:39 ERROR emhttp]: Failed loading state file from "/usr/local/emhttp/state/shares.ini" with "Invalid File Path: /usr/local/emhttp/state/shares.ini, or Extension: ini" {"apiVersion":"4.29.2+c39b0b26","logger":"emhttp"}

[07:01:39 ERROR emhttp]: Failed loading state file from "/usr/local/emhttp/state/disks.ini" with "Invalid File Path: /usr/local/emhttp/state/disks.ini, or Extension: ini" {"apiVersion":"4.29.2+c39b0b26","logger":"emhttp"}

[07:01:39 ERROR emhttp]: Failed loading state file from "/usr/local/emhttp/state/users.ini" with "Invalid File Path: /usr/local/emhttp/state/users.ini, or Extension: ini" {"apiVersion":"4.29.2+c39b0b26","logger":"emhttp"}

[07:01:39 ERROR emhttp]: Failed loading state file from "/usr/local/emhttp/state/sec.ini" with "Invalid File Path: /usr/local/emhttp/state/sec.ini, or Extension: ini" {"apiVersion":"4.29.2+c39b0b26","logger":"emhttp"}

[07:01:39 ERROR emhttp]: Failed loading state file from "/usr/local/emhttp/state/sec_nfs.ini" with "Invalid File Path: /usr/local/emhttp/state/sec_nfs.ini, or Extension: ini" {"apiVersion":"4.29.2+c39b0b26","logger":"emhttp"}

[07:01:39 ERROR UnraidFileModificationService]: Failed to apply modification: auth-request: {} {"apiVersion":"4.29.2+c39b0b26","logger":"api","context":"UnraidFileModificationService"}

[07:01:39 ERROR UnraidFileModificationService]: Failed to check if file /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php should be applied: Error: Failed to compare Unraid version - missing unraid version {"apiVersion":"4.29.2+c39b0b26","logger":"api","context":"UnraidFileModificationService"}

[07:01:39 ERROR UnraidFileModificationService]: Failed to check if file /usr/local/emhttp/plugins/dynamix/DisplaySettings.page should be applied: Error: Failed to compare Unraid version - missing unraid version {"apiVersion":"4.29.2+c39b0b26","logger":"api","context":"UnraidFileModificationService"}

[07:01:39 ERROR UnraidFileModificationService]: Failed to check if file /etc/hosts should be applied: Error: Failed to compare Unraid version - missing unraid version {"apiVersion":"4.29.2+c39b0b26","logger":"api","context":"UnraidFileModificationService"}

[07:01:39 ERROR UnraidFileModificationService]: Failed to check if file /etc/nginx/nginx.conf should be applied: Error: Failed to compare Unraid version - missing unraid version {"apiVersion":"4.29.2+c39b0b26","logger":"api","context":"UnraidFileModificationService"}

[07:01:39 ERROR UnraidFileModificationService]: Failed to check if file /usr/local/emhttp/plugins/dynamix/Notifications.page should be applied: Error: Failed to compare Unraid version - missing unraid version {"apiVersion":"4.29.2+c39b0b26","logger":"api","context":"UnraidFileModificationService"}

[07:01:39 ERROR UnraidFileModificationService]: Failed to check if file /etc/rc.d/rc.nginx should be applied: Error: Failed to compare Unraid version - missing unraid version {"apiVersion":"4.29.2+c39b0b26","logger":"api","context":"UnraidFileModificationService"}

[07:01:39 ERROR UnraidFileModificationService]: Failed to check if file /usr/local/emhttp/plugins/dynamix/include/.set-password.php should be applied: Error: Failed to compare Unraid version - missing unraid version {"apiVersion":"4.29.2+c39b0b26","logger":"api","context":"UnraidFileModificationService"}

[07:01:39 ERROR UnraidFileModificationService]: Failed to check if file /usr/local/emhttp/plugins/dynamix/include/.login.php should be applied: Error: Failed to compare Unraid version - missing unraid version {"apiVersion":"4.29.2+c39b0b26","logger":"api","context":"UnraidFileModificationService"}

[07:01:39 INFO ConnectPluginModule]: Connect plugin initialized with {"mothership":{"status":"PRE_INIT"},"dynamicRemoteAccess":{"runningType":"DISABLED","error":null,"lastPing":null,"allowedUrl":null},"config":{"wanaccess":false,"wanport":null,"upnpEnabled":false,"apikey":"***REDACTED***","localApiKey":"***REDACTED***","username":"","avatar":"","regWizTime":"","dynamicRemoteAccessType":"DISABLED"}} {"apiVersion":"4.29.2+c39b0b26","logger":"api","context":"ConnectPluginModule"}

[08:01:09 INFO ConnectPluginModule]: Connect plugin initialized with {"mothership":{"status":"PRE_INIT"},"dynamicRemoteAccess":{"runningType":"DISABLED","error":null,"lastPing":null,"allowedUrl":null},"config":{"wanaccess":false,"wanport":null,"upnpEnabled":false,"apikey":"***REDACTED***","localApiKey":"***REDACTED***","username":"","avatar":"","regWizTime":"","dynamicRemoteAccessType":"DISABLED"}} {"apiVersion":"4.29.2+c39b0b26","logger":"api","context":"ConnectPluginModule"}

Aufruf der "Management Settings" in der unraid GUI führt zudem zu einen Absturz der Webgui (reagiert nicht mehr).

Mit CLI folgendes erfolglos versucht:

etc/rc.d/rc.nginx restart

etc/rc.d/tc.php-fpm. restart

Beide Befehle reagieren nicht.

Beim anschließenden "reboot" hängt der Start bei "Starting diadnostics collection".

Hard reset startet dann neu.

Weiß jemand Abhilfe?

Sieht nach USB-Stick Problemen aus.
Würde auf einen Neuen wechseln...

Leider hat ein Wechsel des Sticks die Fehlermeldungen nicht verhindert. Sie sind auch mit dem neuen Stick weiterhin in den Logs vorhanden. Neben den o.a. Logs aus der Datei "graphql-api.log" wirft Syslog auch den folgenden Fehler aus:
Error response from daemon: invalid pool request: Pool overlaps with other one on this address space.

7 hours ago, PinkCarlos said:

Error response from daemon: invalid pool request: Pool overlaps with other one on this address space.

Schau mal in die Advanced settings (Schalter oben rechts) deines Docker Dienstes. Gibt es hier mehrere Netze die sich überlappen?

@JorgeB may an idea about the errors from post 1 here ?

They appear to be related to the API (or Connect) ; first, try booting in safe mode, if Connect is the issue, that should no longer happen; if it still happens in safe mode, and if the full diags are not downloading after this happens, see if you can get the syslog

cp /var/log/syslog /boot/syslog.txt

6 hours ago, JorgeB said:

They appear to be related to the API (or Connect) ; first, try booting in safe mode, if Connect is the issue, that should no longer happen; if it still happens in safe mode, and if the full diags are not downloading after this happens, see if you can get the syslog

cp /var/log/syslog /boot/syslog.txt

Safe reboot without emhttp-errors.

What does it mean "related to Connect"?. Are these errors critical?

Do you need logs for further analysis?

If safe mode works, it suggests an issue with a plugin; if you have Connect installed, try uninstalling it, or make sure it's using the latest version.

9 hours ago, _alo_ said:

Schau mal in die Advanced settings (Schalter oben rechts) deines Docker Dienstes. Gibt es hier mehrere Netze die sich überlappen?

Meinst du diesen Schalter?

Die Netze habe alle unterschiedliche Nummernkreise, keine Überlappungen:

jellystat 172.20.0.x

npm_net 192.168.23.0 (macvlan)

proxy 172.18.0.x

immich-net 172.19.0.x

Edited January 27Jan 27 by PinkCarlos

nein, ich meine die docker-dienst Einstellungen:

hast du hier ggf. ein br1 im gleichen Netz wie br0?

Könnte dies zu dem Fehler führen:

Fragen:
1. Wenn ich keine VM hoste, kann dann vhost0 gelöscht werden?
2. Was bedeutet hier "Metric"?

Analog bis auf "Preserve user defined networks":

3 hours ago, JorgeB said:

If safe mode works, it suggests an issue with a plugin; if you have Connect installed, try uninstalling it, or make sure it's using the latest version.

I have deinstalled connect plugin -> no more emhttp-errors in log file.

Mabe errors occur beause the plugin was installed but I was not logged-in.

If so then it should be an improvement with the next release.

Thanks for support.