Jump to content

mikegeezy

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mikegeezy

  • Rank
    Newbie

Recent Profile Visitors

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

  1. @cybrnook My dude thanks very much for the post, that got it going! The hangup on my end was the firewall rule, once I put that in place the unRAID box connected immediately. Synology didn't connect right off the bat, so I started digging around in /usr/syno/etc/ups and realized there are configuration options that aren't really exposed in the control panel GUI (like the UPS name) Clever trick to setup pfSense with what Synology is looking for. Above comment makes more sense to me now. All this had me scratching my head on why it wouldn't connect without the firewall rule, so I went back and added a LISTEN 192.168.1.1 to upsd.conf. And that appears to be working with the firewall rule disabled.
  2. @cybrnook can you please explain the steps required to setup NUT on pfsense? I've got NUT running just fine and talking to the UPS, but I can't manage to get unRAID to connect as a client. I've added a slave user to upsd.users. I was thinking maybe it needs a LISTEN directive to allow an incoming connection from unRAID, but that just breaks the connection between pfSENSE NUT <-> UPS. I was thinking it needs a MODE=netserver in nut.conf, but seems I'm missing a step there. I would love get them talking, seems like I'm overlooking something simple. If you've got the Synology connection working too, I would love to see that as well. Seems like that needs to be routed through SNMP? THANKS
  3. Yes, that's probably the case. I'll have to check when I get home. Although, it seems like there's not a real advantage to using the cache here. Thanks for the feedback fellas. I'm new to unRAID / the community, good to know it's so supportive.
  4. Folks just want to make a public service announcement here for Synology Hyper Backup users (and maybe other source clients?). If your unRAID backup target share is set to use the cache drive, and your cache is smaller than the backup size, you're going to have a bad time. I'm a bit of an unRAID noob, so I beat my head against the wall with this one for like weeks. I tried running rsync in a docker. I tried spinning up a VM. The logs on both end were pretty much useless. I was able to establish the connection and start the backup, but eventually it would always fail and the rsync daemon process would evaporate. I just happened to browse the cache drive and see the backup stuff stacking up there, and wondered why that was. Once I turned off cache for that share, it worked flawlessly. Can anyone comment on potential workarounds to be able to utilize the cache drive in this scenario?