Bug 1321610 - Systemd-logind crashes for 389-ds-base stress tests
Summary: Systemd-logind crashes for 389-ds-base stress tests
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.2
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-28 15:27 UTC by Sankar Ramalingam
Modified: 2020-12-15 07:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:40:39 UTC
Target Upstream Version:


Attachments (Terms of Use)
Systemd logind crash email report (17.61 KB, text/plain)
2016-03-28 15:27 UTC, Sankar Ramalingam
no flags Details

Description Sankar Ramalingam 2016-03-28 15:27:32 UTC
Created attachment 1140906 [details]
Systemd logind crash email report

Description of problem: Systemd crashes with directory server stress tests.

Please refer - https://bugzilla.redhat.com/show_bug.cgi?id=1321606

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info: Attaching the crash email report.

Comment 2 Sankar Ramalingam 2016-04-13 12:21:00 UTC
Additional info:

We have test cases like the following...
test case #1: Set the system date to ahead of 1 year and then reset the date back to original after about 30 secs.
        Orig_Date="1`date +"%m%d%H%M%Y"`"
        New_Date=`expr $Orig_Date + 1`
        New_Date=`echo $New_Date | cut -c2-13`
        sudo date "$New_Date"

test case #2: Set the system date to 120 secs late. and then reset the date back to original after about 10 secs.

sudo date -s "-2 minutes"

The system started hanging at this point.

Comment 5 RHEL Program Management 2020-12-15 07:40:39 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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