Report Comments posted by sonic6
-
-
11 hours ago, Naticus said:
Change ipvlan to macvlan. Disable allowing host access to custom networks. Disable custom interface br0.
maybe give it a try withoud "disable host access".
for me just this worked:
-docker stop
-only choose macvlan (letting host access active)
-docker start
-wait for alle containers are started
-docker stop
-switch to ipvlan
-docker start
-
-
-
could you please post your docker run command?
also please post the output from the following terminal command:
docker network list
-
1 hour ago, JorgeB said:
please post new diags to see if there's something else in common.
-
-
so, in every syslog from the past, i found this line:
Sep 11 22:26:02 Unraid-1 crond[1944]: exit status 255 from user root php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1
after that, the GUI stopped working.
i unistalled and reinstalled the plugin. now the unraid gui workes fine for the last 3 weeks.
i think there was a problem with the "User Notes" Plugin:
-
-
-
-
-
-
On 7/20/2024 at 8:10 PM, JorgeB said:
in normal boot it usually happens in 1 to 3 days.
Maybe something to do with RAM?
I had just 32GB RAM until i upgrade two day before. On 32GB the calltrace come instantly.
Here i marked the Calltrace at 15:28PM. After a reboot this morning there wasn't any calltrace yet.
-
so, today i did a RAM upgrade. From 32GB to 64GB.
With 32GB RAM the calltrace came straight after all my docker containers started up.
Now with 64GB the calltrace came with a delay of a few hours.
I don't know if this is of interest.
-
-
-
-
-
-
-
1 minute ago, JorgeB said:
any idea where the second one is coming from?
2003:... is the public one from ISP
fd00::... is the internal one ULA (https://en.wikipedia.org/wiki/Unique_local_address)
there must be also a third one... (LLU)
-
4 minutes ago, JorgeB said:
Probably not, but also post output of
1 hour ago, alturismo said:cat /etc/ntp.conf | grep interface
To see if there's something else there
root@Unraid-1:~# cat /etc/ntp.conf | grep interface interface ignore wildcard interface listen 192.168.0.50 # eth0 interface listen fd00::aaa1:59ff:fe2b:ccfd # eth0 interface listen 2003:c0:cf2c:cd00:aaa1:59ff:fe2b:ccfd # eth0 root@Unraid-1:~#
no, there is only keepalived inside a LXC container on my server
-
-
On 7/2/2024 at 9:56 AM, itimpi said:
Have you gone into the scheduler settings and made a change to the parity check ones and clicked "Apply"?
On 7/2/2024 at 9:59 AM, JorgeB said:you will need to do a dummy change to create the corrected cron entry.
oh, didn't know that, so i am sorry.
i will do the dummy change and test it again.
thank you!
Docker Container dont start br0 not found after update
in Stable Releases
same for me, thank you!