On Sat, Jun 03, 2006 at 11:22:16AM -0400, Jean-Louis Martineau wrote:
> Jon LaBadie wrote:
> >On Fri, Jun 02, 2006 at 08:28:40PM -0400, Jean-Louis Martineau wrote:
> >  
> >>Jon LaBadie wrote:
> >>    
> >>>Following up to my own reply:
> >>>
> >>>I checked the most recent debug files and they show the "*.new" files
> >>>are being used.  For example, corresponding to the last listing above,
> >>>two lines from sendbackup...debug:
> >>>
> >>>sendbackup-gnutar: time 0.207: doing level 1 dump as listed-incremental \
> >>> to /var/lib/amanda/gnutar-lists/bigcowUSR_1.new
> >>>
> >>>sendbackup: argument list: gtar --create --file - --directory /usr \
> >>> --one-file-system \
> >>> --listed-incremental /var/lib/amanda/gnutar-lists/bigcowUSR_1.new \
> >>> --sparse --ignore-failed-read --totals \
> >>> --exclude-from /tmp/amanda/sendbackup.USR.20060602043755.exclude .
> >>> 
> >>>      
> >>sendbackup should rename the file (remove  the .new) when the backup 
> >>finish.
> >>Anything in the log showing why it don't rename it?
> >>
> >>That's why you get full dump at every level.
> >>    
> >
> >
> >Nothing about failure to rename, just failure to open the *_0 file.  Here 
> >is
> >a section from one of the clients.
> >
> >  sendbackup: time 0.005: got all connections
> >  sendbackup: time 0.006: spawning /usr/bin/gzip in pipeline
> >  sendbackup: argument list: /usr/bin/gzip --fast
> >  sendbackup-gnutar: time 0.007: pid 21554: /usr/bin/gzip --fast
> >  sendbackup-gnutar: time 0.014: error opening \
> >    /usr/local/var/amanda/gnutar-lists/butchU_0: No such file or directory
> >  sendbackup-gnutar: time 0.014: doing level 1 dump as listed-incremental \
> >    to /usr/local/var/amanda/gnutar-lists/butchU_1.new
> >  sendbackup-gnutar: time 0.307: doing level 1 dump from date: 1970-01-01  
> >  0:00:00 GMT
> >  sendbackup: Can't open exclude file 
> >  '/usr/local/lib/amanda/exclude.gtar': \
> >    No such file or directory
> >  sendbackup: time 0.309: spawning /usr/local/libexec/runtar in pipeline
> >  sendbackup: argument list: gtar --create --file - --directory /u 
> >  --one-file-system \
> >    --listed-incremental /usr/local/var/amanda/gnutar-lists/butchU_1.new 
> >    --sparse \
> >    --ignore-failed-read --totals --exclude-from \
> >    /tmp/amanda/sendbackup.U.20060530030800.exclude .
> >  sendbackup: time 0.315: started index creator: 
> >  "/usr/local/libexec/amgtar -tf - \
> >    2>/dev/null | sed -e 's/^\.//'"
> >  sendbackup-gnutar: time 0.316: /usr/local/libexec/runtar: pid 21556
> >  sendbackup: time 764.914: index created successfully
> >  
> Nothing after that line? You should get two more line:
> sendbackup: time 141.583: parsed backup messages
> sendbackup: time 141.583: pid 28729 finish time Sat Jun  3 07:57:20 2006
> 
> Your sendbackup might crash. Maybe amandad is crashing first?
> 

I noted it was a "section" of the file.

I'm unable to relocate the file my sample above was from.
But in a nearly identical file (and many others) there were
two more lines.   No "parsed backup messages" lines though.

Here is a sample pair of final lines:

sendbackup: time 1626.605:  53:    size(|): Total bytes written: 4248924160 
(4.0GB, 2.5MB/s)
sendbackup: time 1626.605: pid 22946 finish time Tue May 30 04:49:40 2006

In no debug files on either 2.4.X client do "parsed backup messages"
lines appear.  Only on the 2.5.0p2 client/server.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)