[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] Scheduled Backup Error
- Subject: [cobalt-users] Scheduled Backup Error
- From: "Steve Buza" <steve@xxxxxxxxxxxxx>
- Date: Thu Feb 22 22:59:01 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
I'm getting the following email each morning concerning the backup on my
RaQ4i:
From: Cron Daemon [mailto:root@xxxxxxxxxxxxxx]
Sent: Friday, February 11, 2001 4:06 AM
To: root@xxxxxxxxxxxxxx
Subject: Cron <root@www> run-parts /etc/cron.daily
sh: unexpected EOF while looking for `''
sh: -c: line 2: syntax error
Before you flame me, I've searched through the archives and read through 605
entries concerning cron errors, 60+ of which deal with this specific error.
The responses in the archive discussed things like checking each file in
/etc/cron.daily and /etc/logrotate.conf for missing quote characters. All
of the suggestions I found were for things I'd already looked at.
For the sake of completeness, here's my scheduled backup job file:
# Cobalt Networks
# Scheduled Backup
#
# backupset=complete
# target=complete
# protocol=ftp
# resource=username@xxxxxxxxxxxxxxx
# increment=
# scheduled=100
/usr/admserv/cgi-bin/.cobalt/backup/backup.cgi -b complete -t complete -p
ftp -r "username@xxxxxxxxxxxxxx" -s 420 --password 'password'
I have already deleted this file and recreated it through the GUI just to be
sure it wasn't something I had inadvertently touched.
Just for chuckles I ran ./scheduled-backup.admin from the shell and I got
the exact same error 90 seconds into the backup job:
sh: unexpected EOF while looking for `''
sh: -c: line 2: syntax error
...although it doesn't kill the job. And my backup actually completes each
night.
I can't see how the backup is related to cron or logrotate since the same
error occurs when I manually run the script. And of course, all the script
does is run the backup.cgi script under admserv.
Does anyone have an answer for this annoying message? I searched through
the archives for a couple of hours but was unable to find a solution that
works.
Thanks,
Steve