> At 10:59 AM -0800 3/1/02, Dan Schaper wrote: > > >I'm seeing this error in my popper logs, is this a configuration error, or > >just a transient self healing error? > > The error means that Qpopper didn't trust the cache file, because it > was modified after the spool. Qpopper will create a new cache, but > the cost is that the cache couldn't be used for that session, forcing > Qpopper to read through the spool. Is there another process touching > the cache files?
Not necessarily. We are also seeing those 'spool older than cache file' messages. It invariably happens after a new message arrived for a given user AND a subsequent succesful POP session, with 'leave messages on server' set. Example : (anonymized) 10:41:34 popper[9816]: Stats: user 0 0 260 23935643 host ip 10:43:36 popper[12048]: Stats: user 0 0 260 23935643 host ip 10:45:42 popper[14462]: Stats: user 0 0 261 23954722 host ip 10:47:54 popper[16942]: spool older than cache file /var/mail/u/s/.user.cache 10:47:59 popper[16942]: Stats: user 0 0 261 23954734 host ip It is my guess that the session at 10:45:42 did not succeed at updating the .cache file although no error message to this effect was logged. The actual check in popper/pop_cache.c seems robust (and simple) enough. Eric.
