a24425311 Posted February 10, 2019 Share Posted February 10, 2019 (edited) Hi All,  Deleted and Redo, problems solved. 😬 ------- unRaid Version: 6.6.6 HP Microserver n54l 5 HDD 4 + 1 Parity 3TB X 5 Build (No Cache)  I have recently set up a Rsync server on unRaid, it worked like an 1 hour until I moved some files on the destination folder, I don't know why and how this affects the server but now terminal couldn't read rsyncd.conf, it returnscat: /etc/rsyncd.conf: No such file or directory  rsyncd.conf is already placed, the client side couldn't communicate unRaid neither.   The guideline I followedhttps://forums.unraid.net/…/24282-solved-problem-with-sync…/  Any thoughts?  Thanks      Edited February 19, 2019 by a24425311 Quote Link to comment
trurl Posted February 10, 2019 Share Posted February 10, 2019 No need to attach syslog since it is already included in diagnostics zip.  Your link is broken. Can you find that guideline again?  Your go file seems similar to something I had (still have) setup from back on Unraid v4.7. I don't know where to find the guideline I used then either. I think it was written by one of the moderators we seldom see anymore.  I haven't tested it in a while, but it is still in place and my /etc/rsyncd.conf isn't empty. I don't know if it matters but it looks like your go file has that extra rsync stuff on the same line as the emhttp stuff. You might put a line break between them (after the &).  I can't tell from your diagnostics what might be in your /boot/custom folder or if you even have one.         Quote Link to comment
trurl Posted February 10, 2019 Share Posted February 10, 2019 Was this it? I think that is the one I used. Â https://forums.unraid.net/topic/2100-rsync/ Â Quote Link to comment
a24425311 Posted February 10, 2019 Author Share Posted February 10, 2019 (edited) 9 minutes ago, trurl said: Was this it? I think that is the one I used.  https://forums.unraid.net/topic/2100-rsync/  I followed the guide above.  OP was followed your link though.  Let me check my GO file first (but does it matter? since the resync conf file couldn't read by terminal in the first place?)  Thanks.  Edited February 10, 2019 by a24425311 Quote Link to comment
trurl Posted February 10, 2019 Share Posted February 10, 2019 The reason for putting the script in go is so it will get executed at boot and put the conf file in /etc. Â /etc is in RAM so any change made there must be reapplied at boot. Â Quote Link to comment
a24425311 Posted February 10, 2019 Author Share Posted February 10, 2019 (edited) Here are screen caps from MC.  Rsyncd.conf  S20-init.rsyncd  GO  Folder Path Edited February 10, 2019 by a24425311 Quote Link to comment
trurl Posted February 10, 2019 Share Posted February 10, 2019 The last line in S20-init.rsyncd is where it gets put in /etc obviously, but I can't think of any reason why it would have been removed later. I'm a little out of my depth with some of this, since I was just following the guide myself. Quote Link to comment
a24425311 Posted February 11, 2019 Author Share Posted February 11, 2019 I have resolved the problem by simply delete everything I have created and redo the whole process, done! Â Cheers Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.