jcsnider

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jcsnider

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Yeah the redis changes have kept me stable since December. Highly recommend giving them a shot.
  2. I have had no issues since doing the following 3 changes: Switched to Mysql for NextCloud database storage (although I don't think this solved it) Moved over to using a redis container for Nextcloud cache. Changed the nextcloud docker php config to use redis for session cache. See the edits at the bottom of this post for more info. Ymmv.
  3. Mine has locked up again twice today so I am attempting to dig a little deeper. It appears that if you get the process ids from the processes found in D states using the command I posted above (ps axl | awk '$10 ~ /D/'), you can take those pids and get a list of file handles for those processes using the following command: ls -l /proc/pid/fd Here's my output: If my assumption is that all of these php-fpm workers are getting stuck on disk io, having 4 processes trying to write to that sqlite db could be the problem. I don't have redis or anything setup to ha
  4. Yes, I was using it before. Not sure if it was a problem or not but in trying to debug these issues I have stopped using that option and instead have modified my scripts/applications that store files within NextCloud to also trigger an occ files:scan. I think that option also made page load times take longer but that could have been my imagination. Yes but my Unraid has only been running 1 day, 19 hours. Historically when everything has broken down uptime is greater than 3 days, sometimes upwards of a week or two. Very interesting. I wonder if in your case you wou
  5. I'm guessing if you ssh into your unraid server and try to run lsof on any location (ie: lsof /mnt/user) that will also never finish executing (requiring a new terminal instance in order to issue further commands). If you try to fetch diagnostics it will never finish executing either, and if you try to collect those through the WebUI then eventually the WebUI will start giving 500 errors until it's restarted. I never assigned a /tmp docker path, but I modified the php config within NextCloud to use a subdirectory in the /data folder to store upload data as it's being re
  6. Following up. Same issue is happening here as well. Really diving into the issue tonight in hopes of figuring out what's going on... Other posts/threads that seem to be experiencing the same issue dating back to Unraid v6.5 and NextCloud 18.X.X. (I am on NextCloud 20 with Unraid 6.9.X? Beta 35). I am sort of thinking that the workload to run NextCloud is causing the issue to present itself but NextCloud isn't the actual problem. Instead it might be hardware related. @CyaOnDaNet @p3rky2005 If you ssh into your servers what is the output of the following command? It