I doubt that this is related to the last round of pmlogger_daily
changes.
The message more than likely means the label record has not yet been
written because the first dummy pmlogger record (pmcd.pmlogger.host,
pmcd.pmlogger.port and pmcd.pmlogger.archive) has not yet been written.
There is a very small window between the fopen() and the fwrite() in
pmlogger. The existence of the archive files is checked in the guard and
retry loop of pmnewlog (which is where mkaf is likely being called from
in this scenario) so you'd have to be hitting that pmlogger window.
I am guessing this is a logger farm, with lots of pmlogger's being
turned over at the same time.
Any way the Latest archive folio being messed up is not going to have
any long-term bad effects ... just as long as the archives look ok in
the morning.
Fixing this in pmnewlog is not too difficult, but testing the fix is
going to be tricky, as you (Nathan) are the only one with an apparent
non-deterministic test environment ... 8^)>
On Mon, 2009-03-30 at 11:06 +1100, Nathan Scott wrote:
> Hi Ken,
> I'm seeing an occassional pmlogger_daily warning (I think since upgrading the
> pmlogger_daily scripts to the new-weekly-cull/merge-style variant) - not sure
> if its failing to create logs or not ... hard to tell exactly which host its
> coming from (message leaves a bit to be desired, cos mkaf doesn't have the
> full archive path).
>
> Does this look fatal to you?
>
> thanks.
>
> ----- Forwarded Message -----
> ...[mail header snipped]...
>
> mkaf: Warning: cannot extract hostname from archive "20090330.00.10" ...
> skipped
> mkaf: Warning: cannot extract hostname from archive "20090330.00.10" ...
> skipped
>
> ----- End Forwarded Message -----
>
|