Why doesn't this list set the REPLY-TO to amanda-users?
Great idea, I'll check. Your right that I'm not running them serially, but
with a 5 minute windows out of cron. I'll write a wrapper around both to
find out, and add some timestamping to my script's errlog.
-dan
> -----Original Message-----
> From: Jeff Pratt [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 05, 2001 6:51 PM
> To: [EMAIL PROTECTED]
> Subject: Re: schedual line 10: syntax error - HELP
>
>
> Just a thought... are you sure your scripts are COMPLETING
> before the
> run???
>
> Jeff
>
> Dan Garthwaite wrote:
>
> > Help! Short of strace'ing the entire amdump *shudder*, I
> can't grep what
> > the hell is causing this error. Any GUESSES even would be more than
> > welcome.
> > -dan
> >
> >
> >>-----Original Message-----
> >>From: [EMAIL PROTECTED]
> >>[mailto:[EMAIL PROTECTED]]On Behalf Of Dan Garthwaite
> >>Sent: Tuesday, December 04, 2001 10:46 AM
> >>To: [EMAIL PROTECTED]
> >>Subject: schedual line 10: syntax error
> >>
> >>
> >>A moment of introduction:
> >> I'm the UNIX administrator for a branch of Science Applications
> >>International Corporation. I've been using amanda quite
> >>happily now for ~6
> >>months to feed an HP SureStore Ultrium 1/20 ( that's 2TB
> >>native ) backing up
> >>a data center of RH7.1 and HPUX 10.20 boxen.
> >>
> >>The problem:
> >> Extending this system now to back up ~100 windows lusers.
> >>Half of these
> >>are mobile laptops. To compensate for the on again, of again
> >>nature of all
> >>the laptops, I've written an nice awk/bash script to autogenerate
> >>/etc/amandapass and append the lusers to
> >>/etc/amanda/Daily/disklist on the
> >>fly, just before amcheck and amdump run.
> >>
> >> I'm pretty sure the scripts run flawlessly. One of the
> >>features of the
> >>scripts is to append a cylinder label ( 100, 101, 102... ),
> >>the same to each
> >>windows host. ( to keep the 16 dumpers from hitting the same
> >>poor laptop )
> >>This also seems to work well during test runs.
> >>
> >> The problem, adding the whole list of 60 or so clients, the
> >>whole dump run
> >>aborts. The logs in /tmp/amanda/*$(date +%Y%m%d).debug all
> >>check out, look
> >>fine, with no errors. The logs in /var/lib/Daily are
> another matter:
> >>
> >> [amanda@amanda Daily]$ tail amdump.1
> >> process6.mtg.saic.com / 0 1 2001:11:20:22:15:7 271 18
> >> process6.mtg.saic.com /stand 0 1 2001:11:20:22:58:8 20 0
> >> morpheus.mtg.saic.com /stand 0 1 2001:11:20:22:15:37 14 0
> >> --------
> >> driver: schedule line 10: syntax error
> >> driver: adding holding disk 0 dir /var/lib/amanda/dumps
> size 97819744
> >> reserving 97819744 out of 97819744 for degraded-mode dumps
> >> taper: DONE [idle wait: 629.108 secs]
> >> taper: writing end marker. [AL5853 OK kb 0 fm 0]
> >> amdump: end at Mon Dec 3 17:15:42 EST 2001
> >>
> >>and
> >> [amanda@amanda Daily]$ tail log.20011203.0
> >> FAIL planner amanda.mtg.saic.com //wiggin_jo/C$ 0 [dumps
> too big, but
> >>cannot incremental dump new disk]
> >> FAIL planner amanda.mtg.saic.com //win2klinux/C$ 0 [dumps
> >>too big, but
> >>cannot incremental dump new disk]
> >> FAIL planner amanda.mtg.saic.com //jagoe_d/C$ 0 [dumps too
> >>big, but cannot
> >>incremental dump new disk]
> >> FAIL planner amanda.mtg.saic.com //saic37/C$ 0 [dumps too
> >>big, but cannot
> >>incremental dump new disk]
> >> FAIL planner amanda.mtg.saic.com //dan_ny3/G$ 0 [dumps too
> >>big, but cannot
> >>incremental dump new disk]
> >> FAIL planner amanda.mtg.saic.com //esri-1/D$ 0 [dumps too
> >>big, but cannot
> >>incremental dump new disk]
> >> FAIL planner amanda.mtg.saic.com //perkins_d/D$ 0 [dumps
> too big, but
> >>cannot incremental dump new disk]
> >> FINISH planner date 20011203
> >> FATAL driver schedule line 10: syntax error
> >> INFO taper tape AL5853 kb 0 fm 0 [OK]
> >>
> >>Where can I debug the 'schedual line 10: syntax error' in
> >>both of these
> >>files?
> >>
> >> -Dan Garthwaite
> >>
> >>
> >>
> >
> >
>
>
>
