Am Freitag, 4. Juni 2004 13:03 schrieb sysadmin: > I have long suspected the following to be true and now I have > irrefutable proof. The problem is that after a thin client has > issued a dhcp request, the kernel is being down loaded by a server > different to the one that which the machine finally connects to. > > We have four servers running ltsp 3 (these have been there for a year or > so) and I have recently installed a new one running ltsp 4. The ltsp 3 > servers supply kernel 2.4.19-ltsp-1 to the thin clients and the ltsp4 > machine supplies 2.4.24-ltsp-1. Sometimes, if you > access a shell on a machine that is connected to the ltsp 4 machine, and do > a uname -a, you can clearly see the "19" kernel rather than the expectd > "24". > > There is a side issue too whereby some thin clients that connect to the > ltsp 4 sever experience X crashes, or more precisely X does not come up at > all. It could be that the "19" kernel has different video drivers than the > "24" kernel. Until I can get consistent kernels running on the thin > clients that connect to a server, that is the machine which supplies the > kernel is same one that the client connects to, I cannot resolve the X > issue. > > Has anyone experienced problems running an LTSP environment with mixed > releases of LTSP? I suspect the problems will go away when all the servers > have been upgraded to LTSP 4, but I am not in a position to be able to take > all the servers down to upgrade each them en masse. I must keep IT > facilities available to the users and the only method that I can achieve > this is to upgrade the servers one at a time, that is the mixed version > environment must be made to work.
It seems you are running more than one dhcpd on that network and clients tend to get their kernel after dhcp information from server_1 and continue booting, running dhclient and retrieving info from server_2. This is no problem if all the servers supply same services and probably makes kind of load balancing, but it may be bad in a mixed setup. In your place, I'd set all dhcp servers as "non authoritative" and add one host section for each host at only _one_ dhcp server. This way, you can move clients from one server to another at your choice, "emptying" one server for the moment of upgrading to LTSP4. Afterwards (when everything is a homogenous landscape of LTSP4 machines), you could reduce your dhcpd setup to only two dhcp servers, and do loadbalancing e.g. by X -broadcast which is far more reasonable probably. However this has been discussed before, and I'm not experienced enough on this topic to recommend a certain strategy. btw. the kernel messages can be retrieved with the dmesg on the client shell. No idea though if this is in the LTSP tree regularly, in case it's not, you can copy it + the needed libs over from the server tree. Regards, Anselm ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
