bonienl

Community Developer
  • Posts

    10232
  • Joined

  • Last visited

  • Days Won

    65

Everything posted by bonienl

  1. 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.
  2. 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.
  3. This looks okay. Can you update to 6.12.8 and provide the same information. Thx
  4. Can you also post a screenshot of the docker settings page with Docker stopped.
  5. 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.70 Can you post a screenshot of your docker settings page (advanced mode) And post the result of this command docker network ls
  6. This looks like a problem with your USB stick not being read properly. Please take the USB stick out (shutdown server first) and run a file system check on a windows machine.
  7. 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
  8. How do remotely access the server? Are you using vpn or other method? The picture shows there is no nchan communication (this is the background communication to update the gui). Some how your remote access blocks this.
  9. 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.
  10. 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.
  11. 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.
  12. Kubernetes is aimed at datacenter environments, the Unraid solution is mostly used in home environments. Probably this is not a widely requested feature for home use.
  13. @CiscoCoreX I made some typos, sorry for that. Here are the updated files dashboard-test.zip
  14. @CiscoCoreX Can you go to Tools -> PHP Settings Error reporting level = All Categories Then open the View Log Revisit the pages which end up blank and observe the PHP log for any errors. Please post these errors. Thx Fixed my typos, please use the updated files. @KluthR 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.
  15. Unraid should detect address changes and update. Can you provide diagnostics after an address change happened and the gui still listens to the old address. Ps. Are you not using ipv4?
  16. 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. dashboard-test.zip
  17. 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.
  18. This is not about hiding a bug, but starting from scratch and add things back to determine when and where it goes wrong.
  19. 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.
  20. 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]:port or https://[ipv6-address]:port It is a known limitation that SSL/TLS "strict" mode does not support IPv6.
  21. Thanks for the recommendations. I made some updates for Unraid 6.13.
  22. 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
  23. Not all systems exhibit this issue, but I made an update to minimize cpu load when hovering over the bars for Unraid 6.13.
  24. Changed Status to Solved Changed Priority to Other