tjb_altf4 Posted February 25, 2019 Share Posted February 25, 2019 15 minutes ago, dmacias said: 47 minutes ago, tjb_altf4 said: Only issue I've come across is a few plugins that have been updated recently won't allow install on 6.6.7 plugin: installed Unraid version is too low, require at least version 6.7.0-rc1 Not a biggie, but something to be aware of. Which plugins? The maximum in the plg file might have been set to 6.6.6 Only Dynamix System Stats now, other one updated for me just then. Quote Link to comment
bonienl Posted February 25, 2019 Share Posted February 25, 2019 The latest version of Dynamix System Stats only runs on Unraid 6.7. For Unraid 6.6 you'll keep using the existing installed version. 1 Quote Link to comment
Kir Posted February 26, 2019 Share Posted February 26, 2019 (edited) I think he meant that the latest version of Dynamix Syststats does not run on this release version of unRaid 6.7.0 - it requires a RC1 or higher. I observed the same behavior. Edited February 26, 2019 by Kir Quote Link to comment
saarg Posted February 26, 2019 Share Posted February 26, 2019 43 minutes ago, Kir said: I think he meant that the latest version of Dynamix Syststats does not run on this release version of unRaid 6.7.0 - it requires a RC1 or higher. I observed the same behavior. This is a thread for version 6.6.7, so still not 6.7 and not compatible with the latest System stats version. Quote Link to comment
Kir Posted February 26, 2019 Share Posted February 26, 2019 Now I feel stupid for misreading the version number 😏 1 Quote Link to comment
nasforthemass Posted February 27, 2019 Share Posted February 27, 2019 upgrade from 6.6.6 to 6.6.7 successful and smooth. thank you. no docker/vm/network issues. 1 Quote Link to comment
chris_netsmart Posted February 27, 2019 Share Posted February 27, 2019 I also upgraded with no issues. 1 Quote Link to comment
patm95 Posted February 28, 2019 Share Posted February 28, 2019 I upgraded to 6.6.7 2 days ago. Today I got an alert that system notifications were disabled and I seemingly can not enable them. Is this associated with the upgrade, or do I have something else going on? Quote Link to comment
Squid Posted February 28, 2019 Share Posted February 28, 2019 11 minutes ago, patm95 said: I upgraded to 6.6.7 2 days ago. Today I got an alert that system notifications were disabled and I seemingly can not enable them. Is this associated with the upgrade, or do I have something else going on? That sounds like either flash drive problems, or it dropped offline Quote Link to comment
patm95 Posted February 28, 2019 Share Posted February 28, 2019 47 minutes ago, Squid said: That sounds like either flash drive problems, or it dropped offline Thank you for the heads up. I will get an extra flash drive ordered and ready. Then reboot and see what happens. I still have the original flash drive and it's 8 years old. Quote Link to comment
ufopinball Posted February 28, 2019 Share Posted February 28, 2019 Upgraded from 6.6.6 to 6.6.7, no problems with Dockers (Plex, Sickbeard) or VMs (LAMP, Win10, Win7) Uptime for 6.6.6: 67 days, 9 hours, 30 minutes Uptime for 6.6.7: 15 hours, 4 minutes and counting Quote Link to comment
PSYCHOPATHiO Posted February 28, 2019 Share Posted February 28, 2019 On 2/26/2019 at 10:56 PM, Kir said: Now I feel stupid for misreading the version number 😏 I upgraded, then started questioning my sanity... Quote Link to comment
Hoopster Posted February 28, 2019 Share Posted February 28, 2019 16 minutes ago, PSYCHOPATHiO said: I upgraded, then started questioning my sanity... Hmmm, yep, forum name checks out. 😀 1 Quote Link to comment
antron12345 Posted February 28, 2019 Share Posted February 28, 2019 I upgraded yesterday from 6.6.6 to 6.6.7 and now all my docker containers are not showing IP addresses in the docker console and non of my containers are network stable. SAB will open after a while and display the interface. Hitting F5 once will cause the interface to go away with a messgae in the browser stating that the page cannot be reached. Hitting F5 again might / might not display the interface again and it cycles thought this. This happens on all containers. Quote Link to comment
Squid Posted March 1, 2019 Share Posted March 1, 2019 Before you do anything else, get rid of CA resource Monitor. Long deprecated. Who knows if it's even compatible. Quote Link to comment
archedraft Posted March 1, 2019 Share Posted March 1, 2019 I upgraded yesterday from 6.6.6 to 6.6.7 and now all my docker containers are not showing IP addresses in the docker console and non of my containers are network stable. SAB will open after a while and display the interface. Hitting F5 once will cause the interface to go away with a messgae in the browser stating that the page cannot be reached. Hitting F5 again might / might not display the interface again and it cycles thought this. This happens on all containers.This happened on all my custom networked (br0) dockers. I edited to network on each one to bridge and let it reconfigure itself and changed it back to custom (br0) and they are back up and running. Quote Link to comment
kmwoley Posted March 3, 2019 Share Posted March 3, 2019 Hey folks - I ran into a problem with this upgrade. I have custom network's configured for Docker (MACVLAN). After the update, all of my containers started just fine. But one of them started to have some networking issues and I started investigating. I tried changing a setting in that container and when I saved the container, it disappeared! Looking deeper, I notice now that under the networking options for the container config any network which was using a MACVLAN network (e.g. br0.55) now shows Network Type of "None" and the custom networks for MACVLAN aren't an option in the container config. If I apply any changes to a container now, it functionally disappears. I'm going to try rolling back to 6.6.6 to see if it solves the issue... but thought you should know. Anyone else seeing this? Quote Link to comment
kmwoley Posted March 3, 2019 Share Posted March 3, 2019 Confirmed. Rolling back to 6.6.6 solved this issue. Container configs can now select the Custom networks for Network Type. Quote Link to comment
user457453944 Posted March 3, 2019 Share Posted March 3, 2019 Doing this update caused my nginx to not start, however when I tired to manually start it I noticed the dhparams file was empty so once I regenerated it all was fine. Quote Link to comment
ThatDude Posted March 4, 2019 Share Posted March 4, 2019 Upgraded from 6.6.6 to 6.6.7 and now have a boot loop at the blue menu screen, it counts backwards down from 5 then just resets it's self and counts down again. I tried each of the menu options and only memtest86 works. Quote Link to comment
limetech Posted March 4, 2019 Author Share Posted March 4, 2019 1 hour ago, ThatDude said: pgraded from 6.6.6 to 6.6.7 and now have a boot loop at the blue menu screen, it counts backwards down from 5 then just resets it's self and counts down again. I tried each of the menu options and only memtest86 works. Reformat the flash device and reinstall your flash backup zip. Quote Link to comment
limetech Posted March 4, 2019 Author Share Posted March 4, 2019 On 3/2/2019 at 6:42 PM, user457453944 said: Doing this update caused my nginx to not start, however when I tired to manually start it I noticed the dhparams file was empty so once I regenerated it all was fine. Sounds like a flash corruption problem. 1 Quote Link to comment
bonienl Posted March 5, 2019 Share Posted March 5, 2019 Please try the following after upgrading to 6.6.7 rm /var/lib/docker/network/files/local-kv.db /etc/rc.d/rc.docker restart The above resets the Docker network definitions. Quote Link to comment
kmwoley Posted March 7, 2019 Share Posted March 7, 2019 I cannot tell you why or how, but after downgrading from 6.6.7 -> 6.6.6 four days ago, and then upgrading again today from 6.6.6 -> 6.6.7 the issue I reported before (i.e. Custom Network Types not appearing in Docker Container configuration) appears to have gone away. 🤷♂️ Quote Link to comment
Rick Sanchez Posted March 13, 2019 Share Posted March 13, 2019 Since the upgrade, I can no longer access unraid via web GUI, nor via any other machine. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.