Christopher Browne wrote:
I'm getting cases where old files that *ought* to be purgeable are
failing to be tidied out by the tidy: section.

For each such file, I'm getting error messages thus:

Can't stat backup1.2006-05-15.gpg 
(/opt/escrow/info/backups/backup1.2006-05-15.gpg)
Can't stat backup1.2006-05-24.gpg 
(/opt/escrow/info/backups/backup1.2006-05-24.gpg)
Can't stat backup1.2006-05-20.gpg 
(/opt/escrow/info/backups/backup1.2006-05-20.gpg)
Can't stat backup1.2006-05-23.gpg 
(/opt/escrow/info/backups/backup1.2006-05-23.gpg)
Can't stat backup2.2006-05-23.bz2 
(/opt/escrow/org/backups/backup2.2006-05-23.bz2)
Can't stat backup2.2006-05-21.bz2 
(/opt/escrow/org/backups/backup2.2006-05-21.bz2)
Can't stat backup2.2006-05-20.bz2 
(/opt/escrow/org/backups/backup2.2006-05-20.bz2)
Can't stat backup2.2006-05-24.bz2 
(/opt/escrow/org/backups/backup2.2006-05-24.bz2)
Can't stat tld2dump.2006-05-24.gpg (/opt/escrow/site1/tld2dump.2006-05-24.gpg)
Can't stat pgdump.2006-05-23.gpg (/opt/escrow/site1/pgdump.2006-05-23.gpg)
Can't stat tld2dump.2006-05-16.gpg (/opt/escrow/site1/tld2dump.2006-05-16.gpg)
Can't stat tld2dump.2006-05-21.gpg (/opt/escrow/site1/tld2dump.2006-05-21.gpg)
Can't stat tld2dump.2006-05-23.gpg (/opt/escrow/site1/tld2dump.2006-05-23.gpg)
Can't stat pgdump.2006-05-24.gpg (/opt/escrow/site1/pgdump.2006-05-24.gpg)
Can't stat pgdump.2006-05-20.gpg (/opt/escrow/site1/pgdump.2006-05-20.gpg)

The files are there; they have perfectly appropriate permissions; tidy
is clearing out other files that seem to have the same attributes.

The relevant rules are thus:

   postgres.tor_520_dap901::
        /opt/escrow
                recurse=4
                pattern=*.bz2
                age=6

        /opt/escrow
                recurse=4
                pattern=*.gpg
                age=4

        /opt/escrow
                recurse=4
                pattern=*.sig
                age=20

I don't see a good reason to be unable to stat the files...

Run cfagent using truss or strace to see what error is being generated by stat. A likely reason is that the files are > 2Gb and cfagent is not using a stat that support large files. In that case you get E_OVERFLOW or similar.

Regards,
Frank Ranner
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
http://cfengine.org/mailman/listinfo/help-cfengine

Reply via email to