I also think this is related to the overall problem:
2016-12-28 14:14:37 f101b581 [app] [I] Processing by Katello::Api::Rhsm::
CandlepinProxiesController#upload_package_profile as JSON
2016-12-28 14:14:37 f101b581 [app] [I] Parameters: {"_json"=>"[FILTERED]",
"id"=>"432d04cc-d045-4b7f-9c92-2b4eb3dccd93"}
This appears to be what actually makes foreman/katello hang... i'm going to
ride it out and see if it works this time...
On Wednesday, December 28, 2016 at 2:19:14 PM UTC-5, [email protected] wrote:
>
> Well this seems not good... I ended up just pointing it back to the DB on
> the other server, but it looks like there are other issues...
>
> Specifically, when a repo sync runs:
>
> Dec 28 14:02:31 [redacted] pulp[5543]: pulp.server.event.http:ERROR:
> Received HTTP 500 from HTTP notifier to https:
> //[redacted]/katello/api/v2/repositories/sync_complete?token=zZh7D6xYaXaUj8FFfkvtq3ME6kvZegri.
>
>
>
>
> That url gives:
>
> {"displayMessage":"Couldn't find Katello::Repository with
> 'id'=sync_complete","errors":["Couldn't find Katello::Repository with
> 'id'=sync_complete"]}
>
> I'm not sure where to go from here... My only guess is this is an
> inconsistency with the DB somewhere, or that something didn't get
> upgraded/migrated correctly in my katello upgrade from 3.1.x to 3.2.2.
>
>
> Any help is _greatly_ appreciated as when this happens my web UI freezes...
> sometimes requiring me to restart httpd.
>
>
> I'm on IRC: NeilHanlon if you want to chat in realtime.
>
>
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
