Bug 1197716 - pam_systemd: Failed to create session
Summary: pam_systemd: Failed to create session
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 21
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-02 13:27 UTC by Bill Gianopoulos
Modified: 2015-12-02 17:34 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 09:37:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Bill Gianopoulos 2015-03-02 13:27:26 UTC
Description of problem:

This is really the same issue as bug 817395, but I do not seem to have the permissions necessary to re-open a closed bug.

I changed the summary because it is NOT necessary to have  a crontab entry that sudos to see the issue.  it is only required to have some number of things that force authentication happening.  In my case, I have something running on a second server on my LAN that ssh's to this system every 5 minutes to read the UPS stats to see if it should power itself off.

I will try to get more information the next time this issue occurs.  It seems it only occurs after the first reboot after installing fedora updates.

Comment 1 ksacry 2015-04-28 03:03:04 UTC
Happening for me too on Fedora 21.
Seems to be whenever there is a kernel (or possibly some other package) update before I reboot into the new kernel.

Comment 2 Vitorio Sassi 2015-08-11 14:13:37 UTC
It's same with some RedHat boxes. I'm already update kernel and reboot :-)
Red Hat Enterprise Linux Server release 7.1
kernel 3.10.0-229.7.2.el7.x86_64
Does somebody know something about patch or update?

Comment 3 Mateusz Kwiatkowski 2015-10-09 13:49:14 UTC
Hello,
We're observing this issue with CentOS 7.1 

kernel 3.10.0-229.7.2.el7.x86_64
systemd-208-20.el7_1.5.x86_64
dbus-1.6.12-11.el7.x86_64

Comment 4 Fedora End Of Life 2015-11-04 10:13:37 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2015-12-02 09:37:17 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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