Stix

Members
  • Posts

    12
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

Stix's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Figured I'd post this since I'm a complete tool and caused my own pain for months, and it has been driving me crazy! If you're getting the following error: /usr/local/sbin/plexreport:364:in `main': undefined method `[]' for nil:NilClass (NoMethodError) from /usr/local/sbin/plexreport:385:in `<main>' when you run the plexReport command to generate a report. It means your config.yaml is missing the following line(s) at the top: email: title: 'Default Email Header' langauge: 'en' Use this instead: --- email: title: langauge: to blank out the lines (or remove the call within the email_body.erb entirely if you desire). The language line is not required, but the title line (blank or not) is definitely required.
  2. Change the number of CPUs assigned to your folding slot. I found a mention of this issue on the folding forum https://foldingforum.org/viewtopic.php?f=18&t=28863 I haven't been able to access the web UI but I can connect through the os x controller app. I feel like the default settings should work on my network but I still can't connect. ...This is my first post I think. I'm running 2xIntel Xeon E5-2670 @ 2.60GHz on an ASRock EP2C602-4L/D16. This worked perfectly, thanks! Was getting the error: Failed to get assignment from '171.67.108.45:8080': Empty work server assignment and it wasn't working, went through the document and added the following: <cpus v="1"/> Under the CPU Use section. I'm not sure why it matters when it already detects the number of cores but it works!
  3. Most likely not. This was probably caused by the docker change when v6.2 stable was released.
  4. I was able to get the following error: exec: "plexreport": executable file not found in $PATH when being forced to re-load the docker after rebooting my server and all the dockers disappeared. The initial setup had to be re-ran in order to fix the issue in addition to re-installing via template.
  5. Hey all, I am running unRAID v6.2.1 and recently had the main cache drive of my 2 cache drive raid 1 setup fail. I purchased a new cache drive, attached it, and ran a balance. I thought everything was running fine until I went to do a manual trim and noticed it is consistently only trimming 48 kilobytes. Both drives are Samsung 850 EVO 250GB SSD drives. Is there any way I can get trim running properly without backing up the data, formatting the drives, and re-doing my docker image? Here is my drive and raid 1 info: btrfs filesystem show: Total devices 2 FS bytes used 91.01GiB devid 1 size 232.89GiB used 232.88GiB path /dev/sdh1 devid 2 size 232.89GiB used 232.88GiB path /dev/sdi1 btrfs filesystem df: Data, RAID1: total=230.85GiB, used=90.32GiB System, RAID1: total=32.00MiB, used=64.00KiB Metadata, RAID1: total=2.00GiB, used=702.25MiB GlobalReserve, single: total=240.00MiB, used=0.00B Edit: Ended up copying all data to a data drive via midnight commander, formatting the cache drives to riser, then setting them up again as btfrs. Fun times!
  6. Thanks, that is exactly what it was for me too. I added the ip address to the web filtering in eSET Smart Security and good to go now!
  7. I noticed that if I use Safari, CrashPlan works just fine but any other browser it isn't working. Go figure lol
  8. Nice! Would you be able to share those modifications? I've just been dealing with the TV posters being super wide lol
  9. etc This way you can send it to the whole family. Inside the config.yaml.example, there is a section for recipients_email: ['[email protected]', '[email protected]'] You can add that to your config.yaml and then have the cron job trigger using -n so it doesn't send a plex email. (plex owner will still get an email even when this option is selected IIRC)
  10. I think the posters are a set size, but you can try and re-size them by modifying the email_body.erb file and specifying the width / height
  11. I'm getting the exact same thing on a fresh install. Previously, this docker was working flawlessly prior to the latest update.