[archive log failure]

Development
1

I see notifications as following:

----- Forwarded message from Xxxxxxx -----

2

Those archive log failure emails are a new feature in version 2.5.
The only purpose of the emails is to make it easier to notice when
such an error occurs (i.e., these emails do not indicate a new type
of error condition).
Previously, if such a failure occurred, the only way you would know
is if you noticed missing logs in one of the subdirectories of
the <PREFIX>/logs/ directory, or if you noticed the presence of
a new spool/tmp/post-terminate-* directory.

As for the strange directory names, one possible reason could be your
make-archive-name script is producing bad output.

3

HI Daniel,

As for the strange directory names, one possible reason could be your
make-archive-name script is producing bad output.

make-archive-name script does correctly archive the logs to 2016-10-03 folder.

This is the contect of the script:

$ cat make-archive-name

name=$1
flavor=$2
opened=$3
closed=$4
host=`hostname -s`

day=`echo $opened | awk -F - '{printf "%s-%s-%s", $1, $2, $3}'`
from=`echo $opened | awk -F - '{printf "%s:%s:%s", $4, $5, $6}'`
to=`echo $closed | awk -F - '{printf "%s:%s:%s", $4, $5, $6}'`

if [ "$closed" != "" ]; then
   echo $day/$name.$host.$day-$from-$to
else
   echo $day/$name.$host.$day-$from-current
fi

4

Your make-archive-name script works for me.

The next thing to check is your copy of
the <PREFIX>/share/broctl/scripts/archive-log and
the <PREFIX>/share/broctl/scripts/post-terminate script.
Check if you made any changes to those scripts (a bug in
those scripts could potentially run make-archive-name with
invalid parameters).

5

the <PREFIX>/share/broctl/scripts/archive-log and
the <PREFIX>/share/broctl/scripts/post-terminate script.

No modifications on either scripts as far as I can tell:

MD5 (share/broctl/scripts/archive-log) = 0d61804be56f8a61c18c6612bad486c8
MD5 (share/broctl/scripts/post-terminate) = ad4b56dfcfe8c1796a0a755e37256dda

Aashish

6

OK, so the next thing to check is if the archive-log and
make-archive-name scripts are receiving command-line parameters
that are in the expected format. Maybe add a line like this
to those scripts:

   echo $@ >> /tmp/something.out

I'd suggest also checking if there's anything strange in
the <PREFIX>/spool/manager/stderr.log file.