Revan335

Super! Vielen Dank!

Hallo, wo kann man nachsehen wieso sich der @Balya borgserver und @mgutt rsync-server Docker Container sporadisch beenden? Vielen Dank! Viele Grüße Revan335

I have this errors after install in the syslog: Event: Unraid Status Subject: syslog error fail Description: Mar 12 00:06:06 Lucy nginx: 2023/03/12 00:06:06 [error] 9968#9968: *70026 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /stub_status HTTP/1.1", host: "localhost" Mar 12 00:06:06 Lucy nginx: 2023/03/12 00:06:06 [error] 9968#9968: *70027 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /stub_status HTTP/1.1", host: "127.0.0.1" Mar 12 00:06:06 Lucy nginx: 2023/03/12 00:06:06 [error] 9968#9968: *70028 open() "/usr/local/emhttp/nginx_status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /nginx_status HTTP/1.1", host: "127.0.0.1" Mar 12 00:06:06 Lucy nginx: 2023/03/12 00:06:06 [error] 9968#9968: *70029 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status HTTP/1.1", host: "127.0.0.1" Mar 12 00:06:06 Lucy nginx: 2023/03/12 00:06:06 [error] 9968#9968: *70031 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /admin/api.php?auth=&version=true HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "127.0.0.1" Mar 12 00:06:06 Lucy nginx: 2023/03/12 00:06:06 [error] 9968#9968: *70033 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /admin/api.php?auth=&version=true HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "localhost" Mar 12 00:06:06 Lucy nginx: 2023/03/12 00:06:06 [error] 9968#9968: *70035 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "localhost" Mar 12 00:06:06 Lucy nginx: 2023/03/12 00:06:06 [error] 9968#9968: *70036 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "127.0.0.1" Mar 12 00:06:08 Lucy nginx: 2023/03/12 00:06:08 [error] 9968#9968: *70041 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?format=plain HTTP/1.1", host: "localhost" Mar 12 00:06:08 Lucy nginx: 2023/03/12 00:06:08 [error] 9968#9968: *70042 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?format=plain HTTP/1.1", host: "127.0.0.1" Mar 12 00:06:08 Lucy nginx: 2023/03/12 00:06:08 [error] 9968#9968: *70043 "/usr/local/emhttp/api/index.html" is not found (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /api/ HTTP/1.1", host: "127.0.0.1" Mar 12 00:06:08 Lucy nginx: 2023/03/12 00:06:08 [error] 9968#9968: *70044 open() "/usr/local/emhttp/status/format/json" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status/format/json HTTP/1.1", host: "127.0.0.1" Mar 12 00:06:09 Lucy nginx: 2023/03/12 00:06:09 [error] 9968#9968: *70047 open() "/usr/local/emhttp/us" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /us HTTP/1.1", host: "localhost" Mar 12 00:06:09 Lucy nginx: 2023/03/12 00:06:09 [error] 9968#9968: *70048 open() "/usr/local/emhttp/us" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /us HTTP/1.1", host: "127.0.0.1" Mar 12 00:06:09 Lucy nginx: 2023/03/12 00:06:09 [error] 9968#9968: *70049 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status?full&json HTTP/1.1", host: "localhost" Mar 12 00:06:09 Lucy nginx: 2023/03/12 00:06:09 [error] 9968#9968: *70050 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /status?full&json HTTP/1.1", host: "127.0.0.1" Mar 12 00:06:09 Lucy nginx: 2023/03/12 00:06:09 [error] 9968#9968: *70051 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: ::1, server: , request: "GET /status?full&json HTTP/1.1", host: "[::1]" Mar 12 00:06:09 Lucy nginx: 2023/03/12 00:06:09 [error] 9968#9968: *70052 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "localhost" Mar 12 00:06:09 Lucy nginx: 2023/03/12 00:06:09 [error] 9968#9968: *70053 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: , request: "GET /server-status?auto HTTP/1.1", host: "127.0.0.1" Importance: alert @dlandon

Das ist denke ich ein separates Script! Gilt das dann für alle Devices im System? Oder muss man da noch seine Geräte eintragen, weil device usage und die $ Variablen müssen ihre Daten woher nehmen. Oder sowas wie: Aber ist die df Abfrage dann nicht doppelt? Bin kein großer Script Experte und übersehe ggf. was. !bin bash device=$(/mnt/remotes/VUDUO4KSE_Harddisk/) usage=$(df -h /mnt/remotes/VUDUO4KSE_Harddisk/ | grep -i "Hard" | awk '{print $5}') while read -r device usage; do logger -t Devices "Error: $device uses $usage of the available space!" done < <(df | tr -s ' ' | cut -d ' ' -f 1,5 | grep -E '9[5-9]%$')

Awesome! Vielen Dank!

