Daryl C. W. O'Shea wrote:
Justin Mason wrote:
Daryl -- this bug seems to be back with the current command line :(
The previous non-completion bug was different... the server would think
that there were still messages outstanding. In this case it thinks
there are zero messages outstanding.
The interesting part of the log is:
Use of uninitialized value in substitution (s///) at mass-check line 881.
Use of uninitialized value in sprintf at mass-check line 889.
>> WTH!? result is not in the correct format: ror Y 9
EMPTY_MESSAGE,MISSING_DATE,MISSING_HB_SEP,MISSING_HEADERS,MISSING_MID,MISSING_SUBJECT,NO_HEADERS_MESS
AGE,NO_RECEIVED,NO_RELAYS,TVD_SPACE_RATIO,__ENV_AND_HDR_FROM_MATCH,__MISSING_REF,__MISSING_REPLY,__MISSING_THREAD,__UNUSABLE_MSGID
time=1836279597,scantime=0,
format=r,reuse=no,host=talon1.pccc.com
revision 595224 bandages this (well I think it does, not tested) so that
things work until what the cause of the malformed result lines is
determined. I don't think that it was introduced by the cs_cache or
cs_schedule_cache code.
I've opened bug 5720 for this.
Daryl
