It has all my totals but the task detail is mostly missing only showing a handful of tasks completed despite me running the app for years.

It is normal for the "db_purge" job to clean/purge/remove tasks, whenever the project decides to run it. They must have run it recently.

It sure would be nice if they purged all the outdated error tasks from 2014-2016.

Ah. But it also shows old failed tasks from before my host existed but associated with my active host.

Crosslink error?

There are several other threads on this. Here is a link to one of them:


http://www.gpugrid.net/forum_thread.php?id=4485


And hopefully, there is someone who can fix this.

Hopefully these standard BOINC server side utilities will work:

https://boinc.berkeley.edu/trac/wiki/DbPurge

Database purging utility

As a BOINC project operates, the size of its workunit and result tables increase. To limit this growth, BOINC provides a utility db_purge that writes result and WU records to XML-format archive files, then deletes them from the database. Workunits are purged only when their input files have been deleted. Because of BOINC's file-deletion policy, this implies that all results are completed. So when a workunit is purged, all its results are purged too.

db_purge creates an archive/ directory and stores archive files there.

db_purge is normally run as a daemon, specified in the config.xml file. It has the following command-line options:

--app appname
Purge only workunits of the given app.
-d N
Set logging verbosity to N (1,2,3,4)
--daily_dir
Write archives in a new directory (YYYY_MM_DD) each day
--dont_delete
Don't delete from DB, for testing only
--gzip
Compress archive files using gzip
--max N
Purge at most N WUs, then exit
--max_wu_per_file N
Write at most N WUs to each archive file. Recommended value: 10,000 or so.
--min_age_days X
Purge only WUs with mod_time at least X (can be < 1) days in the past. Recommended value: 7 or so. This lets users examine their recent results.
--mod N R
Process only WUs with ID mod N == R. This lets you run multiple instances for increased throughput. Must be used with --no_archive.
--no_archive
Don't archive workunits or results
--one_pass
Do one pass, then quit
--zip
Compress archive files using zip


https://boinc.berkeley.edu/trac/wiki/FileDeleter

Server-side file deletion
Files are deleted from the data server's upload and download directories by two programs:

The file_deleter daemon deletes input and output files as jobs are completed.
The antique file deleter deletes files that were missed by the file_deleter and "fell through the cracks".
The File Deleter

Typically you don't need to customize this. The default file deletion policy is:

A workunit's input files are deleted when all results are 'over' (reported or timed out) and the workunit is assimilated.
A result's output files are deleted after the workunit is assimilated. The canonical result is handled differently, since its output files may be needed to validate results that are reported after assimilation; hence its files are deleted only when all results are over, and all successful results have been validated.
If <delete_delay_hours> is specific in config.xml, the deletion of file is delayed by that interval.
Command-line options:

-d N
set debug output level (1/2/3/4)
--mod M R
handle only WUs with ID mod M == R
--one_pass
exit after one pass through DB
--dry_run
don't update DB (for debugging only)
--download_dir D
override download_dir from project config with D
--sleep_interval N
sleep for N seconds between scans (default 5)
--appid N
only process workunits with appid=N
--app S
only process workunits of app with name S
--dont_retry_errors
don't retry file deletions that failed previously
--preserve_wu_files
update the DB, but don't delete input files
--preserve_result_files
update the DB, but don't delete output files
--dont_delete_batches
don't delete anything with positive batch number
--input_files_only
don't delete output files If you store input and output files on different servers, you can improve performance by running separate file deleters, each one on the machine where the corresponding files are stored.
--output_files_only
don't delete input files
--xml_doc_like L
only process workunits where xml_doc LIKE 'L'
In some cases you may not want files to be deleted. There are three ways to accomplish this:

Use the --preserve_wu_files and/or the --preserve_result_files command-line options.
Include <no_delete/> in the <file_info> element for a file in a workunit or result template. This lets you suppress deletion on a file-by-file basis.
Include nodelete in the workunit name.

The Antique File Deleter

Runs as a periodic task. Removes 'antiques': output files that are older than the oldest WU in the database (not including "no_delete" WUs). These files are created when BOINC clients return after the corresponding WU has been deleted from the database.

The antique files are deleted by using a Unix 'find' command to locate files that are older than the oldest workunit. The find command will work on NFS mounted file systems, and will ignore .nfs stale file markers. The output of find is limited by a 'head' to 50000 files by default.

If the web-server account on your system is not 'apache', add a <httpd_user> element to your config.xml file. Otherwise antique deletion won't work.

Command-line options:

-d N
set debug output level (1/2/3/4)
--dry_run
don't delete any files, just log what would be deleted
--usleep N
sleep this number of usecs after each examined file (Throttles I/O if there are many files.)