Debian Bug report logs - #825949
pam_systemd(su:session): Cannot create session: Already running in a session

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@unex.es>

To: Debian BTS <submit@bugs.debian.org>

Subject: pam_systemd(su:session): Cannot create session: Already running in a session

Date: Tue, 31 May 2016 18:53:43 +0200 (CEST)

Package: libpam-systemd,login

Dear maintainers:

Since I upgraded to stretch, logcheck sends me messages like this each
time I do "su -" to become root:

Security Events for su
=-=-=-=-=-=-=-=-=-=-=-
[...] mymachine su[4887]: pam_systemd(su:session): Cannot create session: Already running in a session


Apparently, "su" is doing something which is not necessary, or in a way
which is not optimal for systemd, or maybe pam_systemd is too picky
about what "su" does.

I don't know which of the two packages is to blame for this, so
I'm filing this report against both, libpam-systemd and login,
in the hope that you both can reach to an agreement about that.

If it happens that everything is ok and working as expected, then
it would be nice to have anyway some rule in /etc/logcheck to avoid
the message being considered as a "security event".

Thanks.

Message #10 received at 825949@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Santiago Vila <sanvila@unex.es>, 825949@bugs.debian.org

Subject: Re: Bug#825949: pam_systemd(su:session): Cannot create session: Already running in a session

Date: Tue, 31 May 2016 19:20:28 +0200

[Message part 1 (text/plain, inline)]

Am 31.05.2016 um 18:53 schrieb Santiago Vila:
> Package: libpam-systemd,login
> 
> Dear maintainers:
> 
> Since I upgraded to stretch, logcheck sends me messages like this each
> time I do "su -" to become root:
> 
> Security Events for su
> =-=-=-=-=-=-=-=-=-=-=-
> [...] mymachine su[4887]: pam_systemd(su:session): Cannot create session: Already running in a session
> 
> 
> Apparently, "su" is doing something which is not necessary, or in a way
> which is not optimal for systemd, or maybe pam_systemd is too picky
> about what "su" does.
> 
> I don't know which of the two packages is to blame for this, so
> I'm filing this report against both, libpam-systemd and login,
> in the hope that you both can reach to an agreement about that.
> 

Which version of login and libpam-systemd?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #15 received at 825949@bugs.debian.org (full text, mbox, reply):

From: Santiago Vila <sanvila@unex.es>

To: Michael Biebl <biebl@debian.org>

Cc: 825949@bugs.debian.org

Subject: Re: Bug#825949: pam_systemd(su:session): Cannot create session: Already running in a session

Date: Tue, 31 May 2016 19:40:00 +0200

On Tue, May 31, 2016 at 07:20:28PM +0200, Michael Biebl wrote:

> Which version of login and libpam-systemd?

Current ones in stretch as of today:

login 1:4.2-3.1
libpam-systemd 230-1

Message #20 received at 825949@bugs.debian.org (full text, mbox, reply):

From: Christian Kastner <ckk@debian.org>

To: 825949@bugs.debian.org

Subject: Re: pam_systemd(su:session): Cannot create session: Already running in a session

Date: Sat, 4 Jun 2016 11:20:20 +0200

[Message part 1 (text/plain, inline)]

On Tue, 31 May 2016 18:53:43 +0200 (CEST) Santiago Vila
<sanvila@unex.es> wrote:
> Since I upgraded to stretch, logcheck sends me messages like this each
> time I do "su -" to become root:
> 
> Security Events for su
> =-=-=-=-=-=-=-=-=-=-=-
> [...] mymachine su[4887]: pam_systemd(su:session): Cannot create session: Already running in a session

logcheck was reporting the same for me, except s/su/schroot/.

> Apparently, "su" is doing something which is not necessary, or in a way
> which is not optimal for systemd, or maybe pam_systemd is too picky
> about what "su" does.
> 
> I don't know which of the two packages is to blame for this, so
> I'm filing this report against both, libpam-systemd and login,
> in the hope that you both can reach to an agreement about that.

I can successfully trace this back to systemd 223-1 (with 222-2,
everything is still fine).

> If it happens that everything is ok and working as expected, then
> it would be nice to have anyway some rule in /etc/logcheck to avoid
> the message being considered as a "security event".

Regards,
Christian

[signature.asc (application/pgp-signature, attachment)]

Message #25 received at 825949@bugs.debian.org (full text, mbox, reply):

From: Laurent Bonnaud <L.Bonnaud@laposte.net>

To: 825949@bugs.debian.org

Subject: Re: pam_systemd(su:session): Cannot create session: Already running in a session

Date: Tue, 28 Feb 2017 15:20:41 +0100

Hi,

the problem is still there in this package version:

Package: libpam-systemd
Version: 232-18

Here is what happens when I su from root to a normal user:

