nblom

I haven't had this issue since I disabled the health check for my plex docker. Are you using Plex with NVIDIA drivers?

I just had it happen again here too. I am back on v6.12-RC5 when it happened. My '/run' had filled up all 32MB. Turns out my plex container had filled up the logs with a bunch of stuff related to the Nvidia Drivers. I have now set the extra parameter of '--no-healthcheck' and that seems to have slowed the increase of the logs down. Edit: I don't think it is directly caused by the Nvida Runtime/Drivers, but more like the healthcheck lines went from "small" to "huge". Example of the new log line: {"level":"info","msg":"Running with config:\n{\n \"AcceptEnvvarUnprivileged\": true,\n \"NVIDIAContainerCLIConfig\": {\n \"Root\": \"\"\n },\n \"NVIDIACTKConfig\": {\n \"Path\": \"nvidia-ctk\"\n },\n \"NVIDIAContainerRuntimeConfig\": {\n \"DebugFilePath\": \"/dev/null\",\n \"LogLevel\": \"info\",\n \"Runtimes\": [\n \"docker-runc\",\n \"runc\"\n ],\n \"Mode\": \"auto\",\n \"Modes\": {\n \"CSV\": {\n \"MountSpecPath\": \"/etc/nvidia-container-runtime/host-files-for-container.d\"\n },\n \"CDI\": {\n \"SpecDirs\": null,\n \"DefaultKind\": \"nvidia.com/gpu\",\n \"AnnotationPrefixes\": [\n \"cdi.k8s.io/\"\n ]\n }\n }\n },\n \"NVIDIAContainerRuntimeHookConfig\": {\n \"SkipModeDetection\": false\n }\n}","time":"2023-05-31T09:45:06-04:00"} {"level":"info","msg":"Using low-level runtime /usr/bin/runc","time":"2023-05-31T09:45:06-04:00"}

Will do! Thanks.

Reverted to RC5 to see if that fixes it. Thanks.

FYI, it happened again. DNS resolution just *poof* gone. Server was running normally just like it has for the years, up until v6.12-rc6.

I have rebooted my server and everything is back to "normal". I will wait and see if 6.12-rc7 resolves this.

adding something more here. Looks like local dns resolution stopped working: root@Fenrir:~# nslookup google.com ;; communications error to ::1#53: connection refused ;; communications error to ::1#53: connection refused ;; communications error to ::1#53: connection refused ;; communications error to 127.0.0.1#53: connection refused ;; no servers could be reached root@Fenrir:~# nslookup google.com 8.8.8.8 Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: google.com Address: 74.125.136.102 Name: google.com Address: 74.125.136.113 Name: google.com Address: 74.125.136.138 Name: google.com Address: 74.125.136.100 Name: google.com Address: 74.125.136.139 Name: google.com Address: 74.125.136.101 Name: google.com Address: 2607:f8b0:4002:c09::64 Name: google.com Address: 2607:f8b0:4002:c09::65 Name: google.com Address: 2607:f8b0:4002:c09::8a Name: google.com Address: 2607:f8b0:4002:c09::8b root@Fenrir:~# nslookup google.com ;; communications error to ::1#53: connection refused ;; communications error to ::1#53: connection refused ;; communications error to ::1#53: connection refused ;; communications error to 127.0.0.1#53: connection refused ;; no servers could be reached root@Fenrir:~#

@Squid I just attempted to stop docker and it failed. I then went to change Network Settings and the UI still thinks docker is running. Got this in the logs: May 25 10:41:55 Fenrir avahi-daemon[29851]: Service "Fenrir" (/services/sftp-ssh.service) successfully established. May 25 10:41:56 Fenrir root: waiting for docker to die ... May 25 10:41:57 Fenrir root: waiting for docker to die ... May 25 10:41:58 Fenrir root: waiting for docker to die ... May 25 10:41:59 Fenrir root: waiting for docker to die ... May 25 10:42:00 Fenrir root: waiting for docker to die ... May 25 10:42:01 Fenrir root: waiting for docker to die ... May 25 10:42:02 Fenrir root: waiting for docker to die ... May 25 10:42:03 Fenrir root: waiting for docker to die ... May 25 10:42:04 Fenrir root: waiting for docker to die ... May 25 10:42:05 Fenrir root: waiting for docker to die ... May 25 10:42:06 Fenrir root: waiting for docker to die ... May 25 10:42:07 Fenrir root: waiting for docker to die ... May 25 10:42:08 Fenrir root: waiting for docker to die ... May 25 10:42:09 Fenrir root: waiting for docker to die ... May 25 10:42:10 Fenrir root: docker will not die! May 25 10:42:10 Fenrir emhttpd: shcmd (419): exit status: 1 May 25 10:42:10 Fenrir emhttpd: shcmd (420): umount /var/lib/docker May 25 10:42:16 Fenrir nmbd[29797]: [2023/05/25 10:42:16.966525, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) May 25 10:42:16 Fenrir nmbd[29797]: ***** May 25 10:42:16 Fenrir nmbd[29797]: May 25 10:42:16 Fenrir nmbd[29797]: Samba name server FENRIR is now a local master browser for workgroup WORKGROUP on subnet 172.28.0.15 May 25 10:42:16 Fenrir nmbd[29797]: May 25 10:42:16 Fenrir nmbd[29797]: ***** fenrir-diagnostics-20230525-1044.zip

Understood. I am using Opnsense as my router with DNS setup as the following: Adguard Home on the router on port 53 --> unbound recursive on port 5353. So far this is the only issue I have seen, which started between rc5 and rc6.

Also, a reboot seems to fix this--for a while.

@Squid So you want me to stop docker and everything? Currently I have a static lease assigned by my router. I use my DNS server from the router as a way to be able to have local DNS resolution. I can try giving it a straight up static IP.

Hi. I am also seeing this. The most obvious way to see this is that Plugins are saying status "not available" as well as Dockers' versions saying "not available". I then went to the console and got: root@Fenrir:~# ping google.com ping: google.com: Name or service not known root@Fenrir:~# Other systems on the same network are not having DNS resolution problems. I don't know if this is related, but this seemed to start AFTER I installed my 1650 Super and the Nvidia Driver Plugin from @ich77. Edit: The diagnostics was pulled while DNS was failing to resolve. I will try to leave it in this state for a bit. Dockers seem to be working fine, so I will leave them running. fenrir-diagnostics-20230525-1001.zip

@limetech Here's what I did: Deleted the two files from /boot/config: rsyslog.cfg rsyslog.conf Rebooted Started the Array Reconfigured the Syslog settings Hit Apply Checked the Syslog and saw that rsyslogd started Verified that there was a file in my share Verified that data was in the file

@Squid I think that worked! Thanks a bunch! Thanks also to @limetech. @Gnomuz we have a way of getting this to work. I am going to close this as solved and retitle as [SOLVED]. There may be more work in order to resolve any issues going from 6.8.3 to 6.9.0 (release). But I will leave that up to these guys.

Changed Status to Solved