[01:29] <sbalneav> Evening all
[01:31] <LaserJock> hi sbalneav
[01:32] <sbalneav> Hey LaserJock
[03:10] <Burgundavia> hey LaserJock
[03:40] <LaserJock> hi Burgundavia
[07:07] <Kamping_Kaiser> anyone here part of netday (sp?) in south africa?
[03:46] <bddebian> Heya
[06:13] <capt_kirk> ogra, you around.  possible LTSP bug I wanted to ask you if you've seen before I submit
[06:20] <capt_kirk> for anyone, for both of the Edubuntu LTSP labs I run if the internet is not available, the LTSP server gets very slow and will not let more than two or three clients log on.  As soon as I can get the internet restored, it gets peppy again and lets all 15 clients log on.  Has anyone else seen behavior like this.  It's a problem here in Tanzania, because our internet connection is not reliable.
[06:30] <capt_kirk> sbalneav, you around?
[06:32] <sbalneav> capt_kirk: yes, back from lunch now
[06:33] <capt_kirk> hi, thanks.  I was wondering if any of you have heard of anything like this: for both of the Edubuntu LTSP labs I run if the internet is not available, the LTSP server gets very slow and will not let more than two or three clients log on. As soon as I can get the internet restored, it gets peppy again and lets all 15 clients log on.
[06:33] <capt_kirk> I originally thought I was seeing things, but I've been able to reproduce it over and over on both suites
[06:34] <sbalneav> Never heard of anything like that.  Sounds like either a router issue at your end, or alternatively, some kind of DNS issue, i.e. something not resolving if your internet is down.
[06:35] <sbalneav> However, there's nothing intrinsically in LTSP that depends on the internet being there.
[06:35] <capt_kirk> Our internet connection is not very reliable here in Tanzania, and if it's not there when the server starts up, it will let the first couple of clients log on and then it slows dramatically, and the rest of the clients either get partway through the LTSP client boot or don't get an IP address at all.
[06:36] <capt_kirk> That's what I thought.  I can't find anything in any of the system logs to show why it's slowing down, and top doesn't show anything hogging either the CPU or memory.
[06:37] <capt_kirk> What I can't figure out is why it lets the first couple of clients boot up, but then won't let more boot after that.
[06:37] <sbalneav> One of the things you'll want to check is that the machine's official hostname is in the /etc/hosts file, resolvable to the loopback.
[06:37] <sbalneav> i.e. if the machine's name is "oogabooga", you'll want something like:
[06:38] <sbalneav> 127.0.0.1 oogabooga oogabooga.your.domain.name
[06:38] <capt_kirk> I'm pretty sure it's not a router issue, because I'm just using a switch directly between the server and the clients.
[06:38] <sbalneav> otherwise, if the machine needs to make a DNS lookup to find it's own name, that may slow things down.
[06:38] <capt_kirk> thanks.  I think it's already set up that way, but I'll check.
[06:41] <capt_kirk> so, it's 127.0.0.1 localhost, and 127.0.1.1 library library.mtc.local where library is the host name.
[06:41] <capt_kirk> does it really need to be on 127.0.0.1?  edubuntu put it on 127.0.1.1 by default
[06:42] <capt_kirk> easy enough to switch here, but it would be nice if it defaulted to the better option if it really matters.
[06:43] <sbalneav> That's fine too.
[06:44] <capt_kirk> that's what i thought.  just wanted to make sure.
[06:44] <capt_kirk> it's that way for both labs
[06:44] <sbalneav> 127.x.y.z is all the same.  Netmask for 127 is 255.0.0.0
[06:44] <capt_kirk> that's what I thought. thanks.
[06:45] <capt_kirk> any other thoughts or places to look in logs, debug options, etc
[06:46] <capt_kirk> when the clients cannot get an IP address from DHCP, there's no indication of why DHCP has failed in the logs.  When the internet comes back up, DHCP kicks back in with out a restart and issues addresses.
[06:47] <sbalneav> That will definitely be a DNS issue.
[06:47] <sbalneav> You using the standard dhcpd.conf filename.
[06:47] <capt_kirk> I am running a local DNS server along with squid on another box, so any local names should resolve even without the internet
[06:48] <capt_kirk> yes.  the only thing I've changed in dhcpd.conf is the network address.
[06:50] <capt_kirk> Yeah.  I just rechecked dhcpd.conf, and all is original except the network address
[06:52] <capt_kirk> Why would DNS be causing DHCP to die after the first few leases?
[06:55] <capt_kirk> (brb - have to fix computer for user in lab...  Darn users get in the way of getting any real work done. ;) )
[07:24] <capt_kirk> sbalneav, back.  So here's where it's an LTSP issue (from my end user's point of view - even if it's really something else, it feels like an LTSP issue, because I can't get the thin client to boot).  I can log on and off of the server and the two or three clients that do get all the way through the initial boot.  It seems like once they have a working thin-client kernel loaded, they're...
[07:24] <capt_kirk> ...alright.  But any additional clients can't get past the PXE DHCP request.
[07:24] <capt_kirk> Both suites are "out of the box" Edgy clean installs
[07:25] <capt_kirk> and both produce identical problems.
[07:25] <sbalneav> Anything in /var/log/daemon.log?
[07:25] <capt_kirk> I don't think so, but let me check again.
[07:28] <cliebow_> dumb question..but i assume you have some leases left available?
[07:28] <cliebow_> i have in testng used up all my leases
[07:29] <capt_kirk> sbalneav, nothing unusual during the time that the internet was down this afternoon.  the same dhcp messages as when the internet is up.  no other messages, warning, etc
[07:30] <capt_kirk> cliebow, good question, but yes leases available.  As soon as the internet comes back, whatever is bogging down the PXE-DHCP request issue (also happens with bootp-DHCP) clears up and the thin clients boot up without a hitch.
[07:31] <sbalneav> Where does it fail?   Does it GET the ip address, then fail on the tftp? Or does it fail on the lease itself?
[07:34] <capt_kirk> two different types of failure.  the first few clients to fail actually get a lease and go through most of the boot sequence, but then when they try to start the LTSP client, they error out with a message that says something like "Unable to start job process" and it stays dead on a terminal screen.  Sorry I can't remember the exact wording now, but it doesn't show up on the server logs and I...
[07:34] <capt_kirk> ...didn't write it down.
[07:35] <capt_kirk> The other failure mode is just no IP address at all
[07:35] <sbalneav> Are you at work now? or at home?
[07:36] <capt_kirk> At home, but one of the labs is just 200 meters away.  (The students might get angry if I boot them off now, though.  A lot are writing papers for tomorrow.)
[07:38] <capt_kirk> I'm SSH'd into the server to pull up logs, but I'll have to walk over to the lab to do any actual testing
[07:38] <sbalneav> Assuming it's some kind of a DNS problem, something you could try is to set up a caching DNS server on the local machine, which forwards to your default dns server.  Then, set your /etc/resolv.conf to point to the local dns server, as opposed to the remote one.  You shouldn't NEED to do this, but without looking more closely at your setup, with you there to check on some things, it's the best I can offer at the moment.
[07:38] <capt_kirk> which I'll be happy to do
[07:38] <sbalneav> you're ssh'ed in?
[07:38] <capt_kirk> yes
[07:39] <sbalneav> Can you paste your /etc/ltsp/dhcpd.conf file to the pastebin?
[07:39] <sbalneav> !pastebin
[07:39] <ubotu> pastebin is a service to post large texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu-nl.org (be sure to give the URL of your paste - see also the #ubuntu channel topic)
[07:39] <capt_kirk> sure
[07:43] <capt_kirk> I pasted it.  I think it's http://paste.ubuntu-nl.org/11063/
[07:44] <sbalneav> domain name's mtc.local?
[07:44] <ogra> drop .local everywhere, thats reserved for network manager ...
[07:44] <sbalneav> other than that, it looks pretty bog-standard.
[07:44] <capt_kirk> Yes.  It's just a campus domain, with no outside resolution
[07:44] <capt_kirk> ok
[07:45] <sbalneav> Be interested to see what your resolv.conf looks like
[07:45] <capt_kirk> just sec
[07:46] <capt_kirk> I think I may have figured it out.  The DNS server in dhcpd.conf is the router, not the other box with DNS/squid.  But why would that cause the first few to work, with later ones failing?
[07:47] <sbalneav> Not sure on that one.  Like I say, the whole thing seems a little goofy.
[07:47] <capt_kirk> sorry.  I'm getting too tired.  the dns server listed is the LTSP server, like it was in the default file
[07:48] <sbalneav> is there a dns server on the ltsp box?
[07:48] <capt_kirk> all i changed was the network from x.x.0.x to x.x.200.x
[07:49] <capt_kirk> no, it's on another box on the internet side of the ltsp server (ltsp has two nics. one for clients and one for internet access.)
[07:49] <capt_kirk> ltsp is 192.168.1.2 and dns/squid is 192.168.1.3
[07:49] <capt_kirk> with router to the outside world as 192.168.1.1
[07:52] <capt_kirk> resolv.conf is http://paste.ubuntu-nl.org/11068/
[07:52] <capt_kirk> I'll drop the .local
[08:03] <sbalneav> hmm
[08:04] <sbalneav> got two cards in this machine?
[08:15] <capt_kirk> yes.  two cards.
[08:16] <capt_kirk> 192.168.1.0 is the public-side network and 192.168.200.0 is the ltsp-side of the network.
[08:20] <capt_kirk> gotta get to bed.  dozing off at the computer.  Tommorrow, I'll take .local off of both suites and try artificially testing by unplugging the internet connection.  Thanks for the help so far.
[10:07] <rockprincess> evening y'all!
[10:12] <highvoltage> good evening your majesty!
[10:13] <LaserJock> hi rockprincess and highvoltage
[10:13] <highvoltage> hey LaserJock
[10:13] <rockprincess> hello Laserjock!
[10:14] <rockprincess> hey highvoltage ;)
[10:14] <highvoltage> (poor bed)
[10:14] <rockprincess> hehe me too! but i have a quick question to you guys
[10:14] <cbx33> hey,,,,,
[10:14] <cbx33> i hate migranes
[10:14] <rockprincess> hello pete ;) how come???
[10:15] <rockprincess> why am I not able to have sound on my thin clients?
[10:15] <rockprincess> i have sound on my server though...
[10:16] <cbx33> edgy/dapper?
[10:16] <rockprincess> edgy
[10:16] <cbx33> hmm
[10:16] <cbx33> is edgy sound on by default?
[10:16] <cbx33> nor do i have the brains to think right now
[10:17] <rockprincess> i came across that subject on the edubuntu mailinglist and noticed that i had a similar problem....
[10:17] <rockprincess> Stphane Graber said something like the clients are using ESD? what is ESD?
[10:19] <bddebian> Electro Static Discharge?
[10:20] <bddebian> Oh, you probably mean the Enlightened Sound Daemon :-)
[10:20] <rockprincess> yep, that sounds about right.....any ideas how i could enable sound on my thin clients?
[10:26] <Burgwork> rockprincess: you need to edit lts.conf
[10:26] <Burgwork> basically tell the thin client it can use sound
[10:26] <rockprincess> Burgwork: cool, thanks for the hint! Is there anything particular that I should edit?
[10:27] <Burgwork> yep, finding you the link now for help
[10:27] <Burgwork> http://www.edubuntu.org/GettingStarted
[10:28] <Burgwork> search for sound
[10:28] <rockprincess> Burgwork: cheers, I appreciate your help :) thank you!
[10:28] <Burgwork> no worries
[10:28] <Burgwork> bddebian: having not setup LTSP/Edubuntu is no excuse for not knowing the answers
[10:28] <Burgwork> look at me. I have never installed either LTSP or Edubuntu
[10:29] <ajmitch> morning
[10:29] <Burgwork> morning ajmitch
[10:29] <Amaranth> i've only played with a live cd
[10:29] <rockprincess> haha you guys never disappoint me, you ALWAYS have the answers thank you :)
[10:30] <Amaranth> did any of you get offered sponsorship to go to seville?
[10:30] <Burgwork> offered sponsorship? nope
[10:30] <Burgwork> did you?
[10:30] <Amaranth> Yes and I'm not sure why
[10:30] <ajmitch> because you're involved with bling
[10:30] <Burgwork> indeed
[10:30] <LaserJock> Amaranth: to UDS or UES?
[10:30] <Amaranth> UDS
[10:31] <bddebian> Burgwork: I don't know anything, don't you know that yet? :)
[10:31] <Amaranth> looking for someone else who knows wtf is going on so they can tell me what to do :)
[10:31] <Burgwork> bddebian: you lie in a horrible horrible manner
[10:31] <Burgwork> Amaranth: say yes, then get your password in order
[10:31] <bddebian> Not hardly :'-(
[10:31] <Amaranth> Burgwork: going to do that tomorrow
[10:32] <Burgwork> expect a wait
[10:32] <ajmitch> Burgwork: s/word/port/, I hope
[10:32] <Amaranth> indeed
[10:32] <ajmitch> I think
[10:32] <LaserJock> I got mine for Paris
[10:32] <Amaranth> that's why i'll do it tomorrow, will have over a month
[10:32] <LaserJock> so I'm good to go if I get an email
[10:32] <Burgwork> ajmitch: ?
[10:33] <ajmitch> Burgwork: I have a messy room, but I saw my passport a few days ago
[10:33] <ajmitch> so I know it's in there
[10:33] <Burgwork> ah
[10:33] <Burgwork> mine went through the wash
[10:33] <Burgwork> need to get a new one
[10:33] <ajmitch> ouch
[10:33] <ajmitch> yeah, I've already replaced one for water damage
[10:33] <Burgwork> it was from Mataro anyway, so it needed to be replaced
[10:33] <ajmitch> cost a lot
[10:33] <ajmitch> ah, sevilla, such a long, long way from NZ
[10:35] <Amaranth> acceptance sent
[10:35] <ajmitch> well done
[10:35] <LaserJock> cool
[10:35] <Amaranth> I feel stupid
[10:35] <ajmitch> because you'll sit around for most of the week?
[10:35] <Amaranth> No, because I'm not sure what to do
[10:35] <Amaranth> Or how stupid I sounded in the email
[10:35] <LaserJock> Amaranth: you doing SoC?
[10:35] <ajmitch> about what?
[10:36] <Amaranth> LaserJock: nope
[10:36] <ajmitch> what are you unsure about?
[10:36] <Amaranth> ajmitch: "You are welcome to either make your own arrangements and claim the expense back after the event or use our agents Eyas, dionne@eyas.co.uk."
[10:37] <ajmitch> right
[10:37] <ajmitch> easiest to get their agent book everythign
[10:38] <Amaranth> I expect doing it yourself would take forever to get compensated. :)
[10:38] <LaserJock> yeah, dionne is good
[10:38] <LaserJock> I went with the agents for Paris
[10:38] <ajmitch> probably not that long, but it's annoying to be broke while there
[10:38] <LaserJock> they did a lot of work since it was kinda last minute
[10:38] <LaserJock> and I didn't have to do a thing
[10:38] <ajmitch> still about 7-8 weeks until UDS
[10:39] <ajmitch> at the moment it's blocked on getting time off
[10:40] <Amaranth> beauty of being unemployed :)
[10:40] <ajmitch> hah
[10:40] <ajmitch> what, that you're broke? ;)
[10:40] <Amaranth> no, lots of free time :)
[10:40] <stgraber> rockprincess: You've hilighted me ?
[10:42] <rockprincess> stgraber: oh, yeah actually i just quoted your last email on that rdp and sound matter on the edubuntu mailinglist
[10:42] <Amaranth> LaserJock: so just send them an email?
[10:42] <LaserJock> Amaranth: the agent?
[10:42] <Amaranth> yeah
[10:42] <Amaranth> i mean, not right now
[10:42] <ajmitch> they'll be used to dealing with confused & stunned geeks
[10:42] <Amaranth> haha
[10:42] <ajmitch> first time out of the US?
[10:44] <LaserJock> 2nd time on airplane?
[10:44] <LaserJock> ;-)
[10:45] <LaserJock> Amaranth: yeah, I think you just email them with like what city you'll be flying out of and what day
[10:50] <cbx33> is it keybuk@ubuntu.com ?
[10:50] <ajmitch> scott@ubuntu
[10:51] <ajmitch> hm, if I went to UDS, maybe I could go via singapore :)
[10:51] <ajmitch> fly via the US one way, and via asia when I return :)
[11:01] <rockprincess> good night all, and thanks for your help as always :)
[11:32] <Amaranth> oops, was eating
[11:32] <Amaranth> first time out of US, second time flying, yeah
[11:32] <Burgwork> ogra: you around?
[11:52] <sbalneav> ogra: ping!