PANIC: No such file or directory

Matthias Andree matthias.andree at gmx.de
Mon Jan 17 21:33:00 CET 2005


"Greg McCann" <greg at cambria.com> writes:

> Unfortunately I seemed to have jumped from the frying pan into the fire.
> A lot of incoming mail is getting rejected and I am now getting errors
> like the following:
>
> procmail: Executing "bogofilter,-epl,-d/home/bogofilter" Invalid log
> file: log.0000000002: No such file or directory PANIC: No such file or
> directory procmail: Error while writing to "bogofilter" procmail: Rescue
> of unfiltered data succeeded

Someone has nuked their log files. Restore the corresponding log file
and .db file (which MUST be older than the log.* file) from backup, run
bogoutil --db-recover, or rebuild from scratch.

If you don't care for minor inconsistencies, you can see if db_verify
complains about the database, if it does not, you may get away with just
rm __db.* log.* but with changes that hadn't migrated from log.* files,
you may already be in an irrecoverable state where only removing the
bogofilter directory and retraining from scratch may help.

> My users have customized .procmailrc files in their home directories, so
> procmail and bogofilter are executed as the users rather than root.  So
> the log.* and __db.* files in the bogofilter directory are owned
> (-rw-------) by the individual users, then when another user's process
> tries to open the same file, access is denied.
>
> This is rather urgent, as legitimate mail is not getting through to
> users right now.

In that case, the procmailrc script (either the global one in /etc or
the user's) is faulty.

BTW, did the system crash recently? If so, check if you have write
caches turned on, or SCSI write caches set to copyback without a proper
battery backup for the cache.

-- 
Matthias Andree



More information about the Bogofilter mailing list