Re: [Cooker] setting up terminal server, client not booting X
On Sat, 19 Oct 2002, Brent Hasty wrote: I have a working configuration of mdk9 terminal server, the clients are booting fast and proper, however I get an x respawning too fast will retry in 5 minuits error on the terminals. How do I go about configuring the x on the terminals, with terminal services? It becomes a little interesting, as / is read only. You would need to su - at the client console and run XFdrake, and try to save the config elsewhere than /etc/X11. Otherwise, you'd need to open up rw to /etc and make sure clusternfs is configured such that new files are created with the syntax XF86Config-4$$IP=x.x.x.x$$. This is covered in the clusternfs docs. Stew Benedict -- MandrakeSoft PPC FAQ: http://www.linux-mandrake.com/en/ppcFAQ.php3 IRC: irc.openproject.net #cooker-ppc
Re: [Cooker] setting up terminal server, client not booting X
On Saturday 19 October 2002 15:26, you wrote: On Sat, 19 Oct 2002, Brent Hasty wrote: I have a working configuration of mdk9 terminal server, the clients are booting fast and proper, however I get an x respawning too fast will retry in 5 minuits error on the terminals. How do I go about configuring the x on the terminals, with terminal services? It becomes a little interesting, as / is read only. You would need to su - at the client console and run XFdrake, and try to save the config elsewhere than /etc/X11. Otherwise, you'd need to open up rw to /etc and make sure clusternfs is configured such that new files are created with the syntax XF86Config-4$$IP=x.x.x.x$$. This is covered in the clusternfs docs. Stew Benedict I tried loging in as a user and then su to root, however i kept getting told I whas inputing the wrong passwd for root. I am certain I had the passwd right, but I still cannot login?
Re: [Cooker] setting up terminal server
On Saturday 05 October 2002 16:56, Todd Lyons wrote: Brent Hasty wrote on Sat, Oct 05, 2002 at 01:29:32AM -0700 : 2 issues fist all my terminals are using the eepro100 ic with pxe. how do I set the server up to boot the terminals using these nics with pxe? What do you want to know. I have PXE setup at the office serving 8.2, 9.0, and Cooker net installs. I used Erwan's pxe server rpms and whatever else it pulled in, then configured them. The config files are very well documented. The only gotcha I came across is that the tftp server is set to use /var/lib/tftpboot instead of /tftpboot. And since it's chrooted, you can't symlink to the network.img, you have to put a copy of it. A simple oneline command in my rsync script (for cooker) took care of keeping it current. Blue skies... Todd where did you get erwan's rpms for pxe?
Re: [Cooker] setting up terminal server
Brent Hasty wrote on Sun, Oct 06, 2002 at 11:46:32PM -0700 : fist all my terminals are using the eepro100 ic with pxe. how do I set the server up to boot the terminals using these nics with pxe? What do you want to know. I have PXE setup at the office serving 8.2, 9.0, and Cooker net installs. I used Erwan's pxe server rpms and where did you get erwan's rpms for pxe? Go to the contribs on any Mandrake Mirror. You'll need pxe*, there's a couple of them. Blue skies... Todd -- | MandrakeSoft USA | Security is like an onion. It's made | | http://www.mandrakesoft.com | made up of several layers and makes | | http://www.mandrakelinux.com | you cry. --Howard Chu| Cooker Version mandrake-release-9.0-0.3mdk Kernel 2.4.19-16mdk msg78344/pgp0.pgp Description: PGP signature
Re: [Cooker] setting up terminal server
On Sat, 5 Oct 2002, Brent Hasty wrote: 2 issues 1 issue - your mailer borks the Reply To: :) fist all my terminals are using the eepro100 ic with pxe. how do I set the server up to boot the terminals using these nics with pxe? Sorry. Several people have asked about PXE. I know Erwan did some PXE work for the clustering project, and I read the docs, but I don't have PXE capable hardware to implement/test. Patches welcome :) second is when booting the terminals (using a boot flopy) it fails at mounting the root filesystem. I have 5 partitions /, /usr, /var, /home, /tmp my exports lists the / (ro,all_squash) /home 192.168.1.0/255.255.255.0(rw, root_squash) do i need to modify my exports to reflect all system partitions? am i overlooking a step to give the terminals permission to mount the shared resources? That should be OK as you list. I'm assuming the subnet is correct for you network. Any messages at the client or server end? Is clusternfs running on the server? You shouldn't have to mount all the partitions specifically, it's only done for /home for rw access. Stew Benedict -- MandrakeSoft PPC FAQ: http://www.linux-mandrake.com/en/ppcFAQ.php3 IRC: irc.openproject.net #cooker-ppc
Re: [Cooker] setting up terminal server
On Saturday 05 October 2002 05:40, Stew Benedict wrote: On Sat, 5 Oct 2002, Brent Hasty wrote: 2 issues 1 issue - your mailer borks the Reply To: :) fist all my terminals are using the eepro100 ic with pxe. how do I set the server up to boot the terminals using these nics with pxe? Sorry. Several people have asked about PXE. I know Erwan did some PXE work for the clustering project, and I read the docs, but I don't have PXE capable hardware to implement/test. Patches welcome :) second is when booting the terminals (using a boot flopy) it fails at mounting the root filesystem. I have 5 partitions /, /usr, /var, /home, /tmp my exports lists the / (ro,all_squash) /home 192.168.1.0/255.255.255.0(rw, root_squash) do i need to modify my exports to reflect all system partitions? am i overlooking a step to give the terminals permission to mount the shared resources? That should be OK as you list. I'm assuming the subnet is correct for you network. Any messages at the client or server end? Is clusternfs running on the server? You shouldn't have to mount all the partitions specifically, it's only done for /home for rw access. Stew Benedict well hopefully I will soon be retiring this old hp kyak terminal server based on 8.2 and ltsp. I will then be running under mdk9.0 and kde3 with all its new goodies. what do you mean by borks and how do I fix it? is it possiable to get the eepro100 to net boot off of the terminal server, as though using a boot rom rather than pxe? I will see about the possiability of patches, but it would be a learning project for me to do. how do i check the status of cluseter-nfs?
Re: [Cooker] setting up terminal server
On Saturday 05 October 2002 05:40, Stew Benedict wrote: On Sat, 5 Oct 2002, Brent Hasty wrote: 2 issues 1 issue - your mailer borks the Reply To: :) fist all my terminals are using the eepro100 ic with pxe. how do I set the server up to boot the terminals using these nics with pxe? Sorry. Several people have asked about PXE. I know Erwan did some PXE work for the clustering project, and I read the docs, but I don't have PXE capable hardware to implement/test. Patches welcome :) second is when booting the terminals (using a boot flopy) it fails at mounting the root filesystem. I have 5 partitions /, /usr, /var, /home, /tmp my exports lists the / (ro,all_squash) /home 192.168.1.0/255.255.255.0(rw, root_squash) do i need to modify my exports to reflect all system partitions? am i overlooking a step to give the terminals permission to mount the shared resources? That should be OK as you list. I'm assuming the subnet is correct for you network. Any messages at the client or server end? Is clusternfs running on the server? You shouldn't have to mount all the partitions specifically, it's only done for /home for rw access. Stew Benedict in the control center under services it shows that clusternfs is running (started at boot) the dmesg printed to screen on a terminal as booting ends with these errors: SIOCADDRT: Network is unreachable Mounting root filesystem 192.168.1.255:/ at /sysroot If this appears to hang, check that the server of 192.168.1.255:/ is able to reverse map my IP address 192.168.1.12 to obtain my hostname client_192_168_1_12 mount: nfsmount filed: Bad file number nfs: mount program didn't pass remote address! mount: mounting 192.168.1.255:/ on sysroot failed: Invalid argument sucessfully obtained IP address via wired link [eth0] FATAL ERROR: failed to mount root filesystem ~reboot~ so it sounds like the terminal is not getting told whear to acess its /sysroot on the server, the ip address of the server, and is not being given permission to mount it. So where do I go to begin to make this work?
Re: [Cooker] setting up terminal server
On Sat, 5 Oct 2002, Brent Hasty wrote: On Saturday 05 October 2002 05:40, Stew Benedict wrote: On Sat, 5 Oct 2002, Brent Hasty wrote: 2 issues 1 issue - your mailer borks the Reply To: :) fist all my terminals are using the eepro100 ic with pxe. how do I set the server up to boot the terminals using these nics with pxe? Sorry. Several people have asked about PXE. I know Erwan did some PXE work for the clustering project, and I read the docs, but I don't have PXE capable hardware to implement/test. Patches welcome :) second is when booting the terminals (using a boot flopy) it fails at mounting the root filesystem. I have 5 partitions /, /usr, /var, /home, /tmp my exports lists the / (ro,all_squash) /home 192.168.1.0/255.255.255.0(rw, root_squash) do i need to modify my exports to reflect all system partitions? am i overlooking a step to give the terminals permission to mount the shared resources? That should be OK as you list. I'm assuming the subnet is correct for you network. Any messages at the client or server end? Is clusternfs running on the server? You shouldn't have to mount all the partitions specifically, it's only done for /home for rw access. Stew Benedict well hopefully I will soon be retiring this old hp kyak terminal server based on 8.2 and ltsp. I will then be running under mdk9.0 and kde3 with all its new goodies. what do you mean by borks and how do I fix it? Your email doesn't have the cooker list Reply To: that most of the posts do. I guess it depends on your mail client. Generally you just leave the Reply To: setting alone. is it possiable to get the eepro100 to net boot off of the terminal server, as though using a boot rom rather than pxe? If you're getting to the point of nfs mounting, it sounds like you are able to boot the eepro100, or you're using a different card for that? I had one 3com card here that would do the initial boot, but then would fail asking for the IP a second time. Erwan told me that it was because it was trying to talk to a pxe server, which didn't exist. (I may not have the terminology exactly right here). I will see about the possiability of patches, but it would be a learning project for me to do. how do i check the status of cluseter-nfs? It's started by a normal initscript, just like nfs-server. Should be 2 processes running: [root@larry root]# service clusternfs start Starting ClusterNFS (rpc.mountd): [ OK ] Starting ClusterNFS (rpc.nfsd): [ OK ] On occasion rpc.nfsd doesn't start the first try. Stew Benedict -- MandrakeSoft PPC FAQ: http://www.linux-mandrake.com/en/ppcFAQ.php3 IRC: irc.openproject.net #cooker-ppc
Re: [Cooker] setting up terminal server
On Sat, 5 Oct 2002, Brent Hasty wrote: On Saturday 05 October 2002 05:40, Stew Benedict wrote: On Sat, 5 Oct 2002, Brent Hasty wrote: 2 issues 1 issue - your mailer borks the Reply To: :) fist all my terminals are using the eepro100 ic with pxe. how do I set the server up to boot the terminals using these nics with pxe? Sorry. Several people have asked about PXE. I know Erwan did some PXE work for the clustering project, and I read the docs, but I don't have PXE capable hardware to implement/test. Patches welcome :) second is when booting the terminals (using a boot flopy) it fails at mounting the root filesystem. I have 5 partitions /, /usr, /var, /home, /tmp my exports lists the / (ro,all_squash) /home 192.168.1.0/255.255.255.0(rw, root_squash) do i need to modify my exports to reflect all system partitions? am i overlooking a step to give the terminals permission to mount the shared resources? That should be OK as you list. I'm assuming the subnet is correct for you network. Any messages at the client or server end? Is clusternfs running on the server? You shouldn't have to mount all the partitions specifically, it's only done for /home for rw access. Stew Benedict in the control center under services it shows that clusternfs is running (started at boot) the dmesg printed to screen on a terminal as booting ends with these errors: SIOCADDRT: Network is unreachable Mounting root filesystem 192.168.1.255:/ at /sysroot If this appears to hang, check that the server of 192.168.1.255:/ is able to reverse map my IP address 192.168.1.12 to obtain my hostname client_192_168_1_12 mount: nfsmount filed: Bad file number nfs: mount program didn't pass remote address! mount: mounting 192.168.1.255:/ on sysroot failed: Invalid argument sucessfully obtained IP address via wired link [eth0] FATAL ERROR: failed to mount root filesystem ~reboot~ so it sounds like the terminal is not getting told whear to acess its /sysroot on the server, the ip address of the server, and is not being given permission to mount it. So where do I go to begin to make this work? Your server is at 192.168.1.255? Stew Benedict -- MandrakeSoft PPC FAQ: http://www.linux-mandrake.com/en/ppcFAQ.php3 IRC: irc.openproject.net #cooker-ppc
Re: [Cooker] setting up terminal server
On Saturday 05 October 2002 09:23, Stew Benedict wrote: On Sat, 5 Oct 2002, Brent Hasty wrote: On Saturday 05 October 2002 05:40, Stew Benedict wrote: On Sat, 5 Oct 2002, Brent Hasty wrote: 2 issues 1 issue - your mailer borks the Reply To: :) fist all my terminals are using the eepro100 ic with pxe. how do I set the server up to boot the terminals using these nics with pxe? Sorry. Several people have asked about PXE. I know Erwan did some PXE work for the clustering project, and I read the docs, but I don't have PXE capable hardware to implement/test. Patches welcome :) second is when booting the terminals (using a boot flopy) it fails at mounting the root filesystem. I have 5 partitions /, /usr, /var, /home, /tmp my exports lists the / (ro,all_squash) /home 192.168.1.0/255.255.255.0(rw, root_squash) do i need to modify my exports to reflect all system partitions? am i overlooking a step to give the terminals permission to mount the shared resources? That should be OK as you list. I'm assuming the subnet is correct for you network. Any messages at the client or server end? Is clusternfs running on the server? You shouldn't have to mount all the partitions specifically, it's only done for /home for rw access. Stew Benedict well hopefully I will soon be retiring this old hp kyak terminal server based on 8.2 and ltsp. I will then be running under mdk9.0 and kde3 with all its new goodies. what do you mean by borks and how do I fix it? Your email doesn't have the cooker list Reply To: that most of the posts do. I guess it depends on your mail client. Generally you just leave the Reply To: setting alone. is it possiable to get the eepro100 to net boot off of the terminal server, as though using a boot rom rather than pxe? If you're getting to the point of nfs mounting, it sounds like you are able to boot the eepro100, or you're using a different card for that? I had one 3com card here that would do the initial boot, but then would fail asking for the IP a second time. Erwan told me that it was because it was trying to talk to a pxe server, which didn't exist. (I may not have the terminology exactly right here). I will see about the possiability of patches, but it would be a learning project for me to do. how do i check the status of cluseter-nfs? It's started by a normal initscript, just like nfs-server. Should be 2 processes running: [root@larry root]# service clusternfs start Starting ClusterNFS (rpc.mountd): [ OK ] Starting ClusterNFS (rpc.nfsd): [ OK ] On occasion rpc.nfsd doesn't start the first try. Stew Benedict try hitting reply all I am using a drakTermServ created boot floppy to get this far with tthe eepro100 when I #] service clusternfs start I get Starting ClusterNFS (rpc.mountd): [ OK ] Starting ClusterNFS (rpc.nfsd): [ FAILED ] so i guess now the question is how do I get rpc.nfsd working?
Re: [Cooker] setting up terminal server
On Saturday 05 October 2002 09:29, Stew Benedict wrote: On Sat, 5 Oct 2002, Brent Hasty wrote: On Saturday 05 October 2002 05:40, Stew Benedict wrote: On Sat, 5 Oct 2002, Brent Hasty wrote: 2 issues 1 issue - your mailer borks the Reply To: :) fist all my terminals are using the eepro100 ic with pxe. how do I set the server up to boot the terminals using these nics with pxe? Sorry. Several people have asked about PXE. I know Erwan did some PXE work for the clustering project, and I read the docs, but I don't have PXE capable hardware to implement/test. Patches welcome :) second is when booting the terminals (using a boot flopy) it fails at mounting the root filesystem. I have 5 partitions /, /usr, /var, /home, /tmp my exports lists the / (ro,all_squash) /home 192.168.1.0/255.255.255.0(rw, root_squash) do i need to modify my exports to reflect all system partitions? am i overlooking a step to give the terminals permission to mount the shared resources? That should be OK as you list. I'm assuming the subnet is correct for you network. Any messages at the client or server end? Is clusternfs running on the server? You shouldn't have to mount all the partitions specifically, it's only done for /home for rw access. Stew Benedict in the control center under services it shows that clusternfs is running (started at boot) the dmesg printed to screen on a terminal as booting ends with these errors: SIOCADDRT: Network is unreachable Mounting root filesystem 192.168.1.255:/ at /sysroot If this appears to hang, check that the server of 192.168.1.255:/ is able to reverse map my IP address 192.168.1.12 to obtain my hostname client_192_168_1_12 mount: nfsmount filed: Bad file number nfs: mount program didn't pass remote address! mount: mounting 192.168.1.255:/ on sysroot failed: Invalid argument sucessfully obtained IP address via wired link [eth0] FATAL ERROR: failed to mount root filesystem ~reboot~ so it sounds like the terminal is not getting told whear to acess its /sysroot on the server, the ip address of the server, and is not being given permission to mount it. So where do I go to begin to make this work? Your server is at 192.168.1.255? Stew Benedict yes is there anything wrong with this ip (192.168.1.255)?
Re: [Cooker] setting up terminal server
On Sat, 5 Oct 2002, Brent Hasty wrote: try hitting reply all I know how to reply, I was just commenting that your return address seems to be different than almost every other message I see on the list, where Reply To: points to the list. Nevermind, it's no big deal. I am using a drakTermServ created boot floppy to get this far with tthe eepro100 when I #] service clusternfs start I get Starting ClusterNFS (rpc.mountd): [ OK ] Starting ClusterNFS (rpc.nfsd): [ FAILED ] so i guess now the question is how do I get rpc.nfsd working? Stop and restart the service. Stew Benedict -- MandrakeSoft PPC FAQ: http://www.linux-mandrake.com/en/ppcFAQ.php3 IRC: irc.openproject.net #cooker-ppc
Re: [Cooker] setting up terminal server
On Sat, 5 Oct 2002, Brent Hasty wrote: So where do I go to begin to make this work? Your server is at 192.168.1.255? Stew Benedict yes is there anything wrong with this ip (192.168.1.255)? .255 is generally used as broadcast address, no? Stew Benedict -- MandrakeSoft PPC FAQ: http://www.linux-mandrake.com/en/ppcFAQ.php3 IRC: irc.openproject.net #cooker-ppc
Re: [Cooker] setting up terminal server
On Saturday 05 October 2002 11:06, Stew Benedict wrote: On Sat, 5 Oct 2002, Brent Hasty wrote: try hitting reply all I know how to reply, I was just commenting that your return address seems to be different than almost every other message I see on the list, where Reply To: points to the list. Nevermind, it's no big deal. I am using a drakTermServ created boot floppy to get this far with tthe eepro100 when I #] service clusternfs start I get Starting ClusterNFS (rpc.mountd): [ OK ] Starting ClusterNFS (rpc.nfsd): [ FAILED ] so i guess now the question is how do I get rpc.nfsd working? Stop and restart the service. Stew Benedict that worked but the terminal still does not mount its root filesystem.
Re: [Cooker] setting up terminal server
On Sat, 2002-10-05 at 13:21, Brent Hasty wrote: I am using a drakTermServ created boot floppy to get this far with tthe eepro100 when I #] service clusternfs start I get Starting ClusterNFS (rpc.mountd): [ OK ] Starting ClusterNFS (rpc.nfsd): [ FAILED ] so i guess now the question is how do I get rpc.nfsd working? Stop and restart the service. Stew Benedict that worked but the terminal still does not mount its root filesystem. Well, below is how I got mine to work. 1. I *do not* use .255 because it is a broadcast address. 2. I *do* have portmap service started because nfs needs it AFAIK. -Larry
Re: [Cooker] setting up terminal server
On Saturday 05 October 2002 06:53, Larry Nguyen wrote: On Sat, 2002-10-05 at 13:21, Brent Hasty wrote: I am using a drakTermServ created boot floppy to get this far with tthe eepro100 when I #] service clusternfs start I get Starting ClusterNFS (rpc.mountd): [ OK ] Starting ClusterNFS (rpc.nfsd): [ FAILED ] so i guess now the question is how do I get rpc.nfsd working? Stop and restart the service. Stew Benedict that worked but the terminal still does not mount its root filesystem. Well, below is how I got mine to work. 1. I *do not* use .255 because it is a broadcast address. 2. I *do* have portmap service started because nfs needs it AFAIK. -Larry I moved to .254 that is ok I turned off portmap, terminal still not mounting its root filesystem I went into a terminal and set msec 2, still not mounting /
Re: [Cooker] setting up terminal server
On Saturday 05 October 2002 01:29, Brent Hasty wrote: is there more documentation lurking about somewhere other than the help button in drakTermServ? 2 issues fist all my terminals are using the eepro100 ic with pxe. how do I set the server up to boot the terminals using these nics with pxe? second is when booting the terminals (using a boot flopy) it fails at mounting the root filesystem. I have 5 partitions /, /usr, /var, /home, /tmp my exports lists the / (ro,all_squash) /home 192.168.1.0/255.255.255.0(rw, root_squash) do i need to modify my exports to reflect all system partitions? am i overlooking a step to give the terminals permission to mount the shared resources?
Re: [Cooker] setting up terminal server
On Sat, 5 Oct 2002, Brent Hasty wrote: On Saturday 05 October 2002 01:29, Brent Hasty wrote: is there more documentation lurking about somewhere other than the help button in drakTermServ? There's a piece I did on mandrakeforum, and the individual packages all have docs. What I would do is try mounting your nfs shares from a normal machine, not a terminal-server client, then you'll at least isolate whether the issue is at the client or server end. Stew Benedict -- MandrakeSoft PPC FAQ: http://www.linux-mandrake.com/en/ppcFAQ.php3 IRC: irc.openproject.net #cooker-ppc
Re: [Cooker] setting up terminal server
Brent Hasty wrote on Sat, Oct 05, 2002 at 01:29:32AM -0700 : 2 issues fist all my terminals are using the eepro100 ic with pxe. how do I set the server up to boot the terminals using these nics with pxe? What do you want to know. I have PXE setup at the office serving 8.2, 9.0, and Cooker net installs. I used Erwan's pxe server rpms and whatever else it pulled in, then configured them. The config files are very well documented. The only gotcha I came across is that the tftp server is set to use /var/lib/tftpboot instead of /tftpboot. And since it's chrooted, you can't symlink to the network.img, you have to put a copy of it. A simple oneline command in my rsync script (for cooker) took care of keeping it current. Blue skies... Todd -- MandrakeSoft USA http://www.mandrakesoft.com Mandrake: An amalgam of good ideas from RedHat, Debian, and MandrakeSoft. All in all, IMHO, an unbeatable combination. --Levi Ramsey on Cooker ML Cooker Version mandrake-release-9.0-0.3mdk Kernel 2.4.19-16mdk msg78204/pgp0.pgp Description: PGP signature
Re: [Cooker] setting up terminal server
Brent Hasty wrote on Sat, Oct 05, 2002 at 10:41:17AM -0700 : /home 192.168.1.0/255.255.255.0(rw, root_squash) Your server is at 192.168.1.255? yes is there anything wrong with this ip (192.168.1.255)? Yes. The first and last IP of a netblock are not usable. Since the netmask is 255.255.255.0, that means that 192.168.1.0 and 192.168.1.255 are not usable as addresses. They are reserved for network usage. Your usable addresses are from .1 to .254. Most people use either .1 or .254 for the gateway outbound (and in recent years, most seem to be using .1) Change your IP and that's one problem that will go away. Blue skies... Todd -- MandrakeSoft USA http://www.mandrakesoft.com Never take no as an answer from someone who's not authorized to say yes. --Ben Reser on Cooker ML Cooker Version mandrake-release-9.0-0.3mdk Kernel 2.4.19-16mdk msg78205/pgp0.pgp Description: PGP signature
