Greg Wooledge <wool...@eeg.ccf.org> writes:
> My immediate thought is to stop throwing away the output of these
> commands, so that if one of them is failing or giving warnings, you can
> actually see what's wrong.
>
> At least get rid of the 2>&1 on all 3 lines, so you get the stderr output.
> Or log the stdout and stderr to a file, if you absolutely can't stand
> the thought that you might ever possibly get it mailed to you.
Syslog shows:
Jun 14 00:01:01 wb5agz CRON[5701]: (root) CMD (/usr/local/etc/daily_backup)
Jun 14 00:01:02 wb5agz kernel: [572848.771718] EXT4-fs (sda1): mounted
filesystem with ordered data mode. Opts: (null)
Jun 14 00:01:02 wb5agz kernel: [572848.941297] EXT4-fs (sdb1): mounted
filesystem with ordered data mode. Opts: (null)
Jun 14 00:27:04 wb5agz rsnapshot[5703]: /usr/bin/rsnapshot halfday: completed
successfully
That was actually where the error originated which was mailed to
me.
This next entry is after the drives were unmounted for the
halfday and shows their remount for the daily rotation
Jun 14 00:27:05 wb5agz kernel: [574412.532306] EXT4-fs (sda1): mounted
filesystem with ordered data mode. Opts: (null)
Jun 14 00:27:06 wb5agz kernel: [574412.792220] EXT4-fs (sdb1): mounted
filesystem with ordered data mode. Opts: (null)
Jun 14 00:27:07 wb5agz rsnapshot[5887]: /usr/bin/rsnapshot daily: completed
successfully
The squawks are coming from rsnapshot, itself and it's output
is not blocked from being mailed. What you saw was the beginning
of the body of the mail message indicating a problem
I did remove the tossing of the standard error output on
the mount commands and mhddfs but syslog shows all those commands
as happening normally.
rsnapshot is telling syslog it completed successfully at
the same time I got the spew and rsnapshot basically failed
safely and did not save a new backup
Martin
