Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About master.h

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. I had that same issue, except after startup my calibre log was full of the timeout error messages. I resolved it by editing the calibre docker and removing the fields for GUAC_USER and GUAC_PASSWORD. Started up like a charm and I can get to the webui without issue.
  2. The culprit was in /etc/cron.d/root. Didn't even think to look there, not sure how I knew to put it there in the first place. Thanks @Squid.
  3. Some time ago I had created a cron job to run a simple file copy script to copy out material periodically to deliver to my parents. I've since removed the file, and I can't find any entries for it when editing my cron jobs with "crontab -e" but every minute or so I get these same three entries in the system log: Sep 25 23:11:01 Saidin crond[1730]: exit status 127 from user root /boot/custom/ToParents.sh Sep 25 23:11:02 Saidin sSMTP[29924]: Unable to locate Sep 25 23:11:02 Saidin sSMTP[29924]: Cannot open :0 It's not a big deal at all, my server functions just fine, but it's certainly cluttering up the log. Any suggestions for a fix?
  4. Clearly I didn't follow step 1 of troubleshooting: search the forums. Thanks for the link @wgstarks. From that link, it doesn't sound like that was the cause of the reboot, just an outdated plugin. I couldn't see anything in the logs that looked like a cause, so I'm assuming something funky with the wiring at my buddy's house.
  5. I manage an unraid server for a friend of mine, recently rebuilt from scratch on some new-to-him hardware. Everything's been fine for a few weeks, but overnight had an unexpected reboot. I got a notification the server started an unscheduled parity check approximately 1:30am CST, and when I checked on it around 6am, it had only been up for something like 5.5 hours. So it definitely rebooted. Normally I'd just attribute it to a small power blip, as he doesn't run it on a battery backup (his whole house is on a backup generator in the event of a true power outage) but I saw several errors in the syslog for "missing csrf_token." Never seen that error before, no idea what it means. I've attached diagnostics, and would appreciate any advice. Thanks! boughserver-diagnostics-20190813-1454.zip
  6. I installed the plugin Community Applications on my server. It will add an "apps" tab to your main Unraid webpage. It's sort of like the iOS app store, or Google Play app store. Search/browse for the docker/plugin you want, and it automatically installs from there. You can download the plugin here: https://forums.unraid.net/topic/38582-plug-in-community-applications/ That's how I install all my dockers. I don't know how to add repos in manually.
  7. I can't remember off the top of my head how to clear logs, I think you can force an update on the docker and it'll wipe all the logs. To prevent it you can add this to the "extra parameters" field week you're editing the docker with the advanced settings button turned on. It will limit your max log size to 50 megabytes --log-opt max-size=50m
  8. It's been a bit since I've installed the docker, but it looks from your screenshot that you're missing some configuration options. Here's what mine looks like. "Host Path 2" is what shares I'm syncing. In my case I passed through /mnt because I'm syncing disk-to-disk between two Unraid systems. EDIT: I see you're actually using the Resilio from the limetech repository, I'm using Linuxserver's repo. Not sure what settings to use or not use on the Limetech version.
  9. Server has been running latest 6.7.0 since it was officially released, no problems at all. Earlier this morning my system rebooted itself, and I'm not 100% sure why. I was running a movie through Handbrake, which I'm guessing is the culprit, but not sure. Fix Common Problems suggested pulling diags and posting here because of the "Machine Check Events" message. It also said I should install mcelog, which I have done, but I don't know how to pull logs from it, or if I even need to. Diags attached, any advice is appreciated. saidin-diagnostics-20190514-1427.zip
  10. I copied out the resilio log from the link on the unraid docker page, hopefully that's enough to go on. For what it's worth, resilio still is able to copy files from my local system to the destination system, all the while endlessly indexing disk1. resilio_log.txt
  11. I've been using Resilio-sync successfully for quite some time now, but recently it seems to have gotten stuck "indexing" one of my read only shares, which in this case, is /mnt/disk1. Indexing ran constantly overnight, I woke up to over 44 million reads on disk1 at the main unraid management page. I know I can view the logs for resilio on the docker page, but how do I grab those out short of a copy/paste of the log window?
  12. Thanks for the quick response. This motherboard is fairly old, I want to say the last BIOS update was back in 2011... maybe earlier... so I'll disregard that. I'll check on disk6 extended smart test as well and replace if needed.
  13. Fix Common Problems notified me of some call traces that were found on my server; not sure what this means or what I need to do to fix it. I've attached diagnostics from my server for review. I'm also getting warnings about disk6: "offline uncorrectable" and "current pending sector" is 168. I'm assuming this means I have a failing disk; I've attached the smart report for that disk as well. saidar-diagnostics-20171215-0952.zip saidar-smart-20171215-0956.zip
  14. I actually do this very thing myself. For a long time I had both my main and backup server in the same house (literally a foot away from each other) so a simple rsync worked just fine. However now that I've moved my backup server to an offsite location, I use a docker called Resilio. Resilio on the primary server indexes whatever folders I choose to pass through and copies them to my backup server's instance of Resilio, again to whatever folders I choose. It took a bit to set up, and the initial index takes a while (especially if you have tons of file, pictures for example) but now that it's set up it works really well.