Strange periodic problem
pschmehl_lists at tx.rr.com
Tue Oct 24 05:35:32 UTC 2017
--On October 24, 2017 at 12:10:39 AM -0500 Paul Schmehl
<pschmehl_lists at tx.rr.com> wrote:
> --On October 23, 2017 at 11:02:54 PM -0500 Adam Vande More
> <amvandemore at gmail.com> wrote:
>> On Mon, Oct 23, 2017 at 9:51 PM, Paul Schmehl <pschmehl_lists at tx.rr.com>
>> I wrote a script to do database backups. It worked well, so I copied it
>> to another server. I had to alter it, because the db was too big to send
>> through email, so it creates the backup, removes the previous days and
>> then sends email to me notifying me that it ran. Except, it doesn't work.
>> And I have no idea why.
>> The periodic script is executable.
>># ls -lsa /etc/periodic/daily/220.dbbackup
>> 2 -rwxr-xr-x 1 root wheel 37 Oct 19 12:31
>> The script calls sh to run the actual script.
>># cat /etc/periodic/daily/220.dbbackup
>> Periodic.conf enables the script.
>># grep dbbackup /etc/periodic.conf
>> The script itself is executable.
>># ls -lsa /usr/local/bin/dbbackup.sh
>> 2 -rwxr-xr-x 1 root wheel 446 Oct 11 23:40
>> The script runs manually, and I get the email.
>> rm: /usr/home/pauls/102217.alldb.sql: No such file or directory
>> (The previous backup doesn't exist, because the script isn't running
>> What have I missed?
>> Does the cron log indicate entry ran?
> No. But that was a really good question, because now that I look at it
> *none* of the periodic scripts are running. Strange.
This is incorrect. I've confirmed that the jobs are running, but there is
no entry in /var/log/cron for any of them, which seems strange.
I'll have to investigate further.
Paul Schmehl, Retired
More information about the freebsd-questions