May 8, 20188 yr I had call traces on my server a few weeks ago. Turned out to be file system corruption on my SSD. Ended up replacing the drive. But now I'm getting them again. ehomeserver-diagnostics-20180507-2243.zip
May 8, 20188 yr 12 minutes ago, trackstarjc2003 said: I had call traces on my server a few weeks ago. Turned out to be file system corruption on my SSD. Ended up replacing the drive. But now I'm getting them again. ehomeserver-diagnostics-20180507-2243.zip Do you have dockers assigned their own IP address on br0 or a VLAN? That is generally what causes macvlan call traces. Not every system gets them, but, I and several others have seen these same call traces and it is always when dockers are assigned their own IP address.
May 8, 20188 yr Author 18 hours ago, Hoopster said: Do you have dockers assigned their own IP address on br0 or a VLAN? That is generally what causes macvlan call traces. Not every system gets them, but, I and several others have seen these same call traces and it is always when dockers are assigned their own IP address. I do. I have Pihole hosted on a separate IP.
May 8, 20188 yr 1 minute ago, trackstarjc2003 said: I do. I have Pihole hosted on a separate IP. I used to have Pi-hole on br0 with a separate IP address as well. It generated macvlan call traces every couple of days. When I added more dockers to br0 with their own IP address, I got call traces more frequently. I have tried several different docker IP configurations to try to isolate the cause. The bottom line is that with even one docker on br0 with its own IP address, I will eventually get call traces. Pi-hole is not the problem, it could be any docker. I have seen the call traces with and without Pi-hole docker in the mix. Currently, I have created a docker VLAN and I have all dockers with a separate IP address on br0.3. It has been over five days without a call trace. In all previous configurations, I had at least one docker on br0 and I could go no more than four days without a call trace. Right now, it appears that br0 is the problem, at least on my system.
May 8, 20188 yr Author 6 minutes ago, Hoopster said: I used to have Pi-hole on br0 with a separate IP address as well. It generated macvlan call traces every couple of days. When I added more dockers to br0 with their own IP address, I got call traces more frequently. I have tried several different docker IP configurations to try to isolate the cause. The bottom line is that with even one docker on br0 with its own IP address, I will eventually get call traces. Pi-hole is not the problem, it could be any docker. I have seen the call traces with and without Pi-hole docker in the mix. Currently, I have created a docker VLAN and I have all dockers with a separate IP address on br0.3. It has been over five days without a call trace. In all previous configurations, I had at least one docker on br0 and I could go no more than four days without a call trace. Right now, it appears that br0 is the problem, at least on my system. Interesting. Unfortunately I only have the one network interface. I might have to get a PCI card. Not sure if pihole will work without its own IP.
May 8, 20188 yr 11 hours ago, trackstarjc2003 said: Interesting. Unfortunately I only have the one network interface. I might have to get a PCI card. Not sure if pihole will work without its own IP. Docker VLANs can still use the unRAID host NIC. My docker VLAN3 has been assigned to the 192.168.3.x subnet whereas the unRAID host as well as everything else on my LAN is in the 192.168.1.x subnet. Both are running on the same physical Ethernet port on my unRAID server. See this discussion for how to do this: I now have Pi-hole running on a Raspberry Pi instead of as a docker, but, it has nothing to do with the call traces. If you want to run Pi-hole on the host/bridge interface, you just need to assign the unRAID GUI to a port other than 80 in Settings>Identification. Pi-hole needs to run on port 80. Edited May 9, 20188 yr by Hoopster
Archived
This topic is now archived and is closed to further replies.