bonienl

Don't see anything wrong in your diagnostics. How are you monitoring the server? On name or ipv4 or ipv6 address?

It is not exactly the same. In this fresh install NFS is not started (correct) because it isn't enabled, while your previous log showed NFS getting started (wrong) with lots of errors. It is really strange that from the moment nginx is started there are errors, can't explain that. IPv4 and IPv6 both look alright. Don't know if it is related to your ethernet controller card, which is a Realtek 2.5G version (but operating on 1G). If you have another NIC perhaps it is worth to try.

Since 6.11.4, see https://docs.unraid.net/unraid-os/release-notes/6.11.4 Only for new installations, existing installations (people upgrading) need to change manually.

With "gear" I mean different equipment from Ubiquiti, including a router, the USG-Pro-4 in my case. This is only a display thing. Connections work fine. Unifi shows MAC addresses but does not further split out the table when multiple IP addresses have the same MAC address. If it is a concern, why not report an issue to Ubiquiti?

This is exactly the same issue we see in this report https://forums.unraid.net/bug-reports/stable-releases/612-unraid-webui-stop-responding-then-nginx-crash-r2451/page/5/?tab=comments#comment-25548 You can try to use "IPv4 only" (disable IPv6)

This is a bug in netbios. You can ignore the message or disable netbios to stop it.

Thanks for testing This is weird in your logs, because NFS is not enabled, it should not get started at all. Yet it does and gives lots of errors. In my testing enabling / disabling NFS in the GUI gives the correct behavior when starting the system. I never get the errors seen in your log. I checked all your config files and can't find anything wrong. A mystery! Somehow I think the RPC/NFS errors are related to the NGINX errors, or in other words the source of these errors make these services fail. Can you post the content of file: etc/nginx/conf.d/servers.conf Yeah unrelated, has nothing to do with the problem. Limetech site doesn't respond to IPv6. We keep on investigating this issue.

I have Unifi network gear and no issues. For those who need macvlan, because ipvlan doesn't work for them (Fritz users), an alternative solution is to disable the bridge function of br0 and make it a plain eth0 interface. Disabling the bridge function is only applicable when no VMs are used using br0. In the docker container settings, the network needs to be re-assigned to the custom-eth0 interface instead of the custom-brr0 interface. We are collecting as much information as possible about the macvlan issue and are looking into getting the Linux kernel developers involved to find a solution. Rest assurred, we also want this issue to be solved.

There is indeed a regression error in 6.12.3. The docker networks are created without IPv6 subnets. From your log: Jul 16 21:23:21 Z-Storage rc.docker: created network br0 with subnets: 10.1.2.0/24; Jul 16 21:23:22 Z-Storage rc.docker: created network br0.69 with subnets: 10.10.0.0/24; I made a fix and tested this. Jul 17 09:55:24 flora rc.docker: created network br0 with subnets: 10.0.101.0/24; 2a02:xxxx:xxxx:101::/64; Jul 17 09:55:25 flora rc.docker: created network br0.6 with subnets: 10.0.106.0/24; fd4f:71d8:b745:45::/64; Docker network # docker network inspect br0.6 [ { "Name": "br0.6", "Id": "67e3be2092a4ec3e618f2c8088aad5148fcba6c1ac54e37c8c5029bd0d557f0b", "Created": "2023-07-17T09:55:25.314164209+02:00", "Scope": "local", "Driver": "ipvlan", "EnableIPv6": true, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "10.0.106.0/24", "Gateway": "10.0.106.1", "AuxiliaryAddresses": { "server": "10.0.106.21" } }, { "Subnet": "fd4f:71d8:b745:45::/64", "Gateway": "fd4f:71d8:b745:45::1", "AuxiliaryAddresses": { "server6": "fd4f:71d8:b745:45:ae1f:6bff:fee4:7c6a" } } ] }, I guess for the time being, you need to stay on 6.12.2 until a new version is released.

Not correct. When using ipvlan it is still possible to set up containers on br0 with a fixed ip address. And this works correctly. I have about 10 containers running this way, including Plex.

Docker does not accept an IPv6 gateway which is a link local address (fe80::...) You need to change the gateway of br0.69 to something like: 2003:df:1f2c:8e45::1 (of course your router must have this address), like your correct example: fd4f:71d8:b745:45::1 Alternatively: if you are using SLAAC, leave the gateway setting empty, and SLAAC will fill-in the link local address, which is then accepted by Docker (weirdness of Docker).

@SpaceInvader Can you test ipv6 and start the system in safe mode?

This is triggered because the DHCP client on your system is continuously adding and removing IP addresses. It is unclear yet to me why this is happening though. Still studying the diagnostics to find a clue. I have seen similar behavior in other diagnostics (together with failing services) and disabling IPv6 and run IPv4 only solves the problem.

In version 6.12 services are bound to valid IP addresses for security reasons, this includes IPv6 addresses when IPv6 is enabled, this requires both IPv4 and IPv6 to have correct assignments. Earlier versions of Unraid did not have this requirement and an improper IPv6 assignment would probably go unnoticed when the server is accessed on its IPv4 address. Thanks for the additional information, it gives me more insight in what is happening.

This looks a lot better, it is a bit of a puzzle why IPv6 gives so much grief on your system.

Can you test with "IPv4 only" setting on br0 and see if that makes a differrence? Please provide diagnostics of the new test. Thx

Unraid 6.12 has improved security, as part of that services are forced to listening to proper network interfaces (both IPv4 and IPv6). If something is not working correctly networkwise due to wrong configurations, it will impact communication.

Your logs contains traces of macvlan issues, see https://docs.unraid.net/unraid-os/release-notes/6.12.0 about known issues. Change in your docker settings macvlan to ipvlan Update to the latest stable version 6.12.3

You need to check your router configuration, it has issues with IPv6. Jul 10 22:15:50 xxxx dhcpcd[1697]: br0: expired address fda2:612d:c297:4585:265e:beff:fe43:dc4d/64 Jul 10 22:15:50 xxxx dhcpcd[1697]: br0: part of a Router Advertisement expired Alternatively set "IPv4 only".

I have seen this happening when the network.cfg file contains incorrect/corrupted information. As suggested above delete the file "network.cfg" and redo your network settings.

Changed Status to Solved Changed Priority to Other

Changed Priority to Minor

Your plex hardware encoder fails. Jul 15 01:04:54 Thor kernel: Plex Transcoder[976]: segfault at 148572f55000 ip 0000148576547204 sp 00007ffc1563c198 error 4 in ld-musl-x86_64.so.1[148576502000+53000] likely on CPU 12 (core 4, socket 0) Test Plex without hardware encoding enabled. See also https://docs.unraid.net/unraid-os/release-notes/6.12.0 about known issues with i915 driver

Changed Priority to Minor

The included diagnostics are from 6.12.2 and for some unknown reason show an incomplete boot up sequence. The diagnostics are missing the driver for the ethernet controller and hence interfaces are not created. This results obviously in no IP address assignments. According to these diagnostics 6.12.2 doesn't have any interfaces at all, this contradicts your statement about reverting. It is impossible the system has connectivity Install version 6.12.3 and include diagnostics of this version. You are looking at a hardware or driver problem, not a bug.