SimonC

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by SimonC

  1. Looks like it's a problem with the script when it attempts to parse the kernel version. Line 29 in the plugin_update_helper script attempts to extract the kernel version : NEW_KERNEL_V="$(grep -E -A2 "Linux kernel" /boot/changes.txt | grep -E "Unraid" | awk '{print $3}' | sort -V | tail -1)" but with this release, it returns (CVE-2021-33909. Replacing $3 bt $2 in the awk command return the proper version 5.15.40-Unraid.
  2. So I decided to update my unRAID server this morning from 6.9.2. to the newly released 6.10.0. I clicked the Update button in the Update Tool and I received a notification that some plugins needed to be updated and to wait for another notification before rebooting my server. Two hours later, I am still waiting for the reboot notification... The last notification I received is attached, with my diagnostics ZIP. From what I understand, its checking which plugin from this list I have installed and it updates them. The only one I have is the nvidia plugin if that can help... prometheus-diagnostics-20220518-1246.zip
  3. Is there a way we could get notified when the remote template changes without applying the changes (or not applying them) directly? Something like what is done in Linuxserver SWAG proxy config which notify the user when default templates are updated. Ex: [cont-init.d] 70-templates: executing... **** The following reverse proxy confs have different version dates than the samples that are shipped. **** **** This may be due to user customization or an update to the samples. **** **** You should compare them to the samples in the same folder to make sure you have the latest updates. **** /config/nginx/proxy-confs/adguard.subdomain.conf
  4. @Squid Any chance you could detail the changes that must be made to the templates to avoid ports to be re-added on update? Is it only to set the required field to false? Thanks!