We had a case where there was a bug in candlepin that caused an exception to not get logged during import. The import was posted to: POST /candlepin/owners/ACME_Corporation/imports we saw this in catalina.out: Dec 20 05:53:54 [http-8443-1] INFO org.candlepin.resource.OwnerResource - Importing archive: /var/cache/tomcat6/temp/pfx6519919396246909676sfx Dec 20 05:53:54 [http-8443-1] INFO org.candlepin.sync.Importer - Extracting archive to: /var/cache/candlepin/sync/import56390156708272648791468243188780346 Dec 20 05:53:54 [http-8443-1] INFO org.candlepin.sync.Importer - Extracting archive to: /var/cache/candlepin/sync/import56390156708272648791468243188780346 but the server was returing a 500 error and all we had in the access log was: 0:0:0:0:0:0:0:1 - - [20/Dec/2011:05:53:55 -0500] "POST /candlepin/owners/ACME_Corporation/imports HTTP/1.1" 500 53 turns out the java code was not properly logging the exception: <beav> catch (CertificateException e) { <beav> throw new ImportExtractionException("unable to extract export archive", e); <beav> } <beav> catch (IOException e) { <beav> throw new ImportExtractionException("unable to extract export archive", e); <beav> two errors, same message:) <beav> Unrecognized field "flexExpiryDays" <beav> that is a bug if it's not being bubbled up <beav> but there's your problem:) <beav> i think bk fixed that today, looking <beav> use 0.5.8 it appears that the code was logging the import error in the DB but not putting it in the log anywhere.
Fixed in d21a2fffbe767c8a3ec5dabbdffe92d3278a708c. You will need 0.5.8 of candlepin to ge tthe fix. That version is in the repos.
mass ON_QA move
Since we're doing a better job at reporting import errors, closing it as verified.