Bug 1018605 - Resources::Candlepin::OwnerInfo: 500 Internal Server Error
Summary: Resources::Candlepin::OwnerInfo: 500 Internal Server Error
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: Nightly
Hardware: x86_64
OS: Linux
unspecified
high vote
Target Milestone: Unspecified
Assignee: candlepin-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-13 18:34 UTC by jmagen@redhat.com
Modified: 2014-01-27 13:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-14 21:51:50 UTC
Target Upstream Version:
mmccune: needinfo+

Attachments (Terms of Use)
katello-debug .tar.gz output (598.32 KB, application/x-gzip)
2013-10-13 18:34 UTC, jmagen@redhat.com 		no flags Details
Comment (93.40 KB, text/plain)
2013-10-13 18:34 UTC, jmagen@redhat.com 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description jmagen@redhat.com 2013-10-13 18:34:42 UTC 
Created attachment 915780 [details]
Comment

(This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).
Comment 1 RHEL Program Management 2013-10-13 18:44:30 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Jesus M. Rodriguez 2013-10-14 13:46:00 UTC 
Verify the database is accessible, the exception shows a bunch of I/O errors which indicates a problem with connecting to the database.
Comment 4 Mike McCune 2013-10-14 18:21:17 UTC 
agree with what Jesus said:

* Check that postgres is running

* run 'katello-service status' and paste that output here

* ensure you have disk space
Comment 5 jmagen@redhat.com 2013-10-14 20:26:20 UTC 
Yesterday, I ran katello-service status and all was running.

I can't re-produce the problem.  I turned off the production sat6 install and setup a develop environment and all is ok.

You can close the bug.
Note You need to log in before you can comment on or make changes to this bug.