Through Raring and Saucy, my two modifications to the given LTSP-PNP
setup have been:
In /etc/dnsmasq.d/network-manager replace the bind-interfaces line
with a bind-dynamic line.
Edit /etc/dnsmasq.d/ltsp-server-dnsmasq.conf: comment out the port=0
line
And those two mods still work for me in
I thought I was done with this kind of issue, but I may be back for
more.
It turns out that the only LTSP client that boots normally is the one
that I was doing all of the above troubleshooting on. Others that I
have tried in my little 2-PC setup all stop at a blank/black screen
after
I'm currently troubleshooting a problem with a Lubuntu Quantal setup
with LTSP (terminal server network).
Most of the clients stop responding at a blank/black screen during
bootup. But only after successfully PXE network booting, getting DHCP
assignments, and beginning the process of booting
No, nis is not on hosts line of nsswitch.conf. I agree that my case is
not the same as the one reported.
But since the problem here is reported to be one in which ntp is being
started before the system is capable of resolving DNS, I couldn't help
but notice the similarity to my previous problem
Agreed. And I had hoped that I could eliminate ntpd as the source of
the problem by using a simple switch in the LTSP configuration to turn
it off for the client. Unfortunately that does not seem to be effective
in disabling ntpd. Troubleshooting that elsewhere .
--
You received this bug
RE Thomas Hood's #120: That is very interesting, though I admit it is
near the outer limits of my current understanding.
To address the only questions above:
The problem is that the LTSP client, after successfully getting
DHCP assignments, fails to download the pxelinux boot image.
It reports
Thanks for the explanation of how removal of /etc/dnsmasq.d/network-
manager sets up a conflict between standalone dnsmasq and NM-dnsmasq.
(But also see my surprising observation below.)
Should this conflict be manifesting itself somehow?
Everything seems to be working right now.
Well, I am
I don't know how my case enters this discussion, but it is certainly
connected to the current default installation wherein network-manager
starts an instance of dnsmasq to act as a DHCP, DNS and TFTP server.
I was troubleshooting an LTSP-PNP client boot problem under Lubuntu
Quantal. I installed
