flyize

Members
  • Posts

    428
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by flyize

  1. 1 hour ago, JorgeB said:

    It's not logged as a disk problem, and SMART looks fine, a lot of CRC UDMA errors so the SATA cable would be the main suspect.

     

    P.S. lots of OOM errors logged, they appear to be caused by Frigate.

    Someday, I'd love to not have to bother you guys, and maybe be able to help. Where do I go to see that those CRC errors in the diagnostics?

  2. You're an angel! That's wonderful news, as I'm about to be travelling for a week and didn't want this thing to die while I was gone! I'll get the cable swapped out.

     

    Yeah, the OOM errors are annoying. It just started happening with the latest version of Frigate. I've notified the devs, but its pretty much just me with the problem. For some reason, ffmpeg likes to occasionally try to grab 80GB+ of RAM. It was bringing down the whole server before I limited the RAM available to the container.

  3. So in your example, if it gets over 750GB, the script will make a list of files from newest to oldest. Then remove the oldest file from the list and recalculate total space used, and do this over and over until it gets under 750GB. Then pass all this off to the Mover, with a list of files it can't touch. Am I understanding correctly?

  4. 7 minutes ago, trurl said:

    Of course, because they are being emulated by parity.

     

    That does at least answer this question though:

     

    But probably better if you post new diagnostics after you get hardware fixes done.

    I went in an mounted /dev/sdk. It's actually emulating the whole device? If so, how will I know when I get it fixed?

     

    edit: Added diagnostics

    truffle-diagnostics-20240228-1458.zip

  5. Has anyone seen this error and been able to resolve it. I believe it started with v28.

     

    Refused to send form data to 'https://nc.domain.com/index.php/login' because it violates the following Content Security Policy directive: "form-action 'self'".

     

    I'm unable to login via Chrome/Edge. Firefox works just fine.

     

    edit: Seems I asked this a week or so ago and forgot. Apologies. Still would love an answer though!