You can import your existing pool and even the config if need be. Try starting a new thread on exactly what’s happening on your drives recognition issue re the v4 installer as I’d like to get that sorted for you as then all other things go away. You also are likely, on the btrfs front, either triggering weakneses in now very old btrfs or have bad memory. This doubles the round trip chat time and break things on slow internet connections. WORKER TIMEOU…īasically you are experiencing a cummulative time out on the Rock-ons as we now redirect from the old http to the new https. Then tried the same again (full reinstall, but i activated my rockstor with a key and enabled stable), same result. Result: took ages and then popped up the empty message below Went to the rockon page, then ‘all’, then clicked update. Is there an issue with rockon update failing? We may be able to address this or track it down at least as that where you need to be really.Īs to the cause of the Rock-on update it’s as mentioned slow internet and a timeout getting the Rock-on info. So I suggest that you start a new thread explaining exactly your experience re the v4 installer. You really shouldn’t be having such difficulties. Take a look at our Pre-Install Best Practice (PBP): But you also likely have a memory issue on your machine. But likely best approached by sorting the openSUSE compatibility bit. So there are literally years of improvements between our 4.10 / 4.12 kernels on the CentOS elrepo side and our new upstream 5.12 kernels with btrfs backports.Įven so your report of many repeated btrfs failures is alarming and uncommon. We now have openSUSE/SuSE on that one which is great, give they now default to using btrfs. Last Stable channel released (3.9.2-57) - April 2020Īlso the reasone we moved from our CentOS base was our failure to keep on top of the kernel updates.Last Testing Channel release (3.9.1-16) - November 2017.Also we no longer support the older CentOS version and haven’t released any updates on our side since ages. Any the core of your update problem is internet speed during the Rock-on update. The installer you are using is now 4 years old, hence the massive amount of updates, work needed on certificate, and the back-config bit. I only caught it because I was trying to figure out what was going on with the I second comment re trying harder with the Suse side. (You guys should also restrict the upload to tar.gz, so the user doesn’t extract the json from inside and try to upload that if an error occurs, like I did), it accepts the upload, it posts things that you can do with the upload but it really doesn’t work, the system can’t use the json and it just silently errors while the user waits. Response = requests.get(remote_root, timeout=10, verify='/etc/ssl/certs/ca-bundle.crt')įile "/opt/rockstor/eggs/requests-1.1.0-py2.7.egg/requests/api.py", line 55, in getĪnd I also had to update /opt/rockstor/src/rockstor/storageadmin/views/config_backup.py to have the fix line 255 isdir(cb_dir) fix so I can import from a backup. Rockstor 3 SSL certificate error when refreshing Rock-ons: a temporary workaround How-toįile "/opt/rockstor/src/rockstor/rest_framework_custom/generic_view.py", line 41, in _handle_exceptionįile "/opt/rockstor/src/rockstor/storageadmin/views/rockon.py", line 395, in _get_available With this fresh install, I also ran into a certificate error trying to update the rockons for the first time I had to rely off this post to help: Note, this is a fresh install, I tried to update to the new version but I’m running into hardware conflicts with Suse it doesn’t see my hard drives and I’m not super interested in trying to over come this issue so I had to roll back to CentOS since that is fully compatible with my hardware. I don’t see any errors coming through /var/log/* or /opt/rockstor/var/log/*īoth remain errorless while I try to run the update so I’m not sure where to look next. Some help would be appreciated, there isn’t an error I can see that I can trace down my self. Here is what the response is from the api/rockons/update command: That’s literally all it says when I try to hit the update button. Unknown internal error doing a POST to /api/rockons/update I’ve tried updating the Rockons but I don’t really get a helpful error message that I can trace down: # Houston, we've had a problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |