[14:53] can everything on the edubuntu add-on cd be installed by apt as a regular package? [15:03] pmatulis: yes [15:09] stgraber: thanks, and what exactly gets installed with 'edubuntu-server' package? [15:09] how does it differ from 'edubuntu-desktop'? [15:10] edubuntu-server installs moodle IIRC [15:10] i see a lot of apache/php stuff as dependencies [15:10] but then it just says it will install 'edubuntu-server' as well [15:11] apache, php and postgresql are moddle deps [15:11] ok, but what exactly what does 'edubuntu-server' give me? [15:11] not ltsp stuff? [15:11] nope === hfsdo_ is now known as hfsdo [16:21] Hi All! [16:22] I've been working on making localapps work on my jaunty ltsp server the last few days. [16:22] perhaps it is working... [16:22] sounds like a strange question, but what test can I use to see if firefox is running as a localapp? [16:29] for example, the system monitor run on the server shows user mrg using 117.7 mb of memory, while sys mon run on client for this user shows mrg using 89.4 mb. Does this tell me something? [16:46] hello? [16:50] dgroos: just login to the client and issue the 'ps' command [16:51] dgroos: if it's there it's there, if it's not it's not [16:52] pmatulis: Thanks! [16:52] dgroos: glad to help [16:55] pmatulis: I do this and I see 2 pids, neither has to do w/firefox pid I don't think--I sure don't see the word, 'firefox' on the output at least--thus no localapp firefox? [16:55] dgroos: if '$ ps ax | grep fire' doesn't give you anything then you're not running FF locally [16:56] dgroos: how did you log in to the client? [16:57] pmatulis: I've got a client up in front of me so have logged into this machine and am typing the commands at a terminal on the thin client machine. [17:01] dgroos: you've opened gnome-terminal you mean? [17:02] pmatulis: yes, I've opened up terminal in the GNOME desktop of the thin client (if that's what you mean) [17:03] dgroos: ok, you need to realize that you're on the server in such a situation, not the client [17:04] dgroos: you need to either access the console of the client or connect to it via SSH [17:04] pmatulis: right! so how do I do either of these--a link to a useful background page would be great! [17:08] dgroos: i recommend console for you right now, there are 2 ways, and the easiest is to simply add something like 'SCREEN_08 = shell' to the default section of your lts.conf file. then reboot the client and access the console with Ctrl-Alt-F8 [17:09] dgroos: run: `ltsp-localapps xterm` in the terminal - it'll give a local xterm [17:10] Then, from the local xterm, run ps like pmatulis told you to see if firefox is running [17:11] alkisg: nice, will try [17:14] alkisg: Thanks--I'm doing this and I get... [17:14] alkisg: is that a jaunty-only thing? [17:14] 'grep fire [17:14] dgroos: so FF is not running [17:15] alkisg and pmatulis: THANKS! now I can try to figure out why it isn't and have a test to figure out if! [17:16] pmatulis: I think it's >= 8.10 [17:17] dgroos: now try: ltsp-localapps firefox [17:18] alkisg: that ltsp-localapps command rocks! [17:18] pmatulis: you don't get a root prompt, though; only a user shell [17:18] alkisg: hmmm, says command not found (did in the local xterm) [17:19] dgroos: no, do it in the terminal [17:19] (gnome-terminal, I mean) [17:19] * pmatulis nods [17:20] alkisg: got it! did it. and it opened firefox... [17:20] dgroos: then you just need to put the lts.conf entry for localapps [17:21] DNS_SERVER=10.160.31.1 / SEARCH_DOMAIN=ioa.sch.gr / LOCAL_APPS_MENU=True [17:21] Modify to suit your needs [17:21] (that's on 3 seperate lines) [17:22] alkisg: thought I did that... I wasn't sure how to get the correct DNS_SERVER and SEARCH_DOMAIN info--that must be my problem... [17:22] dgroos: no, the LOCAL_APPS_MENU=True is enought to run firefox locally [17:22] The other ones are needed later on, when you start surfing :) [17:23] dgroos: upload your lts.conf to pastebin [17:23] dgroos: are you running jaunty? [17:23] alkisg: will do-- pastebin is where? [17:23] http://pastebin.ubuntu.com [17:23] pmatulis: yes [17:23] ...and then paste the url here [17:23] dgroos: maybe just read https://help.ubuntu.com/community/UbuntuLTSP/LTSPLocalAppsJaunty [17:24] alkisg: sorry to cut in [17:24] pmatulis: don't worry I always do that, too, so I don't mind :) [17:24] pmatulis: thanks! I've read it like the bible these last couple of days... [17:32] alkisg: question: which lts.conf, the one in the /opt/ltsp/i386_w_localapps/etc or /var/lib/tftpboot/ltsp/i386_w_localapps? [17:32] /var/lib/tftpboot/ltsp/i386/lts.conf [17:33] If there's another one there with a different name, it won't find it [17:33] alkisg: done! [17:34] dgroos: if you mean that you put it to pastebin, now you have to paste the URL here for us to see it [17:35] alksig: right! http://pastebin.ubuntu.com/202249 [17:35] dgroos: you need a [Default] line on top [17:39] alkis: 1. you mean, just type the word, 'Default' on a line at the top? and 2. I've got an 'lts.conf' and 'lts.conf~' in this location. Is this issue? [17:39] 1. No, I mean with the brackets: [17:39] [Default] [17:39] [17:40] 2. No, it's a backup that gedit did. [17:42] alkisg: OK now is: http://pastebin.ubuntu.com/20224951 [17:42] oops didn't paste right... [17:42] http://pastebin.ubuntu.com/202251 [17:43] dgroos: ok. Reboot the client and start firefox normally from the menus [17:43] ...and see if it runs ok [17:43] (don't logoff; reboot it) [17:43] (ehm, I mean, dont _just_ logoff) [17:44] alkisg: will do :-) [17:48] alkisg: Cool! 1 step at a time :) the firefox title bar says "Mozilla Firefox (on ltsp20) [17:49] alkisg: so now I need to do the NAT that I've read about? [17:49] dgroos: fine, you now have a local firefox :) [17:49] :) [17:49] dgroos: you have the classic 2 nic/2 switches ltsp setup? [17:49] alkisg: yes. [17:50] * alkisg has to internationalize his sch-scripts project... they automatically do all of this [17:50] Well, 1 router and 1 switch... [17:50] Yeah ok the same thing [17:51] Yes? didn't get that last one? [17:52] I've started a project, called sch-scripts, and it can install firefox as a local app and also do the natting thing automatically, with a menu driven interface, but it's in Greek... :( [17:52] (and also a bunch of other staff...) [17:53] dgroos: have you modified your dhcpd.conf at all? [17:53] alkisg: wish I do Greek! [17:53] alkisg: I don't remember--I'll open it... [17:54] dgroos: upload to pastebin your /etc/ltsp/dhcpd.conf and your /etc/network/interfaces [17:54] alkisg: will do. [17:57] alkisg: dhcp.conf at http://pastebin.ubuntu.com/202258 and... [17:59] alkisg: http://pastebin.ubuntu.com/202260 [18:02] dgroos: run these, they'll change your IP to 192.168.0.1 so that it matches dhcpd.conf - your net connection will get down for a few moments: [18:02] invoke-rc.d dhcp3-server stop [18:02] invoke-rc.d NetworkManager stop [18:02] invoke-rc.d networking stop [18:02] sed -i -e 's/192\.168\.0\.254/192.168.0.1/g' /etc/network/interfaces [18:02] invoke-rc.d networking start [18:02] invoke-rc.d NetworkManager start [18:02] invoke-rc.d dhcp3-server start [18:03] alkisg: Thanks! [18:04] alkisg: as root, right? [18:04] dgroos: yes [18:04] dgroos: then, run: [18:04] sed -i -e "s/^# By default this script does nothing\./# By default this script does nothing\.\n\niptables -t nat -A POSTROUTING -j MASQUERADE/" /etc/rc.local [18:05] dgroos: and finally: sed -i -e 's/^[[:space:]]*##*[[:space:]]*net.ipv4.ip_forward[[:space:]]*=[[:space:]]*1/net.ipv4.ip_forward=1/' /etc/sysctl.conf [18:05] And you're done [18:11] alkisg: was doing this on my laptop via NX client and entered the second line above and... got disconnected :) [18:11] (08:02:07 μμ) alkisg: dgroos: your net connection will get down for a few moments [18:12] alkisg: so went back to server and continued w/third line and got message: "Ignoring unknown interface eth0=eth0: [18:12] So if you only pasted half of it, it'll stay down... :( [18:12] dgroos: that's normal [18:12] OK... I'll carry on! [18:20] alkisg: arg! trying to save time/copy-paste and got myself into trouble... [18:20] dgroos: do you want me to put it to pastebin? [18:21] alkisg: Thanks--I can do it but first need to exit from issue... I'll explain: [18:22] alkisg: I typed: sed -i -e "s/^# By default this script does nothing\./ [18:22] ...and then this automatically entered, leaving me a ">" [18:23] ... so I tried to type: exit, quit [18:23] and to no avail--still get the ">" [18:23] dgroos: press Ctrl+C to cancel the editing... [18:23] dgroos: you're typing this, not copy/pasting? Then I'd better tell you what to do, it'll be easier than writing all this [18:24] alkisg: good! I'll do and start over... OK yes, I can't copy/paste as on different computers... [18:24] dgroos: if I put it to pastebin, can you get it from the other computer? [18:25] as long as my server can get on the 'net which it appears it can... [18:27] dgroos: http://pastebin.ubuntu.com/202276/ [18:29] alkisg: got it I'm just about to start line 9 [18:30] alkisg: OK! Thanks! and now I start thin client... [18:30] dgroos: well... [18:31] is it easy to reboot the server? if not, you'll need 2 lines more [18:31] alkisg: it is easy, not super quick but easy :-) I'll do it... [18:32] ok... otherwise do: sysctl -p and: iptables -t nat -A POSTROUTING -j MASQUERADE [18:32] I forgot to put them to pastebin [18:33] Sure--That's quicker... [18:33] (again, as root) [18:35] alkisg: says error: unable to open and preload file "and:" [18:36] dgros: two lines: [18:36] sudo sysctl -p [18:36] sudo iptables -t nat -A POSTROUTING -j MASQUERADE [18:36] I see :) [18:37] got it! [18:37] ok, reboot a client now [18:38] (it turns out it would be much simpler if I modified and gave you the whole script instead of only pasting parts of it :() [18:39] do you mean-- put all of the instructions into a shell script, then I would just run the script? [18:41] dgroos: yes, but I already have that script, and it has some failsafe checks also, the problem was that it displayed some messages in greek, that's why I pasted only parts of it... :( [18:41] alkisg: don't seem able to log into the client :( [18:42] dgroos: ah right there's another problem. Ah, those scripts... [18:42] You have to run: [18:42] sudo ltsp-update-sshkeys [18:42] sudo ltsp-update-image [18:42] Right! [18:43] alkisg: LaserJock recently proposed an idea about having a repository for useful scripts that many people have that could benefit others--seems like this is one that should be there--w/a translation or 2... :) [18:45] dgroos: yes, I also thought that was a great idea, I'll try to internationalize my scripts in the summer and we can upload any of them that seem worthy [18:50] Hmmm... it says 'port 2000 is already defined with /opt/ltsp/images/i386.img in inetd.conf Taking no action. [18:54] dgroos: also normlal [18:55] Now reboot a client [18:59] alkisg: the thin client boots, goes to login screen, I try to login and it says: "No response from server, Restarting" and then the login screen refreshes... [18:59] dgroos: that's the ssh-keys problem, did you run those 2 commands? [19:00] (08:42:21 μμ) alkisg: sudo ltsp-update-sshkeys [19:01] alkisg: yes. After typing that in, it asked for my sudo password, I typed it, hit return, and it went back to the prompt... [19:04] dgroos: Hmmm... I'm pretty sure it's the ssh keys problem. Change your lts.conf with this one, so that you can get a local shell on the terminal: http://pastebin.ubuntu.com/202297/ [19:07] pasted and saved this on the lts.conf file. I'm not sure what to do now? [19:07] Now, reboot the client, [19:07] and when it boots, press Alt+Ctrl+F2 [19:08] You'll get a local terminal. There, write: [19:08] ssh -l your-user-name server [19:08] If I'm right, it'll warn you about the ssh keys not being correct [19:09] Then, if you accept the modified ssh keys, and if you press Alt+Ctrl+F7, you'll be able to logon to the GUI [19:11] This did the trick! I can log on! Now for firefox test... [19:13] dgroos: what did it say about the ssh keys? That it doesn't know the keys, or that they were modified? Because that trick was a temporary only solution, the "permanent" solution is ltsp-update-sshkeys and ltsp-update-image... [19:14] alkisg: it said that it was an unknown host I believe... [19:14] (firefox still can't get to internet :( [19:15] dgroos: press alt+ctrl+f2 again, and see the gateway etc: [19:15] route -n [19:15] this shows the gateway [19:15] cat /etc/resolv.conf [19:15] this shows the dns server [19:16] are these correct? [19:16] hmmmm client froze up, will reboot and do test... [19:19] client won't re-boot. got to a blank screen and curser started to blink... tried alt+ctrl+f2 and did nothing, also... [19:21] OK i just tried to reboot client and it worked this time... [19:22] it is indeed different info... [19:24] cat /etc/resolv.conf says: domain gateway.2wire.net and search gateway.2wire.net and nameserver 192.168.3.1 and the client at route -n says... [19:26] for eth0 Destination 192.168.0.0 and Gateway is 0.0.0.0 and Genmask is 255.255.255.0 and Flags is U and Metric is 0 and Ref is 0 and on the second line... [19:27] for eth0 Destination 0.0.0.0 and Gateway is 192.168.0.0 and Genmask is 0.0.0.0 and Flags is UG and Metric is 0 and Ref is 0 Oh yeah, it says that Use was 0 for both lines. [19:30] dgroos: your gateway is wrong. It should be 192.168.0.1 [19:32] dgroos: does your /etc/ltsp/dhcpd.conf have "options routers 192.168.0.1"? [19:33] alkisg: alkisg: exactly... [19:34] shall I go to the router in my house and change to 192.169.0.1? [19:34] No no [19:34] router means the gateway [19:34] Upload your /etc/ltsp/dhcpd.conf to pastebin, please... [19:36] http://pastebin.ubuntu.com/202320 [19:37] alkisg: I really appreciate your help these few hours, now. I totally understand if you have to get on with the rest of your life :-) I can try to figure this out or ask others... [19:37] Hmm, other than " filename "/ltsp/i386_w_localapps/pxelinux.0"; " it looks ok [19:39] I've got 2 chroots: the i386 and the copy where I'm trying local apps i386_w_localapps as per the directions on https://wiki.edubuntu.org/LTSPLocalAppsJaunty [19:41] dgroos: erm, ok, that's a problem [19:41] E.g. when you did ltsp-update-sshkeys / ltsp-update-image, not both of the images were updated for the new IP [19:42] That's why even after the updating you had problems logging in [19:42] sudo ltsp-update-image -a i386_w_localapps [19:42] You need this one ^^^ to update [19:43] oops... [19:43] or should that be OOPS [19:43] sorry and I'll do it now... [19:43] But still, this doesn't answer why your gateway is wrong [19:44] I wonder... [19:44] there was a firefox bug fix where I had to add a script, here... [19:45] $ cat /opt/ltsp/i386/etc/init.d/chmod-resolv.sh [19:45] #! /bin/sh [19:45] chmod 644 /etc/resolv.conf [19:46] and then run this command to add to the lts.conf file: [19:46] $ cat /var/lib/tftpboot/ltsp/i386/lts.conf [19:46] SEARCH_DOMAIN = ubuntu-ltsp5 || Change this for your own network [19:46] DNS_SERVER = 192.168.1.1 || Change this for your own network [19:46] RCFILE_01=/etc/init.d/chmod-resolv.sh [19:47] does this relate? [19:48] but I should say I added it to the i386_w_localapps lts.conf [19:50] OK--just updated the correct image and was able to log in :) [19:51] dgroos: put /var/lib/tftpboot/ltsp/i386_w_localapps/lts.conf to pastebin [19:51] started firefox browser, said it was running as a localapp, tried to open the tabs but couldn't, then quit [19:52] Your gateway is wrong; firefox won't work until you fix it [19:54] http://pastebin.ubuntu.com/202341 [19:56] dgroos: can you do this in a local terminal again? [19:56] route -n | grep ^0 [19:57] Does it say 192.168.0.0 ?!! [19:57] I'll check... rebooting thin client... [19:57] No need for reboot [19:58] --I meant 'boot' [20:00] it says: 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 [20:03] dgroos: that's fine then... [20:03] The last time you said it was 192.168.0.0 [20:04] dgroos: so, try to ping your dns server: ping 192.168.3.1 [20:04] ping from the server? [20:04] no, from the local terminal on the client [20:04] Erm... that's where you ran the `route -n` command, right? [20:07] right! [20:07] and yes, it did ping! [20:07] Ehm, ok, now try: ping www.google.com [20:08] that worked as well. [20:09] ....ok, now try www.google.com on firefox [20:09] (all this pinging was done from the *local* terminal, right? not a gnome-terminal...) [20:10] correct. [20:10] So, does firefox work now? [20:10] firefox tries to go to site, unsuccessfuly for a while, then quits.... [20:11] I wonder if it has anything to do with: https://help.ubuntu.com/community/UbuntuLTSP/LocalAppsResolvConf ? [20:11] No, if ping works from a local terminal then your resolv.conf is ok [20:11] Try to put this on firefox: http://74.125.39.104 [20:14] hmmm... this time upon launching firefox I quickly closed up the different tabs before it quit, and now it works!!! :) :) [20:15] I think it might have been trying to load a flash video on one of the tabs and maybe ??? [20:15] Heh... maybe it just needed a refresh... [20:15] I'd guess all of might? ;) [20:16] Thanks so much!!! [20:16] I want to record lots of these ideas andinfo for others to use... [20:16] You're welcome... you can put info on the wiki [20:18] I wonder, would it be better to put this info on my blog and reference to it with a 'note for newbies' on the wiki, or put the whole thing directly on the wiki page? Any thoughts? [20:29] alkis and pmatulis too, thanks again :) you keep the wheel turning... David [20:51] alkisg: nice session! [20:51] pmatulis_: nah, it would be much much shorter if I just translated my scripts to english :( [20:52] I tried to make it faster, but it turned out for the worse [21:34] Good evening all, from Brazil! [21:40] hey sbalneav!