Bug 1278796 - logshifter stops sending logs to syslog
Summary: logshifter stops sending logs to syslog
Keywords:
Status: CLOSED DUPLICATE of bug 1284900
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Luke Meyer
QA Contact: chunchen
URL:
Whiteboard:
Depends On: 1284900
Blocks: 1273542
TreeView+ depends on / blocked
 
Reported: 2015-11-06 12:52 UTC by Evgheni Dereveanchin
Modified: 2019-09-12 09:14 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-26 13:02:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2061963 0 None None None Never

Description Evgheni Dereveanchin 2015-11-06 12:52:18 UTC
Description of problem:
in certain conditions, a logshifter process configured for syslog stops sending logs. It reads the pipe yet no messages are received on syslog side. This causes major issues with gear logging as the gear needs a restart to fix this

Version-Release number of selected component (if applicable):
openshift-origin-logshifter-1.8.1.0-1.el6op

How reproducible:
sometimes with gears having high log volume

Steps to Reproduce:
no clear reproducer at the moment. The gear can run for months before this issue reoccurs.

Comment 8 Dan Mace 2015-11-10 15:21:14 UTC
To continue diagnosing this, we'll need either:

1. Steps to reproduce.
2. A stack dump from logshifter while it's observed to be in a stalled state. This can be obtained by issuing a SIGABRT to the logshifter process.

Comment 17 Josep 'Pep' Turro Mauri 2015-11-26 13:02:11 UTC
Investigation of this bug revealed that the root cause is not in logshifter. It appears to be a problem in the kernel's epoll facility. This is being tracked in a separate bug report for the kernel (bug 1284900).

The resolution of the kernel bug should address the problem reported in here for logshifter, so I'm closing this one as a duplicate.

*** This bug has been marked as a duplicate of bug 1284900 ***


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