error: Ignoring rsyncdlog because of bad file mode - must be 0644 or 0444.

[TheWombat]

Hoping someone can help

 

I upgraded from 6.1.9 to 6.2. The upgrade went smoothly however at 4:40:02am every morning I now receive the following email from my UnRaid server.

 

From: Console and webGui login account

Subject: cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null

Body: error: Ignoring rsyncdlog because of bad file mode - must be 0644 or 0444.

 

My UnRaid server (NAS-03) is setup to receive a daily backup from my Synology server (NAS-02). This was set up a long time ago with help from the LimeTech forum and has not been touched. No errors occurred while on 6.1.x, and this email has only been received since upgrading to 6.2. When upgrading to 6.2. I also did install the Community Applications app.

 

My SysLog has the usual backup entries that start at 1am:

 

Sep 17 01:00:06 NAS-03 rsync[2378]: connect from 192.168.1.62 (192.168.1.62)

Sep 17 01:00:06 NAS-03 rsync[2383]: connect from 192.168.1.62 (192.168.1.62)

Sep 17 01:00:07 NAS-03 rsync[2392]: connect from 192.168.1.62 (192.168.1.62)

Sep 17 01:00:08 NAS-03 rsync[2403]: connect from 192.168.1.62 (192.168.1.62)

Sep 17 01:00:09 NAS-03 rsync[2414]: connect from 192.168.1.62 (192.168.1.62)

Sep 17 01:00:10 NAS-03 rsync[2416]: connect from 192.168.1.62 (192.168.1.62)

....

Sep 17 01:52:31 NAS-03 rsync[25470]: connect from 192.168.1.62 (192.168.1.62)

Sep 17 01:52:32 NAS-03 rsync[25476]: connect from 192.168.1.62 (192.168.1.62)

Sep 17 01:52:33 NAS-03 rsync[25482]: connect from 192.168.1.62 (192.168.1.62)

Sep 17 01:52:34 NAS-03 rsync[25488]: connect from 192.168.1.62 (192.168.1.62)

 

Then at 4:40:02 the following

 

Sep 17 04:40:02 NAS-03 root: Community Applications Auto Update Running

Sep 17 04:40:02 NAS-03 sSMTP[31080]: Creating SSL connection to host

Sep 17 04:40:02 NAS-03 sSMTP[31080]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256

Sep 17 04:40:05 NAS-03 sSMTP[31080]: Sent mail for [email protected] (221 2.0.0 closing connection d27sm7017493qtd.37 - gsmtp) uid=0 username=root outbytes=514

 

For my backup configuration on UnRaid I have the following:

 

\\NAS-03\flash\custom\etc\logrotate.d\rsyncdlog

# Rotate /var/log/rsyncd.log

/var/log/rsyncd.log {
missingok
daily
dateext
compress

}

 

\\NAS-03\flash\custom\etc\rc.d\S20-init.rsyncd

#!/bin/bash

if ! grep ^rsync /etc/inetd.conf > /dev/null ; then 
cat <<-EOF >> /etc/inetd.conf
rsync   stream  tcp     nowait  root    /usr/sbin/tcpd  /usr/bin/rsync --daemon 
EOF
read PID < /var/run/inetd.pid
kill -1 ${PID}
fi

cp /boot/custom/etc/rsyncd.conf /etc/rsyncd.conf
cp /boot/custom/etc/logrotate.d/rsyncdlog /etc/logrotate.d/rsyncdlog

 

\\NAS-03\flash\custom\etc\rsyncd.conf

#The rsyncd.conf file should be placed in the /boot/custom/etc directory. Note that the flash drive it mounted at /boot. So, /boot/custom/etc is really /custom/etc on the flash drive.

uid             = root
gid             = root
use chroot      = no
max connections = 100
pid file        = /var/run/rsyncd.pid
timeout         = 600
log file		= /var/log/rsyncd.log

[dailybackups]
   path = /mnt/user/BackupDaily
   comment = Backups
   read only = FALSE

[weeklybackups]
   path = /mnt/user/BackupWeekly
   comment = Backups
   read only = FALSE

 

I'm unclear as to whether I am now seeing the email error as a result of UnRaid 6.2 or Community Applications or both. And whether this error would have occurred in 6.1.x and it was just that I was not receiving emails about it?

 

File boot\custom\etc\logrotate.d\rsyncdlog currently shows as permissions: -rwxrwxrwx root root

 

By way of attempted solutions I have:

 

logged into console and tried to change file permissions of boot\custom\etc\logrotate.d\rsyncdlog to 0644 or 0444 however the permissions do not change irrespective of logging in as root, using su etc. No error message, just nothing changes.

 

Any suggestions on how to resolve?

 

thanks

 

Alex

 

[TheWombat]

Anyone? Still getting emails at 4:40 each morning ;-(

 

thanks

 

Alex

 

[TheWombat]

Just in case anyone else encounters the same type of issue I can happily say the issue is now solved. After several months of getting the daily email with the error I did some further research which resulted in an edit to my S20-init.rsyncd file to include the line: "chmod 644 /etc/logrotate.d/rsyncdlog".

 

the file contents now are:

 

#!/bin/bash

if ! grep ^rsync /etc/inetd.conf > /dev/null ; then 
cat <<-EOF >> /etc/inetd.conf
rsync   stream  tcp     nowait  root    /usr/sbin/tcpd  /usr/bin/rsync --daemon 
EOF
read PID < /var/run/inetd.pid
kill -1 ${PID}
fi

cp /boot/custom/etc/rsyncd.conf /etc/rsyncd.conf
cp /boot/custom/etc/logrotate.d/rsyncdlog /etc/logrotate.d/rsyncdlog

chmod 644 /etc/logrotate.d/rsyncdlog