Debian Bug report logs -
#679187
ltsp-server: Login from diskless client fails "server not responding. restart ...")
Reported by: Andreas Brogle <brogle@wel.de>
Date: Tue, 26 Jun 2012 21:51:02 UTC
Severity: important
Found in version ltsp/5.4.1-1
Done: Vagrant Cascadian <vagrant@freegeek.org>
Bug is archived. No further changes may be made.
Toggle useless messages
Report forwarded
to debian-bugs-dist@lists.debian.org, LTSP Debian Maintainers <pkg-ltsp-devel@lists.alioth.debian.org>:
Bug#679187; Package ltsp-server.
(Tue, 26 Jun 2012 21:51:05 GMT) (full text, mbox, link).
Acknowledgement sent
to Andreas Brogle <brogle@wel.de>:
New Bug report received and forwarded. Copy sent to LTSP Debian Maintainers <pkg-ltsp-devel@lists.alioth.debian.org>.
(Tue, 26 Jun 2012 21:51:05 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Package: ltsp-server
Version: 5.4.1-1
Severity: important
Dear Maintainer,
since a month ago, ltsp had been working for me fine for several years.
With an update of Debian Sid I get this problem first time, if any of the users on the clients tries to login with ldm.
"Keine Antwort des Server. Neustart ..." (translates to "server not responding. restart ...")
Although this bug seems to exist since years, I couldn't find a solution for me, despite of extensively researching the internet. Nobody seems to understand the problem.
I found out a way to avoid the above, but it's not practically :
Make a root account in the chroot environment.
Do a login as root on a client console.
<CTRL> + <ALT> + F1
Make a ssh connection to the server.
[client$] ssh server
Switch back to ldm.
<ALT> + F7
Login as user with ldm works now as it should as long, as the client machine is not rebooted.
I hope this helps one of the developers to solve that bug. There seems to be something wrong with ssh.
Thanks,
Andreas
-- Package-specific info:
chroot information: /opt/ltsp/i386
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.4-4.slh.1-aptosid-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ltsp-server depends on:
ii debconf [debconf-2.0] 1.5.44
ii debconf-utils 1.5.44
ii debootstrap 1.0.41
ii gettext-base 0.18.1.1-9
ii iproute 20120521-3
ii lsb-release 4.1+Debian7
ii openssh-client 1:6.0p1-2
ii python 2.7.3~rc2-1
ii tcpd 7.6.q-23
ii update-inetd 4.43
Versions of packages ltsp-server recommends:
ii dnsmasq 2.62-3
ii nbd-server 1:3.1.1-1
ii nfs-kernel-server 1:1.2.6-2
ii openbsd-inetd [inet-superserver] 0.20091229-2
ii openssh-server 1:6.0p1-2
ii squashfs-tools 1:4.2-4+b1
ii tftpd-hpa 5.2-2
Versions of packages ltsp-server suggests:
pn audiooss <none>
ii dnsmasq 2.62-3
ii fluxbox [x-window-manager] 1.3.2-4
ii isc-dhcp-server [dhcp3-server] 4.2.2.dfsg.1-5
ii ldm-server 2:2.2.10-1
ii libasound2-plugins 1.0.25-2
ii ltsp-docs 1.1-1
ii ltspfs 1.1-2
ii metacity [x-window-manager] 1:2.34.3-2
ii pulseaudio 2.0-3
pn qemu-user-static <none>
pn sdm <none>
ii x11-utils 7.7~1
ii xauth 1:1.0.7-1
ii xfce4-session [x-session-manager] 4.8.3-2
ii xfwm4 [x-window-manager] 4.8.3-1
-- debconf information:
ltsp-server/build_client: false
Information forwarded
to debian-bugs-dist@lists.debian.org, LTSP Debian Maintainers <pkg-ltsp-devel@lists.alioth.debian.org>:
Bug#679187; Package ltsp-server.
(Thu, 28 Jun 2012 00:45:03 GMT) (full text, mbox, link).
Acknowledgement sent
to Vagrant Cascadian <vagrant@freegeek.org>:
Extra info received and forwarded to list. Copy sent to LTSP Debian Maintainers <pkg-ltsp-devel@lists.alioth.debian.org>.
(Thu, 28 Jun 2012 00:45:03 GMT) (full text, mbox, link).
Message #10 received at 679187@bugs.debian.org (full text, mbox, reply):
On Tue, Jun 26, 2012 at 11:35:16PM +0200, Andreas Brogle wrote:
> since a month ago, ltsp had been working for me fine for several years.
>
> With an update of Debian Sid I get this problem first time, if any of the
> users on the clients tries to login with ldm.
> "Keine Antwort des Server. Neustart ..." (translates to "server not
> responding. restart ...")
The recent versions of LTSP (ltsp-update-sshkeys) and LDM do not verify IP
addresses when making the ssh connection.
Sounds like you also need to update your LTSP chroot to use the newer verison
of LDM (2.2.10-1), or if that's not possible, configure
/etc/ltsp/ssh_known_hosts.* to include an entry for each of the IP addresses of
your servers.
live well,
vagrant
Information forwarded
to debian-bugs-dist@lists.debian.org, LTSP Debian Maintainers <pkg-ltsp-devel@lists.alioth.debian.org>:
Bug#679187; Package ltsp-server.
(Thu, 28 Jun 2012 11:01:00 GMT) (full text, mbox, link).
Acknowledgement sent
to Andreas Brogle <brogle@wel.de>:
Extra info received and forwarded to list. Copy sent to LTSP Debian Maintainers <pkg-ltsp-devel@lists.alioth.debian.org>.
(Thu, 28 Jun 2012 11:01:27 GMT) (full text, mbox, link).
Message #15 received at 679187@bugs.debian.org (full text, mbox, reply):
Am Donnerstag, 28. Juni 2012 schrieb Vagrant Cascadian:
> On Tue, Jun 26, 2012 at 11:35:16PM +0200, Andreas Brogle wrote:
> > since a month ago, ltsp had been working for me fine for several years.
> >
> > With an update of Debian Sid I get this problem first time, if any of the
> > users on the clients tries to login with ldm.
> > "Keine Antwort des Server. Neustart ..." (translates to "server not
> > responding. restart ...")
>
> The recent versions of LTSP (ltsp-update-sshkeys) and LDM do not verify IP
> addresses when making the ssh connection.
>
> Sounds like you also need to update your LTSP chroot to use the newer
> verison of LDM (2.2.10-1), or if that's not possible, configure
> /etc/ltsp/ssh_known_hosts.* to include an entry for each of the IP
> addresses of your servers.
As you suggested I did a
"ltsp-build-client --arch i386 --dist sid --mirror http://192.168.0.10/apt
cacher/cdn.debian.net/debian"
Now it works again :-)
The goal originally had been to minimize maintenance and hardware resources of
the thin clients. Thought it would be a good idea to use Debian Stable for the
chroot environment. So I only had to maintain the server. Seems that was an
aberration.
Bug can be closed.
Thanks,
Andreas
Information forwarded
to debian-bugs-dist@lists.debian.org, LTSP Debian Maintainers <pkg-ltsp-devel@lists.alioth.debian.org>:
Bug#679187; Package ltsp-server.
(Thu, 28 Jun 2012 11:12:44 GMT) (full text, mbox, link).
Acknowledgement sent
to Andreas Brogle <brogle@wel.de>:
Extra info received and forwarded to list. Copy sent to LTSP Debian Maintainers <pkg-ltsp-devel@lists.alioth.debian.org>.
(Thu, 28 Jun 2012 11:12:48 GMT) (full text, mbox, link).
Reply sent
to Vagrant Cascadian <vagrant@freegeek.org>:
You have taken responsibility.
(Thu, 28 Jun 2012 14:39:08 GMT) (full text, mbox, link).
Notification sent
to Andreas Brogle <brogle@wel.de>:
Bug acknowledged by developer.
(Thu, 28 Jun 2012 14:39:09 GMT) (full text, mbox, link).
Message #25 received at 679187-done@bugs.debian.org (full text, mbox, reply):
On Thu, Jun 28, 2012 at 12:35:04PM +0200, Andreas Brogle wrote:
> Am Donnerstag, 28. Juni 2012 schrieb Vagrant Cascadian:
> > The recent versions of LTSP (ltsp-update-sshkeys) and LDM do not verify IP
> > addresses when making the ssh connection.
> >
> > Sounds like you also need to update your LTSP chroot to use the newer
> > verison of LDM (2.2.10-1), or if that's not possible, configure
> > /etc/ltsp/ssh_known_hosts.* to include an entry for each of the IP
> > addresses of your servers.
>
> As you suggested I did a
> "ltsp-build-client --arch i386 --dist sid --mirror http://192.168.0.10/apt
> cacher/cdn.debian.net/debian"
> Now it works again :-)
>
> The goal originally had been to minimize maintenance and hardware resources of
> the thin clients. Thought it would be a good idea to use Debian Stable for the
> chroot environment. So I only had to maintain the server. Seems that was an
> aberration.
It's possible, but requires a little more manual configuration for the server's
ssh keys; another option I keep forgetting about is to specify
LDM_SERVER=server and LDM_SSHOPTIONS="-o CheckHostIP=no" in lts.conf, which
doesn't require configuring the ssh keys.
wheezy will freeze soon (June 30th), so that should be a little bit more stable
than sid in the near future.
> Bug can be closed.
Ok, sending to -done.
thanks!
live well,
vagrant
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Fri, 27 Jul 2012 07:32:45 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Sat Jul 1 13:28:42 2023;
Machine Name:
buxtehude
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.