Jump to content

nraygun

Members
  • Content Count

    56
  • Joined

  • Last visited

Community Reputation

2 Neutral

About nraygun

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks! Got it! For those newbies like me, stop the container, go to Edit, turn on Advanced View, then add "--hostname server" to the "Extra Parameters" field where "server" is your new hostname. Start up the container and you're good to go.
  2. How can I change the hostname of this docker? I think I need to edit /etc/hostname and maybe /etc/hosts, but there doesn't seem to be an editor included in the docker container (vi and nano are not found). I just want my system name to be something readable when I access the Rosetta site. Also, the string displayed when I run hostname in the console is different than the Domain name in the Rosetta site. Is there a different way to change it?
  3. Thinking about this more - if Nextcloud updating is a manual process, what gets updated when the docker gets updated? I just noticed an update to the container (along with DuckDNS and Letsencrypt) but it's still at the same version(18.03) and not the latest(18.04).
  4. Thanks, I think I see it. Some text was black and hard to read in my browser, but it looks like doing it through the Web UI is OK. Although, the last time didn't go so well, so maybe next time I'll try the manual method. "For upgrading the Nextcloud version, please see this guide here. Alternatively, you can update via the Nextcloud webui."
  5. Do I need to regularly update Nextcloud from within Nextcloud or do the Docker updates keep Nextcloud up to date?
  6. I got it! I restored an old version of Nextcloud from /data/updater-"instanceID"/backups and ran a manual update and it worked!
  7. My instance of Nextcloud is also stuck. I edited the config.php file as you recommended and now it just says "Update in process". Before it said it was on step 6. Has anyone else gotten their Nextcloud back up and running after trying to upgrade to 18.03? Mine is dead in the water right now!
  8. Yes. Just make sure it's before your backup script. I suppose you could just add the one line to your backup script and put a sleep in there for 15 minutes too.
  9. So wait. I was copying the borg executable from one place to /usr/local/bin on startup so that it's available to a backup script. Not sure that was the right way to do it, but it seemed to be a way to add utilities to the system. Right now, I'm copying this file to /tmp, then chmod +x, then deleting the file after the script is done. Is this the recommended way to do this now?
  10. Ugh. After some experimenting, I found the culprit - MyEtherWallet Chrome Extension. Toggling it makes the issue appear/disappear. Removing it. Not even sure why that extension would even mess with web pages. I cleared a bunch of stuff in my system too. Lesson learned - next time start with extensions.
  11. Upgraded from 6.7.2 and it went fast and smooth. However, I get a double header in my user scripts page using Chrome. If I use Incognito mode in Chrome, it works as does Firefox. I cleared my cache of everything except passwords. There's also a "Waiting for..." message at the bottom left of the screen on this page. I suppose I could use Incognito mode, but I'd rather not. Any ideas?
  12. Day 4 and no errors! This is the longest I've gone with no errors on the backup drive. I think I'm going to call this the solution. I also turned spin down back on. Lesson learned here is that the spin down setting doesn't appear to affect the unassigned drives. Thank you @johnnie.black for the help with this and keeping me on the track of this all being related to spin down!
  13. Day 3 - all good! I'm going to turn on spin down so the array spins down after an hour and see if this still works.
  14. Woohoo! No errors! None on Sunday and none this morning. Will continue to monitor.
  15. No error! I see the scripts ran at the times I expected, this morning at 1am and 1:15am. I won't know if this is the final solution until I get more days with no errors. However, if this happens to be the solution, why wouldn't my wakeup script cause the error too? Afterall, the drive is probably sleeping prior to it running like before the backup script runs. Maybe the backup script does a read or a write when the drive is sleeping that the wakeup script is not doing. I think my script is doing a read. The first thing the backup script does is start a VM which acts like a sort of activity monitor (I start a dummy VM called scripts at the start and then end this VM at the end of script so I can see from the dashboard if the scripts are running). Stay tuned.