Still see situations whereby the server cronjob fails to complete a job for different reasons, but registers the job as processed.
Here an example of a db change issue,
14.12.2008-17:09 - DEBUG - Call function 'db_update' in plugin 'mysql_clientdb_plugin' raised by event 'database_update'. 14.12.2008-17:09 - ERROR - Unable to connect to the database 14.12.2008-17:09 - DEBUG - Processed datalog_id 117
job gets removed from job queue even as it failed.
I have also seen examples
- when an unix command is called, which cannot be found resulting in the job being marked as processed.
- when an unix command responds with an error resulting in the job being marked as processed.
The debug output seems to be less verbose in the later svn versions. For instance the database error above does not tell anything about which database is being called, was it a authentication issue or was it a connection refused issue.