Bug 1315266

Summary: Capsule stops listening on 9090 after log rotate
Product: Red Hat Satellite Reporter: Brad Buckingham <bbuckingham>
Component: Foreman ProxyAssignee: Dmitri Dolguikh <ddolguik>
Status: CLOSED ERRATA QA Contact: Chris Duryee <cduryee>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.1.3CC: abalakht, bbuckingham, bkearney, cduryee, cwelton, dmitri, ehelms, katello-qa-list, ohadlevy, peter.vreman, sauchter, sreber, suprabhu, xdmoon
Target Milestone: UnspecifiedKeywords: PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/12295
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1273785 Environment:
Last Closed: 2016-07-27 09:25:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1273785    
Bug Blocks: 1122832    

Comment 2 Bryan Kearney 2016-03-09 15:11:58 UTC 
Upstream bug assigned to ddolguik
Comment 3 Bryan Kearney 2016-03-09 15:12:02 UTC 
Upstream bug assigned to ddolguik
Comment 4 Bryan Kearney 2016-03-17 14:12:08 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/12295 has been closed
-------------
Anonymous
Applied in changeset commit:7cc71a107f37f1c7dfc12f2791906565e796bed6.
Comment 5 Chris Duryee 2016-03-24 19:02:57 UTC 
how I verified:

* confirmed foreman-proxy was running, and that ruby was listening on port 9090 with netstat
* ran logrotate -f /etc/logrotate.conf
* confirmed foreman-proxy was still running, that ruby was listening on 9090, and the pid was different
Comment 8 errata-xmlrpc 2016-07-27 09:25:52 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1501