Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

TechMed

Members
  • Joined

  • Last visited

Everything posted by TechMed

  1. This was an informative read. It helped me achieve a better understanding of the subtleties of the shutdown process(es) – thanks for that. So, I updated the various timings as suggested and factored these into my current (pun intended) power outage/UPS shutdown timings. I am happy to report that it appears to have worked since we have had yet another outage (this is 2020 right?) and I had a graceful shutdown. Now it is time to dive into gracefully shutting down the network appliances and UPS devices. Thanks again for all the assistance. Happy New Year everyone!
  2. This was a great and informative read. It helped polish the edges of some things I was not sure about. *Recommended Read* --------------------------------------------------------------------------- This is just a quick post to ‘close the loop’ as it were, on this sub. I have opted to go a different route than NC, as the only reason I was installing it was for the CalDav/CardDav capabilities. (It baffles me there isn’t a Docker for just xxxDAV). Anyway, a huge thank you to everyone to contributed, particularly SARRG and CHBMB, with their tireless efforts to help everyone. Irrespective of any one individual, kudos to you all as this is what makes the unRAID community so great. I hope the New Year is a safe, happy, and prosperous one for all! Thanks, everyone!
  3. Thanks for the feedback; I have a total of four UPS devices. They work well and do what they are setup/intended to do, including the shutdown process. The previous post explains the details of where the shutdown hangs. So, plenty of devices to control/regulate/condition the power. Thanks.
  4. Hi @dlandon, I hope your holiday season is going enjoyably! Apologies for the tag, but we went down this road once before and got it fixed, so... Also, I am on 6.8 stable, I do daily plug-in and docker updates, so all are also the latest. I read up to here from our last posts and geez, looks like all the new bits and pieces that have gone into the 6.8 release are keeping you crazy busy; sorry to pile on ☹ I’m having a situation again where the power went out and the primary server did not shut down again until I restarted the ancillary servers; all the details are the same as this previous link we worked. I have attached the logs for you to review at your convenience. Given the increased frequency of our power issues I do want to get this figured out, but no major rush. I truly appreciate all of your hard work; some of the minutia discussed here shows a high understanding on your part. Well done! Thanks! COMPLETE_tower01-diagnostics-20191227-1640.zip tower01-diagnostics-20191227-0533.zip
  5. Happy Christmas Eve! Apparently, my attempt to lookup and understand and implement the ‘docker run’ command was ineffective; I wound up blowing up my configs. Fortunately, I am an avid backer-upper so I was able to restore the config(s) – shout out to Squid! Would you mind sharing the correct syntax for the usage of the command? docker run mariadb and docker run nextcloud most assuredly are not it 😊 Thanks! I will post results immediately afterwards. Appreciate it.
  6. Unfortunately that did not work, same error. Sadly this one popped up as well: An exception occurred while executing 'UPDATE `oc_file_locks` SET `lock` = `lock` + 1, `ttl` = ? WHERE `key` = ? AND `lock` >= 0' with params [1577163023, "files\/7190a9b863f60ecb007e84a38723d83a"]: SQLSTATE[40001]: Serialization failure: 1213 Deadlock found when trying to get lock; try restarting transaction The file I tried to transfer is a 2.4 Gb .iso file. Are there any further potential fixes you might be aware of? Thanks again for your assistance.
  7. Just to follow up: I have made the change but will not be able to test until much later tonight or tomorrow morning (US-EST). Thanks for the suggestions. Gotta run... J
  8. I will; I changed it to the 10G based on some of the other posts/sites solutions that were out there. That line was originally set to '0'. Out of curiosity, and an attempt to understand, does setting it to zero basically make the value unlimited? Thanks again for your assistance!
  9. A few months back, but I thought I removed everything out of the appdata folder. The new install(s) looked like a fresh install when installed a few days ago. I have attached all of the files. Looking at them it appears that the 'default' from Nextcloud does not have a date. So just for complete clarity your saying: stop the containers (LetsEncrypt, MariaDB, and Nextcloud), backup the files listed, DELETE the files listed above, restart the containers, and let those files rebuild themselves? default -from LetsEncrypt default -from Nextcloud nginx.conf proxy.conf ssl.conf
  10. Hi @saarg, Thanks a bunch for replying. Fresh install - four days, maybe. These log files are just clips from from about the middle down. I can provide the entire file(s) if needed. Yes, it is the LSIO image; I am following Ed's install guide from his video's for installing Nextcloud and LetsEncrypt. Thanks again for replying! P.S. Do you have any links to follow for: - How to force delete a file and folder that will not delete from the GUI - (this may belong over in the LetsEncrypt thread) how to check on an Edgerouter that hairpin is actually working?
  11. Hi All - I have read back over 15 pages of this thread along with hours of Googling and it seems like no one has found a solution (or posted if they did) to the “Error when assembling chunks, status code 504” error when transferring larger files. It seems like it occurs whenever the file is larger than about 2 Gb. Also, in order to clear the persistent ‘processing files’ after the 504 error, I just restart the Nextcloud container. I am running the latest LSIO containers of LetsEncrypt, MariaDB, and Nextcloud (shoutout to SpaceInvader One). I am using the container web GUI to ‘copy’ files from a Windows 10 box. While 80% of the files go across like their collective a$$es are on fire, some take quite a while to ‘uploading’ and ‘processing files’. I have found many posts indicating changing certain config files parameters, but other than two of them most don’t seem to exist in the container version; particularly the PHP changes suggested. So, I ask the Community at large if you have had any similar experiences and what, if any, resolutions they may have applied. I have attached chunks of the log files from LetsEncrypt and Nextcloud to show some of the recent errors. Thanks in advance for any assistance! Nextcloud – 17.0.2 PHP - Version: 7.3.12 NEXTCLOUND-PHP-error-log.txt NEXTCLOUND-Ngnix-error-log.txt LETSENCRYPT-Ngnix-access.log
  12. I will do that. Thanks again for taking the time to drill-down into all this. I know for me, UD is becoming a greater necessity as I convinced some of my friends to cloud share their extra storage space. So there are many that appreciate your work. Take care and Happy Holidays to you and yours.
  13. Hello @dlandon, Yes and no. 'No' in so much as when I restarted I did not have to do a parity check 👏. 'Yes' in that the server did not actually shutdown, I had press the power button; this has never happened before. The only reason this incomplete shutdown could be an issue is if I had a power outage, which is how this whole sub-thread got started. Thoughts? (Great job though! Thanks for the fixes!)
  14. Hi @dlandon, Definitely a step closer. Got past the previous stop point, but now stops at: As requested I have attached Diags. Thanks! tower01-diagnostics-20191201-0232.zip
  15. HI @FreeMan I am by no means a wiz with Rsync, but I think the easiest way to accomplish this is to not use the 'delete' flag. Maybe only use that command/flag once every six months or so to do some housecleaning. Hope that sparks some thought. Have a great weekend!
  16. Hi @dlandon, Just double checking, you want the logs from '/flash/logs/' correct? I will play with this over the weekend and post for you. Thanks again for all you do!
  17. Hi @FreeMan, First I am FAR from an expert, but coincidentally I am actually backing up systems right now. There are folks here significantly more knowledgeable about UD than myself. That said I can speak to #3 & #4 from personal experience. #3 - No problems. Have read through the link in #4 and you should be golden! #4 - I think most everyone will agree that a NFS connection is better. With respect to the connection, I HIGHLY recommend looking at this link as @tr0910 (and others) put in a great deal of work to make backups a breeze. I will not lie, it is a bit of work, but not only is it worth the work, it is a fast efficient and @#$%ed near fool-proof method to doing backups. I too started with Duplicati and bailed after the second multi-day backup; Rsync is WAY better. Have fun! This is actually an enjoyable project!
  18. That is the assumption I was running with; stumbled across it by shear luck! haha Despite the occasional head scratching, I really appreciate the tool. For me it makes transferring files between servers, regardless if it between floors or cities, much easier. Thanks again for the assist.
  19. Thanks much for taking a look at it. If this helps at all, when I catch this happening I restart the server that is down and the shutdown proceeds as expected. Thanks again for the info.
  20. please see attached... tower01-diagnostics-20191128-1900.zip
  21. Got it! I do not want to dirty the thread, but for the benefit of the student, do you know where can I research how to write a (in DOS parlance) ".bat" file that can be run before the actual 'shutdown' command is sent? (and thanks for the quick reply!)
  22. Hello @dlandon, Happy Holidays one and all! So, I just had a power outage and the UPS shutdown executed as expected. However, (and I neglected to address this way back when I discovered it, ugh) my Unassigned Devices (UD) do not disconnect during shutdown, if those devices are already off (power outage or not), and the primary halts shutting down. I was able to complete the shutdown and reboot after restarting the other servers UD was connected to prior to power outage. My question is, and please bear with me as I am trying to learn, in an effort to stop this from happening in the future, do I open Putty and copy (cp) the ‘lib.php’ to the ‘/usr/local/emhttp/plugins/unassigned.devices/include/’ directory and restart the primary server? I attached the Diag log and my setup is as follows: I have a dual Mellanox 10Gb NIC in the primary server and single Mellanox 10Gb NIC in two other servers. There is an NFS connection through UD on the primary server to each of the other two servers. If the connections in UD, on the primary server, are not disconnected before the other two servers shutdown, the primary will not execute a clean shutdown and hangs until the other two servers are back up. I am open to any directions, suggestions, solutions. Thanks in advance for your patience and any assistance! tower01-diagnostics-20191129-0019.zip
  23. Decisions, decisions, decisions... Makes perfect "pfSense" to me! Thanks! 😁 I am going to check them out. I am currently leaning the way of @jonathanm, but I am absolutely open to everyone's suggestions as I am still on the fence. Thanks @blaine07! Going to step away as I don't want to booger up the thread. Thanks everyone. Happy Turkey Day in the USA! 🦃
  24. 👍 Thank you for confirming - your doing exactly what I am looking to accomplish. This will be after I get pfSense up and running. Funny, that was an additional question I had. When/if you have the time: Why standalone? and a number of posts around show folks making two pfSense systems up. Why?

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.