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


Channel log from 19 September 2017   (all times are UTC)

00:09GodFather has left IRC (GodFather!~rcc@47.33.250.142, Ping timeout: 240 seconds)
00:41GodFather has joined IRC (GodFather!~rcc@47.33.250.142)
01:00dgroos has joined IRC (dgroos!~dagro001@vpn.mpls.k12.mn.us)
01:01
<dgroos>
troubleshooting of AD/pbis-open/ltsp moves forward…
01:03* vagrantc hides
01:03
<dgroos>
I’m needing to open terminal, root locally via epoptes. The Xterm opens but it has no prompt, just the cursor
01:03
:-D
01:04
sorry!
01:04
So actually, just trying to get the xterm to work so I can test the school computers from my house.
01:06
<vagrantc>
just use a virtual machine...
01:06GodFather has left IRC (GodFather!~rcc@47.33.250.142, Ping timeout: 240 seconds)
01:06
<dgroos>
But I just had a thought about the client terminal not working properly: I made a xterm default conf file in my home dir and maybe that is messing things up?
01:06
<vagrantc>
dgroos: also, pretty serious about seeing if it works with ltsp-build-client --fat-client
01:07
dgroos: that will more easily confirm the issue of weather there are conflicting rules for pam than manually reverting everyrthing
01:07GodFather has joined IRC (GodFather!~rcc@47.33.250.142)
01:08
<dgroos>
I’ve used vm’s before a good bit but still I don’t really know how to set it up exactly, but will figure it out if the current lead doesn’t move the problem-solving forward…
01:09
The person at pbis-open had the idea that the RequireMembershipOf setting was getting messed up.
01:10
So I checked on the server and it was properly set, then was trying to go into a client I launched with epoptes, but then got stuck since I can’t run a command on the client!
01:10
That would bring the problem on the client into greater resolution.
01:13
So, looks like I need to test this tomorrow in the classroom since not getting it to work from home.
01:14
vagrantc: what’s the difference between the —cleanup / and —fat-client commands?
01:16
<vagrantc>
dgroos: well, the command for "ltsp-update-image --cleanup /" and the "ltsp-build-client --fat-client" are two totally different commands.
01:16
ltsp-build-client builds a chroot in /opt/ltsp/ARCH and then builds /opt/ltsp/images/ARCH.img out of that
01:17
"ltsp-update-image --cleanup /" builds an image in /opt/ltsp/images/ARCH.img out of the server's /
01:18
dgroos: if you built your ltsp environment in a chroot, it won't have any of the AD configuration
01:19
normally, the ltsp-pnp method is much simpler and easier, but once you go messing with arbitrary configuration files on the server, we can't always sanitize the resulting LTSP image because we're not omniscient
01:20
<dgroos>
*dgroos looks disappointed…
01:21
OK. Where does the ltsp-build-client get it’s info from to create the chroot.
01:21
?
01:22
<vagrantc>
by default, a distribution mirror
01:22
<dgroos>
the desktop’s system minus anything added after install?
01:22
<vagrantc>
e.g. Ubuntu, Debian
01:22
<dgroos>
Oh…
01:22
<vagrantc>
by default, it'll create a thin-client image, hence the --fat-client parameter
01:24
<dgroos>
So, if I just ran the command on server (via ssh from home) right now I’d get this chroot-then-img w/out pbis stuff?
01:24
<vagrantc>
dgroos: just
01:24
dgroos: er, yes
01:24
dgroos: it would replace your existing image, but that's easy enough to recreate, right?
01:25
dgroos: you're running ubuntu?
01:25
<dgroos>
yes, from my effort it’s just a few letters in the right place, from the computers perspective it is the instructions for an ant colony to build a castle…
01:25
yes
01:25
16.04.3
01:27
am rebooting the server, then will: sudo ltsp-build-client —fat-client
01:27
<vagrantc>
dgroos: so, "ltsp-build-client --fat-client"
01:27
why reboot the server?
01:29
<dgroos>
um… I just tried to run epoptes and got lots of GtkWarnings: so thought I would clean that up… it was quick.
01:31
just checking—that’s sudo… right?
01:31
<vagrantc>
yes, you'll need to run it with root privledges
01:33
<dgroos>
Got…NOTE: Root directory /opt/ltsp/amd64 already exists, this will lead to problems, please remove it before trying again. Exiting.
01:33
error: LTSP client installation ended abnormally
01:33
so… I’ll delete that directory, yes?
01:35
<vagrantc>
sounds like you've done that before
01:35
move it aside if you're at all unsure about what it's doing there ...
01:36
mv /opt/ltsp/amd64 /opt/ltsp/old-amd64
01:37
<dgroos>
got it!
01:38
brb
01:47lucascastro has joined IRC (lucascastro!~lucas@186.193.179.228.jupiter.com.br)
01:50adrianor1 has joined IRC (adrianor1!~adrianorg@189.58.238.64.dynamic.adsl.gvt.net.br)
01:51
<dgroos>
back!
01:52
OK will mv it. I first installed with the ‘old’ ltsp-pnp page, then I installed/ran ltsp-manager. maybe that was it?
01:53adrianorg has left IRC (adrianorg!~adrianorg@177.18.102.121, Ping timeout: 240 seconds)
01:55
<dgroos>
it’s running.
01:56
vagrantc: will it change any of my dnsmasq settings? I’ve commented out the proxy line so other computers in the school don’t PXEboot Ubuntu.
01:57GodFather has left IRC (GodFather!~rcc@47.33.250.142, Ping timeout: 240 seconds)
01:58
<vagrantc>
dgroos: no, it just builds a chroot in /opt/ltsp/amd64 and then generates an image in /opt/ltsp/images/amd64.img and copies the appropriate kernel/initrd/boot files into the tftp directory
01:58rkwesk has joined IRC (rkwesk!4f827c78@gateway/web/freenode/ip.79.130.124.120)
02:00
<rkwesk>
vagrantc: hello from Greece
02:01
<dgroos>
k, thanks vagrantc, for all this info and help.
02:01
<rkwesk>
vagrantc: in preparation for writing documentation for ltsp for stretch and buster
02:02
vagrantc: any preferences for my clean install of basic system before ltsp?
02:03
vagrantc: one nic or two. dhcpd or dnsmasq ?
02:04
vagrantc: netinstalls are ok?
02:09
vagrantc: sysvinit or systemd? hopefully older box with bios ok cause I have no uefi box now and i386 versions
02:12
<dgroos>
hmmm… just finished running: sudo ltsp-build-client --fat-client and after doing many many things it concluded with:
02:12
<rkwesk>
vagrantc: both ltsp-pnp and separate chroot versions? (obviously not at same time)
02:12
<dgroos>
No LTSP chroots found, please run ltsp-build-client
02:12
error: LTSP client installation ended abnormally
02:12
problem?
02:14
<rkwesk>
dgroos: David, have you included a desktop and xorg in chroot first?
02:14
<vagrantc>
rkwesk: ya sas!
02:14* vagrantc might spell it abysmally
02:14
<vagrantc>
gia?
02:15
dgroos: wow... you got it rought
02:15
<rkwesk>
vagrantc: geia is better but remember it is transliterated from another alphabet
02:16
<vagrantc>
rkwesk: :)
02:16
rkwesk: as far as documentation goes, i think we should move to describing the ltsp-pnp method as preferred
02:17
rkwesk: once we get ltsp-manager into debian, we can recommend that.
02:17
<rkwesk>
vagrantc: ok. what about other questions?
02:18
<vagrantc>
rkwesk: what do you mean by netinstall?
02:18
rkwesk: i don't think the init system matters enough to say one or the other ... it's basically not relevent as far as i'm concerned
02:19
<rkwesk>
vagrantc: an iso that uses almost all pkgs from Internet rather than from iso
02:19
<vagrantc>
rkwesk: the chroot documentation would be good, but i'd put it as the alternate method
02:19
rkwesk: i think installing debian is a bit out of scope ... the assumption should be that you have debian installed already
02:20
<dgroos>
rkwesk: ah, not yet I think…
02:20
vagrantc: rought? probably that’s not good…
02:20
<rkwesk>
vagrantc: if I recall stretch still defaults to sysvinit not systemd
02:20
<vagrantc>
dgroos: did you get any more messages above that indicating why it failed?
02:20
dgroos: rough is what i meant to say
02:21
rkwesk: no, it's been systemd by default since jessie
02:21
rkwesk: but really, the init system isn't (yet) significant for LTSP
02:21
<rkwesk>
vagrantc: aha, ok
02:22
<dgroos>
vagrantc: right.
02:22
<vagrantc>
rkwesk: did i miss any of your questions? :)
02:22
<dgroos>
I see this: Setting up thermald (1.5-2ubuntu4) ...
02:22
Running in chroot, ignoring request.
02:22
invoke-rc.d: policy-rc.d denied execution of start.
02:22
<vagrantc>
that should be fine
02:22
<rkwesk>
vagrantc: my questions were mainly about preparing a blank disk before installing ltsp but not documenting that part
02:23
<dgroos>
And these don’t look good: Creating config file /etc/default/grub with new version
02:23
grub-probe: error: cannot find a device for / (is /dev mounted?).
02:23
grub-probe: error: cannot find a device for /boot (is /dev mounted?).
02:23
grub-probe: error: cannot find a device for /boot/grub (is /dev mounted?).
02:23* vagrantc wonders why grub is installed at all
02:24
<vagrantc>
dgroos: another option ... try without the fat-client ... we can add that later
02:24
<dgroos>
? um? I did a normal install and isn’t that a part of a normal install?
02:24
OK
02:24
<vagrantc>
dgroos: not for LTSP
02:24
<rkwesk>
dgroos: have you used mount -o bind /dev/ /path of chroot/dev
02:25
<vagrantc>
dgroos: first purge /opt/ltsp/* and then re-run ltsp-build-client
02:25
<dgroos>
not since before I started using ltsp-pnp several years back.
02:25
OK
02:25
<vagrantc>
ltsp-build-client is barely maintained ... i test it for debian, not sure anyone tests for ubuntu
02:26
<rkwesk>
dgroos: in order to install desktop and xorg you need a few mounts, starting with one I mentioned
02:28
vagrantc: are you in North America or the Netherlands?
02:29
<dgroos>
OK, trying to regroup here… I’m wondering if maybe it would be best to go back to using sudo ltsp-update-image --cleanup / and see if I can track down the RequireMembershipOf setting on the client image tomorrow.
02:30
I’m doing a lot of things I don’t fully (ok barely) grasp.
02:30
at this point.
02:30
<rkwesk>
vagrantc: at my age I am up at strange hours, surely you are not?
02:31
<vagrantc>
rkwesk: almost as far west as you can get in north america :)
02:31
the wild west is east of here
02:31
<rkwesk>
vagrantc: Hawaii or Guam then?
02:32
vagrantc: I originally hail from Connecticut
02:32
<vagrantc>
rkwesk: continental :)
02:33
<rkwesk>
vagrantc: ok so it is 7:30 pm where you are
02:35
vagrantc: I never travelled to your neck of the woods
02:37
<vagrantc>
rkwesk: don't think i've ever been to connecticut, but visited greece once :)
02:38
<rkwesk>
vagrantc: ok so any netinst iso is ok and pnp first then separate chroot second
02:38
<vagrantc>
rkwesk: sounds fine to me, sure
02:39
<rkwesk>
vagrantc: if you ever think of visiting again I definitely want a heads up so we meet
02:40
rkwesk signing off, waves!
02:40
<vagrantc>
rkwesk: which part of greece?
02:40
<rkwesk>
vagrantc: Athens
02:40
<vagrantc>
rkwesk: you've met alkisg ?
02:41
<rkwesk>
vagrantc: a couple of times when he would com to run a workshop but not lately
02:42
vagrantc: it would be a special treat if we all three met sometime
02:42
<vagrantc>
rkwesk: alright, let's make it happen :)
02:42* vagrantc waves to rkwesk
02:43
<rkwesk>
vagrantc: waves
02:43rkwesk has left IRC (rkwesk!4f827c78@gateway/web/freenode/ip.79.130.124.120, )
02:46
<dgroos>
vagrantc: to return things to how they were… I’ll remove the amd64 that just got built (it’s 4.2 GiB), return /old-amd64 to /amd64 (it’s 20 KiB) then re-run ltsp-update-image —cleanup /
02:46
yes?
02:48adrianor1 is now known as adrianorg
02:50lucascastro has left IRC (lucascastro!~lucas@186.193.179.228.jupiter.com.br, Remote host closed the connection)
02:51
<vagrantc>
dgroos: the old-amd64 shouldn't be used if you're using "ltsp-update-image --cleanup /"
02:51
in fact, it could cause issues
02:54
<dgroos>
OK, I’ll get rid of both of the amd64 dirs, then re-run. Thanks!
03:18
vagrantc: Heading off! I’ll post what I find out tomorrow!
03:19dgroos has left IRC (dgroos!~dagro001@vpn.mpls.k12.mn.us, Quit: dgroos)
03:45vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
04:45mmarconm has joined IRC (mmarconm!~mmarconm@177.7.75.214)
04:46
<mmarconm>
finally i got zsnes installed on ltsp-chroot
04:46
LOL
05:04mmarconm has left IRC (mmarconm!~mmarconm@177.7.75.214, Quit: Leaving)
06:05||cw has left IRC (||cw!~chrisw@unaffiliated/cw/x-1182934, *.net *.split)
06:09Guest32437 has left IRC (Guest32437!bennabiyma@gateway/shell/matrix.org/x-nxibmyqiurikutsp, Ping timeout: 264 seconds)
06:09alexxtasi[m] has left IRC (alexxtasi[m]!alexxtasim@gateway/shell/matrix.org/x-zgwkpddebebkcvss, Ping timeout: 252 seconds)
06:10||cw has joined IRC (||cw!~chrisw@unaffiliated/cw/x-1182934)
06:19Eric5 has joined IRC (Eric5!~eric@sdi.iut-valence.fr)
06:41mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk)
07:18alexxtasi[m] has joined IRC (alexxtasi[m]!alexxtasim@gateway/shell/matrix.org/x-jrmzgztifmeivnte)
07:33Guest85302 has joined IRC (Guest85302!bennabiyma@gateway/shell/matrix.org/x-sjhpjxcljspklfsl)
08:05Eric5 has left IRC (Eric5!~eric@sdi.iut-valence.fr, Ping timeout: 255 seconds)
08:45Eric5 has joined IRC (Eric5!~eric@sdi.iut-valence.fr)
09:46TatankaT has left IRC (TatankaT!~tim@193.190.253.114, Ping timeout: 252 seconds)
09:51Eric5 has left IRC (Eric5!~eric@sdi.iut-valence.fr, Ping timeout: 240 seconds)
09:53TatankaT has joined IRC (TatankaT!~tim@193.190.253.114)
09:54Eric5 has joined IRC (Eric5!~eric@sdi.iut-valence.fr)
10:21GodFather has joined IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net)
10:30ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
10:57Eric5 has left IRC (Eric5!~eric@sdi.iut-valence.fr, Ping timeout: 240 seconds)
11:35stevecook has joined IRC (stevecook!5ad76ee5@gateway/web/freenode/ip.90.215.110.229)
11:39
<stevecook>
Hello. Just testing out the "GUI" pnp ltsp installation. Installed on my bare metal rig and trying to set up a Virtualbox VM client. When booting up the client, it is picking up the fact it needs to boot form the network and goos so far as setting up nbd client. At which point it throws the error "socket failed: connection refused". Is this a problem related to my trying to run the clinet in a VM. Or is it something esle that I can
11:40
<alkisg>
stevecook: the line was too long, it was cut there: Or is it something esle that I can
11:40
There's a problem with /etc/nbd-server/conf.d/ltsp_i386.conf file
11:41
<stevecook>
ah ok#
11:41
Could you let me know how to fix it please Alskig?
11:42
at the moment, that conf file is empty
11:42
I should ssay, this is on ubuntu 32 bit server
11:43
<alkisg>
OK, wait 1 minute...
11:43
<stevecook>
cheers
11:45
<alkisg>
!learn nbd-server-bug as Currently there's an issue with "ltsp-config nbd-server", to fix it run this as root: arch=$(dpkg --print-architecture); printf "[/opt/ltsp/$arch]\nexportname = /opt/ltsp/images/$arch.img\nreadonly = true\nauthfile = /etc/ltsp/nbd-server.allow\n"; service nbd-server restart
11:45
<ltsp>
Error: "/opt/ltsp/$arch" is not a valid command.
11:45
<alkisg>
!learn nbd-server-bug as `Currently there's an issue with "ltsp-config nbd-server", to fix it run this as root: arch=$(dpkg --print-architecture); printf "[/opt/ltsp/$arch]\nexportname = /opt/ltsp/images/$arch.img\nreadonly = true\nauthfile = /etc/ltsp/nbd-server.allow\n"; service nbd-server restart`
11:45
<ltsp>
The operation succeeded.
11:45
<alkisg>
!nbd-server-bug
11:45
<ltsp>
'nbd-server-bug: (#1) nbd-server hanging bug: https://github.com/yoe/nbd/commit/741495cb08503fd32a9d22648e63b64390c601f4, solved in version 3.4-1, or (#2) Currently there\'s an issue with "ltsp-config nbd-server", to fix it run this as root: arch=$(dpkg --print-architecture); printf "[/opt/ltsp/$arch]\nexportname = /opt/ltsp/images/$arch.img\nreadonly = true\nauthfile = /etc/ltsp/nbd-server.allow\n"; service nbd-server (1 more message)
11:46
<alkisg>
!forget nbd-server-bug 2
11:46
<ltsp>
The operation succeeded.
11:46
<alkisg>
!learn ltsp-config-bug as `Currently there's an issue with "ltsp-config nbd-server", to fix it run this as root: arch=$(dpkg --print-architecture); printf "[/opt/ltsp/$arch]\nexportname = /opt/ltsp/images/$arch.img\nreadonly = true\nauthfile = /etc/ltsp/nbd-server.allow\n" > /etc/nbd-server/conf.d/ltsp_$arch.conf; service nbd-server restart`
11:46
<ltsp>
The operation succeeded.
11:46
<alkisg>
!ltsp-config-bug
11:46
<ltsp>
'ltsp-config-bug: Currently there\'s an issue with "ltsp-config nbd-server", to fix it run this as root: arch=$(dpkg --print-architecture); printf "[/opt/ltsp/$arch]\nexportname = /opt/ltsp/images/$arch.img\nreadonly = true\nauthfile = /etc/ltsp/nbd-server.allow\n" > /etc/nbd-server/conf.d/ltsp_$arch.conf; service nbd-server restart'
11:48
<alkisg>
stevecook: that one ^
11:49
<stevecook>
hi alskig. I'm sorry, but i am not clear what precisely of all of that last bit I am supposed to execute. Is it all of this: arch=$(dpkg --print-architecture); printf "[/opt/ltsp/$arch]\nexportname = /opt/ltsp/images/$arch.img\nreadonly = true\nauthfile = /etc/ltsp/nbd-server.allow\n" > /etc/nbd-server/conf.d/ltsp_$arch.conf; service nbd-server restart'
11:50
or is all of that supposed to be done in stages?
11:50
<alkisg>
stevecook: run sudo -i to get a root prompt
11:50
In there, yes, paste all of this, except for the last '
11:50
All in a single line
11:51
Also, alk + tab writes alkisg, so that you don't mistype it ;)
11:51
<stevecook>
ok
11:51
done
11:51
will check out now
11:51
<alkisg>
OK
11:52
<stevecook>
still saying connection refused. Should I rebuild the image and/or reboot server perhaps?
11:52
<alkisg>
No. Now try this:
11:52
!nbd-client
11:52
<ltsp>
nbd-client: To try mounting the NBD image from the client initramfs: nbd-client 192.168.67.1 -N /opt/ltsp/i386 /dev/nbd0
11:53
<alkisg>
...put the server IP there
11:55
You can also try this on the server directly: nbd-client -l localhost
11:55
...to list the available exports
11:57
<stevecook>
that last one threw back: E: listing not allowed by server.
11:58
I am attempting to locate my server ip with the following command: ifconfig | grep inet and am getting the following:
11:59
inet addr:10.42.0.251 Bcast:10.42.0.255 Mask:255.255.255.0
11:59
inet6 addr: fe80::8522:535b:b885:5b38/64 Scope:Link
11:59
inet addr:127.0.0.1 Mask:255.0.0.0
11:59
inet6 addr: ::1/128 Scope:Host
11:59
Is it the first of third dof these?
11:59
<alkisg>
be back in 20'
11:59
<stevecook>
ok
12:13
<alkisg>
stevecook: yes your ip is 10.42.0.251
12:13
(your server ip)
12:14
So from the client initramfs prompt, try: nbd-client 10.42.0.251 -N /opt/ltsp/i386 /dev/nbd0
12:14
<stevecook>
ok, will do. will come on back here in a few moments
12:14
<alkisg>
OK, I'll come back in another 20' :)
12:14
But type your progress...
12:15
<stevecook>
cheers alskig
12:20
ok, when I enter the following at the initramfs prompt:
12:20
nbd-client 10.42.0.251 -N /opt/ltsp/i386 /dev/nbd0
12:20
I get the following:
12:21
Negotiation: ..Error: Read failed: Enf of file
12:21
Exiting
12:27Eric5 has joined IRC (Eric5!~eric@sdi.iut-valence.fr)
12:28
<alkisg>
stevecook: then there's still something wrong with your nbd-server
12:28
stevecook: to solve this quicker, let me have a look via vnc:
12:28
!vnc-dide
12:28
<ltsp>
vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
12:28
<stevecook>
ok hang on
12:30lucascastro has joined IRC (lucascastro!~lucas@189.90.38.210.jupiter.com.br)
12:33
<alkisg>
stevecook: you were missing the ipappend 3 step
12:33
<stevecook>
wow....thanks alkisg
12:33
<alkisg>
np
12:34
<stevecook>
did i do something wrong in the gui installation to casue that problem?
12:35
<alkisg>
I think it's my fault, I don't think I put ipappend in the ltsp-manager code base
12:36
<stevecook>
ah ok. cheers though mate. i really can't thank you enough for your help
12:36
<alkisg>
I'll upload a new version that will solve the issue
12:36
<stevecook>
brilliant. Thanks alkisg
12:36
<alkisg>
press ctrl+c in tilda to terminate vnc
12:36
<stevecook>
is it okay for me to close the screen share?
12:36
<alkisg>
yes please do so
12:36
<stevecook>
ok cheers
12:36
<alkisg>
Cheers :)
12:38
<stevecook>
client is in and all working...:)
12:38
right....clonzilla image done pronto!
12:39
thanks again.... off to play with my shiny new client
12:39
<alkisg>
You're welcome
12:41stevecook has left IRC (stevecook!5ad76ee5@gateway/web/freenode/ip.90.215.110.229, Quit: Page closed)
13:17ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)
13:50lucascastro has left IRC (lucascastro!~lucas@189.90.38.210.jupiter.com.br, Remote host closed the connection)
14:00adrianorg has left IRC (adrianorg!~adrianorg@189.58.238.64.dynamic.adsl.gvt.net.br, Ping timeout: 248 seconds)
14:03alkisg1 has joined IRC (alkisg1!~alkisg@ubuntu/member/alkisg)
14:10alkisg1 has left IRC (alkisg1!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)
14:32adrianorg has joined IRC (adrianorg!~adrianorg@189.58.238.64.dynamic.adsl.gvt.net.br)
14:51SCott__ has joined IRC (SCott__!cc3ffdbf@gateway/web/freenode/ip.204.63.253.191)
14:52SCott__ has left IRC (SCott__!cc3ffdbf@gateway/web/freenode/ip.204.63.253.191, Client Quit)
15:11GodFather has left IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net, Ping timeout: 240 seconds)
15:23lucascastro has joined IRC (lucascastro!~lucas@186.193.179.228.jupiter.com.br)
15:25GodFather has joined IRC (GodFather!~rcc@75-145-237-204-Michigan.hfc.comcastbusiness.net)
15:26mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)
15:32bennabiy has joined IRC (bennabiy!~bennabiy@unaffiliated/bennabiy)
15:35bennabiy has left IRC (bennabiy!~bennabiy@unaffiliated/bennabiy, Client Quit)
15:56Guest85302 has left IRC (Guest85302!bennabiyma@gateway/shell/matrix.org/x-sjhpjxcljspklfsl, Changing host)
15:56Guest85302 has joined IRC (Guest85302!bennabiyma@unaffiliated/bennabiy)
15:56Guest85302 has joined IRC (Guest85302!bennabiyma@gateway/shell/matrix.org/x-sjhpjxcljspklfsl)
15:58Guest85302 is now known as bennabiy
16:33lucascastro has left IRC (lucascastro!~lucas@186.193.179.228.jupiter.com.br, Remote host closed the connection)
16:37fernavat has joined IRC (fernavat!bbbd4e2d@gateway/web/freenode/ip.187.189.78.45)
16:38
<fernavat>
hello people!
16:39
i dont know if you can help me, I installe ltsp-manager in a ubuntu mate 16.04 x64, x32 and debian mate x64, and in none of them can boot a client
16:43
It says "Gave up waiting for root device... ALERT! /dev/nbd0 does not exist. Dropping to a shell!!"
17:01Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
17:09lucascastro has joined IRC (lucascastro!~lucas@170.78.53.20)
17:34
<alkisg>
!ltsp-config-bug | echo fernavat:
17:34
<ltsp>
'fernavat: ltsp-config-bug: Currently there\'s an issue with "ltsp-config nbd-server", to fix it run this as root: arch=$(dpkg --print-architecture); printf "[/opt/ltsp/$arch]\nexportname = /opt/ltsp/images/$arch.img\nreadonly = true\nauthfile = /etc/ltsp/nbd-server.allow\n" > /etc/nbd-server/conf.d/ltsp_$arch.conf; service nbd-server restart'
17:37vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
18:03
<fernavat>
thank you alkisg, did it and same problem, I've noticed that I dont have the file "/etc/ltsp/nbd-server.allow" could this be the problem?
18:04
<alkisg>
fernavat: no, that shouldn't exist
18:04
!ipappend
18:04
<ltsp>
ipappend: o temporarily solve DHCP problems in the initramfs, try putting IPAPPEND 3 after the APPEND line in /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default. More info: http://www.syslinux.org/wiki/index.php/SYSLINUX#IPAPPEND_flag_val_.5BPXELINUX_only.5D
18:04
<alkisg>
fernavat: also replace "ipappend 2" with "ipappend 3" in /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
18:07GodFather has left IRC (GodFather!~rcc@75-145-237-204-Michigan.hfc.comcastbusiness.net, Remote host closed the connection)
18:07GodFather_ has joined IRC (GodFather_!~rcc@75-145-237-204-Michigan.hfc.comcastbusiness.net)
18:08
<alkisg>
vagrantc: Hi! How would you feel about defaulting to ipappend 3 instead of 2? in ltsp, not just in ltsp-manager?
18:23
<vagrantc>
alkisg: hmmmm... off the top of my head I can't see a reason not to ... but maybe I'm missing something
18:24
i guess the root server might be different than the tftp server, but that's an unusual corner case and probably requires manual configuration anyways
18:25* vagrantc wants to kill off ltsp-build-client and replace it with something simpler.
18:25
<vagrantc>
maybe ltsp6 will just happen by technical and temporal erosion
18:28GodFather_ has left IRC (GodFather_!~rcc@75-145-237-204-Michigan.hfc.comcastbusiness.net, Ping timeout: 240 seconds)
18:41Eric5 has left IRC (Eric5!~eric@sdi.iut-valence.fr, Ping timeout: 252 seconds)
18:44
<alkisg>
vagrantc: one problem that I can think of, is that we'll miss the other dhcp options like dns servers
18:44
<fernavat>
alkisg: that file already had "ipappend 3" after each append, did not find any line with "ipappend 2"
18:44
<alkisg>
We already miss that with proxydhcp, so we're using lts.conf instead, but now we'll lose them in the normal dhcp mode of dnsmsq too
18:45
fernavat: something strange happens then. Can you try this from the client?
18:45
!nbd-client
18:45
<ltsp>
nbd-client: To try mounting the NBD image from the client initramfs: nbd-client 192.168.67.1 -N /opt/ltsp/i386 /dev/nbd0
18:45
<alkisg>
(put your server ip there)
18:46
<vagrantc>
alkisg: with the default being fat clients, that is somewhat significant
18:47
alkisg: having to specify them in lts.conf isn't great, especially if they change networks
19:08
<fernavat>
alkisg: tryed: nbd-client 10.1.2.37 -N /opt/ltsp/images/amd64.img /dev/nbd0.... Negotiation: ..Error: Read failed: End of file Exiting
19:09
<alkisg>
fernavat: did you restart nbd-server? what are the contents of that conf file?
19:09
cat /etc/nbd-server/conf.d/ltsp_i386.conf
19:09
<vagrantc>
alkisg: i forget if we have an option like DNS_SERVERS=server that could be a reasonable default in many cases
19:10
alkisg: appears there are fallbacks for DNS, so that isn't horrible
19:10
<alkisg>
vagrantc: well, in the new default installation, the ltsp server is also a dns server, and the clients default to that one
19:11
<vagrantc>
right
19:11
<alkisg>
It also provides caching, but there were some considerations about cache poisoning from other dnsmasq users...
19:11
<vagrantc>
if people are severely concerned about that, they can configure DNS in lts.conf
19:15
alkisg: are people really that concerned about dns cache poisoning? it basically requires a compromised dnsmasq or other dns servers...
19:16
i mean, is there any additional vulnerability by using dnsmasq?
19:16ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
19:18lucascastro has left IRC (lucascastro!~lucas@170.78.53.20, Remote host closed the connection)
19:23
<fernavat>
alkisg: after reviewing that file, I noticed it was wrong, fixed it and now the client boots, thank you alkisg
19:30
<alkisg>
vagrantc: no idea, that's about all I've heard about it :)
19:30
fernavat: you're welcome
19:31
vagrantc: so you're basically ok with ippappend 3. right?
19:31
<vagrantc>
alkisg: i think so
19:31
alkisg: if it's a disaster, we can always revert it :)
19:32
alkisg: but we've encouraged it for so long...
19:32
<alkisg>
Hehe, cool :)
19:32
I think we'll mostly hear complains about "why do I have to set these things that I had in dhcpd.conf, in lts.conf now..."
19:33
Eh, they can just edit a conf file and revert to ipappend 2 if needed
19:33
I wonder how fernavat got ipappend 3 though
19:33
<vagrantc>
well, reverting to ipappend 2 is more complicated than it should be...
19:33
<alkisg>
Maybe he followed both the ltsp-pnp and the ltsp-manager pages
19:33
I'm in favor of shipping a pxelinux.cfg/default file, that is not generated by ltsp :D
19:33
Just put vmlinuz xx there and work with symlinks :D
19:34
No regeneration at all, they can just go there and edit stuff
19:36
<fernavat>
I only followed the ltsp-manager in 3 clean install servers
19:41
in ubuntu 32 appears ipappend 2, in ubuntu 64 appears ipappend 3
19:52
in order to boot the client from ubuntu 32 server I had to change ipappend to 3
19:54
how do I know if a client booted as thin or fat?
19:57
<alkisg>
fernavat: you can see it in epoptes
19:57
green vs blue icon (=fat)
20:18
<fernavat>
alkisg: Great! Thanks again for your great help, I had days trying to figure this out
20:24lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
20:37lucascastro has left IRC (lucascastro!~lucas@201.182.221.14, Remote host closed the connection)
20:41lucascastro has joined IRC (lucascastro!~lucas@201.182.221.14)
20:49dgroos has joined IRC (dgroos!~dagro001@205.215.175.117)
20:52
<dgroos>
vagrantc: I’d like to try your idea of booting a client with out all the pbis stuff on it.
20:53
I've been spoiled with ltsp-pnp and haven't had to build chroots in a few years
20:54Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
20:55
<dgroos>
Is there someplace where there are written instructions I could follow to build an Ubuntu 16.04.3 ltsp image via a chroot?
20:55
<vagrantc>
"ltsp-build-client"
20:55
or... "sudo ltsp-build-client"
20:56
you might want to purge everything in /opt/ltsp/ first ... or move it to /opt/ltsp.old or something
20:57
<dgroos>
OK
20:57
I think there was something about making some mount points?
21:01
OK, it’s building!
21:01
<vagrantc>
dgroos: all the ones i know of are mounted by default
21:02
/sys, /dev/pts, /proc
21:04
<dgroos>
vagrantc: ok, thanks
21:05GodFather_ has joined IRC (GodFather_!~rcc@47.33.250.142)
21:18
<dgroos>
vagrantc: ended with an error, same as yesterday (http://paste.ubuntu.com/25575209/) Should I try MATE or might that have different issues since the server is running Ubuntu?
21:19
I’m googlin portions of these error message but no luck so far.
21:24
<vagrantc>
dgroos: try building without --fat-client
21:32
<dgroos>
Actually, I had forgotton that one from yesterday and did exactly as you had typed above, so I did build w/out the —fat client.
21:32
<vagrantc>
i guess ubuntu's just plain broken
21:33
<dgroos>
Here’s the content of the grub that’s referred to (http://paste.ubuntu.com/25575249/)
21:34
:-( OK, I thought it was a great idea to test the idea that something disruptive from pbis was getting loaded into the client image.
21:36
So, the best guess is that some module is waylaying LDM’s normal process of authenticating, so authentication is trying to happen locally on the client, so that’s not good.
21:37
Interesting that when the server was JOINED to AD, nothing was written to the auth.log during login attempts.
21:38
again, thanks so much vagrantc for your time and effort, I’ll keep noodling this…
21:39dgroos has left IRC (dgroos!~dagro001@205.215.175.117, Quit: dgroos)
22:09ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection)
22:33GodFather has joined IRC (GodFather!~rcc@47.33.250.142)
22:34GodFather has left IRC (GodFather!~rcc@47.33.250.142, Remote host closed the connection)
22:49GodFather_ has left IRC (GodFather_!~rcc@47.33.250.142, Ping timeout: 240 seconds)
23:09GodFather_ has joined IRC (GodFather_!~rcc@47.33.250.142)
23:13fernavat has left IRC (fernavat!bbbd4e2d@gateway/web/freenode/ip.187.189.78.45, Ping timeout: 260 seconds)