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
-
-
The "docker network ls" command is useful to see what docker has created as networks.
These coming days I'll try to replicate your set up and see in more detail what is happening.
Some explanation: 6.12 uses a different implementation when bridging is disabled and macvlan is enabled, when upgrading from 6.11 - it should - convert automatically to the new settings without user intervention, it is not clear what exactly happens in your situation.
The usual fix is to manually edit the container(s) and set the proper settings.
-
Unraid 6.12.8 has an earlier kernel (point) version, because later kernels have a modification which breaks bonding.
For future Unraid versions we made a modification to support bonding on latest kernel versions.
-
This looks okay.
Can you update to 6.12.8 and provide the same information.
Thx
-
Can you also post a screenshot of the docker settings page with Docker stopped.
-
Something went wrong in the creation of the docker networks.
Feb 16 10:53:04 unraid-outer root: Error response from daemon: network dm-ac543d521cd9 is already using parent interface vhost2.60 Feb 16 10:53:08 unraid-outer root: Error response from daemon: network dm-c962d0d87feb is already using parent interface vhost4.70Can you post a screenshot of your docker settings page (advanced mode)
And post the result of this command
docker network ls -
This is indeed a bug, since routes should be added to either br0 or eth0 (depending on what is in use).
I made a fix for this for upcoming 6.13 version (might get backported to 6.12).
Thanks
-
1
-
-
Every release comes with the latest 6.1.x kernel version available at the time.
I don't remember the exact 6.1.x kernel versions for Unraid 6.12.3 and 6.12.4.
-
54 minutes ago, KluthR said:
Were there big changes between .3 and .4 in the linux base system?
In Unraid 6.12.4 we introduced a fix for macvlan. To make this work seemlessly for users the system automatically updates configuration files and other relevant settings when bridging gets enabled or disabled.
This introduces the config files updates on the flash device.
-
We will incorporate these changes for upcoming Unraid version 6.12.7 (and 6.13 of course).
I have done a similar fix for VMs, which may experience the same thing.
It would be nice if more users can confirm this fix works for them.
Thanks everyone for participating and bringing in some useful information and help to uncover this situation.
Though it is still a mystery to me why some people have slow write access to their flash device, something to keep an eye on.
-
1
-
1
-
-
-
1
-
-
Can you go to Tools -> PHP SettingsError reporting level = All CategoriesThen open the View LogRevisit the pages which end up blank and observe the PHP log for any errors.Please post these errors.ThxFixed my typos, please use the updated files.
The fix is not really the answer to the root cause, which I don't know but it prevents unnecessary writing to the flash device.
-
2
-
-
I made an update for two files which check for changes in the docker configuration and update as needed.
The check now also looks for the presence of _SUBNET_ to make valid changes.
rc.docker --> copy this file to folder /usr/local/etc/rc.d and make the file executable (chmod +x rc.docker)
DockerClient.php --> copy this file to folder /usr/local/emhttp/plugins/dynamix.docker.manager/include
Please test if this solves the delays.
Thx.
-
Followed the same steps (using Unraid version 6.12.6 on Chrome browser)
1. Start system with factory settings
2. Change default timezone to my own timezone (Europe)
Loading the Dashboard page is always instant.
A couple of things you can try, which hopefully give more insight
Try each suggestion at the time to see its effect.
1. Access the system using its IP address. e.g. http://192.168.1.100 (replace by your server address)
2. Under network settings change to a static DNS server assigment, e.g. use 1.1.1.1 or 8.8.8.8
3. Under display settings change "Show Dashboard apps --> None"
4. Do a file system check (using Windows) on your USB device to check for any errors to repair
Ps. The file "php.slow.log" shows the dashboard page loading takes a long time (duh) without further details.
-
This is not about hiding a bug, but starting from scratch and add things back to determine when and where it goes wrong.
-
1
-
-
It is unclear why this is happening, could be specific to your set up.
Try the following
1. Make a backup of your current flash device, see Main -> Flash -> Flash Backup
2. Install the plugin “Dynamix Factory Reset”
3. Do a factory reset and keep your disk assignments.
4. After a reboot the system has all default settings
Check the behavior of the GUI in this state
You can restore docker containers by installing CA and use it to do a restoration (make sure your docker settings are correct before doing so)
Configure your VM settings as required and re-install VMs by creating a new VM and select the existing image.
If desired you can always restore the flash device from the backup using the creator tool.
-
Stop Docker and VM service and retry.
-
Thanks, can you post diagnostics, it will allow us to investigate the issue in more detail.
To access the GUI on its IPv6 address use:
http://[ipv6-address]:portor
https://[ipv6-address]:portIt is a known limitation that SSL/TLS "strict" mode does not support IPv6.
-
Try the following:
1. Clear your browser's cache and cookies history
2. Use a different browser to test
3. Use a different PC to test
-
Not all systems exhibit this issue, but I made an update to minimize cpu load when hovering over the bars for Unraid 6.13.
-
1
-
-
Changed Status to Solved
Changed Priority to Other
-
7 hours ago, Niklas said:
I have notification auto close set to 0 but we still have to acknowledge notifications after closing then?
Next release has automatic acknowledgment when life time is zero.
-
1
-
-
I did a quick test and set the DNSv6 server to the link local address of my router, and this works.
This is how my resolv.conf file looks like.
# Generated by dhcpcd from bond0.dhcp domain bergware.com nameserver 10.0.101.100 nameserver 10.0.101.200 # Generated by rc.inet1 nameserver fe80::1ae8:29ff:febd:80c7 -
6 hours ago, Thx And Bye said:
This is the default behavior for many routers (e.g. OpenWRT) if IPv6 is enabled and the router handles DNS forward.
By default they then advertise their own local IPv4 and link-local/ULA IPv6 as DNS servers via DHCP.
Usually to support DNS resolutions for your local devices. You wouldn't want to advertise a global DNS server via DHCP in this case.
Thanks for this explanation, I was not aware of this implementation.
I have set up a local DNS server (pihole) and configured my router to provide clients with the IP address of pihole as DNS server, this is working fine in combination with DHCP/SLAAC.
As far as I know we haven't changed the "dhcpcd" package which is handling all DHCP requests.
Not sure why dhcpcd would add the interface name to the IP address, this is clearly not needed (wrong).
Perhaps a workaround is to set a static DNS server entry and use the given LL IPv6 address.
-
On 8/17/2023 at 11:20 AM, lucahammer said:
Content of resolv.conf
# Generated by dhcpcd from br0.dhcp, br0.ra domain localdomain nameserver 192.168.178.2 nameserver fe80::1ae8:29ff:fe42:1f04%br0
When DHCP is used then the server obtains the DNS information from your router.
Using a link-local address as DNS server is wrong and your router should be configured with a global DNS server address instead. This could be the IPv6 address of the router itself (if it can act as DNS forwarder) or a public DNS server address.
Alternatively you can set a static DNS entry in the Unraid network settings. e.g. 2001:4860:4860::8888 and/or 2001:4860:4860::8844 (google DNS servers)
SOLVED-ish - Updating 6.11.5 to 6.12.8 - container custom networks all gone on dropdowns
in Stable Releases
Posted
Sorry for the late reply, but I have some personal issues to deal with first.
I can't test at the moment, but there are two ways to deal with your configuration.
1. Define eth0 as bonding interface as well (next to bond2). Then upgrade and see if all assignment are correctly processed.
2. If the above doesn't work, then (temporary) configure eth2 as regular interface (remove bonding)