From owner-freebsd-ports-bugs@freebsd.org Tue Jul 12 13:59:14 2016 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B610B92144 for ; Tue, 12 Jul 2016 13:59:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0C6B11EBF for ; Tue, 12 Jul 2016 13:59:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u6CDxDLb097496 for ; Tue, 12 Jul 2016 13:59:13 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 211033] sysutils/rsyslog8: CPU hangs at 100% with I/O error on stdout/stderr Date: Tue, 12 Jul 2016 13:59:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: xavi.garcia@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: brd@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2016 13:59:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211033 Bug ID: 211033 Summary: sysutils/rsyslog8: CPU hangs at 100% with I/O error on stdout/stderr Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: brd@FreeBSD.org Reporter: xavi.garcia@gmail.com Flags: maintainer-feedback?(brd@FreeBSD.org) Assignee: brd@FreeBSD.org rsyslogd hangs in an infinite loop trying to write a syslog record to a file descriptor.=20 truss -p pid outputs write(1,"2016-07-06T10:01:23.061615+00:00"...,116) ERR#5 'Input/output erro= r' write(1,"2016-07-06T10:01:23.061615+00:00"...,116) ERR#5 'Input/output erro= r' write(1,"2016-07-06T10:01:23.061615+00:00"...,116) ERR#5 'Input/output erro= r' write(1,"2016-07-06T10:01:23.061615+00:00"...,116) ERR#5 'Input/output erro= r' write(1,"2016-07-06T10:01:23.061615+00:00"...,116) ERR#5 'Input/output erro= r' write(1,"2016-07-06T10:01:23.061615+00:00"...,116) ERR#5 'Input/output erro= r' It is not displayed here but the message written is exactly the same every = time (truss -s 1024 -p pid) We assumed it was the same bug that was closed upstream on https://github.com/rsyslog/rsyslog/issues/318 but we cannot reproduce it wi= th the proof of concept. Furthermore, building the binary with debug mode (WITH_DEBUG=3Dyes) stopped the bug from being triggered and we cannot get a coredump to investigate. We then forced the debug build with optimisations on (-O2) and we still can= not reproduce the error. We have seen this happening in fd 1 and fd 2. The command `fstat -p pid` returned root rsyslogd 1073 2 - - bad that means bad file descriptor in stat(2) and errno.h (EBADF). --=20 You are receiving this mail because: You are the assignee for the bug.=