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


Channel log from 17 August 2010   (all times are UTC)

00:06dobber has joined #ltsp
00:25Raed23 has joined #ltsp
00:25Raed23 has left #ltsp
00:59ltspbot has joined #ltsp
01:23irule has quit IRC
01:34alexqwesa has quit IRC
01:35alexqwesa has joined #ltsp
01:40gnunux has joined #ltsp
01:41
<gnunux>
hi
01:58poff has joined #ltsp
02:06alkisg has joined #ltsp
02:15sweetpi has quit IRC
02:27poff has quit IRC
02:32mistik1 has quit IRC
02:38mistik1 has joined #ltsp
02:42biomorph has joined #ltsp
02:43mistik1 has quit IRC
02:43mistik1 has joined #ltsp
03:00mikkel has joined #ltsp
03:18Da-Geek has joined #ltsp
03:23bobby_C has joined #ltsp
03:25F-GT has quit IRC
03:42F-GT has joined #ltsp
03:51bobby_C has quit IRC
03:52biomorph has quit IRC
03:53Selveste1__ has quit IRC
03:53Selveste1__ has joined #ltsp
03:58pasmen has joined #ltsp
04:08bobby_C has joined #ltsp
04:32intelliant has joined #ltsp
04:33
<intelliant>
Hi!
04:33
Facing some wierd behaviour in authenticating against ldap
04:42
<Appiah>
:)
04:48
<intelliant>
Appiah: good to fined you here
04:48
*find
04:49
Appiah: it is allowing one user to login and none others while authenticating against ldap
04:50
it is the same config I was speaking about a few days back
04:50
I got around working with it today only
04:51alkisg has quit IRC
04:52
<intelliant>
this is what authlog has to say - http://pastebin.com/MJjWUSy2
04:53
something wrong with dbus
04:53
i confess I am unble to understand a word in there
04:55IceDreK has joined #ltsp
05:04IceDreK has quit IRC
05:06
<intelliant>
cyberorg: there?
05:11alkisg has joined #ltsp
05:15dlezcano has quit IRC
05:23
<intelliant>
okay, found something here - https://answers.launchpad.net/ltsp/+question/115286
05:25
<alkisg>
I don't think the person in that launchpad question is using LDAP...
05:25
He's just having ssh keys problems
05:26
(or maybe compiz problems)
05:31pasmen has quit IRC
05:35
<Appiah>
intelliant: well it auths
05:35
so not a prob there
05:35
<intelliant>
alkisg: you may be right. just verifying the scenario at my end as coincidentally the one who cud log in is on a 64-bit machine
05:36
but anyways there is only a single i386.img to boot from
05:36
Appiah: yes auth is working fine
05:36
looks something after that
05:37
the only thin-client which logged in and loaded the desktop successfully is different from all the others
05:37
just doing another round of tests
05:37
brb with the results
05:43alkisg has quit IRC
05:45
<intelliant>
tried with other thin-clients also
05:45
only a particular user is being allowed to login and none other from any TC
05:49
so it can't be a driver issue as well
05:50
<cyberorg>
intelliant, hi :)
05:56loathsome has quit IRC
05:56Faithful has quit IRC
05:58loathsome has joined #ltsp
06:03
<intelliant>
cyberorg: kinda lost - http://ubuntuforums.org/archive/index.php/t-1375510.html
06:04
<cyberorg>
great, good luck :)
06:06
try re/moving compiz from the server
06:06
also use LTSP_DEBUG_TERMINAL to debug
06:09alkisg has joined #ltsp
06:10
<intelliant>
but this issue does not look like a driver issue and nor a compiz issue
06:10
then how would it allow one user and none other?
06:10
<alkisg>
!compiz
06:10
<ltspbot>
alkisg: "compiz" :: if compiz is giving you problems, one way to disable it for all users is: sudo gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type string --set /desktop/gnome/session/required_components/windowmanager metacity
06:12
<cyberorg>
intelliant, first step is to be absolutely sure that is not the issue so move/disable/remove it
06:12alkisg1 has joined #ltsp
06:13
<alkisg1>
to disable compiz, sudo gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type string --set /desktop/gnome/session/required_components/windowmanager metacity
06:13
Ah, I thought the bot was down, but it was me, I got disconnected :)
06:15pmatulis has joined #ltsp
06:15alkisg has quit IRC
06:15alkisg1 is now known as alkisg
06:19
<intelliant>
executed this - " sudo gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type string --set /desktop/gnome/session/required_components/windowmanager metacity "
06:24
it worked :)
06:24
<alkisg>
A compiz problem, then :)
06:24
<intelliant>
cyberorg: alkisg: Appiah: thanks
06:25
yes confirmed
06:26
<cyberorg>
compiz wrapper script should have taken care of starting another WM instead of session crashing
06:30
<Appiah>
so you disabled compiz and it started working?
06:32
<intelliant>
Appiah: yes
06:33
so 2 stage problems solved - 1. ldap connectivity issue 2. problem caused due to compiz
06:33
but yet i don't know why it was allowing only one user(the same one) which was not necessarily the first one to login
06:35
<alkisg>
That user had "None" selected in the appearance settings
06:39
<cyberorg>
intelliant, reply to the forum thread/bug reports so others searching find the solution
06:40
<intelliant>
doing so
06:40
:)
06:48
http://ubuntuforums.org/showthread.php?p=9729614#post9729614
06:54[GuS] has joined #ltsp
07:02GodFather has joined #ltsp
07:04alkisg has quit IRC
07:05ThE-RiX has joined #ltsp
07:09RiXtEr has quit IRC
07:09RiXtEr has joined #ltsp
07:12ThE-RiX has quit IRC
07:35Selveste1__ has quit IRC
07:35Selveste1___ has joined #ltsp
07:59
<_UsUrPeR_>
Has anybody had problems with 10.04 LTSP clients logging themselves out back to LDM?
08:00
I am having problems where clients log themselves out to LDM, then after logging back in, localapps do not work, and I cannot open a shell on another terminal.
08:00
stranger still, after a client reboot, I am still having the same problem.
08:00
any suggestions would be appreciated.
08:05
<Appiah>
when do they log out to ldm?
08:05
checked /var/log/messages ?
08:06
<_UsUrPeR_>
/var/log/messages on the server or client?
08:07
Appiah: hmm. here's the /var/log/messages http://pastebin.com/ULD46Wcx
08:08
though none of that appears to be relevant. KVMBR0 is the bridge that I am using for access to this server though...
08:09
<Appiah>
thats the server log right?
08:09
<_UsUrPeR_>
correct
08:09
I cannot access the client log because I cannot open a shell or localapps
08:09
<Appiah>
ssh then?
08:10
<_UsUrPeR_>
yeah, I just installed openssh on the chroot
08:10
lemme try that
08:12
hmm. ssh is not working either. It just stops responding after I enter a password for root
08:12mikkel has quit IRC
08:13
<_UsUrPeR_>
I have rebooted the client multiple times now. At first I thought it was a RAM issue on the client, but the longer this goes on, I am starting to think it's the server.
08:18
hmm
08:18
something interesting from daemon.log http://pastebin.com/spam.php?i=iVNhzfv9]
08:18
err http://pastebin.com/spam.php?i=iVNhzfv9
08:21Blinny has joined #ltsp
08:21
<Blinny>
All my PS/2 mice aren't working this morning. FUN.
08:25
<_UsUrPeR_>
:/
08:26
another strange thing: if I boot a second client, it works fine. It can open a shell on the second terminal, and can run localapps.
08:27
and now the first client works as well after restarting nbd-server
08:34
<pmatulis>
why do i get a high pitch sound when booting my laptops (tried 2) with my lucid ltsp server? :)
08:34
<_UsUrPeR_>
pmatulis: is it coming from the speakers?
08:36
<pmatulis>
_UsUrPeR_: it appears to be mic/speaker feedback
08:36
<_UsUrPeR_>
do the following: open a terminal on your laptop "client". Run "ltsp-localapps xterm". In there, type "alsamixer". I'd bet you there is a volume gain set super high.
08:38
<pmatulis>
_UsUrPeR_: thing is, it's never happened before (jaunty, karmic), now, with this (not very much used) lucid rig i have 2 laptops seeing this
08:39
<_UsUrPeR_>
hmm
08:39
<pmatulis>
_UsUrPeR_: also, i get this at the login screen, no login yet
08:40
<intelliant>
for ltsp-cluster what are the steps one needs to do whenever adding a new node ?
08:40
<_UsUrPeR_>
intelliant: node = appserve? Like adding another server to the cluster?
08:41
pmatulis: does the sound remain after login?
08:42
intelliant: I'm checking some notes I have from 9.10, but it looks like you need to add a line to /etc/ltsp/lbsconfig.xml
08:43
<intelliant>
yes
08:43
<_UsUrPeR_>
intelliant: in there, below the nodes listed, add the next node. Also, increment the "max threads" by 1
08:43
<pmatulis>
_UsUrPeR_: i didn't try
08:43
<intelliant>
you mean on root server
08:43
?
08:44
<_UsUrPeR_>
intelliant: correct. on the root server.
08:44
pmatulis: give that a shot. see if it's just a volume change
08:45
<pmatulis>
_UsUrPeR_: ok, need to find an isolated room, will report back
08:45
<_UsUrPeR_>
k
08:46
<intelliant>
_UsUrPeR_: and then do I need to restart anything?
08:47
<_UsUrPeR_>
intelliant: I don't recall having to restart anything... in /etc/init.d/ is there anything for lbserver or ltsp-lbserver?
08:47
if there is, you will probably need to restart those processes
08:47
it may be ltsp-cluster-lbserver
08:48alkisg has joined #ltsp
08:49bobby_C has quit IRC
08:53mikkel has joined #ltsp
08:56
<intelliant>
reloaded the service
09:04F-GT has quit IRC
09:08
<intelliant>
it seemed to have worked
09:08
stuck with some other issues before I can confirm this 100%
09:14Blinny has quit IRC
09:17dgroos has joined #ltsp
09:20F-GT has joined #ltsp
09:22Blinny has joined #ltsp
09:29
<dgroos>
ping alkisg
09:56ltspbot` has joined #ltsp
09:56-brown.freenode.net- [freenode-info] help freenode weed out clonebots -- please register your IRC nick and auto-identify: http://freenode.net/faq.shtml#nicksetup
09:57ltspbot has quit IRC
10:18Da-Geek has quit IRC
10:25gnunux has quit IRC
10:25GodFather has quit IRC
10:30staffencasa has joined #ltsp
10:33dobber has quit IRC
11:05intelliant has left #ltsp
11:05intelliant has joined #ltsp
11:05
<intelliant>
Yes the node addition method worked
11:05
bfn
11:05intelliant has left #ltsp
11:16
<_UsUrPeR_>
ok
11:17
I have come up with another crash, but this time I am able to check the log files on my client
11:17
in syslog, it's got the following errors
11:17
nbd9: unknown partition table
11:17
nbd9: NBD_DISCONNECT
11:17
nbd9: receive control failed (result -32)
11:18
nbd9: queue cleared
11:23migue has joined #ltsp
11:24
<migue>
hi
11:25
i have a question about ltsp+pcmcia nic
11:26
could be ltsp floppy boot on a laptop with a pcmcia card?
11:29dgroos1 has left #ltsp
11:34jhutchins_lt has joined #ltsp
11:35atomic007za has joined #ltsp
11:35
<atomic007za>
hi
11:36
I just purchased a Intel nic and have disable flow control with the example given on https://help.ubuntu.com/community/UbuntuLTSP/FlowControl#Disabling flow control on the switch
11:36
and when I boot my clients they are still slow
11:36
any ideas?
11:40
<alkisg>
measure the bandwidth with netperf or iperf
11:44
<migue>
naybody know about ltsp and pcmcia card?
11:44
*anybody
11:47jhutchins_lt has quit IRC
11:48
<johnny>
migue, what specs does such a laptop have?
11:49
is it even powerful enough to be an ltsp client?
11:50
why would you want to involve a floppy?
11:50
you can use gpxe from a floppy if your network card doesn't have pxe
11:50
but for a laptop not to have built in pxe, it must be pretty old
11:55dgroos1 has joined #ltsp
11:55
<atomic007za>
Hi Alkisg, I have done that not sure if I am doing anything wrong but here is the output
11:55
http://pastebin.com/rzUw9ZvD
11:55
does not look like examples
11:56
<alkisg>
what command line do you use? which parameters?
11:56
You're supposed to install it to the chroot, update the image, and then run `netperf server <more parameters>` from the client SCREEN_01...
11:56
<atomic007za>
netperf
11:57
<alkisg>
Or iperf, whichever you like...
11:57
<atomic007za>
there is an example thethas a result if that is typed
11:57
<alkisg>
I wrote an example at https://help.ubuntu.com/community/UbuntuLTSP/Trunking
12:01
<atomic007za>
thx, I get this http://pastebin.com/ParRq6zG
12:02
wait
12:03cellofellow has joined #ltsp
12:03
<atomic007za>
yes same relsult
12:04
<cellofellow>
I think I've done something wrong. I've attempted to set up an LTSP fat-client system from these instructions https://help.ubuntu.com/community/UbuntuLTSP/FatClients.
12:04
<atomic007za>
and my ethtool look like this http://pastebin.com/ausaYXZ6
12:05
<cellofellow>
When I first went to boot it said there was no vmlinuz or initrd.img, which there wasn't in /var/lib/tftpboot/ltsp/i386
12:05
<alkisg>
atomic007za: are you running this on a *****local***** client terminal? SCREEN_01=shell in lts.conf?
12:05
<cellofellow>
so I copied mine from /boot, and now it boots the kernel but can't mount the root filesystem, I get dropped to the initramfs BusyBox shell.
12:06
<alkisg>
cellofellow: no copying from /boot won't work
12:06
<cellofellow>
alkisg: figured. Where do I get/how do I make the kernel image?
12:07
<alkisg>
cellofellow: they're automatically built at the end ltsp-build-client, which calls ltsp-update-kernels
12:07
<atomic007za>
I am logged into the server via Putty, Must I ty the thin clients?
12:07
*try
12:07
<alkisg>
cellofellow: if, for some reason, your ltsp-build-client failed, then there's no point to try the kernels, you'd need to rebuild a new chroot
12:07
<cellofellow>
alkisg: I've run both but neither one puts anything in /opt/ltsp/i386/boot
12:07
oh
12:08
<alkisg>
cellofellow: let's check. ls -lha /opt/ltsp/i386/boot
12:08
What do you have there?
12:08
<atomic007za>
alkisg: I am logged into the server via Putty, Must I try the thin clients?
12:08
<alkisg>
atomic007za: yes, you want to measure the client <=> server communication, so running something from the server will just measure server <=> server communication
12:08
<cellofellow>
$ ls -lha /opt/ltsp/i386/boot
12:08
total 188K
12:08
drwxr-xr-x 3 root root 4.0K 2010-08-16 23:44 .
12:08
drwxr-xr-x 20 root root 4.0K 2010-08-16 19:51 ..
12:08
-rw-r--r-- 1 root root 157K 2010-03-23 03:37 memtest86+.bin
12:08
-rw-r--r-- 1 root root 15K 2010-08-16 23:44 pxelinux.0
12:09
drwxr-xr-x 2 root root 4.0K 2010-08-16 23:44 pxelinux.cfg
12:09
oops, flood
12:09
<alkisg>
!pastebot
12:09
<ltspbot`>
alkisg: "pastebot" :: The LTSP pastebot is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebot, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
12:09
<atomic007za>
ic will do it now
12:09
<cellofellow>
anyway, as you can see it's just memtest and pxelinux
12:09
so, do I need to rebuild my chroot from scratch? Or can I fix this damaged one?
12:09
<alkisg>
cellofellow: you don't have any kernels installed at the chroot. I'm guessing ltsp-build-client didn't finish properly. I'd try it from the start if I were you, and enable "unlimited scrollback" in the terminal to see if something goes wrong
12:10
cellofellow: you can of course try to install a kernel to the chroot, but I'm not sure if that's the only thing missing...
12:10
<cellofellow>
ok
12:11* cellofellow is glad he used apt-cacher-ng, otherwise it'd take all day to build this thing *again*
12:13
<cellofellow>
by default, how is the root directory mounted? Is it NFS? NBD?
12:16
<alkisg>
cellofellow: if you used that wiki page, you'd have MOUNT_PACKAGE_DIR="/var/cache/apt/archives", which saves everything with no need for apt-cacher
12:16
<cellofellow>
oh
12:16
I read the comment describing that wrong.
12:17
# This uses the server apt cache to speed up downloading.
12:17
# You can't use apt on the server while building the chroot, though.
12:17
what's that second line supposed to mean, then?
12:17
<alkisg>
English isn't my native language, so feel free to change that page to make it easier to read :)
12:17jhutchins_lt has joined #ltsp
12:17
<cellofellow>
heh, don't think I can fix that sentence unless I know what it means.
12:17
<alkisg>
It means that while the chroot is using that dir, you can't apt-get install stuff on the server
12:18
<cellofellow>
oh, so it locks the servers dpkg?
12:18
<alkisg>
Yup
12:20
<atomic007za>
alkisg: I am running it from a thin client and get this: http://pastebin.com/KzcirwJs
12:21
looks the same
12:21
<alkisg>
atomic007za: you're not running it from a **************************local********************* terminal on the client
12:21
<atomic007za>
but it is the "same PC"
12:21
<alkisg>
!localxterm
12:21
<ltspbot`>
alkisg: "localxterm" :: while sitting on a thin client, open a gnome terminal. In that, run: ltsp-localapps xterm. An xterm will open. That xterm runs locally, so any commands you enter there are executed directly on the client.
12:21
<alkisg>
That's one way to get a local terminal. Another one, which gives you a root shell, is to put the following in lts.conf:
12:21
[Default]
12:22
SCREEN_02=shell
12:22
<atomic007za>
ic, wow so much to learn
12:22
<alkisg>
SCREEN_07=ldm
12:22
<cellofellow>
alkisg: well, thanks for that one, but I'm already using apt-cacher-ng for now.
12:22
<alkisg>
Currently you're just measuring your server's CPU speed...
12:23
cellofellow: sure, i'm just saying that if you indeed followed that page, then apt-cacher won't be used at all.
12:23
<cellofellow>
alkisg: I didn't quite understand that comment so I commented the line. Silly me.
12:23
<alkisg>
np
12:23
<cellofellow>
I followed it sorta. :P
12:24
apt-cacher-ng would definitely be a boon on a network with any more than a half-dozen Ubuntu servers/workstations.
12:25
<alkisg>
On ltsp labs it doesn't matter as it's only a single pc
12:25
<cellofellow>
I know that.
12:25
<alkisg>
I used to use squid for apt caching before using fat clients...
12:26
<cellofellow>
squid is more general purpose, yeah.
12:26
If I had a really big network I'd probably run apt-mirror or similar such thing for a full mirror.
12:33[GuS] has quit IRC
12:34redbaritone has joined #ltsp
12:35
<cellofellow>
it is nice that gnome-terminal has unlimited scrollback now, isn't it?
12:39
can I tell it to install a gui-less system when it builds the chroot, and I'll just add fluxbox later?
12:39
better yet, can I tell it to install fluxbox?
12:42
<alkisg>
Fluxbox? does that work ok with ubuntu/ltsp?
12:43
<cellofellow>
works with ubuntu, and I'm making a fat client, not a thin client.
12:43
but a very skinny fat client
12:43
<atomic007za>
alkisg: sorry balting a bit here, I have logged in as local user but cant find netperf
12:44
<cellofellow>
lubuntu-desktop would be nice but I tried that in FAT_CLIENT_DESKTOPS and it didn't work
12:44
<atomic007za>
* log into local terminal on thin client
12:44
<alkisg>
cellofellow: ok, I understand you're making a fat client, but it's still ltsp under the hood. E.g. the fluxbox display manager may fight with ldm (it should work fine but never tested)
12:44
<atomic007za>
* logged into local terminal on thin client, but cant find netperf
12:44
<cellofellow>
alkisg: do I have to use ldm?
12:45
<alkisg>
cellofellow: how are you planning to authenticate the clients?
12:45
<cellofellow>
hadn't really thought about it
12:45
<alkisg>
atomic007za: (07:56:46 μμ) alkisg: You're supposed to install it to the chroot, update the image, and then run `netperf server <more parameters>` from the client SCREEN_02...
12:46
cellofellow: and, why wouldn't you want ldm to automatically do that for you?
12:46
<cellofellow>
ok...
12:46
I just don't want to wait 2 hours to download ubuntu-desktop.
12:46
slow inet connection here
12:48
<alkisg>
Why didn't lubuntu-desktop work? Any error messages?
12:48
<cellofellow>
I don't remember what they were. I can try again.
12:48
<alkisg>
All of the -desktop environments should work for fat clients, if they don't file appropriate bug reports
12:48
(not that they're tested; but we're insterested on fixing any problems)
12:49
<cellofellow>
ok, I'm trying lubuntu-desktop again.
13:14komunista has joined #ltsp
13:30Mip5 has joined #ltsp
13:33
<Mip5>
Hey Gang - I've setup an ltsp server - dual 3 GHz xeons, 8 gb memory. I've followed the howto for thinclients and NAT, and it appears to work, but I'm not seeing "firefox on ltsp20" as I would expect. How else can I check that it's working?
13:33
<cellofellow>
alkisg: http://ltsp.pastebin.com/ztcj8yzE <- here's what happened
13:34
<alkisg>
Mip5: do you mean localapps? Can you paste your lts.conf?
13:34
<Mip5>
alkisg: Doh! Yes, I mean localapps. I'll paste it the lts.conf
13:35
<cellofellow>
here's my ltsp-build-client.conf http://ltsp.pastebin.com/NNMiAvUa
13:35
<alkisg>
cellofellow: urm, I see. We prohibit the installation of network-manager-gnome in the chroot because it disconnects the interface while booting... hmm....
13:36
I don't see any easy workarounds, one way to do it would be to allow network-manager-gnome and jockey-gtk but dpkg-divert their upstart scripts
13:36
<cellofellow>
lubuntu-desktop isn't a task, darn, it's a metapackage.
13:36
<alkisg>
Do file a bug report with that, so that we pick it up when we have some time for it
13:36
<cellofellow>
on what package? ltsp? lubuntu-desktop?
13:37
<Mip5>
alkisg: Here's the lts.conf http://ltsp.pastebin.com/YHprXLpK
13:37
<alkisg>
ltsp (ubuntu) (not the upstream LTSP one)
13:37
<cellofellow>
ok
13:37
<alkisg>
Mip5: and you installed firefox to the chroot like http://help.ubuntu.com/community/UbuntuLTSPKarmicLocalAppsFirefox says?
13:38
<cellofellow>
alkisg: so, on the ltsp project in launchpad, or the ltsp-server package?
13:38
<Mip5>
alkisg: yes, though, I suppose I could do it again in case I made some error. It would tell me that the package was already installed, right?
13:39
<alkisg>
cellofellow: https://bugs.launchpad.net/ubuntu/+source/ltsp/+filebug
13:39
Mip5: nah, let's troubleshoot it. Open a localxterm:
13:39
!localxterm
13:39
<ltspbot`>
alkisg: "localxterm" :: while sitting on a thin client, open a gnome terminal. In that, run: ltsp-localapps xterm. An xterm will open. That xterm runs locally, so any commands you enter there are executed directly on the client.
13:39
<cellofellow>
alkisg: ok
13:41
<Mip5>
alkisg: okay, a new terminal opened up
13:41mistik1 has quit IRC
13:42
<alkisg>
Mip5: ok, run firefox from there. Does it work?
13:42
<Mip5>
alkisg: I ran ps aux | grep firefox, and got some results
13:42
whoops - I jumped the gun - hold on.
13:43
alkisg: yes, firefox runs when I launch it from that terminal
13:44
<alkisg>
Mip5: delete lines 5 and 7 from your lts.conf and reboot the client
13:44
<cellofellow>
alkisg: ok, all set https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/619398
13:45
alkisg: what now? I don't really want to use ubuntu-desktop, and I don't think xubuntu or kubuntu are any smaller. All I need is something to run the cinelerra renderfarm node on, and ffmpeg.
13:45
<alkisg>
Nice, thanks
13:46
cellofellow: well, you can do the dpkg-divertion manually, and go on installing lubuntu-desktop
13:46
Let me see the easiest way...
13:46
<cellofellow>
alkisg: ok, but I'll need to build a bare chroot first. How do I do that? Just put ubuntu-standard in FAT_CLIENT_DESKTOPS?
13:47
<alkisg>
cellofellow: sudo gedit /usr/share/ltsp/plugins/ltsp-build-client/Ubuntu/030-fat-client
13:47
Remove jockey and network manager from the blacklist
13:47
Then re-run ltsp-build-client with lubuntu.
13:47
<cellofellow>
ok, where's the blacklist?
13:48
<alkisg>
It should finish properly (but the clients won't really boot because of network manager)
13:48
Open that file, you'll find it
13:48
<cellofellow>
oh, missed that oops
13:48
<alkisg>
When ltsp-build-client finishes, ping me to tell you the dpkg-divert line...
13:48
Note down everything you're doing and add it to the bug report when it works :)
13:49
<Mip5>
alkisg: I've rebooted the client. I didn't rebuild the image or anything like that after editing lts.conf.
13:50
<cellofellow>
alkisg: ok, modified the blacklist and rebuilding now. This'll take a few minutes.
13:50
<alkisg>
Mip5: ok, so if you start firefox from the gnome menu it doesn't start locally?
13:51
<Mip5>
alkisg: firefox starts and appears to run fine. It just doesn't say, "running ltsp20" above the menu bar, like I was expecting
13:52
<alkisg>
Mip5: ok, open a localxterm again
13:52
ps -ef etc, does firefox run locally?
13:53
<Mip5>
alkisgn: the localxterm's open, but I don't understand your request
13:53
<alkisg>
ps -ef | grep firefox
13:53
Do you see firefox-bin there in the localxterm?
13:54* cellofellow goes to lunch
13:55
<Mip5>
yes. It shows up both when I launch ff from the gnome menu, and when I launch it from the localxterm.
13:56
<alkisg>
And when you run it from the localxterm, you still don't see "running on ltsp20" on the title bar?
13:57
<Mip5>
right - I don't see that "running on ltsp20"
13:58
<alkisg>
OK then everything's fine, just firefox doesn't use that specific wording
13:59
<Mip5>
alkisg: okay - it's just strange b/c it does show up on my other server, and the setup and install were *supposed* to be the same. Perhaps I made an error somewhere....
13:59
alkisg: when is it necessary to rebuild or update the client image - whenever there have been changes to the chroot?
14:00
<alkisg>
Yup
14:00
(rebuild is only necessary when you change releases, e.g. karmic => lucid)
14:00
<Mip5>
okay - so I should go back to my original lts.conf file and reboot
14:00
<alkisg>
chroot apt-get update / upgrade ==> then ltsp-update-image
14:00
<Mip5>
okay - thanks
14:01
<alkisg>
Mip5: the 5 and 7 lines are not needed
14:01
You don't need to put them back...
14:01
<Mip5>
really?
14:01
<alkisg>
LOCALAPPS is True by default
14:01
And you only need to specify the MENU_ITEMS if you install something to the chroot but you *don't* want it to show up on the menus
14:01
<Mip5>
so, as long as app has been installed into the chroot, and added to the menu line, it's good to go?
14:02
<alkisg>
That's usually a rare use case...
14:02
So, no, you don't need to add apps to the menu line.
14:02
<Mip5>
okay - thanks
14:02
<alkisg>
np
14:02
<Blinny>
alkisg: Anyone ever tell you that you are teh aweszome?
14:03
<Mip5>
I was just going to say that.
14:03
<alkisg>
Heh, thanks Blinny. Everything fine with keepalive?
14:03
<Blinny>
Feeble attempt at the way kids are talking nowadays.
14:03
alkisg: Your precedence find was spot-on. I guess *that* is what changed. My hosts.allow
14:03
<Mip5>
alright - thanks again alkisg. See y'all in the 'hood.
14:05Mip5 has left #ltsp
14:08vagrantc has joined #ltsp
14:20Mip5 has joined #ltsp
14:21
<Mip5>
Hey Gang, I've got firefox running as a localapp. I can print from openoffice (which is not setup as a localapp), but not from firefox. Is there a way to enable printing for localapps?
14:28
I'll check back later, after lunch. Thanks.
14:28Mip5 has left #ltsp
14:40
<cellofellow>
alkisg: well, it's still building that image. Taking its time downloading packages.
14:41pmatulis has quit IRC
14:43mstrohmeyer has joined #ltsp
14:46
<mstrohmeyer>
hello
14:46
<cellofellow>
so, I take it this localapps stuff is to mix the fat and thin client modus operundi? Run fat apps in a thin system?
14:51
<alkisg>
cellofellow: yup
14:51
<mstrohmeyer>
i have a thin client which puts the monitor to sleep right after it says loading client system
14:51
what can i do to track down whats happening
14:52
<cellofellow>
sleeping monitor sounds like the video card isn't outputting anything and the monitor goes into its no-signal auto-sleep mode.
14:52
<mstrohmeyer>
and how does one track down why a video card isn't outputting...?
14:52
<alkisg>
Try either XSERVER=vesa or XRANDR_MODE_0=1024x768 in lts.conf
14:52
<mstrohmeyer>
ok
14:52
thanks
14:53
<cellofellow>
vesa sucks performance-wise but it almost always works, which is a good thing I suppose.
14:53Blinny has quit IRC
14:53
<alkisg>
...and it's a way to make sure that it's a video problem :)
14:54
<cellofellow>
do I have to ltsp-update-image every time I make a change to lts.conf?
14:54HigglyPiggly has joined #ltsp
14:54
<cellofellow>
(that, and I'd like to see a man page detailing everything that can go in an lts.conf)
14:55
<alkisg>
!lts.con
14:55
<ltspbot`>
alkisg: Error: "lts.con" is not a valid command.
14:55
<cellofellow>
man 5 lts.conf, currently can't do that.
14:55
<alkisg>
!lts.conf
14:55
<ltspbot`>
alkisg: "lts.conf" :: http://manpages.ubuntu.com/lts.conf
14:55
<HigglyPiggly>
are most people using retired workstations/desktops/laptops or getting specifically designed thin clients for this...
14:56
<alkisg>
cellofellow: you don't need to update the image if you modify lts.conf
14:56
<cellofellow>
ok
14:56
alkisg: what does require an image update?
14:56dgroos has quit IRC
14:56
<alkisg>
Anything that writes to /opt/ltsp/i386
14:57
<cellofellow>
doesn't the lts.conf go in /opt/ltsp/i386/etc/ltsp/? Or does it just go in /etc/ltsp/?
14:57bobby_C has joined #ltsp
14:57
<alkisg>
cellofellow: /var/lib/tftpboot/ltsp/i386/lts.conf
14:58
<cellofellow>
oh
14:58
<alkisg>
HigglyPiggly: both, I guess. Even new workstations are sometimes used... (for fat clients)...
14:59
<johnny>
yeah.. i switched my retired computers to some msi wind nettops with 2GB ram
14:59
probably overdid it a bit on the ram.. but it's pretty awesme
14:59
<cellofellow>
I wonder which is used more, fat clients or centrally-managed desktops?
15:00
I know at my university it's dual-boot (Snow Leopard and WinXP) iMacs, mostly. They're centrally managed with Novell Zen I think.
15:00
johnny: that does sound awesome
15:01
<HigglyPiggly>
we just bought some thin clients from 10ZiG technologies and they do not like to work with anything. its really frustrating
15:02
<alkisg>
cellofellow: when I was looking around for fat clients, I didn't see any good implementations I could use... ltsp fat clients is the best I could find. Do you know of any other related technologies (with 1 image for many clients?)
15:02
<johnny>
i think i would have been happy with regular thin clients if flash wasn't so terrible over the network
15:02
<alkisg>
HigglyPiggly: any specific problems? also, distro/version?
15:02
<cellofellow>
alkisg: puppet maybe, but it's for servers.
15:02
<HigglyPiggly>
ubuntu 8.04, 8.10, and 10.04 all have issues
15:02
<johnny>
or maybe your hardware is the issue
15:03
not ubuntu
15:03
<mstrohmeyer>
XSERVER=vesa and the other one didn't help....
15:03
<alkisg>
cellofellow: but that requires different images for each server, right?
15:03
<mstrohmeyer>
i still get a black screen
15:03
<cellofellow>
johnny: so, why fat clients instead of thin clients with localapps Firefox?
15:03
<johnny>
because i didn't have enough ram
15:03
<cellofellow>
alkisg: I honestly don't know.
15:03
<johnny>
cellofellow, puppet wouldn't work
15:03
as the images don' actually move
15:03
or get deployed
15:04
puppet pushes
15:04
ltsp pulls
15:04
<cellofellow>
I wonder if anyone has used ltsp fat clients to provision a cluster of servers.
15:04
<johnny>
seems feasible
15:04
just depends on what the servers do
15:04
if all they do is crunch, then yes
15:05
<cellofellow>
(actually, that's kind of what I'm doing. I want to turn a bunch of Windows laptops into a Cinelerra renderfarm)
15:05
<johnny>
if they operate on local data.. not so awesome
15:05
<alkisg>
I think one here was looking to do that, I don't know if he managed it...
15:05
mstrohmeyer: if you press alt+ctrl+f1 on the client, do you get a terminal screen?
15:06
HigglyPiggly: what kind of issues?
15:07
<mstrohmeyer>
i do not get a terminal screen, and i'm concerned its because the keyboard isn't responding, because the old thin clients we're trying to replace will boot up properly to this image but the keyboard won't work at all
15:07
<HigglyPiggly>
just general issues like keyboards not working, images working on one type but hte next type kernel panics with that image
15:07
<alkisg>
HigglyPiggly: well, you need to take it one problem at a time. Ask for specific problems/error messages etc
15:08HigglyPiggly has quit IRC
15:08
<cellofellow>
alkisg: you scared him off
15:08
<alkisg>
Damn I forgot my magic wand which solves all the problems without asking for error messages...
15:08
<cellofellow>
gee, I'd like one of those sometimes
15:09
<mstrohmeyer>
okay so my screen is sleeping and if i type ctrl-alt-f1, nothing happens, and caplocks/scrolllock/numlock don't light up when i hit them on the keyboard
15:09
<alkisg>
mstrohmeyer: distro/version?
15:09
<mstrohmeyer>
ubuntu hardy
15:09
<cellofellow>
I wonder if the Magic SysRQ keys work, or if your IO is completely hosed.
15:09
<alkisg>
If the clients are very new, you might want to try lucid instead
15:10
Try also with SCREEN_07=shell in lts.conf
15:10
<mstrohmeyer>
its a NPO, so they can't afford to upgrade all of their thin clients and so we have to be able to use the old ones as well. will the lucid images work on theold thin clients you think?
15:11
<alkisg>
Specs?
15:11
(ram/cpu)
15:11
(and graphics cards)
15:11
<mstrohmeyer>
on the server or the thin clients
15:11
<alkisg>
Thin clients
15:11
My 10 year old pcs work fine with lucid...
15:11
<mstrohmeyer>
intel atom n270 1gb ram, intel 945GSE
15:11
thats the newer one actually
15:12
sorry you were asking about the old one i'm sure
15:12
<cellofellow>
what's the typical specs for an LTSP (thin clients, not fat clients) server?
15:12
<johnny>
it's all in the docs
15:12
iirc
15:12
<cellofellow>
(for fat clients a simple NAS would probably do the job I think)
15:12
<johnny>
!docs
15:12
<ltspbot`>
johnny: "docs" :: For the most current documentation, see https://sourceforge.net/apps/mediawiki/ltsp/index.php?title=Ltsp_LtspDocumentationUpstream
15:12
<johnny>
or used to be anyways
15:12
also.. what happened to sbalnaev
15:13
<alkisg>
mstrohmeyer: yup, the old ones
15:13
<mstrohmeyer>
yea sorry i am trying to get the specs for you one second
15:13
<alkisg>
cellofellow: a nas could server one rw image for each client, but not the same image to many clients
15:13
So that wouldn't be easy to maintain...
15:14
<mstrohmeyer>
wtf via Eden CPU....
15:14
is that arm based?
15:14
<cellofellow>
I don't quite understand, but OK.
15:15
<mstrohmeyer>
no its x86... and the video card specs are "Analog video via VGA output"
15:16
<alkisg>
ram?
15:16
<mstrohmeyer>
64MB
15:16
<johnny>
that's a bit too low
15:17
<alkisg>
Ouch. That's the lowest minimum for lucid, sometimes it hangs on booting but if it boots it's ok afterwards
15:17
<mstrohmeyer>
haha the joy of not having money to do things that cost money! gogo NPO!
15:17
<alkisg>
Even 96mb would be better, if it's possible
15:17
<johnny>
i think the ram is soldered in on those
15:17
it's a fanless board
15:18
really small
15:18
<mstrohmeyer>
yup
15:18
<johnny>
but do they take compact flash?
15:18
<mstrohmeyer>
its from disklessworkstation.com, a TK-3350/533 and they don't even admit to ever having made them on their website anymore
15:18
let me crack the case and see
15:18
<johnny>
if they take compact flash, you could perhaps use some sort of swapping mechanism with a coupel cheap cf cards
15:19
instead of relying on the network swap
15:19
i guess that depends on how saturated your network is tho.. as to whether that's valuable or not
15:20
<mstrohmeyer>
oh man they have an sdram slot! and it has a stick of 128....
15:20
<johnny>
hah..
15:20
well you're good to go then
15:20
i obviously haven't seen ever eden board
15:20
i just know it was popular to have the ram soldered in
15:20
<cellofellow>
how long would a CF-card SSD swap last?
15:21
<mstrohmeyer>
i hadn't even heard of an eden cpu until just now so you're still ahead of me
15:22
<johnny>
which npo is this btw?
15:22
and where are they located
15:25
<mstrohmeyer>
its in the US, washington state
15:25
they have a bunch of offices but they have a tight budget
15:25
i'm going to try a lucid image on the server and see if either/both of the thin clients can boot
15:25
thanks for the help
15:26
<alkisg>
vagrantc: I wonder if it would be better, instead of blacklisting packages in 030-fat-client, to dpkg-divert the upstart/initscripts of network-manager, jockey-gtk etc in ltsp-client.postinst... E.g. now lubuntu-desktop can't be installed because it depends on network-manager (and maybe some debian desktop package has the same problems)...
15:26
<vagrantc>
dpkg-diversions are pretty ugly...
15:27
<cellofellow>
alkisg: did you mean me?
15:27
<alkisg>
cellofellow: yeah, but other desktop environments could have the same problem too
15:29
cellofellow: e.g. instead of reporting the problem in ltsp, you could ask lubuntu to lower "Depends: network-manager" to "Recommends: network-manager". But would that change be accepted?
15:29
<cellofellow>
probably not
15:29
lubuntu-desktop ought to be a task, not a metapackage.
15:30
<alkisg>
ubuntu-desktop is a metapackage too. It just recommends network-manager, it doesn't depend on it
15:31
<cellofellow>
oh, hm
15:32
well, might be worth a try. Could add lubuntu to that bug and attach a patch changing the Depends to Recommends.
15:33
<mstrohmeyer>
man i really hope this is not as stupid of a question as it sounds, ltsp-server-standalone installs ubuntu-desktop right.....
15:34
<cellofellow>
no idea, but I'm making fat clients, but skinny fat clients. :)
15:37mistik1 has joined #ltsp
15:38
<johnny>
mstrohmeyer, maybe :)
15:38
mstrohmeyer, it's just that i knew somebody wit your last name and first initial and wondered if you had gotten into computers :)
15:38
<alkisg>
mstrohmeyer: no, it doesn't
15:39
mstrohmeyer: e.g. one might want to install it to a kde desktop..
15:39
<johnny>
mstrohmeyer, that's only if you choose ltsp from the alternative install ?
15:41
<mstrohmeyer>
ive been told my last name is very common in germany, much like smith in the US
15:42
alkisg: i will install ubuntu-desktop as soon as the new image is done prepping
15:42
<alkisg>
mstrohmeyer: you have a server with no desktop environment installed?
15:42mikkel has quit IRC
15:42
<johnny>
the internet is a small place
15:43
<alkisg>
Yeah, only a few billion souls on it :D
15:43
<mstrohmeyer>
this is just a test environment, i just installed it this morning,ive not installed it manually however
15:44
johnny: what was your friends first name
15:45
<johnny>
melinda
15:46
<mstrohmeyer>
wrong gender haha
16:26
<cellofellow>
yay, it's done downloading packages and is now actually installing stuff in my chroot.
16:31
taking its time of course
16:32
so, what does a dkpg-divert do anyway? Move a file but tell dpkg where it is so it can still access it?
16:33
<alkisg>
Yes, so that package upgrades will still put that file in the diverted location
16:33
<cellofellow>
nifty
16:36vagrantc has quit IRC
16:39vagrantc has joined #ltsp
16:39
<cellofellow>
here's a surprisingly large amount of Gnome bits in Lubuntu.
16:39
not as much as Xubuntu, but a bunch.
16:40
bits of XFCE too, geepers.
16:42
should have tried with fluxbox :/
16:45vagrantc has quit IRC
16:50
<cellofellow>
aarh, now it has to download the kernel package which is 30MB and will take another 30 minutes to download. I so wish I could do this at home where I have 1.5Mbps (not much I know) not this snailish 256Kbps.
16:51
my house is just across the street, it has wifi, but it's just far enough away I can't connect to it from here. :(
16:51
<johnny>
cellofellow, get a bigger antena :)
16:51
<alkisg>
You could just do it there and transfer the chroot :)
16:52
<johnny>
cellofellow, i wouldn't call them gnome bits.. most of them are pretty standard bits of an OS
16:52
most..
16:52
<cellofellow>
alkisg: :/ wish I had done that earlier.
16:53Ghidorah has joined #ltsp
16:53
<johnny>
that's where nonsense arguments about bloat start from :)
16:53
<cellofellow>
johnny: bigger antenna would work I think, but my router doesn't have external antennas. :\
16:53
<Ghidorah>
Hello everyon. What would cause a terminal not to be able to login? I'm able to log in locally to the server.
16:53
<johnny>
ah, that would be problematic
16:53
Ghidorah, error messages
16:54
<Ghidorah>
It just times
16:54
<johnny>
please start with those
16:54
<Ghidorah>
out
16:54
<cellofellow>
I don't want a desktop I want basically a tiny little system to run one app *once*.
16:54
<johnny>
can you connect from ssh ?
16:54
<cellofellow>
app happens to need X
16:54
<johnny>
from a machine not a thin client Ghidorah ?
16:54
<Ghidorah>
Johnny: yes
16:54
<johnny>
where does it time out
16:54
c'mon dude
16:54
help us
16:54
don't make us pull it out of you
16:55
<Ghidorah>
It is timing out after entering the password.
16:56mstrohmeyer has quit IRC
16:57
<Ghidorah>
Is there any log that you're aware of that I may reference?
16:59
<johnny>
sure.. client /var/log/ldm.log
16:59
or anything on the server in /var/log
16:59
<alkisg>
cellofellow: you may make a screen script that launches your app instead of ldm, then (but you'd need a specific user for each client - LDM_USERNAME / LDM_PASSWORD etc)
17:00
Ghidorah: a common problem is ssh keys (ltsp-update-sshkeys). Distro/version?
17:01
<Ghidorah>
I'm un Ubuntu 10.04. I've run ltsp-update-sshkeys a few times
17:01
<alkisg>
And also ltsp-update-image?
17:01
<Ghidorah>
correct.
17:01
I'll run it again.
17:01
<alkisg>
Do you see a login attempt at the server /var/log/auth.log?
17:03
<Ghidorah>
alkisg: I see the login attempt.
17:03
<alkisg>
What exactly does it say?
17:04
<Ghidorah>
It says authentication failure, even though I have tried with multiple different accounts
17:05
<alkisg>
OK. Put this on your /var/lib/tftpboot/ltsp/i386/lts.conf:
17:05
[Default]
17:05
SCREEN_02=shell
17:05
SCREEN_07=ldm
17:05
<Ghidorah>
k
17:05
<alkisg>
Reboot the client, and switch to vt2 with alt+ctrl+f2
17:05
At that terminal, run: ssh user@server
17:05
Change user to an existing username, but leave server as it is.
17:06
Check if you're able to login from there, without seeing any warnings at all.
17:07
<Ghidorah>
will do.
17:09
is there a known scenario when ltsp-update-sshkeys doesn't function?
17:09
I got a warning about adding RSA host to the list of known hosts
17:10
<alkisg>
You shouldn't be getting a /var/log/auth.log entry though
17:10
OK, now, after you said OK to that warning, switch to vt7 and try again on ldm
17:10
<Ghidorah>
I was able to log in
17:11
<alkisg>
OK. Try ltsp-update-sshkeys and ltsp-update-image once more, just to be sure
17:11
<Ghidorah>
k
17:11
is there any output expected from ltsp-update-sshkeys?
17:11
<alkisg>
No
17:12
<Ghidorah>
any log file that it references?
17:12
<alkisg>
syslog?
17:13
You can also do "sudo sh /usr/sbin/ltsp-update-sshkeys" to see the trace
17:14
<cellofellow>
hey hey it's building the image now
17:15
<Ghidorah>
alkisg: while I dont understand what I was doing wrong earlier... it is working now
17:15
<alkisg>
I think I've seen ltsp-update-sshkeys fail sometimes, but I didn't pinpoint it as I'm using a dynamic IP on the server, so I have to use LDM_SSHOPTIONS="-o StrictHostKeyChecking=no -o CheckHostIP=no -o LogLevel=silent" in lts.conf
17:15
<Ghidorah>
Thank you for your help!
17:16
<alkisg>
np
17:21
<cellofellow>
hm, network booting doesn't seem to be particularly speedy
17:22
<alkisg>
13 seconds for my fat clients, as opposed to 50 seconds for local boot
17:22
<cellofellow>
maybe it's just virtualbox
17:22
(I have a real computer to test it on later but virtualbox just for a quick check)
17:23
<alkisg>
How much ram did you put in the guest?
17:23
<cellofellow>
768MB
17:23
<alkisg>
(and what are your server specs?)
17:23
<cellofellow>
server's actually an Ion box, so not that hot
17:23
besides, I need to do those dpkg-diverts you were talking about
17:24
on jockey and network manager
17:24
<alkisg>
Right
17:24
Also remove "quiet splash" from /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default to better see any boot problems
17:24
Does it hang now on the splash screen?
17:25
<cellofellow>
no
17:25
<alkisg>
What, it actually boots?
17:25
<cellofellow>
well, the bootloader loads, the kernel boots, and I see Plymouth. Didn't wait around long enough to see if it got to LDM.
17:25
Because I remembered I needed to do the divert.
17:26
<johnny>
knipwim_, another update on dracut :)
17:26
<alkisg>
I think it would hang on plymouth, while nm was trying to get a network address...
17:26
But do try booting before dpkg-divert, to see exactly what's needed
17:26
<cellofellow>
ok
17:26
i'll turn off plymouth though so I can see
17:27
does the syslinux/pxelinux config format have comments?
17:27
<alkisg>
Yes, with a # in front
17:28
I think something like this will be needed in the chroot: sudo dpkg-divert --divert /etc/network-manager.conf.diverted --rename /etc/init/network-manager.conf
17:28
<cellofellow>
let's see what happens when I boot it without it.
17:28
<alkisg>
Right
17:29
<johnny>
how come you haven't bugged the networkmanager dude about this issue alkisg
17:29
there should be no reason to disable networkmanager
17:29
<alkisg>
No time for everything, johnny... :)
17:29
<johnny>
ltsp spends too much time working around things
17:29
instead of actually talking to upstream
17:30
imo
17:30
altho sadly the ssh with null cipher thing was blocked by powers above us :(
17:30
<alkisg>
I filed a bug about the problem with 1 managed interface and 1 unmanaged, though (=classic ltsp setup)
17:30
...and it hasn't been solved for over a year
17:30
<johnny>
why would you need 1 unmanaged?
17:30
why not let networkmanager manage it
17:30
<alkisg>
Unmanaged == a static ip in /etc/network/interfaces. It's the classic ubuntu/ltsp setup from the alternate cd
17:31
<johnny>
you really have to bug the maintainer if you want something done :)
17:31
no need for that static ip in there
17:31
networkmanager can do it
17:31
i've done it with networkmanager, works easy
17:31
<cellofellow>
i'm letting nm manage my wired network for the ltsp, and my wireless for inet.
17:31
<johnny>
at least in lucid
17:31
never needed to before
17:31
<alkisg>
Sure, but it's a bug, and we'd have to change the ltsp code to create a system connection with network manager, so we'd have to depend on it then
17:32
<johnny>
that's ok
17:32
<alkisg>
Not all admins want network manager
17:32
<johnny>
they are dumb
17:32
<alkisg>
It doesn't support all configurations, e.g. you can't do bonding with it
17:32
<johnny>
it's pulled in as part of the desktop environment anyways
17:32
sure.. in that case ,it should allow unmanaged
17:32
<cellofellow>
alkisg: so the problem is the system gets an IP from DHCP when the PXE stuff starts, and just keeps that IP. But when nm gets going it resets the nic and stops?
17:32
<johnny>
since you can have more complicated rules
17:33
just for normal people, letting networkmanager manage it is ok
17:33
i think it's ok to use networkmanager automatically if it's there especially
17:33
<alkisg>
cellofellow: not exactly. Initramfs asks again for a dhcp lease. And then, network manager asks for an ip for the third time, and then it breaks - at least I imagine so, I haven't tested it for a long time
17:33
<johnny>
even if it's not a dep
17:34
too bad pxe can't pass the lease :(
17:34
<alkisg>
johnny: in any case, it _is_ a bug that hasn't been solved for over a year
17:34
<johnny>
sure.. just takes some prodding
17:34
just like every other bug people want solved
17:35
<alkisg>
We're using 1 nic setups here so I don't care much, so I left it the prodding for other persons who use 2 nic setups :)
17:36redbaritone has quit IRC
17:36
<cellofellow>
I'm using a 2-nic setup but I don't really care about the internet access for my fat clients. All I need is LAN. (I've been using a LiveUSB and link-local (zeroconf) addresses up till now.)
17:37
ok, the vbox fat client got up to Starting LTSP client..... [OK] and then seems to have frozen. No network traffic, no CPU.
17:38
what's my ltsp260 login for the tty1?
17:38
that's still working
17:39
oh, getting something, says NetworkManager blocked for more than 120 seconds.
17:39
I think diverting nm sounds like a great idea.
17:39
<alkisg>
OK, go ahead :)
17:40
<cellofellow>
alkisg: what about jockey, should I divert it too?
17:40
<alkisg>
That's not critical, but you don't want it to popup to ask people to install drivers... so yeah
17:40
I think that's in /etc/xdg/autostart
17:41
<cellofellow>
yeah
17:48irule has joined #ltsp
17:55
<cellofellow>
well, got to LDM that time
17:55
now it's authenticating, logging in....
17:56
taking its sweet-monkey time
17:57
<alkisg>
Looks like your virtual client or net isn't good enough...
17:58mstrohmeyer has joined #ltsp
18:00dlezcano has joined #ltsp
18:00
<mstrohmeyer>
i have a hardy ltsp-server box, and when it boots one of our new thin clients, the kernel panics
18:00
<cellofellow>
pcmanfm doesn't like it for some reason, gave me an error box "cannot connect to FAM. Please make sure you have FAM or GAMIN running"
18:00
<mstrohmeyer>
the message preceeding the panic is : eth0: SIOCGIFINDEX: No such Device
18:00
no devices to configure
18:00
can't open /tmp/net-eth0.conf
18:01
<alkisg>
mstrohmeyer: what nic on the client?
18:01
It's probably a missing module, you might need a newer kernel. Why not try out Lucid instead? Hardy is too old anyway now...
18:02
<mstrohmeyer>
Realtek RL8111
18:02
because lucid won't boot on our older thin clients.... and there isn't enough to replace all of them
18:02
my next step is to try and boot multiple kernels based on mac address
18:02
<alkisg>
mstrohmeyer: why won't it boot? any error messages?
18:03
I think you should troubleshoot those, not the hardy problems..
18:03
<mstrohmeyer>
the other issue is the company can't afford to have the server updated, so it would have to be an updated debootstrap installing a lucid image which is pretty hairy in itself
18:04
<alkisg>
I'm not sure I got this, why wouldn't lucid work on your server?
18:04
(with a normal installation?)
18:04
<mstrohmeyer>
lucid would work on the server, but the company lacks the financing to have lucid installed on the server
18:05
<alkisg>
Hmmm I think that would take much less time than solving the hardy problems, though. OK, anyway, here's a page to add modules:
18:05
https://help.ubuntu.com/community/UbuntuLTSP/AddingModules
18:05
<mstrohmeyer>
great thank you
18:08Lumiere has quit IRC
18:11bobby_C has quit IRC
18:13
<cellofellow>
where does the lts.conf file go, again?
18:14
<alkisg>
/var/lib/tftpboot/ltsp/i386/lts.conf
18:15
<cellofellow>
[default]
18:15
NFS_HOME=/home
18:15
that should make /home on the fat clients by an NFS mount of /home on my server?
18:15
s/by/be/
18:16
/home 176.16.0.0/16(rw,sync,no_subtree_check)
18:16
that's my /etc/exports
18:20
<alkisg>
Sounds ok, try it with SCREEN_02=shell in lts.conf - it should be mounted even before logging in to ldm
18:21komunista has quit IRC
18:25
<cellofellow>
so, the image thing, how's that work? It gets served up by nbd as a read-only hard drive or something?
18:25
I notice it's squashfs
18:26
<alkisg>
Exactly, and with a tmpfs/aufs on top of it
18:26
<cellofellow>
not much different from how the livecd works, then. I guess, anyway.
18:31
aha, the real box boots WAY faster than the virtualbox
18:31* cellofellow thinks he shouldn't use virtualbox without hardware acceleration
18:31
<alkisg>
Late here, goodnight all
18:32ThE-RiX has joined #ltsp
18:32
<mstrohmeyer>
alkisq: is there a page that lists modules and hardware that works with them? for instance, to see if r8169 will work with the RLT8111/8168B ?
18:32alkisg has quit IRC
18:35RiXtEr has quit IRC
18:39staffencasa has quit IRC
18:46Ghidorah has quit IRC
18:49Selveste1___ has quit IRC
18:55Selveste1___ has joined #ltsp
18:59
<mstrohmeyer>
exit
18:59mstrohmeyer has quit IRC
19:09F-GT has quit IRC
19:13Lumiere has joined #ltsp
19:23
<cellofellow>
haha!! Sweet success!
19:24F-GT has joined #ltsp
19:39alkisg has joined #ltsp
19:42
<alkisg>
cellofellow: nice! please write any info needed to get lubuntu running to the bug report :)
19:44
Hmmm a better way may be to modify the ltsp initscripts so that they *delete* the network-manager upstart/init scripts on booting - that would even be cross distro...
19:45ogra_cmpc has quit IRC
19:53johnny has left #ltsp
19:54johnny has joined #ltsp
19:55
<cellofellow>
ok, weird. Tried it on my brothers laptop and the first time I got a kernel panic. Since then, it sits there waiting for DHCP. Wireshark shows that the DHCP DISCOVER and REQUEST packets are getting through, and it
19:55
it's responding with DHCP OFFER packets, but they aren't being excepted and no lease is being made.
19:56
now he's gotten really grumpy with me and won't let me keep it to figure out what's wrong.
19:57
s/excepted/accepted/
19:57ogra_cmpc has joined #ltsp
20:00
<alkisg>
Is it a very new laptop? E.g. core 2 duo etc?
20:00
<cellofellow>
actually it's a little Acer Aspire One.
20:01
Atom CPU, hyperthreaded, don't remember the model number.
20:01
It is fairly new.
20:02
<alkisg>
I've seen that a "sleep 10" is needed on very fast clients... but you won't know if he doesn't let you try :)
20:02jhutchins_lt has quit IRC
20:02
<cellofellow>
sleep 10? where?
20:02
<alkisg>
E.g. put break=mount in pxelinux.cfg/default, wait a few seconds when you get a busybox shell, and then press ctrl+d
20:02
<cellofellow>
oh
20:02
break looks like a debugging tool
20:02
<alkisg>
If that boots it, then you can just put a sleep in ltsp_nbd
20:03
It is
20:03
<cellofellow>
well, at this point I 1) don't have the laptop, he took it back home with him. He's paranoid I'll break something, though I've run LiveUSBs on it before without trouble.
20:03
2) It won't work with DHCP.
20:04
It worked once, but quit.
20:04
My grandma's Core2Duo worked fine, no kernel panics or need to add sleeps to it.
20:05
worse comes to worse I have a coule SD cards I can make into LiveUSBs.
20:05
s/coule/couple of/
20:07
<alkisg>
What I'm saying is a way to bypass dhcp problems
20:07
(_some_ specific dhcp problems that are caused by inappropriate boot sequence)
20:09
<cellofellow>
but how does editting pxelinux.conf/default help when the PXE in the network card can't even obtain an IP address and TFTP pxelinux?
20:12
<alkisg>
Oh. I thought that was the second dhcp request, in the initramfs...
20:12
Are you using the default dhcpd.conf? With root-path and everything?
20:13
<cellofellow>
works on a different laptop
20:13
here, let me pastebin
20:14
http://ltsp.pastebin.com/wqdVsWQN
20:14
<alkisg>
The router there is on a different subnet...
20:15
<cellofellow>
which line?
20:15
<alkisg>
Urm, I guess the range line :)
20:15
<cellofellow>
oh
20:16
the range is in the 172.16.1.0/24 address space but the subnet is still 172.16.0.0/16
20:16
<alkisg>
OK just realized that
20:16
<cellofellow>
anyway, just rebooted that other box and it didn't work.
20:17
<alkisg>
You don't happen to have another dhcp server runinng on a hardware router, right?
20:17
<cellofellow>
I turned that off.
20:18
there is one on the wifi network but that shouldn't cause any trouble
20:18
<alkisg>
Dunno... looks ok
20:19
<cellofellow>
does dhcpd log anywhere?
20:21
<alkisg>
/var/log/daemon.log, and it also has a "verbose" option
20:22
But I don't use it so I'm not really experienced with it... (I use dnsmasq)
20:22
<cellofellow>
I generally use dnsmasq too, and was going to but this came with dhcpd. Can I see your dnsmasq config?
20:22
or a sample
20:23
do you use the tftp server in dnsmasq?
20:24
<alkisg>
dpkg -L ltsp-server | grep dnsmasq
20:24dgroos has joined #ltsp
20:24
<cellofellow>
found the problem, my / is full.
20:24
<alkisg>
No, I left tftpd-hpa because of dependency problems
20:24
Heh
20:25
I'm using dnsmasq in proxydhcp mode though, so that I actually use my router's dhcp server and dnsmasq only fills the boot filename... https://help.ubuntu.com/community/UbuntuLTSP/ProxyDHCP
20:25
<cellofellow>
I foolishly left only 5GB for / on this computer when I installed it. It is my grandpas Solitaire machine, actually, and I didn't expect to be editting video on it.
20:26
alkisg: nifty
20:26
<alkisg>
Just purge some of the apt cache to make room...
20:26
<cellofellow>
yeah...
20:27
or put yet another bind mount from /home into /var. I have it for /var/tmp and /opt/ltsp
20:31
maybe my brother will let me try again
20:33
I could nuke these unused Vista partitions.
20:34
nah, takes forever to move partitions.
20:41
can I write a custom screen script (/usr/share/ltsp/screen.d/) and pass options to it with lts.conf? Per-machine options, you know?
20:42
<alkisg>
Sure
20:42
<cellofellow>
hm, I'm looking at the rdesktop script right now and not sure it's what I want.
20:43
can I set the $USER in shell?
20:44
<alkisg>
Can you describe your desired end result?
20:44
E.g. what user would run your app?
20:44
There are no users in the chroot by default...
20:45
<cellofellow>
user $USER (1000) would run `cinelerra -d $PORT`
20:45
I could run two instances on some boxes with 2 cores.
20:45
<alkisg>
You don't care about security/authentication etc?
20:45
<cellofellow>
thing is different instances need different ports.
20:46
<alkisg>
All clients would use the same user, 1000?
20:46
<cellofellow>
nah, not worried about security. Yes, user 1000 for all of them.
20:46
<alkisg>
Won't that have problems with all users working on the same nfs-mounted home dir?
20:46
<cellofellow>
$PORT needs to be different for each one, though. I suppose I could hard-code the USER.
20:47
the cinelerra master node parcels out the jobs so they all write to different files.
20:47
<alkisg>
PORT is easy, you can either pass it with lts.conf or even calculate it from the client ip
20:47
<cellofellow>
They read the same files, but write to different ones.
20:47
<alkisg>
In that case I think you can just add a user to the chroot
20:47
<cellofellow>
$PORT actually i'd like to default to 4000 but some boxes will need to have 4001 for a second instance. (It isn't multi-threaded so I run an instance per core.)
20:48
to do that just ltsp-enter-chroot; adduser?
20:48
<alkisg>
Yes, and just "su" to that user from the screen.d script
20:49
(never done that, but I think it'll work)
20:50
While developing your script, it might be a good idea to start with a single "xterm" so that you try stuff manually before putting them to a script
20:51
<cellofellow>
is there an xterm screen script?
20:51
<alkisg>
nope :)
20:51
<cellofellow>
pity
20:51
maybe I'll just disable my ldm and use the shell screen.
20:53
<alkisg>
You can just modify a little any of those scripts, e.g. rdesktop, and put "SCREEN_07=yourscript"...
20:53
<cellofellow>
yeah
20:54
so, how do I pass a PORT variable to myscript?
20:54
using ltsp.conf
20:54
<alkisg>
All lts.conf variables should already be sourced without you doing anything
20:55
(keep the `. /usr/share/ltsp/screen-x-common` though)
20:56
<cellofellow>
huh? so, I could just put something in there like CINELERRA_PORT_01=4000 and access that?
20:56
<alkisg>
Yup
20:56
<cellofellow>
ok, awesome
20:56
<alkisg>
That's the good thing about using a framework, as opposed to trying to implement fat clients from scratch :)
21:08alkisg has quit IRC
21:21sweetpi has joined #ltsp
21:26jhutchins_lt has joined #ltsp
21:42dgroos1 has left #ltsp
21:43jhutchins_lt has quit IRC
22:07dgroos has quit IRC
22:14irule has quit IRC
22:47cellofellow has quit IRC
23:02mistik1 has quit IRC
23:03mistik1 has joined #ltsp