Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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.