ljm42
Administrators
-
Joined
-
Last visited
Everything posted by ljm42
-
@Gymnae I moved your post here: https://forums.unraid.net/topic/154030-6128-log-spammed-with-references-to-unraid-apiphp/ @Cout99 Please post your diagnostics in that thread so we can compare them
-
As a first cut I'd suggest rebooting. It is difficult to do a lot of back and forth in the release thread, so if the issues persist please start a new thread here: https://forums.unraid.net/forum/55-general-support/ Be sure to upload your diagnostics.zip file (from Tools -> Diagnostics)
-
Hmm our other conversation about this was in a release thread too, which makes it hard to track conversations across releases. Please open a bug report here: https://forums.unraid.net/bug-reports/stable-releases/ with screenshots and fresh diagnostics. Thanks!
-
You have manually upgraded the OS but the Connect plugin is out of date. Navigate to the Plugins tab and update all plugins, should be good then. Also, be sure to copy the changes.txt file from the 6.12.8 zip along with bz* or things will get confused.
-
This release has two very important fixes around security and data integrity, along with other improvements and bug fixes. All users are encouraged to read the release notes and upgrade. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the Connect, NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.6, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully (this release takes another stab at preventing issues related to Docker not stopping properly) If you have the latest Connect plugin installed, or Unraid 6.12.7-rc2: Open the dropdown in the top-right of the Unraid webgui and click Check for Update. More details in this blog post If you don't have the Connect plugin installed Go to Tools -> Update OS and switch to the "Stable" branch if needed. If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip.
-
So Docker has still been holding the /var/lib/docker mount open for some folks. If you have been affected, please test Unraid 6.12.7-rc2 which does a "lazy unmount" of /var/lib/docker. This means instead of trying to unmount and giving up if it can't, it will wait until it is not in use and then automatically unmount. This should eliminate the need to ever have to manually run `umount /var/lib/docker` again.
-
Thanks for reporting! Unraid 6.12.7-rc2 will strip leading zeros from IP addresses to prevent other folks from running into this:
-
Regarding the Docker security advisory, Unraid 6.12.7-rc2 is now available with Docker 24.0.9 and runc 1.1.12:
-
So Docker has still been holding the /var/lib/docker mount open for some folks. If you have been affected, please test Unraid 6.12.7-rc2 which does a "lazy unmount" of /var/lib/docker. This means instead of trying to unmount and giving up if it can't, it will wait until it is not in use and then automatically unmount. This should eliminate the need to ever have to manually run `umount /var/lib/docker` again.
-
The Unraid 6.12.7-rc1/rc2 releases contain bug fixes and security updates that we'd like feedback on before releasing 6.12.7. If you installed rc1, please upgrade to rc2 as it fixes problems related to installing license keys. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the Connect, NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.6, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type: umount /var/lib/docker The array should now stop successfully (this release takes another stab at preventing issues related to Docker not stopping properly) If you have the Connect plugin installed and updated to the latest version Open the dropdown in the top-right of the Unraid webgui and click Check for Update. More details in this blog post If you don't have the Connect plugin installed Go to Tools -> Update OS and switch to the "Next" branch. If the update doesn't show, click "Check for Updates" Wait for the update to download and install If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. Reboot This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip. Upgrade notes This release has two very important fixes. First, we updated Docker to incorporate fixes for their recent security advisory. Second, we fixed a corner case bug which can lead to data loss if a newly added array drive has a non-standard partition layout. If you add one of these drives, the second time you start the array the drive will show as unformatted. If this happens please contact support and we can help you with data recovery. Even if you have not encountered this issue, we recommend upgrading so that you will not be affected when adding drives in the future. This release also includes some nice fixes in networking, Docker containers, Time Machine support, and VMs as well as fix for a slowdown some systems were having on the Dashboard. We have also improved the SMART attribute handling for NVME and SSD drives. Details below. Known issues Out of date plugins Out of date plugins can cause problems, we recommend they be kept current. Call traces and crashes related to macvlan If you are getting call traces related to macvlan (or any unexplained crashes, really), as a first step we recommend navigating to Settings > Docker, switching to advanced view, and changing the Docker custom network type from macvlan to ipvlan. This is the default configuration that Unraid has shipped with since version 6.11.5 and should work for most systems. Note that some users have reported issues with port forwarding from certain routers (Fritzbox) and reduced functionality with advanced network management tools (Ubiquity) when in ipvlan mode. If this affects you, see the alternate solution available since Unraid 6.12.4. Network problems due to jumbo frames If you are having network issues of any kind, confirm that you have not enabled jumbo frames. Navigate to Settings > Network Settings > eth0 and confirm the Desired MTU is 1500. For more information see the Fix Common Problems warning for jumbo frames. Problems due to Realtek network cards Upgraded kernel fixes the deadlock issue with jumbo frames and the in-tree Realtek 8125 driver. However, we still recommend following the advice above regarding jumbo frames. If you continue to have network stability issues and Tools > System Devices shows that you have a Realtek ethernet controller, grab the part number shown and search Community Apps to see if there is a Realtek vendor-supplied driver plugin for that device. For more information, see the support page for Realtek driver plugins. Other issues? We highly recommend installing the Fix Common Problems plugin as it will warn you of common configuration problems. If you are having other crashes or stability issues, navigate to Settings > Syslog Server and enable Mirror syslog to flash. This will cause additional wear and tear on you USB flash boot device but is useful in the short term for gathering logs after a crash. After the next reboot, navigate to Tools > Diagnostics and download your anonymized diagnostics (as of 6.12.5, diagnostics automatically include logs that were mirrored to the flash drive). Finally, start a new topic and provide all the details of the issue. Once the issue is resolved, be sure to disable Mirror syslog to flash. Rolling back Be aware that rolling back to an earlier release will make your system vulnerable to the Docker security issues and potential data loss scenario mentioned in Upgrade notes. If rolling back earlier than 6.12.6, also see the 6.12.6 release notes. Changes vs. 6.12.6 Bug fixes and improvements Docker: Fix WG routes added to the correct interface (br0 or eth0 or bond0) Use "lazy unmount" unmount of docker image to prevent blocking array stop Updated to address multiple security issues (CVE-2024-21626, CVE-2024-24557) Networking improvements: Boot faster by checking for carrier before assigning DHCP addresses Remove leading zeros from IPv4 and IPv6 addresses New '/etc/rc.d/rc.inet1 status' and '/etc/rc.d/rc.inet1 status ip' commands to aid with network troubleshooting from the command line Notifications: Add ntfy.sh to notification agents SMART improvements: Fix NVME Selftest Fix display of 'Accumulated power on time, hours:minutes xxxxx:yy' SMART attribute Display KB/MB/GB/TB written in SMART Attributes for SSDs Add 'SSD endurance remaining' SMART Attribute System logging: By default, syslog is copied to USB boot flash on shutdown, see Settings > Syslog Server to disable Logs from the above and Mirror syslog to flash are now available the next boot on Tools > Syslog and in diagnostics VM Manager: Fix for downgrade: if the VM template has been updated to the latest QEMU machine type it will not be found upon downgrade. This change finds latest current version for a given machine type. ZFS: Use zpool import "-f" flag to permit import of foreign pools Other: Enable EFI boot by default for fresh installations Fix slowdown on Dashboard and Docker pages (and reduces flash device writes) Formatting: do not initialize device partition layout if already valid. Update OS: redesigned Update OS and Downgrade OS pages, refer to blog post Fix MacOS unable to write 'flash' share and restore Time Machine compatibility (fruit changes) Allow Community Apps (if installed) to automatically start containers when doing a multi-install Feedback form: change DONE button to CANCEL Package updates docker: version 24.0.9 kernel-firmware: version 20231226_abfcad8 Linux kernel version 6.1.74 CONFIG_USB_SERIAL_XR: USB MaxLinear/Exar USB to Serial driver CONFIG_CAN: CAN bus subsystem support CONFIG_CAN_NETLINK: CAN device drivers with Netlink support CONFIG_CAN_GS_USB: Geschwister Schneider UG and candleLight compatible interfaces CONFIG_SCSI
-
Everything in Unraid runs as root, including the Docker Daemon. The better containers then reduce their privs to user 99 and group 100. Moving away from root is a much larger discussion with many consequences. Actually forcing all containers to run as a non-privileged user will reduce the functionality of Docker. For instance, you wouldn't be able to have a backup container that has access to all your files, or give an editor like Code Commit access to edit files on the flash drive. So this is not a change that should be made lightly. This is the first ever Docker escape flaw, and we will have an rc release out soon that resolves it. Note that this flaw is only a problem if the Docker containers you choose to install are malicious. If you are concerned, you may choose to disable any risky containers you have installed, and avoid updating/installing containers until you have updated to the forthcoming rc release.
-
Thanks, I did not notice those diags get added. I'm not sure how we'll solve this yet.
-
Glad you got past it. 6.12.6 has additional protections for this issue with the Docker image. This means something is holding the share open. Be sure to close any open web terminals or SSH shells, if they are open to a share that will prevent the array from stopping.
-
Please review the updated release notes: https://docs.unraid.net/unraid-os/release-notes/6.12.6/ particularly these sections: Call traces and crashes related to macvlan Problems due to Realtek network cards
-
I highly recommend that you leave ipvlan enabled, or take the steps listed in the release notes to make macvlan safe.
-
I'd recommend reading the Known Issues area of the release notes: https://docs.unraid.net/unraid-os/release-notes/6.12.6/ Specifically, you'll want to switch from macvlan to ipvlan and consider installing drivers for your Realtek RTL8125B network card
-
Assuming DHCP is available on your network, probably the easiest is to delete these files from the flash drive and reboot into bare metal: config/network.cfg config/network-rules.cfg
-
Well that is interesting : ) No, in fact it will be easier because you won't have to tell the browser to ignore certificate errors. When used as intended, it will have a fully valid certificate. See https://docs.unraid.net/connect/remote-access/
-
It looks like there might be some partial config files causing problems. On your flash drive, open the config/wireguard folder and delete any files/folders you find there, then refresh the page.
-
Hi, I need to let you know that you are not using Unraid Connect Remote Access as intended. All you are doing is exposing your webgui to the Internet, you are not using our full solution which includes a valid certificate for ip.your-personal-hash.myunraid.net. This is not secure. I would highly recommend NOT using your own DDNS with an invalid certificate, see this blog post for security best practices: https://unraid.net/blog/unraid-server-security-best-practices Having said that, I am trying to figure out what has caused this to stop working between 6.12.4 and 6.12.6. Please do not respond with these private details publicly, either send me a DM in the forum or open support request: https://unraid.net/contact and ask to have it reassigned to ljm42. Either way, please include a link back to this thread so I can more easily follow the conversation. 1) Please show me a screenshot of your router port forwarding config. It should show TCP port 44444 being forwarded to 192.168.0.99, port 443. 2) Please provide me with the full url (including the port) that you think should work to access your server remotely. 3) Go to Settings > Management Access and copy/paste all of the "Local Access URLs" that are listed there. 4) Open a web terminal and run: curl https://wanip.unraid.net Then copy/paste the results. This will tell me your server's WAN IP. 5) In your normal browser from your normal Mac/Windows/whatever computer, while on the same network as the server, with no VPN running, visit https://wanip.unraid.net/ and copy/paste the results 6) Note that on a normal network, the WAN IPs shown for #3 and #4 will be the same. If they are different, you will need to do some research to figure out how your network has multiple WAN IPs.
-
Something on your network is routing outgoing traffic from the Unraid server through a different WAN IP than you are expecting. I'd guess you have it behind some sort of VPN service, but I don't know. Whatever WANIP is used for outgoing communication from the server is the same WANIP that is used for the port forward check and when the Connect Dashboard checks for Remote Access availability.
-
What version did you upgrade from? Is the WAN IP that you blacked out correct? What happens when you press the Check button? Please upload your diagnostics (from Tools -> Diagnostics)
-
This behavior can happen when SSL is disabled, the browser gets fixated on the SSL URL and doesn't want to use the non-SSL URL. The fix is to clear your cache and restart your browser as mentioned in the warning shown when you disable SSL: I would not expect the upgrade from 6.12.3 to 6.12.6 to have disabled SSL, but I'm glad you are back in. If you need help setting up SSL in the new version see https://docs.unraid.net/unraid-os/manual/security/secure-webgui-ssl/
-
Looks like this test could use some improvements for your situation. The good news is it doesn't look like you have anything to worry about: Dec 16 04:35:31 BKHunraid kernel: mce: [Hardware Error]: Machine check events logged Dec 16 04:35:31 BKHunraid kernel: [Hardware Error]: Corrected error, no action required.
-
Can you show a screenshot of what the scanning modal says when it gets stuck? Please also upload your diagnostics (from Tools -> Diagnostics)
