Tâche #21082: ssh -X impossible juste après instance - Distribution EOLE - Ensemble Ouvert Libre Évolutif

Tâche #21082

Scénario #21077: Traitement express MEN (34-36)

ssh -X impossible juste après instance

Added by Joël Cuissinat over 5 years ago. Updated over 5 years ago.

Status:

Fermé

Priority:

Normal

Assigned To:

Daniel Dehennin

Target version:

sprint 2017 34-36 Equipe MENSR

Start date:

07/25/2017

Due date:

% Done:

100%

Estimated time:

2.00 h

Spent time:

1.50 h

Remaining (hours):

0.0

Description

Après avoir instancié un serveur en 2.6.2, une connexion en ssh -X affiche :

X11 forwarding request failed on channel 0

Ce n'est plus le cas si on redémarre le service ssh et qu'on se connecte de nouveau.

Associated revisions

Revision 0a876f93 (diff)
Added by Daniel Dehennin over 5 years ago

OpenSSH service must restart with network

Our template use the old upstart “restart” which is now replaced in
Ubuntu with “systemctl” or “invoke-rc.d”.

tmpl/openssh-server: update template to conform to Ubuntu script.

Ref: #21082

History

#1 Updated by Daniel Dehennin over 5 years ago

Le problème vient du fait que le service SSH n’est pas redémarré lors de la phase d’instance.

Cela vient du template eole-common:source:tmpl/openssh-server qui utilise une commande upstart pour redémarrer le service:

--- /etc/network/if-up.d/openssh-server    2017-08-28 10:19:50.475489275 +0200
+++ openssh-server    2017-08-28 10:19:43.315488781 +0200
@@ -30,7 +30,13 @@
     exit 0
 fi

-# We'd like to use 'reload' here, but it has some problems; see #502444.
-restart ssh || true
+# We'd like to use 'reload' here, but it has some problems; see #502444.  On
+# the other hand, repeated restarts of ssh make systemd unhappy
+# (#756547/#757822), so use reload in that case.
+if [ -d /run/systemd/system ]; then
+    systemctl reload --no-block ssh.service >/dev/null 2>&1 || true
+else
+    invoke-rc.d ssh restart >/dev/null 2>&1 || true
+fi

 exit 0