févr. 28 15:01:36 irancy su[7313]: Successful su for bonnaudl by root
févr. 28 15:01:36 irancy su[7313]: + /dev/pts/0 root:bonnaudl
févr. 28 15:01:36 irancy su[7313]: pam_unix(su:session): session opened for user bonnaudl by root(uid=0)
févr. 28 15:01:36 irancy su[7313]: pam_systemd(su:session): Cannot create session: Already running in a session
févr. 28 15:01:39 irancy su[7313]: pam_unix(su:session): session closed for user bonnaudl

If I pile up 2 su (normal user -> root -> normal user), then I get no error message and the creation of a new session:

févr. 28 15:17:23 irancy su[9191]: Successful su for bonnaudl by root
févr. 28 15:17:23 irancy su[9191]: + /dev/pts/2 root:bonnaudl
févr. 28 15:17:23 irancy su[9191]: pam_unix(su:session): session opened for user bonnaudl by bonnaudl(uid=0)
févr. 28 15:17:23 irancy systemd-logind[2859]: Existing logind session ID 50 used by new audit session, ignoring
févr. 28 15:17:23 irancy systemd[1]: Started Session c2 of user bonnaudl.
févr. 28 15:17:23 irancy systemd-logind[2859]: New session c2 of user bonnaudl.
févr. 28 15:17:24 irancy su[9191]: pam_unix(su:session): session closed for user bonnaudl
févr. 28 15:17:24 irancy systemd-logind[2859]: Removed session c2.

-- 
Laurent.

Message #30 received at 825949@bugs.debian.org (full text, mbox, reply):

From: IOhannes m zmoelnig <umlaeute@debian.org>

To: Debian Bug Tracking System <825949@bugs.debian.org>

Subject: Re: pam_systemd(su:session): Cannot create session: Already running in a session

Date: Wed, 19 Jul 2017 11:23:34 +0200

Package: libpam-systemd
Version: 232-25
Followup-For: Bug #825949

Dear Maintainer,

this is just to confirm that the behaviour is still there, now that stretch has
been released.


-- System Information:
Debian Release: 9.0
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libpam-systemd depends on:
ii  dbus            1.10.18-1
ii  libc6           2.24-11+deb9u1
ii  libpam-runtime  1.1.8-3.6
ii  libpam0g        1.1.8-3.6
ii  libselinux1     2.6-3+b1
ii  systemd         232-25
ii  systemd-sysv    232-25

libpam-systemd recommends no packages.

libpam-systemd suggests no packages.

-- debconf-show failed

Message #35 received at 825949@bugs.debian.org (full text, mbox, reply):

From: Thomas D <sdktda@gmail.com>

To: 825949@bugs.debian.org

Subject: pam_systemd(su:session): Cannot create session: Already running in a session

Date: Tue, 19 Sep 2017 09:36:28 +0200

[Message part 1 (text/plain, inline)]

Dear maintainers,

I can confirm this bug is present in an up-to-date Stretch as of today.
Are there any plans on this being fixed in Stretch?

BR
Thomas

[Message part 2 (text/html, inline)]

Message #40 received at 825949@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Thomas D <sdktda@gmail.com>, 825949@bugs.debian.org

Subject: Re: Bug#825949: pam_systemd(su:session): Cannot create session: Already running in a session

Date: Tue, 19 Sep 2017 20:21:56 +0200

[Message part 1 (text/plain, inline)]

Am 19.09.2017 um 09:36 schrieb Thomas D:
> Dear maintainers,
> 
> I can confirm this bug is present in an up-to-date Stretch as of today.
> Are there any plans on this being fixed in Stretch?

Not that I'm aware of. Do you want to work on it?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #45 received at 825949@bugs.debian.org (full text, mbox, reply):

From: Thomas D <sdktda@gmail.com>

To: Michael Biebl <biebl@debian.org>

Cc: 825949@bugs.debian.org

Subject: Re: Bug#825949: pam_systemd(su:session): Cannot create session: Already running in a session

Date: Wed, 20 Sep 2017 09:03:56 +0200

[Message part 1 (text/plain, inline)]

2017-09-19 20:21 GMT+02:00 Michael Biebl <biebl@debian.org>:

> Am 19.09.2017 um 09:36 schrieb Thomas D:
> > Dear maintainers,
> >
> > I can confirm this bug is present in an up-to-date Stretch as of today.
> > Are there any plans on this being fixed in Stretch?
>
> Not that I'm aware of. Do you want to work on it?
>
>
>


I am not sure I have the skills needed to fix this.

I mean, Christian Kastner mentions that it works in systemd 222-2:
> I can successfully trace this back to systemd 223-1 (with 222-2,
> everything is still fine).


So I can do a diff between 222-2 and current systemd. However, if the
change is non-trivial I would probably not be able to fix it.


BR
Thomas

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.