bonienl
-
Posts
10233 -
Joined
-
Last visited
-
Days Won
65
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by bonienl
-
-
2 hours ago, emrepolat7 said:
Could this be related to rc?
No, this is not coming from stock Unraid
-
If you get a login prompt it means the destination is reachable but credentials are not accepted.
Try clearing your windows credentials.
-
5 hours ago, DiscoverIt said:
Is there a way to modify how rc.sshd functions?
A future version will add and remove dynamically Wireguard tunnels when these are made active or inactive.
-
Changed Status to Closed
Changed Priority to Other
-
7 hours ago, isvein said:
... the docker implementation on Unraid is not meant to work with custom networks with custom subnets
Unraid is not involved in custom networks created by the user, it is however managing macvlan / ipvlan custom networks.
When you create your own custom networks using docker CLI, it is your own responsiblity to do the correct creation of such a network.
-
In rc6 we have added more security and samba is restricted to valid interfaces with an IP address only.
You need to delete the following line in "Samba extra configuration" configuration
interfaces = "10.0.85.237;capability=RSS,speed=10000000000"This line prevents samba to listen on the main interface.
-
Make sure the default route for your main interrface eth0 is first choice by giving it a metric value of 1
Next, you need to give higher metric values to the default routes configured on your VLAN interfaces or when no default route is needed for these VLAN interfaces, set the metric to 0.
In your current setup system replies may follow different paths, which leads to routing/firewall issues.
-
Quote
In my Duplicacy Container I mounted /mnt/user to /unraid
You should not do that. This gives access to everything on the system, including unwanted shares and content.
Instead use a more specific path, like
/mnt/user/myfolder --> /unraid
-
1
-
1
-
-
2 hours ago, L0rdRaiden said:
I have some macvlan errors but no crashes so far. With 6.11 everything was fine.
Regarding the fix by disable bridging, is that even an option? if I disable bridging how can I give an static IP to every docker?
Sure it is an option if you are NOT using VMs.
When bridge is disabled you need to use the regular interfaces, like eth0 (see docker settings).
Assignment of static IP addresses needs to be redone for the new interface(s) for each container, but works as before.
-
1
-
-
When a process is exited on signal 6 it means it failed to get the memory allocation required to run it.
Start with booting your system in safe mode without plugins, docker and VM running.
Then start adding things.
-
2 hours ago, JorgeB said:
If yes and since it's not the number of cores if might be worth trying with a new Unraid install to rule out any config issues,
I created the plugin "Dynamix Factory Reset" to start the system as new, it preserves the license key and optionally the array and pools.
Backup your configuration first when you want to restore it afterwards.
-
2
-
-
-
-
We discussed this internally, but have no real answer or explanation other then it might be due to high numbered cores.
Since we can not test this ourselves, you might want to try the following:
Instead of isolating high numbered cores, isolate lower numbered cores (< 32) and see if that solves the issue.
-
Thanks for testing.
For the moment, it seems the only reliable macvlan usage is without bridging enabled.
-
Thanks.
Those second and third call traces are caused by something else, don't know exactly what but it is not by macvlan.
-
Are you able to start something on your server which makes "continues" call traces or does it stay with this single call trace?
-
1 hour ago, sonic6 said:
Here we are again:
Does it crash after this?
I have seen something similar but server keeps working.
-
7 hours ago, emb531 said:
I can do this, but why is it happening in the first place? Did something change with Avahi that it restarts every hour now?
You are using automatic IP assignment (DHCP) with a lease time of 2 hours, this means that after 1 hour DHCP will do a renewal, which avahi sees as a restart.
You can make the DHCP lease time longer, e.g. one or more days.
-
I made a small update, please use this version.
You need to edit the network settings, e.g. change automatic to static and back and then apply to make the necessary changes.
-
May 4 06:32:19 AlsServerII kernel: traps: tvh:tcp-start[21116] general protection fault ip:145de58625be sp:145ddaf448b8 error:0 in ld-musl-x86_64.so.1[145de5851000+4b000]
This is indeed a different error, caused by a memory allocation error when loading a module
-
3 hours ago, alturismo said:
sure, 1st feedback, somehow the little Server crashed completely last nite now while i left it in the last state
Thanks for testing, we will further investigate what happened, based on your syslog
-
@alturismo would you mind to do another test?
I made an update to the script we use to initialize the network (see attachment). I don't know if the solution will work and need some testing.
To this test do the following
- Stop docker and vm services
- Copy the file rc.inet1 to folder /etc/rc.d
- Make the file executable: chmod +x /etc/rc.d/rc.inet1
- Reconfigure your eth0 interface and enable bridging again (this triggers a config update with new setting)
- Start docker service
- Reconfigure your container to use macvlan br0 instead of eth0
- Run your test
Thanks
-
1
-
1 minute ago, alturismo said:
ok, for now its looking good after a few minutes, usually the 1st error comes after a few seconds when i put some load on the interface ... so for now, looks like your suspicion could be correct
Thank you for testing, this certainly help us pinpoint the problem.
1 minute ago, alturismo said:may i ask what the downside is with this setup ? (not using a bridge)
Bridge function is required when using VMs.
-
1
-
Unraid OS version 6.12.0-rc6 available
-
-
-
-
-
in Prereleases
Posted
The upcoming rc version has a fix.
I will write a "how to do" once released.