Hey,
OK looking at this bug, if I understood the issue properly, I think I
found what the problem is.
With libpam-systemd installed, UsePAM set to yes, the ssh process with
lower privileges is assign to the user session, when shutting down,
systemd is going through all the user sessions and kill
On Mon, 2015-08-17 at 12:23 +0200, Laurent Bigonville wrote:
The correct solution is IMVHO is to use libpam-systemd with UsePAM
set
to yes. On other solution is to change the KillMode, but doing so,
you'll probably loose the connection if the ssh service is restarted.
Both doesn't seem to be
On Mon, 17 Aug 2015 16:51:42 +0200 Christoph Anton Mitterer
cales...@scientia.net wrote:
On Mon, 2015-08-17 at 12:23 +0200, Laurent Bigonville wrote:
The correct solution is IMVHO is to use libpam-systemd with UsePAM
set
to yes. On other solution is to change the KillMode, but doing so,
I've been struggling with an appropriate fix for this bug.
I've also found that installing libpam-systemd seems to fix this for me in
my testing. (If I discover it still to be a problem, I'll post again).
However, I'd like to understand why libpam-systemd makes a difference if
anyone has any
On Tue, 2015-05-12 at 10:20 +1000, Matt Black wrote:
I've also found that installing libpam-systemd seems to fix this for
me in my testing. (If I discover it still to be a problem, I'll post
again). However, I'd like to understand why libpam-systemd makes a
difference if anyone has any
On Tue, 2015-05-12 at 10:49 +1000, Matt Black wrote:
Interesting. The important thing here then is my question - WHY does
libpam-systemd make a difference in some cases?
I think Russ mentioned it before already,... it may be simply some
timing issues i.e. libpam-systemd's presence slowing the
I've also found that installing libpam-systemd seems to fix this for
me in my testing. (If I discover it still to be a problem, I'll post
again). However, I'd like to understand why libpam-systemd makes a
difference if anyone has any insight?
It doesn't, I still have the problem occasionally
Christoph Anton Mitterer cales...@scientia.net writes:
On Tue, 2015-05-12 at 10:49 +1000, Matt Black wrote:
Interesting. The important thing here then is my question - WHY does
libpam-systemd make a difference in some cases?
I think Russ mentioned it before already,... it may be simply some
On Wed, 29 Apr 2015 02:57:28 -0400 Matthew Dawson
matt...@mjdsystems.ca wrote:
On Sun, 15 Jun 2014 01:20:41 +0200 Christoph Anton Mitterer
Since openssh-server comes with systemd support, whenever a host
is shut down or restarted, ssh connections to that host just
hang and are no longer
On Sat, 2015-05-02 at 18:55 -0700, Steven Monai wrote:
I was having this same problem on a new, minimal Jessie installation.
Installing libpam-systemd (and rebooting) fixed it.
I somewhat doubt that this is really a fix.
When I reported the problem in the beginning, I've always had
On Sun, 15 Jun 2014 01:20:41 +0200 Christoph Anton Mitterer
Hi.
Since openssh-server comes with systemd support, whenever a host
is shut down or restarted, ssh connections to that host just hang
and are no longer cleanly terminated (one also doesn't see the
shutdown message anymore).
I'd
Re: Christoph Anton Mitterer 2014-06-15
20140614232041.29765.83096.report...@heisenberg.scientia.net
Since openssh-server comes with systemd support, whenever a host
is shut down or restarted, ssh connections to that host just hang
and are no longer cleanly terminated (one also doesn't see the
Hi,
On Sat, Dec 13, 2014 at 07:04:30PM +0100, Christoph Anton Mitterer wrote:
On Sat, 2014-12-13 at 15:01 +0100, Marc Haber wrote:
I would like to have a method to
kill all ssh sessions with the exception of my own ones, or the single
session that I happen to type the command restarting
On Sat, Dec 13, 2014 at 07:14:53PM +0100, Christoph Anton Mitterer wrote:
On Sat, 2014-12-13 at 15:06 +0100, Marc Haber wrote:
/lib/systemd/system/ssh.service in current sid has
After=network.target in its Unit stanza and still not cleanly kills
off ssh sessions.
Since the ssh.service
On Sun, 2014-12-14 at 16:19 +0100, Marc Haber wrote:
It might be expected by somebody very familiar with how new init
works. It is surprising to people who aren't and undresired by some of
them.
Again, this is why we have this bug. And when I talked about absolutely
expected behaviour I meant
Answering two of your mails in one, since all of this got really off
topic.
On Sun, 2014-12-14 at 15:46 +0100, Marc Haber wrote:
Yes, but GNU/Linux is not a grüne wiese approach, it is migrating
millions of existing systems.
Sure, but this doesn't mean that one cannot pick out single points,
On Fri, Oct 10, 2014 at 11:52:24AM +0200, Tom Hutter wrote:
The solution provided under
https://bugzilla.redhat.com/show_bug.cgi?id=626477 suggests to killall ssh
sessions, when stopping sshd. I prefer to have at least one ssh session
open to my server when restarting ssh, if something goes
On Fri, Oct 10, 2014 at 05:44:14PM +0200, Christoph Anton Mitterer wrote:
a) if sshd crashes or when it is restarted/reloaded (or when the network
is restarted), we do not want ssh sessions to terminate, right?
At least that's what we always had. I would like to have a method to
kill all ssh
On Fri, Oct 10, 2014 at 06:51:20PM +0200, Tom Hutter wrote:
If ssh is restarted, my hack does exactly the expected. The ssh user
sessions stay alive. Only, if the network is shut down, the sessions will be
terminated. Looking at this excerpt from systemd.special(7), I would say,
my hack
On Sat, Oct 11, 2014 at 06:33:39PM -0700, Russ Allbery wrote:
Christoph Anton Mitterer cales...@scientia.net writes:
But I mean before thinking about how to handle it technically,... it
should probably decided what do we actually want. Like even if ssh
itself (the binary) behaves different
On Sat, Oct 11, 2014 at 08:12:56PM -0700, Russ Allbery wrote:
I have no problems with the current behavior under systemd, so I'm not the
one to ask for a solution. It makes no difference at all to me whether I
get a clean connection shutdown from a host when it's being rebooted.
It makes a
On Sun, Oct 12, 2014 at 04:12:07AM +0200, Christoph Anton Mitterer wrote:
On Sat, 2014-10-11 at 18:33 -0700, Russ Allbery wrote:
Yes, a lot of people being *quite* upset when they stop ssh to restart it
with debugging or to temporarily bring it down while working on something,
discover
On Fri, Oct 10, 2014 at 10:51:04AM -0500, David Lechner wrote:
I have found that using ssh.socket instead of ssh.service makes
clients shut down cleanly most of the time (sometimes they will
still hang, but it is rare).
systemctl disable ssh.service
systemctl enable ssh.socket
Do I
On Sat, 2014-12-13 at 15:01 +0100, Marc Haber wrote:
I would like to have a method to
kill all ssh sessions with the exception of my own ones, or the single
session that I happen to type the command restarting sshd in.
Since there is no definition of which are yours (the ones logged in to
your
On Sat, 2014-12-13 at 15:06 +0100, Marc Haber wrote:
/lib/systemd/system/ssh.service in current sid has
After=network.target in its Unit stanza and still not cleanly kills
off ssh sessions.
Since the ssh.service unit file only starts the listener daemons and not
the sessions neither explicitly
On Friday 10 October 2014 22:50:31 Christoph Anton Mitterer wrote:
Sure,... I never claimed it wouldn't work... just that I'm not sure
whether I like the idea of having a separate unit file for the ssh
sessions.
I mean you have a similar concepts in many other daemons (like httpd or
some
On Sat, 2014-10-11 at 11:23 +0200, Tom Hutter wrote:
Exactly. Stop apache, nginx, mysql, postgres and tell me, how many
children processes will be left, once you stopped it.
As ssh behaves differently and keeps the children alive, you have to
handle it differently :-)
Sure...
But I mean
Christoph Anton Mitterer cales...@scientia.net writes:
But I mean before thinking about how to handle it technically,... it
should probably decided what do we actually want. Like even if ssh
itself (the binary) behaves different from apache/etc. - do we want to
keep that in the unit-files
On Sat, 2014-10-11 at 18:33 -0700, Russ Allbery wrote:
Yes, a lot of people being *quite* upset when they stop ssh to restart it
with debugging or to temporarily bring it down while working on something,
discover that their session was terminated in a way that's never happened
with ssh in the
Christoph Anton Mitterer cales...@scientia.net writes:
Well never too late to change something *if* it was the cleaner way to
handle it. =)
But having stopping sshd kill open sessions is not cleaner. It would be a
pretty serious regression.
Anyway,... what would you propose then to bring
Hi,
I had the same issue under Debian Wheezy with systemd 204-14~bpo70+1
As systemd is in constant development and Jessie is currently running
version 215-5+b1 it maybe resolved in more recent versions than 204-14.
The solution provided under
https://bugzilla.redhat.com/show_bug.cgi?id=626477
Hi,
I also created a workaround for my minimal environment, just yesterday.
It involves patching /etc/acpi/powerbtn-acpi-support.sh
(I use acpid/acpi-support-base for power events)
and adding aliases for 'shutdown' and 'reboot':
On Fri, 2014-10-10 at 11:52 +0200, Tom Hutter wrote:
Therefore I added a service, to solve this under the current Debian
Wheezy version I am running.
Hmm I'm a bit torn apart between thinking that this is either an ugly
hack or a clean solution ^^
ExecStart=/bin/true
At least this seems a hack
On Fri, 2014-10-10 at 12:54 +0200, I. Schrey wrote:
I also created a workaround for my minimal environment, just yesterday.
It involves patching /etc/acpi/powerbtn-acpi-support.sh
(I use acpid/acpi-support-base for power events)
and adding aliases for 'shutdown' and 'reboot':
I have found that using ssh.socket instead of ssh.service makes clients
shut down cleanly most of the time (sometimes they will still hang, but
it is rare).
systemctl disable ssh.service
systemctl enable ssh.socket
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
On Fri, 2014-10-10 at 18:51 +0200, Tom Hutter wrote:
Hmm I'm a bit torn apart between thinking that this is either an
ugly hack or a clean solution ^^
Never said it's not a hack. I may disagree in the word ugly ;-)
;-)
If ssh is restarted, my hack does exactly the expected. The ssh user
Hi,
I'm also getting this behaviour from a stripped-down Jessie VM that uses
systemd.
It started when I switched that VM from sysv to systemd a couple of
months ago.
It's reproducible on that VM - happens every time.
openssh-server package version: 1:6.6p1-7.
Funny enough, this doesn't
Package: openssh-server
Version: 1:6.6p1-5
Severity: normal
Hi.
Since openssh-server comes with systemd support, whenever a host
is shut down or restarted, ssh connections to that host just hang
and are no longer cleanly terminated (one also doesn't see the
shutdown message anymore).
I'd
See Also:
https://bugzilla.redhat.com/show_bug.cgi?id=626477
smime.p7s
Description: S/MIME cryptographic signature
39 matches
Mail list logo