Hallo, kann man sich über eine Speicherwarnung benachrichtigen lassen? Würde gerne ne Info über den Speicherverbrauch der VU+ Platte oder anderweitige UD Geräte informiert werden bevorzugt per Mail/Unraid Notification. Gibt es da ne Möglichkeit für? Dann weiß man wenn der Speicher der Platte .... aus geht. Vielen Dank! Viele Grüße Revan335

Hier sprechen die drüber.

Vielen Dank! @alturismo @mgutt Teste es mit den beiden mal. Sieht aber schon mal deutlich besser aus.

Wäre mir nicht bekannt. Leider kein Update seit 2021. Teste es aber mal mit den Werten.

Was hat dein Test ergeben? Hab ebenfalls 2 WD RED SN700. Einmal Board und einmal PCIe Karte. Gigabyte Technology Co., Ltd. C246M-WU4-CF , Version Default string American Megatrends Inc., Version F5 BIOS Datum: Di 09 Nov 2021 12:00:00 AM CET

@alturismoUnd scheinbar diesen Eintrag im syslinux:

@mguttHave the Script a ignored Option for example this Entry's?

@alturismoDu meinst dieses hier? Muss ich mal schauen, das ich den Filter dort finde. Verschwindet es damit nur aus der Anzeige oder auch aus dem Syslog an sich?

@ArchonwKann man auch unterschiedliche Rechte setzen? Bspw. 192.168.178.133 192.168.178.131(sec=sys,rw) 192.168.178.132(sec=sys,r)

Leider nein. Ebenso: mount.nfs: an incorrect mount option was specified Unglaublich! Es funktioniert. Wie geil! Vielen, Vielen Dank! Es klappt sogar mit Name in der fstab sowie in der Regel. Vielen Dank für die Erklärung, wofür die Regel Option ist.

Hallo, kann man diese Syslog Meldungen fixen oder wenn nicht kritisch/unwichtig ausblenden? Event: Unraid Status Subject: syslog error Description: Mar 9 21:55:33 Unraidserver kernel: CIFS: VFS: \\VUSOLO2\Harddisk error -9 on ioctl to get interface list Mar 9 22:05:55 Unraidserver kernel: CIFS: VFS: \\VUSOLO2\Harddisk error -9 on ioctl to get interface list Mar 9 22:16:18 Unraidserver kernel: CIFS: VFS: \\VUSOLO2\Harddisk error -9 on ioctl to get interface list Mar 9 22:26:40 Unraidserver kernel: CIFS: VFS: \\VUSOLO2\Harddisk error -9 on ioctl to get interface list Mar 9 22:37:03 Unraidserver kernel: CIFS: VFS: \\VUSOLO2\Harddisk error -9 on ioctl to get interface list Importance: alert Event: Unraid Status Subject: syslog error Description: Mar 9 21:48:59 Unraidbackupserver kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:02:00.0 Mar 9 21:48:59 Unraidbackupserver kernel: nvme 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Mar 9 21:48:59 Unraidbackupserver kernel: nvme 0000:02:00.0: device [15b7:5006] error status/mask=00000001/0000e000 Mar 9 21:49:04 Unraidbackupserver kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:02:00.0 Das eine ist eine SMB Einbindung per UD von ner USB Platte am VU+ Receiver am Hauptserver. Die andere SMB Meldung kann ich gerade nicht posten weil er Probleme beim verbinden mit dem QNAP NAS und dessen Share hat. Die wäre auch per UD per SMB eingebunden. Das andere ist vermutlich die NVMe die per PCIe Adapter im Backupserver steckt. Die ist im RAID 1 mit der NVMe am Mainboard. Vielen Dank! Viele Grüße Revan335

Privat

No. Only from the Apps Tabs that used the Community Applications for Plugins and Docker.

Many Thanks to all! Specialized to @Frank1940 Its working on Android, Linux, Win not tested at the Moment! Maybe I can found the Root of this Evil and Pain! Can a Parity Check, Sync .... be the cause, this running scheduled quarterly or after a unclear/unclean shutdown?

Vermutlich wurde des Rätsels Lösung gefunden. Die Ursache allerdings noch nicht:

I changed. Reboot in Safe Mode no new Changes of the Permission. Its drwx for user, group, others. Reboot in Normal GUI Mode. No Permission Change. Start VM Service, no Permission Change. Start Docker Service, no Permission Change. SMB Works! Awesome!🤘🎉😘💗🥳🚀🎸🎇🎆🥰😍🤩 I'm testing it tomorrow on the different Devices and Users. And forwarding the New Configuration to the State of the old Boot Drive. Maybe I can find the whatever that change the Permission.

Yes, Docker and VM are deactivated before Boot in Safe Mode. No, I don't entry there.

Do you mean only this three Directorys without Recursive?

Sorry no changes for this three Directorys in Safe Mode. @Frank1940

Have you any Idea for this?