drdebian

Members
  • Posts

    85
  • Joined

  • Last visited

About drdebian

  • Birthday August 31

Converted

  • Gender
    Male
  • ICQ
    6478117

Recent Profile Visitors

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

drdebian's Achievements

Rookie

Rookie (2/14)

10

Reputation

  1. Please, don't try to help me all at once... 😂 It's great to have to rm /var/log/* every day to keep the system running.
  2. Ever since I upgraded to the latest version of Unraid, I keep getting alerts from the "Fix Common Problems" plugin regarding my /var/log being almost full. Indeed it is, with the biggest files being syslog*. Looking at the syslog files more closely, 99% of their contents look something like this: Aug 6 03:14:19 ul18s009 nginx: 2023/08/06 03:14:19 [error] 3265#3265: *6574127 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/notify?buffer_length=1 HTTP/1.1", host: "localhost" Aug 6 03:14:19 ul18s009 nginx: 2023/08/06 03:14:19 [error] 3265#3265: MEMSTORE:00: can't create shared message for channel /notify Aug 6 03:14:20 ul18s009 nginx: 2023/08/06 03:14:20 [crit] 3265#3265: ngx_slab_alloc() failed: no memory Aug 6 03:14:20 ul18s009 nginx: 2023/08/06 03:14:20 [error] 3265#3265: shpool alloc failed Aug 6 03:14:20 ul18s009 nginx: 2023/08/06 03:14:20 [error] 3265#3265: nchan: Out of shared memory while allocating message of size 9033. Increase nchan_max_reserved_memory. Aug 6 03:14:20 ul18s009 nginx: 2023/08/06 03:14:20 [error] 3265#3265: *6574133 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/devices?buffer_length=1 HTTP/1.1", host: "localhost" Aug 6 03:14:20 ul18s009 nginx: 2023/08/06 03:14:20 [error] 3265#3265: MEMSTORE:00: can't create shared message for channel /devices Aug 6 03:14:21 ul18s009 nginx: 2023/08/06 03:14:21 [crit] 3265#3265: ngx_slab_alloc() failed: no memory Aug 6 03:14:21 ul18s009 nginx: 2023/08/06 03:14:21 [error] 3265#3265: shpool alloc failed Aug 6 03:14:21 ul18s009 nginx: 2023/08/06 03:14:21 [error] 3265#3265: nchan: Out of shared memory while allocating message of size 9033. Increase nchan_max_reserved_memory. /var/log seems to be mounted like this according to /etc/mtab: tmpfs /var/log tmpfs rw,relatime,size=131072k,mode=755,inode64 0 0 Any ideas how to further track down the issue?
  3. It's definitely not that I couldn't add something to the go file, quite to the contrary. The problem I have with this is that this feels like an ugly hack that should not be necessary. I really don't understand what has changed from 6.11.x to 6.12.3 that suddenly prevents Unraid from listening to the tailscale network without having its services reloaded in the go file. Something this fundamental should be made available somewhere in the Unraid settings IMHO, especially if people confronted with this new behaviour see downgrading to the previous minor release as their only option.
  4. I'm sorry, but I disagree with this issue being closed. Tailscale used to work perfectly fine on Unraid 6.11.x and now it's broken even on 6.12.3 (which is what I'm on), due to whatever reason that didn't exist on the previous minor release. I don't see myself fuzzing in the go file just to get a particular docker container working that should be working out of the box as it used to be.
  5. I'd go with the i9-9900k, it's gonna make your build much more future proof. If you're running Plex, you'll definitely want the extra horsepower for hardware transcoding using Intel's QSV, which is cheaper and less power hungry (=cooler) than a dedicated GPU for this use case. You'll also appreciate the faster CPU for the nightly jobs Plex is going to run over your library, scanning for intros, creating thumbnails and whatnot, none of which would benefit from GPU or QSV.
  6. Is that gonna include using something like pigz for multicore compression of backups? Would love to see that! In the meantime, is there any way to make the plugin use pigz instead of gzip for compression of files?
  7. I'd recommend Tdarr instead, watching over target folders only.
  8. I have the same problem, something appears to be broken in the nftables script. As far as I can tell, you're not going through the VPN nor Tor due to those problems.
  9. Yes, by all means. I just upgraded to a SuperMicro X11SCQ mainboard, which has 4 fan headers, one of them being for the CPU. It would be great if the auto fan plugin could be enhanced to allow for control over which of the sensor control which of the fans. Right now it's all or nothing, which is kind of suboptimal.
  10. Don't know if this problem still persists, but I found this very helpful: https://yannickdekoeijer.blogspot.com/2012/04/modding-dell-perc-6-sas-raidcontroller.html Basically you have to mask pins 5 and 6 to prevent the card from interrupting the boot process. Worked like a charm on my B360M-D2V.
  11. I wouldn't dare try, it says it may break at any time... not something I want for managing my network...
  12. too bad there's no 6.0.x version of this yet... I have to run the controller on a raspberry pi in the meantime...
  13. Thanks for the quick reply, you got me onto the right track for solving the problem. Turns out that when I first installed Tdarr, I created a share for the Tdarr cache (which was never really used). For some reason, this share now was set to "Use cache drive: yes" (previously no), which in consequence prevented Tdarr from using that path on the SSD directly. Setting the share back to not using the SSD fixed the problem immediately. I will remove the unnecessary share at the earliest opportunity.
  14. Hi guys, have there been any breaking changes in Tdarr recently? I'm running the :qsv branch and I just noticed that all my automatic transcodes of h264->hevc have been failing for at least 2 weeks now (don't ask busy at work, so no time to check my logs before), while everything had been working for several months without problems. At first, I thought it might have to do with bad input files, but running them through my separate Handbrake watch folder worked fine (also using the QSV /dev/dri device as I'm using in Tdarr). Using the same files in Tdarr produced errors, I kept getting "ERROR: avio_open2 failed, errno -2" error messages in the transcoding log. I switched to a non_qsv h265 profile that is otherwise identical, and with that transcoding works, albeit painfully slow. tl;dr: QSV is effectively broken for me and I'm looking for a fix. Any ideas? EDIT: Problem was caused by a misconfiguration on my system, preventing Tdarr from accessing the tdarr-cache path on the SSD.
  15. Hey guys, how can I use Tdarr to transcode my library of audio files down from way too high quality rips? I have a ton of flac and mp3-320 files that I would like to cut down in size by converting them to mp3-192 (more than good enough for my ears and equipment). I guess I'm supposed to use something ffmpeg related, but I'm at a loss how to handle non-video files using which plugins... Any help greatly appreciated!