On Wed, Dec 16, 2020 at 15:37:32 -0500, Gene Heskett wrote:
> On Wednesday 16 December 2020 12:23:28 Nathan Stratton Treadway wrote:
> 
> > On Wed, Dec 16, 2020 at 09:42:47 -0500, Gene Heskett wrote:
> > > You reminded me of that, so its now done. We'll see if that fixes
> > > it.
> >
> > (Note that putting in the quote characters should prevent the shell
> > from aborting due to the syntax error, but it won't fix the underlying
> > problem that the contents of the PARTS_WRITTEN variable appear to be
> > bogus at that point in time.  Though if you want to debug that issue
> > further, it's probably best if you reply to that branch of this thread
> > directly :) )
> >
> I'll see if, in my somewhat decreased mental state, I can figure out how 
> to echo that into the log file. Jon L. seems to think a bit of perl that 

Well, there was a tantalizing hint already included in the output you
posted to the list, so you may not need to actually chage the script for
that part.

Perhaps you shoud just go ahead and post the script; that would at least
let us see what what script processing matches up with the output you
posted earlier.


> amanda uses has been updated in the last year or so and has broken 
> amanda somehow. 

Off hand, I am thinking there is a bug in the amstatus Perl code which
gets triggered when you have a two-tape run, and then also a fix needed
in your shell script so that PARTS_WRITTEN is always set correctly and
the script can properly deal with a two-tape run.

(Because you only see the error for the double-tape runs, I'm less
inclinded to suspect a Perl upgrade is the issue [rather than a more
general bug in amstatus, as it parsess the Amanda log file], but we may
need to wait until the next time it happens before we can track it
down.)

                                                        Nathan

----------------------------------------------------------------------------
Nathan Stratton Treadway  -  natha...@ontko.com  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

Reply via email to