yanju
-
Posts
14 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by yanju
-
-
-
-
-
4 hours ago, JorgeB said:
If using ipvlan doesn't work for you, other options are disabling bridge and use macvlan if no VM needs it or use two NICs.
Thanks
I will try to do this -
2 hours ago, shinzi said:
自定义网络不行吗?我用的还是默认的,顶多部分docker用的br0 网络
是的 自定义网络不行
-
On 5/14/2023 at 1:36 PM, shinzi said:
可能是docker的Docker 自定义网络类型的问题?设置为ipvlan就好了……如果原来是macvlan的话
设置成ipvlan 自定义的docker服务器 shh连接 连不上 有什么办法解决吗
-
On 5/15/2023 at 6:23 PM, JorgeB said:
This is harmless, these are not:
May 10 00:19:52 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] May 10 00:19:52 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]
Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
Hello
I switched to ipvlan
But my custom docker server SHH can't connect, is there any way to solve it?
There is no problem under Macvlan -
On 5/14/2023 at 1:36 PM, shinzi said:
可能是docker的Docker 自定义网络类型的问题?设置为ipvlan就好了……如果原来是macvlan的话
已经改成这样了。试试会不会在崩溃 谢谢
-
51 minutes ago, JorgeB said:
This is harmless, these are not:
May 10 00:19:52 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] May 10 00:19:52 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]
Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
Thanks
I will try to do this -
May 14 09:07:16 Tower mcelog: Kernel in lockdown. Cannot enable DIMM error location reporting
-
Hello
My server version is 6.11.5 and I have been experiencing crashes and crashes recently
I read the system log and found that it is a kernel error
I hope to get your help hereSupermicro X10SRL-F
Intel® Xeon® CPU E5-2618L v3 @ 2.30GHz
Linux 5.19.17-Unraid x86_64
bond0: fault-tolerance (active-backup), mtu 1500
May 13 01:12:03 Tower kernel: WARNING: CPU: 6 PID: 1845 at net/netfilter/nf_conntrack_core.c:1208 __nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack]
-
On 5/10/2023 at 9:31 AM, EndlessJY said:
解决了吗?我也是同样的问题,全部失联,服务不能访问,ping不通🥲
并没有解决 我今天早上又崩溃了
-
版本是 6.11.5
每隔大概半个月就会发生这种事情。 unraid 崩溃但是服务器本身还在运行,只是与外界断开 无法登录web和上面的任何docke,并且使用超微自带的IPMI也无法远程关机。只能自己手动强制重启- 1
6.11.5更新至6.12.8 连不上服务器
in Chinese / 简体中文
Posted
网络应该正常的 访问应用界面都可以看到里面的app