Hi Jeroen,
The best place to see why an agent failed is in the fossology log file 
(/var/log/fossology/fossology.log).
If you look there and see a "spawning too fast" error, that is a known (major) 
bug.  See:

http://bugs.linux-foundation.org/show_bug.cgi?id=636

If it is something different than what is in the bug report, please let us know.

Thanks,
Bob Gobeille


On Feb 10, 2011, at 5:49 AM, Jeroen Baten wrote:

> 
> This is the info I found. Maybe it helps you people.
> 
> 
> Kind regards, Jeroen Baten
> 
> jq_pk 128
> jq_job_fk     108
> job_name      Package Scan
> jq_type       pkgagent
> job_priority  0
> jq_args       SELECT pfile_pk as pfile_pk, pfile_sha1 || '.' || pfile_md5 ||
> '.' || pfile_size AS pfilename, mimetype_name AS mimetype FROM
> uploadtree INNER JOIN pfile ON upload_fk = '7' INNER JOIN mimetype ON
> (mimetype_pk = '1' OR mimetype_pk = '2' OR mimetype_pk = '3') AND
> uploadtree.pfile_fk = pfile_pk AND pfile.pfile_mimetypefk =
> mimetype.mimetype_pk AND pfile_pk NOT IN (SELECT pkg_rpm.pfile_fk FROM
> pkg_rpm) AND pfile_pk NOT IN (SELECT pkg_deb.pfile_fk FROM pkg_deb)
> LIMIT 5000;
> jq_runonpfile pfile_pk
> jq_starttime  2011-02-10 13:45:42.098366+01
> jq_endtime    2011-02-10 13:45:52.166725+01
> jq_end_bits   2
> jq_endtext    Failed: Failed: Agent terminated prematurely
> jq_elapsedtime        00:02:44
> jq_processedtime      00:00:01
> jq_itemsprocessed     29
> job_submitter 
> job_queued    2011-02-10 13:40:11.799265+01
> job_email_notify      fossy
> job_upload_fk 7
> depends on    40
> required by   127, 129
> _______________________________________________
> fossology mailing list
> fossology@fossology.org
> http://fossology.org/mailman/listinfo/fossology

_______________________________________________
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology

Reply via email to