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


Channel log from 23 April 2014   (all times are UTC)

00:01gdi2k has joined IRC (gdi2k!~gdi2k@180.190.224.53)
00:23telex has left IRC (telex!~telex@freeshell.de, Remote host closed the connection)
00:24telex has joined IRC (telex!~telex@freeshell.de)
00:25gdi2k has left IRC (gdi2k!~gdi2k@180.190.224.53, Ping timeout: 240 seconds)
00:29gdi2k has joined IRC (gdi2k!~gdi2k@180.190.224.53)
00:36gdi2k has left IRC (gdi2k!~gdi2k@180.190.224.53, Ping timeout: 240 seconds)
00:37gdi2k has joined IRC (gdi2k!~gdi2k@180.190.224.53)
00:44gdi2k has left IRC (gdi2k!~gdi2k@180.190.224.53, Ping timeout: 276 seconds)
00:48lmds_ has left IRC (lmds_!~lmds@tui.pi-et-ro.net, Ping timeout: 240 seconds)
00:50lmds_ has joined IRC (lmds_!~lmds@tui.pi-et-ro.net)
01:53Ark74 has joined IRC (Ark74!~Ark74@189.214.42.128.cable.dyn.cableonline.com.mx)
02:13paulv__ has joined IRC (paulv__!485603af@gateway/web/freenode/ip.72.86.3.175)
02:29john___ has joined IRC (john___!a5546a05@gateway/web/freenode/ip.165.84.106.5)
02:43john___ has left IRC (john___!a5546a05@gateway/web/freenode/ip.165.84.106.5, Ping timeout: 240 seconds)
03:30paulv__ has left IRC (paulv__!485603af@gateway/web/freenode/ip.72.86.3.175, Ping timeout: 240 seconds)
04:58freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)
06:24lmds_ has left IRC (lmds_!~lmds@tui.pi-et-ro.net, Ping timeout: 276 seconds)
06:26lmds_ has joined IRC (lmds_!~lmds@tui.pi-et-ro.net)
06:41mealstrom has left IRC (mealstrom!~Thunderbi@46.63.63.163, Ping timeout: 265 seconds)
07:17work_alkisg is now known as alkisg
07:24mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.71.254)
07:31flo1546796 has joined IRC (flo1546796!~flo154679@2001:660:5001:156:26be:5ff:fe13:f2db)
07:31flo1546796 has joined IRC (flo1546796!~flo154679@unaffiliated/flo1546796)
07:43hboomsma has left IRC (hboomsma!~hboomsma@office.hostnetbv.nl, Quit: Leaving)
08:03bennabiy has left IRC (bennabiy!~Thunderbi@96-37-209-0.dhcp.leds.al.charter.com, Ping timeout: 255 seconds)
08:04bennabiy has joined IRC (bennabiy!~Thunderbi@96-37-209-0.dhcp.leds.al.charter.com)
08:05adrianorg has left IRC (adrianorg!~adrianorg@177.132.217.108, Read error: Operation timed out)
08:07adrianorg has joined IRC (adrianorg!~adrianorg@177.204.157.64.dynamic.adsl.gvt.net.br)
08:22freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Ping timeout: 240 seconds)
08:35freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)
08:53adrianorg has left IRC (adrianorg!~adrianorg@177.204.157.64.dynamic.adsl.gvt.net.br, Ping timeout: 240 seconds)
08:54adrianorg has joined IRC (adrianorg!~adrianorg@177.156.226.215)
09:13alkisg has left IRC (alkisg!~alkisg@plinet.ioa.sch.gr, Ping timeout: 264 seconds)
09:30work_alkisg has joined IRC (work_alkisg!~alkisg@194.63.234.224)
09:36freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Quit: So long and thanks for all the fish.)
09:38Gremble has joined IRC (Gremble!~Ben@host-92-27-135-217.static.as13285.net)
09:38Gremble is now known as Guest92413
09:51Ano has joined IRC (Ano!5a506921@gateway/web/freenode/ip.90.80.105.33)
09:54
<Ano>
Hello ! I changed the file /opt/ltsp/i386/etc/lts.conf ( which is part of the chroot, tell me if I'm wrong) to enable usb device. Which service do I have to reload to change the configuration ?
09:57
<Ark74>
Ano, you are assuming that we know a lot of stuff about your system, but first comes first. The file you should edit is: /var/lib/tftpboot/ltsp/i386/lts.conf
09:58
and you only need to reboot the (thin) client to enable the changes on the file
10:00
<Ano>
Thanks, didn't know the chroot folder tree could change from a dsitro to an other. I wanna be more explicite if that doesn't work
10:01
explicit*
10:03
<Ark74>
sure, test it out, also for usb support, have you add the client user to the fuse group??
10:06
<Ano>
Nope I read something about that but it was not explain, I thought it was for server and clients using fuse
10:06
I made a mistake obviously
10:07
I will try to catch it again
10:07Guest92413 has left IRC (Guest92413!~Ben@host-92-27-135-217.static.as13285.net, Ping timeout: 252 seconds)
10:08adrianorg has left IRC (adrianorg!~adrianorg@177.156.226.215, Ping timeout: 252 seconds)
10:09Guest92413 has joined IRC (Guest92413!~Ben@host-92-27-135-217.static.as13285.net)
10:10adrianorg has joined IRC (adrianorg!~adrianorg@177.156.226.215)
10:16
<Ano>
It works
10:16
Thank you Ark74
10:17ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Read error: Operation timed out)
10:17
<Ark74>
you're welcome :)
10:24ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
10:26
<Ano>
I have questions about chroot, I read the doc about it, which is clear but unprecise. Tell me if describes chroot is boring for you. So there is my first question
10:27GrembleBean has joined IRC (GrembleBean!~Ben@host-92-27-135-217.static.as13285.net)
10:27
<Ano>
If the chroot is an independant tree can I install stuffs only on it ? Stuff could be users, packages. . .
10:28Guest92413 has left IRC (Guest92413!~Ben@host-92-27-135-217.static.as13285.net, Ping timeout: 252 seconds)
10:28
<Ark74>
Ano, i'm going to bed, just quick pointers. Sure you can install packages, set up users. But AFAIK you shouldn't use chroot users
10:29
if you wanna use chroot apps, then you need to enable "local apps"
10:30
install the applications on the chroot, will decrease the bandwith but increase the use of local resources on thin clients
10:30
installing them **and enabling them**
10:31
the local apps is also enabled at lts.conf
10:31
<Ano>
Thanks for the answer, I'll reflect about that
10:31
<Ark74>
hope it gave you an quick overview
10:31
<Ano>
Yes you have =)
10:32
gooden nacht
10:32
<Ark74>
ok, see you later
10:34* Ark74 realize that it's almost dawn O_O!
10:35
<Ano>
What ? The night ?
10:41
Thanks for the support ! See around
10:41Ano has left IRC (Ano!5a506921@gateway/web/freenode/ip.90.80.105.33, Quit: Page closed)
10:52GrembleBean has left IRC (GrembleBean!~Ben@host-92-27-135-217.static.as13285.net, Read error: Operation timed out)
11:05GrembleBean has joined IRC (GrembleBean!~Ben@host-92-27-135-217.static.as13285.net)
11:10GrembleBean has left IRC (GrembleBean!~Ben@host-92-27-135-217.static.as13285.net, Ping timeout: 252 seconds)
11:13MrV has left IRC (MrV!~Edgar@31.163.201.104, Ping timeout: 240 seconds)
11:15GrembleBean has joined IRC (GrembleBean!~Ben@host-92-27-135-217.static.as13285.net)
11:24GrembleBean has left IRC (GrembleBean!~Ben@host-92-27-135-217.static.as13285.net, Quit: I Leave)
11:27MrV has joined IRC (MrV!~Edgar@31.163.201.104)
11:28adrianorg has left IRC (adrianorg!~adrianorg@177.156.226.215, Ping timeout: 264 seconds)
11:29adrianorg has joined IRC (adrianorg!~adrianorg@177.134.56.147)
11:30work_alkisg is now known as alkisg
11:30|Paradox| has left IRC (|Paradox|!~iamparado@c-24-125-247-216.hsd1.va.comcast.net, Ping timeout: 276 seconds)
11:48adrianorg has left IRC (adrianorg!~adrianorg@177.134.56.147, Ping timeout: 265 seconds)
11:55adrianorg has joined IRC (adrianorg!~adrianorg@179.187.26.91.dynamic.adsl.gvt.net.br)
12:05
<alkisg>
!socat
12:05
<ltsp>
socat: One way to share a console with a remote person is: [local pc] forward port 5500; apt-get install socat; socat tcp-listen:5500,keepalive=1 stdio,raw,echo=0 [remote pc] apt-get install socat screen; socat SYSTEM:"sleep 1; exec screen -xRR ra",pty,stderr tcp:REMOTE-IP:5500 & screen -l -S ra
12:07freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)
12:34mealstrom has left IRC (mealstrom!~Thunderbi@46.63.71.254, Quit: mealstrom)
12:34mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.71.254)
13:02mgariepy has left IRC (mgariepy!mgariepy@ubuntu/member/mgariepy, Remote host closed the connection)
13:04mgariepy has joined IRC (mgariepy!mgariepy@ubuntu/member/mgariepy)
13:35wouter has joined IRC (wouter!~wouter@barbershop.grep.be)
13:36
<wouter>
so, I've installed ltsp-server-standalone on a wheezy machine, which apparently defaults to NFS
13:36
how do I change things so it uses NBD instead?
13:36* wouter <- nbd userland maintainers, not going to use NFS if I can avoid it ;-)
13:36
<wouter>
s/maintainers/maintainer/
13:39
<alkisg>
Hi wouter
13:39
Have you ran ltsp-build-client?
13:40
Btw thanks for all the nbd fixes :)
13:40
After ltsp-build-client, run `ltsp-update-image --config-nbd`
13:41
<wouter>
alkisg: I have done that, but it still uses nfs
13:41
I may not have done things in the right order, though
13:41
<alkisg>
Then either edit /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default, so that ltsp-NBD is first, or edit BOOT_METHODS in $CHROOT/etc/ltsp/update-kernels.conf, then update-initramfs -u, then update kernels
13:41
<wouter>
aaaahh
13:41
that's inside the chroot?
13:41
I was looking for that file _outside_ the chroot :-)
13:41
<alkisg>
The second method yes
13:41
It's per chroot
13:42
The first method basically means "I edited pxelinux.cfg/default manually, don't automatically update that file anymore"
13:42
<wouter>
fair enough
13:42* wouter runs ltsp-update-image
13:43
<wouter>
I guess it failed because I ran things out of order
13:43
I ran ltsp-update-image before ltsp-build-client
13:43
well, that is
13:43
before ltsp-build-client was finished running
13:43
I ran it again, but then the update-kernels.conf was probably overwritten
13:44
<alkisg>
Nah... ltsp-update-image --config-nbd actually creates /etc/nbd-server/conf.d/<chroot>.conf
13:44
It prepares the server, not the chroot
13:44
But, there's a second step required on a per-chroot basis, i.e. pxelinux.cfg
13:45
<wouter>
mm, pxelinux.cfg still defaults to ltsp-NFS
13:46
<alkisg>
Check $CHROOT/boot/pxelinux.cfg/, is it still NFS there?
13:46
<wouter>
ah, but that's because I changed the wrong thing in update-kernels.conf, I suppose
13:47* alkisg isn't using debian yet, so he might have missed some step, like e.g. running /usr/share/ltsp/update-kernels inside the chroot :)
13:47
<wouter>
mm, no, that still isn't working
13:48
<alkisg>
$CHROOT/etc/ltsp/update-kernels.conf : BOOT_METHODS="NBD NFS AOE"
13:48
chroot $CHROOT /usr/share/ltsp-update-kernels
13:48
check $CHROOT/boot/pxelinux.cfg/*
13:48
Is NBD first?
13:49
<wouter>
only contains NBD, currently
13:49
<alkisg>
Then, ltsp-update-image gets it inside i386.img, and ltsp-update-kernels gets it from there and copies it to the server's tftp
13:50
I.e. ltsp-update-kernels reads i386.img, not the $CHROOT
13:50
<wouter>
ah
13:50
okay
13:51
nope, still no joy
13:52
<alkisg>
Is pxelinux.cfg/default a symlink to pxelinux.cfg/ltsp ?
13:52* alkisg doesn't remember if we changed that before or after wheezy...
13:52
<wouter>
no, it's a simple file
13:52
<alkisg>
In the chroot, does pxelinux.cfg/default exist? Does it get autoupdated? (check date)
13:53
$CHROOT/boot/pxelinux.cfg/default
13:53
<wouter>
the one outside does autoupdate, because when I fix it manually and run update-kernels again, the nbd option is back to nfs
13:53
where should pxelinux.cfg be inside the chroot?
13:53
<alkisg>
(04:53:14 μμ) alkisg: $CHROOT/boot/pxelinux.cfg/default
13:53
Check both the chroot and i386.img (loop-mount it)
13:54
If i386.img is older and contains nfs, run ltsp-update-image again
13:54
<wouter>
amd64.img, but yes, I'll do that :)
13:55
same timestamp
13:56Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
13:56* alkisg shrugs... I could check via vnc if you like... x11vnc -connect srv1-dide.ioa.sch.gr
13:58
<wouter>
should be running now
14:00
okay, that's probably what I missed, then
14:00
eeps
14:00
right, sorry
14:00
I assume ltsp-update-kernels is only necessary when installing a new kernel?
14:01
<alkisg>
Normally yes, but it's also used manually if you change update-kernels.conf and need a new pxelinux.cfg/default
14:01
<wouter>
right
14:01
<alkisg>
It's triggered automatically by kernel postinst hooks
14:01
<wouter>
okay
14:01
things *seem* fine now
14:01* wouter test-boots a tc
14:02
<wouter>
yup, seems to work
14:02
:-)
14:03
except for the bit where I broke login... I can fix that, though
14:04
<alkisg>
wouter: have you ever tried anything related to caching on the client side? E.g. I'm thinking of using dmcache to cache whatever parts of amd64.img are read from the network, in a local disk on the client, so that on subsequent reads (even on subsequent boots) the local copy is used...
14:04
Or would it be better to implement caching inside nbd-client?
14:05
Example use case, having 100 fat clients (nbd image >> 1 GB) on e.g. a 100 mbps network... automatic local caching there would *a lot*
14:06
<wouter>
alkisg: I've heard of people trying dmcache, but they weren't very successful
14:08
<alkisg>
Ouch... would it be possible for someone to implement it inside nbd-client? Not necessarily upstream, if it's not a feature you'd like to see added...
14:08
<wouter>
nbd-client isn't the right place for that kind of stuff
14:09
I do agree it'd be nice if that would work, but adding that to nbd-client is a layering violation if I've ever heard one
14:09
<alkisg>
I think xnbd implemented something similar as part of their xnbd-server, not in the -client
14:09
<wouter>
they implement auto syncing between two servers, not quite the same thing
14:09
<alkisg>
They support local caching afaik
14:10
True, it's not exactly the same thing...
14:10
So, forking e.g. nbd-client into ltsp-nbd-client-that-supports-read-only-local-caching, wouldn't be a good idea?
14:10
I should look to implement that elsewhere?
14:11
<wouter>
dmcache *should* work
14:11
I didn't try it myself
14:11
"someone else failed" doesn't mean "it will fail for you", nor "it's a bad idea" :-)
14:11
I think that's the way to go
14:11
<alkisg>
Thanks... I'll start experimenting with that, then
14:11
Do you have 2 minutes to chat about https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/696454 too?
14:12
I.e. about connection closing, client-side
14:12
You mentioned, "Instead, I suggest you look into having the kernel send out NBD_CMD_DISC on its own at poweroff. I'm sure Paul will accept such a patch."
14:12
<wouter>
not right now -- at a customer
14:12
<alkisg>
OK, np
14:12
<wouter>
thanks for your help, though :-)
14:12
<alkisg>
The problem there is that we need `ifconfig eth0 down`, otherwise it won't poweroff correctly
14:13
k, later :)
14:15alkisg is now known as work_alkisg
14:26
<bennabiy>
work_alkisg: Did you get my posts about how to make a mint demo of 14.04?
14:26
<work_alkisg>
bennabiy: to ask it in the mint IRC channel? yup... did you get one yet?
14:27flo1546796 has left IRC (flo1546796!~flo154679@unaffiliated/flo1546796, Quit: Quitte)
14:28
<bennabiy>
One thing they suggested is to install 14.04, then install mate 1.8 manually, and then add the mint repo for upstream deb http://packages.linuxmint.com qiana main upstream import and install mint-meta-core and mint-meta-mate and then I think the mint artwork
14:28
If you want a quick and dirty rough tester until the RC in 2 weeks or so
14:31work_alkisg1 has joined IRC (work_alkisg1!~alkisg@plinet.ioa.sch.gr)
14:31
<work_alkisg1>
Sorry, power failure...
14:31
<bennabiy>
You can also pick and choose packages that might apply and just apply them to your situation in 14.04
14:31
http://packages.linuxmint.com/list.php?release=Qiana
14:32
work_alkisg1: welcome back
14:32
<work_alkisg1>
Nah, I'd like to check its overall quality, not just specific packages, to see if it's more suitable than gnome-fallback for schools here
14:33
<bennabiy>
One thing they suggested is to install 14.04, then install mate 1.8 manually, and then add the mint repo for upstream deb http://packages.linuxmint.com qiana main upstream import and install mint-meta-core and mint-meta-mate and then I think the mint artwork
14:33work_alkisg has left IRC (work_alkisg!~alkisg@194.63.234.224, Ping timeout: 240 seconds)
14:33
<work_alkisg1>
Currently the main issue we have left with gnome-fallback, is that ubuntu broke the keyboard indicator with its customized panel/indicators etc
14:33work_alkisg1 is now known as work_alkisg
14:33
<bennabiy>
that hurts
14:33
How long has that been broken?
14:34
<work_alkisg>
And the "new way to do things" doesn't work in many cases, e.g. shortcuts don't work, layout switching in SDL apps doesn't work, etc etc
14:34
I only use LTS releases so I only know it broke after 12.04, it wasn't broken then
14:35
Well, it was broken in 3 other places, again only due to ubuntu-specific changes, but we managed to work around those issues
14:35
Anyway, time to go, bb guys, later...
14:39Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Remote host closed the connection)
15:18nintendo1889 has joined IRC (nintendo1889!uid23646@gateway/web/irccloud.com/x-aokkwrbibrycubjq)
15:18
<nintendo1889>
hello everybody
15:20
<Hyperbyte>
Hi!
15:26paulv_ has left IRC (paulv_!466e7c4f@gateway/web/freenode/ip.70.110.124.79, Ping timeout: 240 seconds)
15:37mealstrom has left IRC (mealstrom!~Thunderbi@46.63.71.254, Ping timeout: 252 seconds)
16:04bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
16:06Ark74 has left IRC (Ark74!~Ark74@189.214.42.128.cable.dyn.cableonline.com.mx, Remote host closed the connection)
16:13bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Read error: Operation timed out)
16:14ncd209 has joined IRC (ncd209!~ncd209@83-244-242-194.cust-83.exponential-e.net)
16:14
<ncd209>
how can I check my clients nic speed?
16:14
thats been negotiated
16:25
<||cw>
miitool?
16:33mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.21.12)
18:42telex has left IRC (telex!~telex@freeshell.de, Remote host closed the connection)
18:44telex has joined IRC (telex!~telex@freeshell.de)
19:03imox has joined IRC (imox!~imox@p57A9688A.dip0.t-ipconnect.de)
19:06imox has left IRC (imox!~imox@p57A9688A.dip0.t-ipconnect.de, Client Quit)
19:49
<Zaphoid>
For larger implementations under Ubuntu 12.04.4, is it suggested to use nbd or nfs?
19:50freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Quit: So long and thanks for all the fish.)
19:55
<||cw>
Zaphoid: compressed nbd should use less bandwidth
19:56
<Zaphoid>
||cw: That was my assumption, but I'm having an issue where clients seem to be disconnecting for no apparent reason.
19:57
The clients don't realize it until they attempt to access something new, fail the reconnect, and then have squashfs errors due to the obvious problem of being unable to access their root partition.
19:58
<||cw>
there was some discussion a few days ago http://irclogs.ltsp.org./?d=2014-04-17 around the hour 20 mark
19:59
there's also discussion earier that day on how to switch, seems like it's not too hard to toggle back and forth
19:59
<Zaphoid>
Thanks, I'll read through. Been trying to find mention of it in the logs, but the searchy thing won't let me search for "nbd" without specifying a user name
19:59
<||cw>
yeah
20:00
I added alkisg's name since he's one of the main gurus here :)
20:00
<Zaphoid>
The issue I've been running into lately has been 2 - 5 hours after a full system reboot, a subset of the clients will disconnect.
20:00
I'll remember that
20:01
<||cw>
how many clients?
20:01
<Zaphoid>
I have one 20 client install where, after a full reboot, 6 - 7 of the stations will all disconnect roughly 2 hours and 20 minutes after they start up. Different 6 - 7 each time.
20:01
<||cw>
I have a dozen or so and haven't had any issues
20:01
<Zaphoid>
I'm looking at a 60 station install shortly, but would really like to figure this out before I implement that
20:03
<||cw>
my "netstat -anp | grep nbd | wc -l" shows 21 sockets, basically doing fat clients, server is a single vcpu 512MB ram virtual machine
20:05
<Zaphoid>
Interesting. I show 24 lines. Similar setup. VM with 1gb of ram, fat clients, etc, etc. Using the Intel NUCs
20:06
When the disconnect happens, the socket disappears, obviously.
20:08
Reading the netstat more carefully, two stations have two sockets open...
20:09
What is the average uptime on your dozen or so? Do they ever go down unexpectedly?
20:10
<||cw>
if they do i don't hear about it, they really just run rdesktop though
20:11
some are used around the clock 5 days a week though, and it was resetting all the time I'd likely hear about it
20:12
checked a random one, uptime 8 days
20:12
<Zaphoid>
OK. I have some that are super stable (80+ day runtime at this point). ANd it seems if they get past the first couple days of uptime, they are great. Just the first 48 hours seem to be rough
20:14phanh has joined IRC (phanh!c6ec0023@gateway/web/freenode/ip.198.236.0.35)
20:15
<phanh>
hello
20:16
Anyone can offer us some advices about server spec for ltsp-cluster project plz?
20:18phanh has left IRC (phanh!c6ec0023@gateway/web/freenode/ip.198.236.0.35, Client Quit)
20:31
<Zaphoid>
||cw: I'm reading a lot about alkisg talking about AOE around the end of last year, first of this year. Is that still a thing people are considering?
20:31nintendo1889 has left IRC (nintendo1889!uid23646@gateway/web/irccloud.com/x-aokkwrbibrycubjq)
20:31
<||cw>
not that I've seen
20:35
<Zaphoid>
OK
21:14imox has joined IRC (imox!~imox@p57A9688A.dip0.t-ipconnect.de)
21:15imox has joined IRC (imox!~imox@p57A9688A.dip0.t-ipconnect.de)
21:22gbaman has left IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com, Remote host closed the connection)
21:29
<Zaphoid>
||cw: Have you seen an nbd error of: Read failed: Inappropriate ioctl for device
21:32
<||cw>
only when I've rebuilt the image
21:32
<Zaphoid>
That is what comes up when the client attempts to access the root partition after the disconnect.
21:32
Well, the connect gets attempted, then the read fails
21:32
Then sQUASHFS errors
21:33
<||cw>
well, yeah
21:33
but that's just a side effect
21:33gbaman has joined IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com)
21:33
<Zaphoid>
Yes
21:34
Expected when the root partition is pulled out from under it
21:35
Found a debian bug that talks about it (he was using it for swap partition) that is unresolved.
21:35
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656258
21:38imox has left IRC (imox!~imox@p57A9688A.dip0.t-ipconnect.de, Quit: imox)
21:40
<Zaphoid>
||cw: What ubuntu are you running off of?
21:41
<||cw>
I have a 10.04 and a 13.10
21:41
the 13.10 is just out of testing though, not full production yet
21:41
<Zaphoid>
What nbd-server versions are those running?
21:42
<||cw>
2.9.14-2 and 3.3-3
21:42
package versions
21:42dave has joined IRC (dave!7a3e10cb@gateway/web/freenode/ip.122.62.16.203)
21:42
<Zaphoid>
OK
21:43dave is now known as Guest16445
21:44
<Zaphoid>
Informational, I suppose
21:44
I'm kinda grasping at straws.
21:44
<Guest16445>
I am having two services running on the same Ubuntu machine: Samba4 AD and LTSP 5
21:46
I am trying to integrate both of them so that I can use Samba4 AD users with LTSP server.
21:46
But when I do that user receive disconnection on the remote host.
21:46
Can anyone help me with this?
21:47
<||cw>
Guest16445: can you login to the desktop locally with an AD user?
21:47
and can you ssh in as an AD user?
21:49
<Guest16445>
from which machine?
21:50
for localhost yes
21:50
for the LTSP client machine (thin client) no
21:50
<||cw>
and ssh ?
21:50
<Guest16445>
same for SSH as well. I can loging on localhost using SSH
21:51
<||cw>
from any other computer?
21:51
<Guest16445>
but I cannot login to thinclient machine with SSH
21:51
<||cw>
well, no, it only has a root user
21:51
but the graphical login is presented from the server
21:52
<Guest16445>
okay. But when i am using two different servers, one for the LTSP and one for the Samba it is working fine
21:52
I read somewhere that LTSP uses ssh for the autentication
21:53
<||cw>
it does.
21:53vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
21:54
<||cw>
I'm not totally sure how all that works though.
21:54
<Guest16445>
so do I have to modify my sshd_conf for that ?
21:54
okay
21:54
<Zaphoid>
To be able to ssh into the ltsp client, you'll need to modify the sshd_conf on the client to allow either root logins, or create a user for that purpose
21:54
<||cw>
I'd expect that if you can ssh as an AD user, then it would work
21:55
but if you want to use an ad user to login to the client itself, you'd need to modify a lot of things
21:55
<Guest16445>
ssh to which machine ? localhost or thin client?
21:55
<||cw>
to the server
21:56
<Guest16445>
yes i was expecting the same
21:56
<||cw>
typically you dont ever connect to the client itself
21:57
<Guest16445>
do you know which file does LTSP use to identify the list of users ?
21:58
Because by default it should use /etc/passwd
22:00
<||cw>
it uses pam, i think
22:00
gotta run though
22:02
<Guest16445>
cool cheers
22:04
<vagrantc>
Guest16445: what do you mean by identify the users?
22:04
client-side or server-side?
22:21
<Guest16445>
on the server side when i run getent passwd
22:22
it gives me all ad users
22:22
but when i tried to login with those ad users it authenticates and then receive disconnection by user
22:23
<vagrantc>
can you ssh to the server as one of those AD users?
22:23
<Guest16445>
yes i can
23:15mealstrom has left IRC (mealstrom!~Thunderbi@46.63.21.12, Ping timeout: 252 seconds)
23:51Guest16445 has left IRC (Guest16445!7a3e10cb@gateway/web/freenode/ip.122.62.16.203, Quit: Page closed)