IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 12 October 2011   (all times are UTC)

00:16hughessd has left IRC (hughessd!~hughessd@173-164-117-109-Oregon.hfc.comcastbusiness.net, Quit: gone for some reason)
00:17staffencasa has left IRC (staffencasa!~staffenca@128-193-150-235.oregonstate.edu, Ping timeout: 255 seconds)
00:37Parker955_Away is now known as Parker955
00:37loather-work has left IRC (loather-work!~khudson@wsip-98-175-250-115.sd.sd.cox.net, Quit: This computer has gone to sleep)
00:44vagrantc has joined IRC (vagrantc!~vagrant@75.150.46.245)
00:50loather-work has joined IRC (loather-work!~khudson@wsip-98-175-250-115.sd.sd.cox.net)
01:00mgariepy_ has left IRC (mgariepy_!~mgariepy@modemcable045.105-81-70.mc.videotron.ca, Remote host closed the connection)
01:04vagrantc has left IRC (vagrantc!~vagrant@75.150.46.245, Ping timeout: 260 seconds)
01:46loather-work has left IRC (loather-work!~khudson@wsip-98-175-250-115.sd.sd.cox.net, Quit: This computer has gone to sleep)
01:52GodFather has left IRC (GodFather!~rcc@d47-69-227-53.col.wideopenwest.com, Quit: Ex-Chat)
01:57loather-work has joined IRC (loather-work!~khudson@98.175.250.115)
02:11knipwim has left IRC (knipwim!~wim@ip4da83870.direct-adsl.nl, Ping timeout: 252 seconds)
02:14Roasted_ has joined IRC (Roasted_!~jason@c-174-54-213-184.hsd1.pa.comcast.net)
02:20knipwim has joined IRC (knipwim!~wim@ip4da83870.direct-adsl.nl)
02:51Parker955 is now known as Parker955_Away
02:58andygraybeals has left IRC (andygraybeals!~andy@h169.89.213.151.dynamic.ip.windstream.net, Ping timeout: 260 seconds)
03:22Roasted_ has left IRC (Roasted_!~jason@c-174-54-213-184.hsd1.pa.comcast.net, Ping timeout: 248 seconds)
05:23hughessd has joined IRC (hughessd!~hughessd@71-20-34-17.war.clearwire-wmx.net)
05:30loather-work has left IRC (loather-work!~khudson@98.175.250.115, Quit: This computer has gone to sleep)
06:09mistik1 has left IRC (mistik1!mistik1@unaffiliated/mistik1, Ping timeout: 240 seconds)
06:11hughessd has left IRC (hughessd!~hughessd@71-20-34-17.war.clearwire-wmx.net, Quit: gone for some reason)
06:30komunista has joined IRC (komunista!~slavko@adsl-195-168-237-112.dynamic.nextra.sk)
06:41mistik1 has joined IRC (mistik1!mistik1@unaffiliated/mistik1)
07:00mistik1 has left IRC (mistik1!mistik1@unaffiliated/mistik1, Ping timeout: 248 seconds)
07:06mistik1 has joined IRC (mistik1!mistik1@unaffiliated/mistik1)
07:20Steve_the_Pirate has joined IRC (Steve_the_Pirate!~Gary@host86-166-104-72.range86-166.btcentralplus.com)
07:41dobber has joined IRC (dobber!~dobber@213.169.45.222)
08:57FrozenZia has left IRC (FrozenZia!pbrown@shell.paivola.fi, Ping timeout: 252 seconds)
08:57FrozenZia has joined IRC (FrozenZia!~pbrown@shell.paivola.fi)
09:04xsl has joined IRC (xsl!~silence@static-b4-252-232.telepac.pt)
09:31bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
09:39junkY_San has joined IRC (junkY_San!8d251fe1@gateway/web/freenode/ip.141.37.31.225)
09:40
<junkY_San>
hey there
09:41
i've tried to create a custom xsession file for one user through ~/.xsession
09:42
it started once, but i wanted to change it and selected "gnome" at the login manager which also worked. but now the .xsession file is completly ignored
09:45
<Hyperbyte>
What do you want to do with the .xsession?
09:49
<junkY_San>
start firefox
09:59
<Hyperbyte>
For only one user?
10:00
<junkY_San>
yes
10:01
i just found the problem
10:01
the ~/.dmrc file contained session=gnome-failsafe
10:01
i set session=default and it works again
10:01
but the next problem is firefox won't start multiple times on different machines :/
10:19junkY_San has left IRC (junkY_San!8d251fe1@gateway/web/freenode/ip.141.37.31.225, Quit: Page closed)
10:44xsl has left IRC (xsl!~silence@static-b4-252-232.telepac.pt)
10:51xsl has joined IRC (xsl!~silence@static-b4-252-232.telepac.pt)
10:54alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
10:54xsl has left IRC (xsl!~silence@static-b4-252-232.telepac.pt)
11:02xsl has joined IRC (xsl!~silence@static-b4-252-232.telepac.pt)
11:11Trixboxer has joined IRC (Trixboxer!~Trixboxer@office.supportdepartment.net)
11:28Parker955_Away is now known as Parker955
11:42muppis has left IRC (muppis!muppis@viuhka.fi, Quit: Bagpipes from Baghdad)
11:52Parker955 is now known as Parker955_Away
11:52muppis has joined IRC (muppis!muppis@viuhka.fi)
11:57[GuS] has joined IRC ([GuS]!~MysT@200.123.112.224)
11:57[GuS] has joined IRC ([GuS]!~MysT@unaffiliated/gus/x-663402)
12:01ogra_ has left IRC (ogra_!~ogra@80.152.237.3, Excess Flood)
12:03ogra_ has joined IRC (ogra_!~ogra@p5098ed03.dip0.t-ipconnect.de)
12:11brunolambert has joined IRC (brunolambert!~brunolamb@nat/revolutionlinux/x-pdnizgossgamdgaw)
12:22
<mgariepy>
good morning everyone
12:30
<highvoltage>
good morning
12:37fgth has joined IRC (fgth!~fgth@APoitiers-257-1-12-241.w90-38.abo.wanadoo.fr)
12:38
<fgth>
Hi everybody
12:42jason_ has joined IRC (jason_!ada36451@gateway/web/freenode/ip.173.163.100.81)
12:45
<jason_>
hello!
12:47andygraybeals has joined IRC (andygraybeals!~andy@h169.89.213.151.dynamic.ip.windstream.net)
12:55andygraybeal has joined IRC (andygraybeal!~andy.gray@obsidian.casanueva.com)
12:55
<highvoltage>
wow the channel is cheery this morning :D
12:56
ah d'oh, I thought this was #edubuntu :p
12:56
<andygraybeal>
:)
13:02
<jason_>
what's the likely issue if your client is continually sitting at the ubuntu splash screen during boot?
13:02
nothing is showing up in logs but DHCP chatter on occasion
13:02
<alkisg>
!quiet-splash
13:02
<ltsp>
alkisg: quiet-splash: to disable the splash screen in Ubuntu, in order to see any boot error messages, run `sudo gedit /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default` and remove quiet splash .
13:04
<jason_>
Received DHCP NAK is looping
13:04
hmm
13:05jason_ has left IRC (jason_!ada36451@gateway/web/freenode/ip.173.163.100.81, Changing host)
13:05jason_ has joined IRC (jason_!ada36451@unaffiliated/roasted)
13:05jason_ has joined IRC (jason_!ada36451@gateway/web/freenode/ip.173.163.100.81)
13:06
<alkisg>
jason_: look at your server logs, if you don't see why there, look for a second rogue dhcp server in your network
13:06
<jason_>
there is no "network"
13:07
server - to - client
13:07
its the intel server with ppc chroot today
13:07
<fgth>
Anybody's available to help a ltsp newbie in understanding how it works ?
13:09
<alkisg>
!docs
13:09
<ltsp>
alkisg: docs: For the most current documentation, see https://sourceforge.net/apps/mediawiki/ltsp/index.php?title=Ltsp_LtspDocumentationUpstream
13:09
<alkisg>
fgth: there's a fine pdf there that describes the architecture
13:10dead_inside has joined IRC (dead_inside!~dead_insi@76.75.3.174)
13:11
<fgth>
Well it's not really about architecture... Some details :
13:11
I have an Ubuntu-ltsp server (from alternate CD), and a thin client
13:12
the client boot with PXE : all is OK
13:12ogra_ has left IRC (ogra_!~ogra@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 244 seconds)
13:12
<fgth>
Just after install, I had only a console on the thin client, no GUI
13:13ogra_ has joined IRC (ogra_!~ogra@p5098ed03.dip0.t-ipconnect.de)
13:13
<fgth>
On the console I was "in the memory" of the thin client, not on the server.
13:14
Now I install ubuntu-desktop in the chroot. OK, I have a GUI on the thin client. But I'm always "in the memory" of the client...
13:14
How can I have programs running in the memory of the server ??
13:16
<alkisg>
Don't install ubuntu-desktop in the chroot
13:16
Erase that chroot and start from scratch
13:16
And install ubuntu-desktop on your server
13:17
sudo ltsp-build-client is the way to build a chroot without reinstalling your server from the alternate cd
13:18
<fgth>
OK. Ubuntu-desktop is already on the server, it's an ubuntu desktop version, not server
13:18
<alkisg>
(04:12:51 μμ) fgth: Just after install, I had only a console on the thin client, no GUI ==> hmmm then I can't explain that
13:18
Build a new chroot and if it happens again it needs troubleshooting
13:19
<mgariepy>
maybe lts.conf doesn't have screen_07 set ?
13:19
<alkisg>
It shouldn't need an lts.conf at all though...
13:19
<mgariepy>
or the default is ldm on screen_07 ?
13:19
<alkisg>
The alternate CD doesn't provide an lts.conf by default
13:19
Yes, it's the default for ldm
13:20
<fgth>
alkisg: "hmmm then I can't explain that" Really ? I might have a GUI on the thin client directly after install ?
13:20
<alkisg>
You're supposed to, yes
13:21
After installation with the alternate cd you're supposed to be able to directly boot, login, and work on thin clients
13:21
<fgth>
Well. I'll try to re-install in this case... Strange
13:21
<alkisg>
OK, if you hit any problems, don't try random stuff, just ask here for help :)
13:21
<jason_>
I think I screwed up my copy command
13:22
some of my permissions weren't retained
13:22
cp -p -R
13:22
<fgth>
alkisg: ;) thx
13:22
<jason_>
going to run cp -a instead to port the chroot
13:22
<alkisg>
jason_: rsync -a works too, I don't know if cp creates dev nodes?
13:22
<jason_>
alkisg: are dev nodes required for that?
13:23
<alkisg>
ls /opt/ltsp/i386/dev/
13:23
(powerpc for you)
13:23
<jason_>
some guy in another chat told me I should have used cp -rP
13:23
<alkisg>
Don't know, I only know that rsync -a works.
13:26
<jason_>
just curious, if I tarball /var/lib/tftpboot and extract it on the server, would that retain perms too?
13:26
(just for my own sake of knowledge)
13:27
<alkisg>
You'd need to use --numeric-ids, and yes
13:27
<jason_>
with that ls command I see a bunch of files here showing up in yellow text on my term screen
13:27
agpart, audio, audio 1 2 3, console, core, dsp, dsp dsp dsp loop loop loop midi midi midi ram ram ram ram ram rmi rmi rmi smpt tty tty tty
13:27
etc
13:27
<alkisg>
Yes, those are device nodes, I don't know if cp copies them, you'd need to read the man page to be sure
13:28
<jason_>
I'll play it safe and use rsync -a :)
13:28
I'll be sure to notate that too in the wiki if this flies
13:28
I hope it's what's causing my issues, but them being network issues I'm just not sure.
13:29
<alkisg>
How are you copying? over the network?
13:29
<Hyperbyte>
I think cp -a copies them
13:29
<alkisg>
WIth nfs? what?
13:29
<Hyperbyte>
But rsync definitely does it
13:36dberkholz has joined IRC (dberkholz!~dberkholz@gentoo/developer/dberkholz)
13:36
<jason_>
remind me... what folders do I need to port to the other server... just /opt/ltsp/powerpc and /var/lib/tftpboot/, as well as the dhcp config, right?
13:51
<fgth>
Well. I dropped /opt/ltsp and ran ltsp-build-client. /opt/ltsp/i386 was recreated, and the thin client can now connect to the GUI : fine !
13:52
<jason_>
how the flip did rsync -a not work either
13:52
it's still me:me 700
13:53
<alkisg>
(04:29:10 μμ) alkisg: How are you copying? over the network?
13:53
Reading fast is a good skill also, not only typing fast ;)
13:53
<fgth>
Now I've another question : I see all the server resources in the GUI of the client, well. But this server has 2 NIC. Is there a way to show only one NIC (on a private network) to the cleint ? Or am I totally "on the server", and can't hide some resources ?
13:54
<alkisg>
fgth: reading the docs would help you there :) The default setup is with 2 NICs, one dedicated for the clients. But when they login, they *are* on the server, so they can access everything the server can.
13:57
<fgth>
It's that I begin to understand... So if I want that the clients are on a dedicated network, not seeing the other lan connected on the second NIc of the server, I must use fat clients, right ? And in that case programs will be launched in the client memory ? No alternative ?
13:59veloutin_ has joined IRC (veloutin_!~vvinet@nat/revolutionlinux/x-fnkjseqmegsqvjml)
13:59Gadi has joined IRC (Gadi!~romm@ool-4571ca04.dyn.optonline.net)
13:59veloutin_ has left IRC (veloutin_!~vvinet@nat/revolutionlinux/x-fnkjseqmegsqvjml, Remote host closed the connection)
13:59
<alkisg>
fgth: if you want that, you can disable access to the *server* so that it doesn't see the rest of your network
14:00
Or you can set up squid, iptables etc for more fine-tuned filtering
14:00mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Read error: Connection reset by peer)
14:00
<jason_>
wow
14:00
Im stupid
14:00
<alkisg>
With fat clients yes, it's like you say it, they'd access only the private lan and they'd run stuff locally
14:00
<jason_>
I was trying to rsync -a to an NTFS drive and expect it to work
14:00
I'll surely note this in my wiki
14:00
"What NOT to do"
14:00
derp derp
14:02
<fgth>
alkisg: "disable access to the *server*" ? Can you give some details ? Home disabling access if the client is "in the server", using it's memory ?
14:02
An example :
14:03
ifconfig show me the two interfaces in a terminal. Can I hide the second nic and network ?
14:03
<alkisg>
fgth: imagine your server as a normal ubuntu installation, nothing ltsp related
14:04
So your question probably is: "how can I have this pc access the internet but not the lan"?
14:04
Right?
14:04
The answer is, use iptables to drop all the traffic that is directed to your lan
14:04
And only allow traffic to your gateway + the internet
14:04
Then your ltsp clients will also have the same restrictions
14:04
<fgth>
A bit more complex :
14:05
the server is on a lan with its first nic, and the second nic should serve the "ltsp network" with thin clients
14:06
so from the server, we will be able to see the files created by the clients, and, for example, print them
14:06
I try to detail
14:07
<alkisg>
Do you want the clients to be able to access the internet?
14:07
What would happen if you completely disabled your other, non-ltsp-facing NIC?
14:07
How would the clients access the internet?
14:09
You can very easily "hide" that nic; just don't assign an ip to tit
14:09
*it
14:09
But I don't think that's what you want
14:09
<fgth>
alkisg: if I disable the non-ltsp nic, the server is isolated, so it has not access to the lan, and internet (it itself access to the internet via the lan and a router)
14:09
<alkisg>
Right, so that's not what you want
14:10
You want the server to be able to access the internet, but not the lan, correct?
14:10mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy)
14:10
<alkisg>
Do other PCs on your LAN (not ltsp clients) need to access the server?
14:11
<fgth>
:) the server must access to the lan to access internet :/ No the otjer PC don't need that, the "server" is only a ltsp server
14:11
*other*
14:11
Let me try to explain what I see
14:12
and add some important things for the understanding :)
14:13
So : on the center is a router with 3 interfaces. One to internet, one to the lan, on to antoher lan (let's call it DMZ for the moment)
14:13
whouo : "*one to *another lan"
14:14
now the LTSP server has 2 NIC : one on the lan, one on the DMZ
14:14
the thin clients are connected on the DMZ network
14:15
If they have an IP in this network, they can access to the internet directly via the router : no need to "jump" via the LTSP server
14:16
Now, we want on the LTSP server to have access to the files created on the clients, for, as I said, print them for example on printers on the lan.
14:16
But the thin clients must NOT see directly this lan
14:17
ouch. Do you see ? :-!
14:19
<alkisg>
(phone...)
14:22
<fgth>
Ok I'm back in 5 minutes, too
14:29
back
14:31
<Gadi>
fgth: if you share LTSP server print queues to the network, the thin clients will pick them up and you can print directly to them from local applications
14:31
<alkisg>
back too :)
14:32
(05:16:26 μμ) fgth: Now, we want on the LTSP server to have access to the files created on the clients, for, as I said, print them for example on printers on the lan.
14:32
==> the files created on the clients are on the server
14:32
So of course the server will see its own filesystem
14:32
Again: all the ltsp client processes run on the server
14:33
<fgth>
Gadi: why not ?
14:33
<alkisg>
So don't think it like "what the ltsp clients can see on my network and whatnot"
14:33
Think "what my server can see"
14:33
From what I understand, you want your ltsp server to only be able to access the internet and your network printers, nothing else
14:33
That's easily done with iptables or firewall
14:35loather-work has joined IRC (loather-work!~khudson@wsip-98-175-250-115.sd.sd.cox.net)
14:37
<fgth>
alkisg: I see. In this case it don't need two NIC, just specific access via the router to the printers for it, for example.
14:42Ghidorah has joined IRC (Ghidorah!4a7e0f79@gateway/web/freenode/ip.74.126.15.121)
14:42
<fgth>
Now I need to add more informations to my explanations... The thin clients are available for public access. The server is a desktop : a user will work on it, and while checking what the public users do on the clients, he must access to the lan, printers, but also servers, shares, ...
14:42
so :
14:42
<Ghidorah>
Does anyone use syslog to monitor their thin clients?
14:42
I've set SYSLOG_HOST to my syslog server
14:42
but I'm not getting any data on the syslog server
14:43
<fgth>
I can't limit the interface on the LAN side for this computer. In this case, do you think that there is a way to limit the thin client ?
14:45
<alkisg>
fgth: again. When a user works on a thin client, he works on the server
14:45
So whatever limits apply to a user working on your server apply to thin client sessions too
14:46
There's no "limit thin client" concept, as the users work on the server when they're logged on thin clients
14:46
So, you want to limit network access for people working on your server, on a per-user basis?
14:47
<knipwim>
Ghidorah: you have to setup the server syslog to monitor remote log calls
14:48
Ghidorah: I use the following settings (added to your existing ones)
14:48
http://en.gentoo-wiki.com/wiki/LTSP#System_Logging
14:50
<fgth>
alkisg: I begin to understand what it is possible to do... Because thin clients users works on the server, the only way to completely isolate them is to use FAT clients. And maybe NFS to access to a share on the server for centralising the files ?
14:51
<alkisg>
fgth: you could also move the server "behind" another "server" that would do that isolation that you want
14:51
If your clients are not good enough to be fat
14:51
Fat clients use sshfs by default so they work on the server /home
14:51
<Ghidorah>
knipwim: Did you have to do anything else to the thinclient other than SYSLOG_HOST?
14:51
<fgth>
And maybe do what Gadi said : share printers via cups on the server ?
14:51
<alkisg>
Printer sharing with fat clients == checking a box in the server printer propreties
14:52
<Hyperbyte>
Pfff... spent the whole day getting some damned javascript selection menu to work in Firefox, Opera -AND- Internet Explorer 5.
14:52
Why-o-why do I do this to myself....
14:53
<knipwim>
Ghidorah: i didn't even add a syslog host, since i only have one server to do everything
14:54
<fgth>
OK. I believe that have some tests to do :) Thx for this interesting and productive conversation.
14:55
<knipwim>
Ghidorah: you might also need a tcp block in the syslogng conf
14:55
depending on the log program which is used on the client
14:55Steve_the_Pirate has left IRC (Steve_the_Pirate!~Gary@host86-166-104-72.range86-166.btcentralplus.com, Ping timeout: 260 seconds)
14:56andygraybeals has left IRC (andygraybeals!~andy@h169.89.213.151.dynamic.ip.windstream.net, Ping timeout: 259 seconds)
15:09andygraybeals has joined IRC (andygraybeals!~andy@h127.204.213.151.dynamic.ip.windstream.net)
15:12Lumiere has joined IRC (Lumiere!~jstraw@unaffiliated/jstraw)
15:25staffencasa has joined IRC (staffencasa!~staffenca@128-193-150-236.oregonstate.edu)
15:28loather-work has left IRC (loather-work!~khudson@wsip-98-175-250-115.sd.sd.cox.net, Quit: This computer has gone to sleep)
15:28
<jason_>
damn
15:28
ported the chroot over again
15:28
this time retaining permissions
15:28
updated network settings, dhcp service, ssh keys, image
15:28
still looping @ DHCPNAK
15:32
hmm, lease unavaialble...
15:38vagrantc has joined IRC (vagrantc!~vagrant@c-76-105-252-50.hsd1.or.comcast.net)
15:38dobber has left IRC (dobber!~dobber@213.169.45.222, Remote host closed the connection)
15:42fgth has left IRC (fgth!~fgth@APoitiers-257-1-12-241.w90-38.abo.wanadoo.fr)
15:46komunista has left IRC (komunista!~slavko@adsl-195-168-237-112.dynamic.nextra.sk, Quit: Leaving.)
15:47usuario has joined IRC (usuario!~usuario@189.161.117.226)
16:12Steve_the_Pirate has joined IRC (Steve_the_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com)
16:13hughessd has joined IRC (hughessd!~hughessd@173-164-117-109-Oregon.hfc.comcastbusiness.net)
16:13jason_ has left IRC (jason_!ada36451@gateway/web/freenode/ip.173.163.100.81, Ping timeout: 251 seconds)
16:23vagrantc has left IRC (vagrantc!~vagrant@c-76-105-252-50.hsd1.or.comcast.net, Ping timeout: 276 seconds)
16:29loather-work has joined IRC (loather-work!~khudson@adsl-75-60-103-58.dsl.sndg02.sbcglobal.net)
16:35abeehc has left IRC (abeehc!~bob@2001:1938:1a3:0:216:41ff:fe2c:9b3c, Read error: Operation timed out)
17:13[GuS] has left IRC ([GuS]!~MysT@unaffiliated/gus/x-663402, Remote host closed the connection)
17:14khildin has joined IRC (khildin!~robb@ip166-155-209-87.adsl2.static.versatel.nl)
17:14khildin is now known as khildin_away
17:14khildin_away is now known as khildin
17:15abeehc has joined IRC (abeehc!~bob@2001:1938:1a3:0:216:41ff:fe2c:9b3c)
17:15mikkel has joined IRC (mikkel!~mikkel@80-71-132-15.u.parknet.dk)
17:25Steve_the_Pirate has left IRC (Steve_the_Pirate!~Gary@cpc16-haye17-2-0-cust169.haye.cable.virginmedia.com, Quit: Leaving)
17:35khildin has left IRC (khildin!~robb@ip166-155-209-87.adsl2.static.versatel.nl, Ping timeout: 260 seconds)
17:41andygraybeals_ has joined IRC (andygraybeals_!~andy@h214.212.22.98.dynamic.ip.windstream.net)
17:41andygraybeals has left IRC (andygraybeals!~andy@h127.204.213.151.dynamic.ip.windstream.net, Ping timeout: 240 seconds)
17:45komunista has joined IRC (komunista!~slavko@adsl-195-168-237-112.dynamic.nextra.sk)
17:54vagrantc has joined IRC (vagrantc!~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net)
18:28pscheie has left IRC (pscheie!~pscheie@74-95-141-141-Minnesota.hfc.comcastbusiness.net, Quit: Leaving)
18:35khildin_away has joined IRC (khildin_away!~robb@ip166-155-209-87.adsl2.static.versatel.nl)
18:35khildin_away is now known as khildin
18:38pscheie has joined IRC (pscheie!~pscheie@74-95-141-141-Minnesota.hfc.comcastbusiness.net)
18:40khildin has left IRC (khildin!~robb@ip166-155-209-87.adsl2.static.versatel.nl, Ping timeout: 245 seconds)
18:48Parker955_Away is now known as Parker955
18:52loather-work has left IRC (loather-work!~khudson@adsl-75-60-103-58.dsl.sndg02.sbcglobal.net, Quit: This computer has gone to sleep)
19:16usuario has left IRC (usuario!~usuario@189.161.117.226, Ping timeout: 248 seconds)
19:18khildin has joined IRC (khildin!~robb@ip166-155-209-87.adsl2.static.versatel.nl)
19:23khildin has left IRC (khildin!~robb@ip166-155-209-87.adsl2.static.versatel.nl, Ping timeout: 252 seconds)
19:25khildin has joined IRC (khildin!~robb@ip166-155-209-87.adsl2.static.versatel.nl)
19:30nubae has joined IRC (nubae!~nubae@opensuse/member/nubae)
19:31khildin has left IRC (khildin!~robb@ip166-155-209-87.adsl2.static.versatel.nl, Ping timeout: 245 seconds)
19:33Ghidorah has left IRC (Ghidorah!4a7e0f79@gateway/web/freenode/ip.74.126.15.121, Ping timeout: 252 seconds)
19:42pscheie has left IRC (pscheie!~pscheie@74-95-141-141-Minnesota.hfc.comcastbusiness.net, Remote host closed the connection)
19:50khildin has joined IRC (khildin!~robb@ip166-155-209-87.adsl2.static.versatel.nl)
19:51hughessd has left IRC (hughessd!~hughessd@173-164-117-109-Oregon.hfc.comcastbusiness.net, Quit: gone for some reason)
19:54jason_ has joined IRC (jason_!ada36451@gateway/web/freenode/ip.173.163.100.81)
19:54
<jason_>
hey guys. still having continual DHCP Ack issues with booting my clients. Question. Would it cause a problem if I'm using a 10.04 chroot on a 11.04 system?
19:55khildin has left IRC (khildin!~robb@ip166-155-209-87.adsl2.static.versatel.nl, Ping timeout: 252 seconds)
19:56
<alkisg>
jason_: no, it should work. A dhcp problem is even unrelated to if you have a chroot or not.
19:56
<jason_>
k, just wanted to make sure
19:56
going to run wireshark quick and see what's up
19:56
<alkisg>
jason_: which dhcp server are you using? isc-dhcp?
19:56
<jason_>
ALL I can see in syslog and the client boot screen w/o quiet-splash is the DHCP Ack. nothing more.
19:56
yes isc
19:57
11.04 system
19:57
<alkisg>
First, to make sure that this is you only problem:
19:57
!ipappend
19:57
<ltsp>
alkisg: Error: "ipappend" is not a valid command.
19:57
<alkisg>
Ah no
19:57
You're getting a dhcp NAK in pxe, right?
19:58
<jason_>
ubuntu-ltsp01 dhcpd: DHCPNAK on 192.168.100.20 to 00:0a:95:81:74:17 via eth0
19:58
I'm sorry
19:58
I said that wrong
19:58
<alkisg>
Sorry, in initramfs, ok, let me write a factoid for that..
19:59
!learn ipappend as to temporarily solve DHCP problems in the initramfs, try putting IPAPPEND 3 as the last line of /var/lib/tftpboot/ltsp/i386/pxelinux.cfg. You might also need to specify nbdroot=server-ip:2000 in the kernel command line.
19:59
<ltsp>
alkisg: The operation succeeded.
19:59khildin has joined IRC (khildin!~robb@ip166-155-209-87.adsl2.static.versatel.nl)
19:59
<alkisg>
OK, try that ^
20:00
<jason_>
wait
20:00
wait wait wait
20:00
I may have screwed something up
20:00komunista has left IRC (komunista!~slavko@adsl-195-168-237-112.dynamic.nextra.sk, Quit: Leaving.)
20:00
<jason_>
alkisg: when I went back into the configs to troubleshoot I was comparing the contents of certain files.
20:00
one of the files was the tftp file
20:01
where I removed the "quiet splash" entry
20:01
on the G4 server, there was also something about an NBD port
20:01
er
20:01
on the Intel server, there was something about an NBD port
20:01
on the G4 server, there was not
20:01
so I removed it as part of making it match the G4 setup
20:01
maybe tat's why
20:02
<alkisg>
Ah sorry
20:02
You don't even use pxelinux
20:02
<jason_>
yeah
20:02
<alkisg>
You're using yaboot
20:02
<jason_>
but seeing the nbdroot=server-ip:2000 made me think
20:02
because I think it said something about NBD Port - 2000 in there
20:02
that I deleted
20:02
gahhh...
20:02
<alkisg>
No, that shouldn't matter
20:02
<jason_>
oh?
20:02
<alkisg>
NBD comes later on
20:02
Pastebin your dhcpd.conf
20:03
<jason_>
pastebin.com/wvj1eT0N
20:04
www.pastebin.com/wvj1eT0N
20:07
<alkisg>
jason_: does yaboot.conf contain kernel parameters? can you pastebin it?
20:08
<jason_>
www.pastebin.com/tsCZqMUX
20:08
I actually DO have the nbd2000 in there
20:08
I th ought it was tftp but here its yaboot
20:12
<alkisg>
append="quiet splash nbdport=2000 ip=192.168.100.20:192.168.100.1:192.168.100.1:255.255.255.0:ltsp20:eth0:none"
20:12
jason_: try this in your yaboot.conf ^
20:13
Completely temporary, just to verify that you only have a dhcp problem
20:13
Also remove quiet splash if you want :)
20:13Mava has left IRC (Mava!~Mava@a91-154-45-40.elisa-laajakaista.fi, Ping timeout: 240 seconds)
20:14loather-work has joined IRC (loather-work!~khudson@adsl-75-60-103-58.dsl.sndg02.sbcglobal.net)
20:15Gadi has left IRC (Gadi!~romm@ool-4571ca04.dyn.optonline.net, Read error: Connection reset by peer)
20:16
<jason_>
alkisg: failed right away @ failed to connect to NBD server. sitting at iniramfs now.
20:16
<alkisg>
Cool
20:16
That means it got the ip and tried to connect
20:16
Now try manually connecting to your server
20:16
<jason_>
..how?
20:16
<alkisg>
nbd-client 192.168.100.1 2000 /dev/nbd0
20:17
That's your ltsp server IP, right?
20:17
<jason_>
100.1, yes
20:17Gadi has joined IRC (Gadi!~romm@ool-4571ca04.dyn.optonline.net)
20:17
<alkisg>
OK, what's the result from that command?
20:18
<jason_>
no such file or dir
20:19
<alkisg>
In your client initramfs
20:19
Not on your server
20:19
<jason_>
I did
20:19khildin has left IRC (khildin!~robb@ip166-155-209-87.adsl2.static.versatel.nl, Ping timeout: 276 seconds)
20:19
<jason_>
wait
20:19
sec
20:20
nbd vs ndb
20:20
not the same :P
20:20
connection refused
20:20Mava has joined IRC (Mava!~Mava@a91-154-45-40.elisa-laajakaista.fi)
20:20
<alkisg>
OK, so you have an nbd problem on your server now
20:20
On the server, netstat -nap|grep :2000
20:23
<jason_>
nothing happens
20:23
just returns back to the prompt
20:23
<alkisg>
grep nbd /etc/inetd.conf
20:24
<jason_>
9572 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/nbdswapd
20:24
<alkisg>
No nbd port there
20:24
sudo ltsp-update-image --force
20:24
Ah no
20:24
Did you do it?
20:25
I'm not sure if 11.04 uses inetd or nbd-server, probably still inetd but not sure
20:26khildin has joined IRC (khildin!~robb@ip166-155-209-87.adsl2.static.versatel.nl)
20:26
<jason_>
yeah I'm not sure either. No I didnt do update-image --force
20:27
wonder what I did wrong :/
20:27
<alkisg>
Check if there's an /etc/nbd-server dir, and if it has anything there
20:27
<jason_>
yes
20:27
nbd-server
20:27
in etc
20:27
its empty though
20:28
<alkisg>
Put this in inetd.conf: 2000 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/nbdrootd /opt/ltsp/images/powerpc.img
20:28
Check if the last file (powerpc.img) exists
20:29
<jason_>
yes it exists
20:29
where is inetd.conf
20:30
<alkisg>
/etc/inetd.conf, the one you grepped for nbd just before
20:33
<jason_>
reboot any services?
20:33
or just reboot the client?
20:34
<alkisg>
sudo service openbsd-inetd restart
20:34
And then try nbd-client 192..... on the initramfs again
20:35khildin has left IRC (khildin!~robb@ip166-155-209-87.adsl2.static.versatel.nl, Ping timeout: 240 seconds)
20:35
<jason_>
negotiation ..size = 541520b
20:35
bs 1024, sz 541520
20:36
<alkisg>
Cool, reboot the client
20:36
<jason_>
alkisg: is that something I did wrong?
20:36
or is this something a powerpc chroot needs that wasnt auto generated?
20:36
<alkisg>
I think that ltsp-build-client puts that line in inetd.conf, and you of course didn't run it on your i386 server
20:36
So put that on your notes too
20:37
Or, ltsp-update-image --force
20:37
That would also put it automatically, but it would overwrite your yaboot.conf and we didn't want that
20:37
<jason_>
alkisg: why are you
20:37
so
20:37
damn
20:37
smart
20:37
<alkisg>
As you have the static ip there because of your dhcp problem
20:37
:)
20:37
<jason_>
SERIOUSLY
20:37
stop being a genius
20:37
like. wow. how the hell else would I have known to do this
20:37
<alkisg>
I'm trying hard, but I'm too damn to do it :(
20:38
<jason_>
oh wait. I would never. ever. EVER have figured it out
20:38
and I never put things down. I'm always working on SOMETHING. If anything, I'm doing too much at once at any given point in the day.
20:38
and even considering that
20:38
I would have never figured that out
20:38
<alkisg>
*dumb
20:38
<jason_>
that linet hat you told me to add
20:38
<alkisg>
Meh my english fail me a lot recently
20:38
<jason_>
would it apply to pretty much anybody?
20:39
<alkisg>
In 10.04-11.04
20:39
<jason_>
like if a random joe shmoe from alaska tried to duplicate my setup he would run into that same issue?
20:39
<alkisg>
In 11.10 it's a different story
20:39
<jason_>
what's changing in 11.10?
20:39
for better or worse?
20:39
<alkisg>
nbd-server is no longed launched from inetd
20:39
So anyway, you still have the dhcp problem
20:39
<jason_>
I do?
20:39
<alkisg>
What we did now is force a static IP to a single client
20:39
<jason_>
I'm at the login screen on the client
20:39
oh
20:40
gotcha...
20:40
<alkisg>
Not helpful for many clients... :)
20:40
<jason_>
very true...
20:40
should I try DHCP now?
20:40
<alkisg>
It won't make a difference, we just solved the nbd problem and made sure that your problem is indeed dhcp related
20:40
Yes, revert yaboot.conf as it was
20:41
Then reboot, and pastebin the dhcp parts from your syslog
20:41
(reboot the client)
20:42
<jason_>
so let's say I'm setting up a 11.10 server
20:42
would that entire step just not be needed?
20:42
would it work on the fly?
20:43
<alkisg>
You'd need to not do that step, but edit /etc/nbd-server/config instead
20:43
<jason_>
www.pastebin.com/bEP3PskT
20:43
would I use the exact same config line?
20:44
<alkisg>
No, a completely different section
20:44
<jason_>
k
20:44
I cancelled the syslog because it just loops
20:44
you can see 4-5 repeated sections
20:45
<alkisg>
I assume that the problem is that dhcp3-server thinks that the second request comes from a different client
20:45
Because the client sends a different id on pxe vs on initramfs
20:46
You could try another dhcp server like dnsmasq, or you could try to find some setting in dhcpd.conf that would make it understand it's the same client
20:47
<jason_>
alkisg: dumb question
20:47
and I have good reason for asking this
20:47
if I reinstall Ubuntu, is it likely I'll run into this same issue again?
20:47
because I didnt have a 64 bit server available, and one is coming to me soon
20:47
meanwhile I wanted to just launch this 32 bit server for the heck of it
20:48
I hate to waste time on it if a new install is likely to not even have this issue whatsoever
20:48
<alkisg>
I'm guessing it will
20:48
<jason_>
it will... come back?
20:48
or not show itself?
20:49
<alkisg>
I think that you'll have exactly the same problem, with exactly the same solution
20:49
<jason_>
so this isn't something I caused?
20:49
because when I set up this server, I was screwing with network settings a lot
20:49
mostly because it had 2 NICs
20:49
and I didnt know which NIC was which
20:50
most servers I set up, Linux has assigned them as eth0 eth1 eth2 eth3 beginning from the left
20:50
this one was backwards, whcih threw me through a loop
20:50
so I did a lot of network config in the interface file but nothing too much more than that
20:50
I had wiped the 70.network.rules or whatever it was and rebooted so it re-generated itself
20:51
<alkisg>
I don't think your network fiddling had anything to do with the problem
20:51
Try removing "autoritative", maybe it'll help
20:51
And restart your dhcp3-server
20:51
<jason_>
wait
20:51
what hte hell
20:51
I have two scopes
20:52
www.pastebin.com/8Aeav9pk
20:52
<alkisg>
Yes but the first one is ignored
20:52
As you don't have an ip in that range
20:52
<jason_>
oh
20:52
damn I thought that was it
20:52
<alkisg>
Remove it to be sure
20:53
I thought you deliberately put it theere
20:53
<jason_>
oh no. I had no idea it was there.
20:54
Im using a super tiny monitor on this server so I probably missed it entirely
20:54
it was probably there as part of the default and I never axed it
20:54
ah made no difference
20:54
dangit
20:54
I'm really pushing time too...
20:54
I should be going. :(
20:55
thanks alkisg, I'll tackle it more next time
20:55
<alkisg>
bb
20:55ACSpike[Work] has joined IRC (ACSpike[Work]!~ACSpike@75-146-170-85-Minnesota.hfc.comcastbusiness.net)
20:59jason_ has left IRC (jason_!ada36451@gateway/web/freenode/ip.173.163.100.81, Ping timeout: 252 seconds)
21:13vagrantc has left IRC (vagrantc!~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net, Ping timeout: 244 seconds)
21:20brunolambert has left IRC (brunolambert!~brunolamb@nat/revolutionlinux/x-pdnizgossgamdgaw, Quit: brunolambert)
21:30mikkel has left IRC (mikkel!~mikkel@80-71-132-15.u.parknet.dk, Quit: Leaving)
21:30mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, Quit: Leaving)
21:33ACSpike[Work] has left IRC (ACSpike[Work]!~ACSpike@75-146-170-85-Minnesota.hfc.comcastbusiness.net)
22:03Gadi has left IRC (Gadi!~romm@ool-4571ca04.dyn.optonline.net)
22:03dead_inside has left IRC (dead_inside!~dead_insi@76.75.3.174, Quit: Leaving...)
22:07mgariepy has joined IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy)
22:16vagrantc has joined IRC (vagrantc!~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net)
22:19loathing has joined IRC (loathing!~khudson@68-25-27-54.pools.static.spcsdns.net)
22:22loather-work has left IRC (loather-work!~khudson@adsl-75-60-103-58.dsl.sndg02.sbcglobal.net, Ping timeout: 255 seconds)
22:22Phantomas has joined IRC (Phantomas!~Phantomas@unaffiliated/phantomas)
22:25hughessd has joined IRC (hughessd!~hughessd@173-164-117-109-Oregon.hfc.comcastbusiness.net)
22:37
<alkisg>
vagrantc: hi, we've internationalized sch-scripts (the italc-like app we use here - and changed the name to "epoptes") and in the next months it'll be in a good shape for mass use. Would you be interested in sponsoring it for Debian, of course if you deem it worthy?
22:37
It works on both ltsp clients and non-ltsp clients
22:38
(classroom management, monitoring, remote control, command execution etc, if you haven't heard of italc)
22:38
python + gtk + shell
22:38
Looks like this, more or less: http://wiki.ubuntu-gr.org/sch-scripts/screenshots?action=AttachFile&do=get&target=sch-scripts.png
22:39
<vagrantc>
alkisg: might be interested, sure!
22:39
<alkisg>
Cool, I'll surely do a demo at BTS then if you guys want :)
22:52Trixboxer has left IRC (Trixboxer!~Trixboxer@office.supportdepartment.net, Quit: "Achievement is not the end, its the beginning of new journey !!!")
22:53loathing has left IRC (loathing!~khudson@68-25-27-54.pools.static.spcsdns.net, Ping timeout: 252 seconds)
22:57bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 252 seconds)
22:58vagrantc has left IRC (vagrantc!~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net, Ping timeout: 260 seconds)
23:00
<alkisg>
Goodnight all
23:00alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
23:00vagrantc has joined IRC (vagrantc!~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net)
23:28Roasted has joined IRC (Roasted!~jason@unaffiliated/roasted)
23:37Roasted has left IRC (Roasted!~jason@unaffiliated/roasted, Remote host closed the connection)
23:50Phantomas has left IRC (Phantomas!~Phantomas@unaffiliated/phantomas, Ping timeout: 256 seconds)