Main page
[00:01] [rptan] hi, anyone familiar with the "failed to connect to NBD server" error for Ubuntu 10.04?
[00:11] toscalix (~toscalix@77.229.115.4) joined #ltsp.
[00:24] [Appiah] does it not always say that?
[00:26] [alkisg] rptan: that's usually because dhcp points the client to the wrong server
[00:27] [alkisg] (or, more rare, because the client is too fast, e.g. core 2 duo)
[00:30] [rptan] alkisg: hm, what i did is install ltsp on a server using alternate cd on amd64
[00:32] [alkisg] Hmmm maybe inetd.conf isn't pointing to the right file then
[00:32] [alkisg] Try this:
[00:32] [alkisg] grep nbd /etc/inetd.conf
[00:32] [rptan] alkisg: it was okay when i tested with VMs, but on the physical machines they need i386
[00:33] [alkisg] And see if the image file is actually present on the file system (/opt/ltsp/images/xxx)
[00:33] [rptan] alkisg: so i removed the directory and did a rebuild of the ltsp-client with the arch i386 option
[00:34] [alkisg] If inetd is pointing to and amd64.img and you have an i386.img, then that's your problem...
[00:34] elias_a (elias@xob.kapsi.fi) joined #ltsp.
[00:34] [rptan] alkisg: ok let me check
[00:37] [rptan] alkisg: wow, ur right on target. do i need to restart anything after editing the conf file?
[00:37] [alkisg] sudo invoke-rc.d openbsd-inetd restart
[00:37] [elias_a] Mikael - are you arond?
[00:37] [elias_a] ...around?
[00:41] [rptan] alkisg: thanks alot, its working fine now.!
[00:41] [alkisg] np
[00:54] toscalix (~toscalix@77.229.115.4) left irc: Remote host closed the connection
[01:32] satellit_ (~satellit@2002:42dc:6d04:0:222:43ff:fe64:e476) joined #ltsp.
[01:38] bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) joined #ltsp.
[01:45] ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
[01:47] ogra (~ogra@ubuntu/member/ogra) left irc: Disconnected by services
[01:47] Nick change: ogra_ -> ogra
[01:47] ogra (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Changing host
[01:47] ogra (~ogra@ubuntu/member/ogra) joined #ltsp.
[01:47] ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
[01:48] tlze (~tlze@2001:470:19:344:230:18ff:fea2:8fea) joined #ltsp.
[01:48] ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Remote host closed the connection
[01:51] otavio (~otavio@debian/developer/otavio) left irc: Read error: Connection reset by peer
[02:12] bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) left irc: Ping timeout: 260 seconds
[02:32] rmcgougan (~rmcgougan@60-234-231-241.bitstream.orcon.net.nz) joined #ltsp.
[02:38] otavio (~otavio@debian/developer/otavio) joined #ltsp.
[02:42] [rmcgougan] Have been trying to set up a 64 bit alternate cd ltsp using Ubuntu lucid lynx as a ltsp server using one ethernet card to communicate with machines on my schools lan, our lan server is SME Server it allocates the dhcp for the lan. Have got client machines initiating the boot process from the i386 boot image on the ltsp server but I get an error saying nbd failure. Have tried dpkg-reconfigure nbd-server to create a config file in
[02:42] [rmcgougan] /etc/nbd-server followed by sudo ltsp-update-image --arch i386 but still the thin clients cannot reach the log in page.
[02:43] [Appiah] 09:32 < alkisg> grep nbd /etc/inetd.conf
[02:43] [Appiah] 09:33 < alkisg> If inetd is pointing to and amd64.img and you have an i386.img, then that's your problem...
[02:44] [alkisg] Heh, it seems that problem is quite common :)
[02:44] [Appiah] ^^
[02:46] [rmcgougan] I thought it was necessary to create an i386 image even though the actual ltsp server is 64 bit because the thin clients are i386 machines is this a foolish mistake on my part?
[02:46] [Appiah] sudo ltsp-build-client --arch=i386
[02:47] [alkisg] rmcgougan: so now you have an i386 image?
[02:47] [alkisg] If you do, then you just need to change inetd.conf...
[02:50] [rmcgougan] Thanks Appiah I did use sudo ltsp-build-client --arch=i386 and have created the i386 image, yes my problem is now how to change the inetd.conf I am a teacher just having a go at setting up an ltsp server in my school and do not know how to change inetd.conf to point at the i386.img
[02:50] [Appiah] just open the file with a text editor
[02:50] [alkisg] rmcgougan: sudo gedit /etc/inetd.conf
[02:55] [rmcgougan] I can use the terminal and can edit conf files but need some step by step help to alter /etc/inetd.conf file - do i just change amd64.img to i386.img within the file?
[02:55] [alkisg] Yes
[02:55] [alkisg] Then, run this to restart inetd: sudo invoke-rc.d openbsd-inetd restart
[02:56] [rmcgougan] Thanks very much for the help.
[03:08] [rmcgougan] I have already tried using K12Linux Live Server media (and now I'm trying Ubuntu Lucid Lynx ltsp) and ran into problems with screen lock ups on the clients and server using K12Linux Live Server when two or three thin clients were running flash player based websites. I read some tips that indicated you can edit the servers lts.conf file to allocate more ram for some applications such as firefox e.g. instead of 32mb ram per client
[03:08] [rmcgougan] for firefox change the allocation to 128mb ram for that application to help avoid screen lock ups with multiple thin clents on flash player websites.
[03:09] [rmcgougan] Do you think this editing of the lts.conf is a good move for schools where children often are using flash palyer based websites?
[03:10] [alkisg] What are your client specs?
[03:10] [alkisg] (CPU/RAM, mostly?)
[03:10] [alkisg] *and VGA
[03:13] [alkisg] *and network speed, 100 mbps or gigabit?
[03:18] [rmcgougan] The specs vary but the machines generally are old with cpu 433-999, 128-512mb ram, vga -not sure but basic and 6-10 years old, network 100mb lan, ltsp server gigabit network cards x2, tried to use ltsp server with a switch but was only 100mb speed switch no gigabit connections. My current network set up is just using one gigabit ethernet card from ltsp server, with dhcp from our separate lan server pointing to the static ip of ou
[03:18] [rmcgougan] r ltsp server to let the client find the boot image.
[03:19] rptan (~d2d5dd50@gateway/web/freenode/x-xgislhsdowuuamop) left irc: Quit: Page closed
[03:19] [alkisg] " My current network set up is just using one gigabit ethernet card from ltsp server" ==> but that is connected to a 100mbps switch, right?
[03:20] [alkisg] That's a little low for LTSP, a gigabit connection from the server to the switch with flow control=off is required for acceptable flash playback
[03:20] [alkisg] https://help.ubuntu.com/community/UbuntuLTSP/FlowControl
[03:22] [rmcgougan] Current set up just goes from ltsp server using one Gigabit ethernet connection on ltsp server straight to lan connection which is all 100mb cabling.
[03:29] [alkisg] So it's a 100mbps connection, too low for flash.
[03:30] tlze (~tlze@2001:470:19:344:230:18ff:fea2:8fea) left irc: Ping timeout: 272 seconds
[03:33] [alkisg] The best thing to do is to upgrade your switch, or at least use multiple cards on the server (https://help.ubuntu.com/community/UbuntuLTSP/Trunking)
[03:33] [Mava] shouldn't flash / browser be runned as a local-app ?
[03:33] [alkisg] With 10-year old PCs with 128 RAM? Not a chance... :)
[03:34] [Mava] heh, in that case =)
[03:34] [Mava] new switch would be perfect to be used
[03:34] [alkisg] Yeah, a 16 port switch with 1 gigabit port here costs about 60 ¬, which isn't much..
[03:34] [rmcgougan] The LTSP server has a gigabit ethernet connection going from it, but our lan is 100mb cabling in our school. So all the client machines are sending data through 100 mb cable.
[03:35] [alkisg] rmcgougan: but is the switch gigabit?
[03:35] [Mava] rmcgougan: the bottleneck link is the one which is between switch and server
[03:35] [alkisg] If it doesn't have a gigabit port, then the connection from the server to the switch is 100 mbps...
[03:36] [rmcgougan] No the switch is not gigabit, sounds like I definately need to use a switch with at least one gigabit port connected directly to the server.
[03:36] [Mava] switch must have at least one gigabit port and the server must be connected to it. in optimal case 10 clients can communicate with 100Mb/s speed with the server
[03:37] [Mava] yah, that is what you want =)
[03:41] [Mava] rmcgougan: as a tip, one good program to monitor current bandwidth usage in linux is bwm-ng. very lightweight and clear software. just shows you how much stuff is going in the network interfaces of the server =)
[03:44] [rmcgougan] Thanks very much your help, that has cleared this up for me. I will invest in a new switch.
[03:44] [alkisg] rmcgougan: make sure to read that page about flow control
[03:44] [alkisg] Otherwise you may buy a gigabit switch and STILL have 100mbps bandwidth
[03:45] [alkisg] (i.e. you may just waste your money if flow control is on)
[03:46] [rmcgougan] alkisg I appreciate the fine tuning about the flow control I have bookmarked the https://help.ubuntu.com/community/UbuntuLTSP/FlowControl page thanks again you've helped me e a lot:-)
[03:55] [Mava] also if you buy some switch which can be configured, it could be possible to disable flow control in the switch. never done that though, but it could also work
[03:58] [rmcgougan] thanks
[03:59] [alkisg] Yup it works, it's something one needs to check before buying a switch.
[04:05] [Mava] mm.. after a quick check i'm not sure after all is it as effective as disabling flow control as explained in that wiki page
[04:06] [Mava] it would be worth to make an experiment =)
[04:07] [Mava] but 2pm. coffee coffee coffee -
[04:11] [alkisg] Mava: I've checked both ways (I wrote that page after some discussion in the mailing list), both are effective, but disabling flow control on the server NIC isn't always possible (depends on the NIC) and of course has some additional administrative overhead.
[04:12] [alkisg] So the "get a good switch" way is always better, as long as one has the extra money
[04:12] [alkisg] (the cheapest configurable switch that I found was 4-5 times more expensive than the unmanaged one)
[04:19] rmcgougan (rmcgougan@60-234-231-241.bitstream.orcon.net.nz) left #ltsp ("Leaving").
[04:31] [Mava] alkisg: ahaa... feeling kind a confused, so... the client cant process data enough fast and it sends PAUSE to server right ?
[04:32] [alkisg] Right, so the server pauses instead of sending data to another client
[04:32] [alkisg] I've benchmarked with flow control off = 990 mbps and with flow control on = 90 mbps with the same switch (by changing flow control on the nic)
[04:32] [Mava] whoa
[04:32] [Mava] and the pause really is tcp connection ?`
[04:33] [alkisg] No, it's an ethernet pause
[04:33] [Mava] sorry, not the pause, but the connection is using tcp protocol ?
[04:33] [alkisg] Yes
[04:33] [alkisg] I've tried that with netperf
[04:33] [Mava] layer 2 level pause ?
[04:33] [alkisg] I'm not sure about the level. But there's also flow control in the tcp protocol, and that is NOT a problem
[04:34] [alkisg] I.e. if the client has to drop data because it receives it very fast, the sender lowers the rate because of the tcp protocol itself
[04:34] [Mava] ah, now it starts to feel much more understandable.. first i thought it was tcp pause, and tcp congestion control is different =)
[04:36] [Mava] and of course, once there happens this flow controlling in the lower levels it stops or lowers the whole ethernet so it affects also to another client connections
[04:37] [Mava] and now once flow control is disabled the congestion control in tcp protocol looks after the client machine =)
[04:37] [Mava] right ?
[04:53] pths (~pts@250.84-48-63.nextgentel.com) left irc: Ping timeout: 245 seconds
[04:54] pths (~pts@250.84-48-63.nextgentel.com) joined #ltsp.
[05:09] pmatulis (~peter@mail.papamike.ca) joined #ltsp.
[05:15] [alkisg] Mava, right, exactly
[05:16] jhutchins_lt (~jonathan@64-151-37-66.dyn.everestkc.net) got netsplit.
[05:16] Appiah (~appiah@ip69.hethane.riksnet.nu) got netsplit.
[05:16] morfic (~morfic@unaffiliated/morfic) got netsplit.
[05:16] korcan (~kshamoun@ip65-44-169-89.z169-44-65.customer.algx.net) got netsplit.
[05:16] dba (~daniel@static.88-198-196-34.clients.your-server.de) got netsplit.
[05:17] Faithful (~Faithful@202.6.145.116) left irc: Ping timeout: 252 seconds
[05:18] jhutchins_lt (~jonathan@64-151-37-66.dyn.everestkc.net) returned to #ltsp.
[05:18] Appiah (~appiah@ip69.hethane.riksnet.nu) returned to #ltsp.
[05:18] morfic (~morfic@unaffiliated/morfic) returned to #ltsp.
[05:18] korcan (~kshamoun@ip65-44-169-89.z169-44-65.customer.algx.net) returned to #ltsp.
[05:18] dba (~daniel@static.88-198-196-34.clients.your-server.de) returned to #ltsp.
[05:24] ruxpin (~pkunk@91-145-86-69.bb.dnainternet.fi) joined #ltsp.
[05:29] cliebow (~cliebow@WatchGuard.ellsworth-hs.ellsworth.k12.me.us) joined #ltsp.
[05:35] otavio (~otavio@debian/developer/otavio) left irc: Ping timeout: 252 seconds
[05:47] Guerdal82_ (~Guerdal82@lns-bzn-48f-81-56-183-225.adsl.proxad.net) left irc: Ping timeout: 272 seconds
[06:08] komunista (~slavko@adsl-195-098-012-069.dynamic.nextra.sk) joined #ltsp.
[06:22] Gadi (~romm@ool-18bbe47a.static.optonline.net) joined #ltsp.
[06:50] otavio (~otavio@debian/developer/otavio) joined #ltsp.
[07:23] ogra (~ogra@ubuntu/member/ogra) left irc: Ping timeout: 265 seconds
[07:24] ogra (~ogra@ubuntu/member/ogra) joined #ltsp.
[07:42] Guerdal82_ (~Guerdal82@lns-bzn-48f-81-56-183-225.adsl.proxad.net) joined #ltsp.
[07:43] highvoltage (~highvolta@ubuntu/member/highvoltage) left irc: Ping timeout: 265 seconds
[07:45] thunsucker (~thunsucke@12.94.187.50) joined #ltsp.
[07:49] highvoltage (~highvolta@ubuntu/member/highvoltage) joined #ltsp.
[07:56] evilx (~evilx@70.230.159.178) joined #ltsp.
[08:13] pmatulis (~peter@mail.papamike.ca) left irc: Ping timeout: 248 seconds
[08:14] staffencasa (~staffenca@128-193-153-150.oregonstate.edu) joined #ltsp.
[08:15] Barbosa_ (~Barbosa@187.58.24.236) joined #ltsp.
[08:19] Barbosa (~Barbosa@189.27.125.20.dynamic.adsl.gvt.net.br) left irc: Ping timeout: 276 seconds
[08:46] pmatulis (~peter@mail.papamike.ca) joined #ltsp.
[08:51] atkuepker (~akuepker@dsl254-058-194.sea1.dsl.speakeasy.net) joined #ltsp.
[09:04] vizz (~vizz@vizz.ws) joined #ltsp.
[09:06] [vizz] which components i need, to get sound working at debian ltsp?
[09:07] japerry (~japerry@drupal.org/user/45640/view) left irc: Quit: japerry
[09:07] [thunsucker] vizz: do your thin clients have sound cards?
[09:08] [vizz] yes
[09:08] [thunsucker] vizz: then sound should work for them
[09:09] [thunsucker] vizz: does it not?
[09:09] [vizz] it didn't, i have installed pulseaudio on server and client and SOUND=yes in lts.conf
[09:09] [vizz] doesn't
[09:10] [thunsucker] vizz: are you using any screen scripts? like rdp script
[09:10] [thunsucker] vizz: if you are not using screen script, try leaving sound=yes out of lts.conf
[09:13] [vizz] no screen scripts, i tried without lts.con to
[09:14] [vizz] here are some hacks, i will try that http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537526
[09:15] [thunsucker] vizz: so you get no sound at all?
[09:16] [thunsucker] vizz: on the client, did you go into sound settings and look around?
[09:16] [vizz] in the chroot?
[09:17] [thunsucker] on the tc desktop
[09:17] [thunsucker] vizz: you running squeeze?
[09:18] [vizz] true
[09:20] [thunsucker] vizz: sorry i'm not super familiar with that setup but if that stuff that you linked in that bug report might help
[09:20] [thunsucker] vizz: of course you could always hang out til vagrantic is here, he wrote that bug report
[09:21] [vizz] ok, thanks
[09:21] [thunsucker] vizz: sorry couldn't help more
[09:21] [thunsucker] the only other thing i can suggest
[09:21] [thunsucker] is
[09:21] [thunsucker] SOUND_DAEMON=PULSE
[09:21] [thunsucker] might work....dunno
[09:29] Selveste1 (~Selveste1@4103ds1-nks.0.fullrate.dk) left irc: Ping timeout: 245 seconds
[09:38] japerry (~japerry@drupal.org/user/45640/view) joined #ltsp.
[09:50] japerry (~japerry@drupal.org/user/45640/view) left irc: Read error: No route to host
[10:12] komunista (~slavko@adsl-195-098-012-069.dynamic.nextra.sk) left irc: Ping timeout: 258 seconds
[10:40] [atkuepker] More Fun with Intel Video: Still having problems with Intel Video on our stock Ubuntu 9.10 installs. Switching to Metacity using gconftool didn't fix it. Any further suggestions?
[10:41] [atkuepker] I did notice that out version of xserver-xorg-video-intel is "2:2.9.0"
[11:16] alkisg1 (~alkisg@ubuntu/member/alkisg) joined #ltsp.
[11:16] alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
[11:27] *** _UsUrPeR_ tips his hat
[11:27] [_UsUrPeR_] can anybody tell me how ltsp-remoteapps works, or how it would be used from an ltsp environment?
[11:30] [_UsUrPeR_] gadi: ping?
[11:31] [johnny] the same?
[11:31] [johnny] in client terminal (via ltsp-localapps xterm) ltsp-remoteapp oocalc
[11:32] *** _UsUrPeR_ attempts
[11:32] [johnny] would open up oocalc on the server
[11:32] [johnny] if your distro has it packaged..
[11:32] [johnny] not sure which version of ubuntu includes it.. or if any do
[11:32] alkisg1 (~alkisg@ubuntu/member/alkisg) left irc: Ping timeout: 248 seconds
[11:32] [_UsUrPeR_] hmm. Ok, so base Desktop installation is what I am using
[11:33] [johnny] it does what it says .. run an app remotely
[11:33] [_UsUrPeR_] on the localapps-opened xterm session, remoteapps exists, however when I attempt to run, nothing happens. is there a log file in /var/log on the server/client that reflects any problems?
[11:34] [johnny] i can imagine some useful cases might be, if a local app triggers an app that isn't truly a dep (and thus not installed) you could tell it to handle it on the server
[11:34] [_UsUrPeR_] yeah, such as opening an ooO doc from localapps firefox session
[11:34] [johnny] sure, but it probably only works on things with .desktop files.. or those that handle them
back next →
1 2
up
Generated by logs2html module for eggdrop v.2.3.4
Find latest version at http://sourceforge.net/projects/logs2html or http://shmupsik.osetia.org