February 26, 201115 yr Noticed this error on my server tonight in the System log - has happened every morning at 04:40:01 since last reboot for some reason. Shawn
February 26, 201115 yr Fixed in -beta5. This error is happening because /etc/cron.daily/logrotate changed in the updated slack release to generate that alert if the logrotate program exits with error, which it is. The error is happening because the files /var/log/btmp and /var/log/wtmp do not exist. These are normal linux log files: wtmp logs all logins, btmp logs all failed (bad) logins. The do not exist on purpose because unRAID doesn't have true user login accounts, so these files are useless and thus deleted. (In other words, these "errors" were happening in 4.7 and below, just not being logged with that alert message.)
Archived
This topic is now archived and is closed to further replies.