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


Channel log from 1 August 2019   (all times are UTC)

01:58vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
03:03kjackal has joined IRC (kjackal!~quassel@162.223.5.124)
03:17kjackal has left IRC (kjackal!~quassel@162.223.5.124, Ping timeout: 272 seconds)
05:22statler has joined IRC (statler!~Georg@p54897D17.dip0.t-ipconnect.de)
05:42ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
05:53Freejack has left IRC (Freejack!~Freejack@unaffiliated/freejack, Ping timeout: 268 seconds)
06:50woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de)
06:52ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Ping timeout: 272 seconds)
07:18ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:19woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 245 seconds)
07:37woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de)
07:45statler has left IRC (statler!~Georg@p54897D17.dip0.t-ipconnect.de, Remote host closed the connection)
08:27statler has joined IRC (statler!~Georg@gwrz3.lohn24.de)
09:03adrianor1 has joined IRC (adrianor1!~adrianorg@187.113.247.112)
09:06adrianorg has left IRC (adrianorg!~adrianorg@177.156.228.158, Ping timeout: 258 seconds)
11:50ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
11:54section1 has joined IRC (section1!~section1@178.33.109.106)
11:55Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
12:23Zentibel has joined IRC (Zentibel!9de6799c@157.230.121.156)
12:24
<Zentibel>
Hello all, I have a problem with my ltsp system at work.
12:25
And shift+enter does not make a new line apparanty
12:26
So I have a debian server running LTSP, but after accidentially deleting the /var/lib/tftpboot directory, and copying over the files from /opt/ltsp/amd64/boot, I get a "/var/lib/tftpboot/pxelinux.0 file not found" error
12:26
I have verified that the file exists
12:27
And that it is readable
12:27
So I am not sure why it wont work
12:27
Also I am not at work atm so I will not be able to try anything until later
12:28
<alkisg>
Zentibel: copy files? Why not just run ltsp-update-kernels?
12:29
<Zentibel>
I didn't know what to do and just saw that someone else sorted it like that
12:29
<alkisg>
Also, it's usually /var/lib/tftpboot/ltsp/i386/pxelinux.0, not in the root of tftp
12:29
<Zentibel>
Yeah I just typed it wrong, sorry
12:29
<alkisg>
OK; also note that it might be serving from /srv/tftp instead
12:29
<Zentibel>
Before when I had a chrootless image doing ltsp-update-image didn't update /var/lib/tftpboot
12:30
I checked /srv/ and its empty
12:30
<alkisg>
ltsp-update-image calls ltsp-update-kernels which updates /var/lib/tftpboot, so you're probably wrong about chrootless
12:31
<Zentibel>
Alright
12:32
The main issue is why it won't find that file even though it exists
12:32
<alkisg>
You probably put it in the wrong path
12:33
Are you using dnsmasq or tftpd-hpa?
12:33
<Zentibel>
dnsmasq
12:33
<alkisg>
tail -f /var/log/syslog while the client tries to boot, will tell you where it's searching
12:33
<Zentibel>
Alright cool
12:33markit has joined IRC (markit!~marco@78-134-22-223.v4.ngi.it)
12:35
<Zentibel>
The thing however is that the thin client says that the file isn't found, where there is a file on the server
12:35
<alkisg>
OK, when you get there if you can't solve it come again
12:35
It's either wrong paths or wrong permissions or wrong server
12:36
In any case, there's not much more to say when you can't test
12:36
<Zentibel>
Ok thanks anyway!
12:57woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Remote host closed the connection)
13:15
<markit>
"Mattermost is a modern open-source solution for team communication, eliminating many of the limits of IRC"
13:15
ops, sorry, wrong channel!
13:15
hi alkisg :)
13:17* mwalters puts on his grumpy old man hat
13:17
<mwalters>
I like the limits of IRC.
13:17
get off my lawn, slack.
13:18
<markit>
mwalters: yes, but I'm also in a different channel and we were wondering why is years we are almost the same 5-7 people, even if is LibreOffice related, so wondered if new people is elsewhere :)
13:19
<mwalters>
Yeah, I've had regional "tech" channel run into the same issues. Once they went to slack, membership/participation skyrocketed
13:19
I'm just grumpy and old ;)
13:20
...and prefer my weechat.
13:56vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
14:00Zentibel has left IRC (Zentibel!9de6799c@157.230.121.156, Remote host closed the connection)
14:11
<alkisg>
Hey markit
14:13shored has left IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi, Read error: Connection reset by peer)
14:13shored has joined IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi)
14:15
<alkisg>
vagrantc: in ltsp-update-image.excludes, I replaced /etc/.git , .hg, .bzr and some others that you had, with /etc/.(!java), i.e. all dot directories in /etc/ are excluded except for java. What was /etc/_darcs, I haven't found any reference of it online...
14:16
<vagrantc>
i suspect those were the ones supported by etckeeper at the time ... or at least the ones i knew about
14:17
since it could store sensitive data...
14:17
<alkisg>
I think /etc/_darcs isn't used though, I don't see any references of it online, so I'll remove it until someone needs it
14:18
Btw, has anyone used "multistrap"? Is it worth it in any cases to point our users there, instead of debbootstrap?
14:19
<vagrantc>
default for etckeeper is git ... the others were just being thorough
14:24
<alkisg>
Commands that are pretty much ready: ltsp, ltsp-dnsmasq, ltsp-initrd, ltsp-ipxe, ltsp-kernel , ltsp-nfs
14:24
Commands that will be ready next week: ltsp-client.conf, ltsp-image, ltsp-info
14:24
Commands that I'm thinking to postpone after the beta or until someone asks for them: ltsp-chroot, ltsp-isc-dhcp, ltsp-nbd, ltsp-swap
14:25
Does anyone think that any of those last commands are required for beta?
14:26BuddyButterfly has joined IRC (BuddyButterfly!~BuddyButt@h2216388.stratoserver.net)
14:26
<alkisg>
I've heard reports about nbd swap being rather unstable, and a bad client may severely affect the server with it, so I was thinking to omit it until someone needs it...
14:26
<BuddyButterfly>
hi
14:26
<alkisg>
Hi BuddyButterfly
14:26
<BuddyButterfly>
alkisg: did the upgrade to 18.04 as you described.
14:26
worked so far flawlessly.
14:27
<alkisg>
Great
14:27
<BuddyButterfly>
only issue is that i do not have any dns resolution on the clients.
14:27
I do have the dns_server settings, etc. in the lts.conf.
14:27
is there from the previous version...
14:28
<alkisg>
What's the output of `ls -l /etc/resolv.conf; cat /etc/resolv.conf` on the clients?
14:28
<BuddyButterfly>
Now the question. Do you have a clue, what could be the issue?
14:28
alkisg: that is a link to the systemd version.
14:28
<alkisg>
Is it broken?
14:28
<BuddyButterfly>
the content is that the server points to localhost: 127.0.0.1:53
14:29
in the resolve.conf
14:29
<alkisg>
Single nic or dual nic?
14:29
<BuddyButterfly>
single nic!
14:29
<alkisg>
(the server)
14:29
<BuddyButterfly>
ah, moment.
14:29
<alkisg>
Also: grep -r DNS /run/ltsp
14:30
Output of that, too
14:30
<BuddyButterfly>
server: single nic.
14:30
on server?
14:30
<alkisg>
Client
14:30
<BuddyButterfly>
on client: grep -r DNS /run/ltsp?
14:30
<alkisg>
Yes
14:30
<BuddyButterfly>
ok, will try. have to first stop xenial verison of ltsp and start bionic....
14:34
client is booting...
14:37
/run/ltsp/passwd:avahi:x:107:114:Avahi mDNS daemon,,,:/var/run/avahi-daemon:/bin/false
14:37
/run/ltsp/ltsp_config_env:DNS_SERVER="192.168.1.1"
14:38
dns server is 192.168.1.1, which is correct.
14:38
<alkisg>
OK, then: getent hosts www.google.com
14:39
And: ping 8.8.8.8
14:39
And: ping www.google.com
14:39
from the client
14:39
<BuddyButterfly>
ah, that can be done easier.
14:39
ping 1.1
14:39
which works!
14:40
getent?
14:40
not available on client.
14:40
ah, sry, getent hosts... gives empty result.
14:41
<alkisg>
So which of those 3 commands work and which don't?
14:41
<BuddyButterfly>
ping 1.1:
14:41
64 bytes from 1.0.0.1: icmp_seq=1 ttl=58 time=16.9 ms
14:41
getent:
14:41
empty
14:41
nothing...
14:41
<alkisg>
ping www.google.com ?
14:41
<BuddyButterfly>
alkisg: hehe, that will not work, as it requires dns resolution ;-)
14:41
<alkisg>
Sure, I wanted to see the message
14:42
<BuddyButterfly>
temporary error with name resolution...
14:42
it is German:
14:42
ping: www.google.com: Temporärer Fehler bei der Namensauflösung
14:42
<alkisg>
systemd-resolve --status => DNS server there?
14:43
And, dpkg -l resolvconf
14:43
(should be uninstalled)
14:44
Also: host 192.168.1.1 www.google.com
14:44
(should work)
14:44
<BuddyButterfly>
host 192.168.1.1 www.google.com:
14:45
host: couldn't get address for 'www.google.com': failure
14:45
<alkisg>
That means your 192.168.1.1 dns server is not working
14:45
Try it from your server now
14:45
<BuddyButterfly>
a dig @192.168.1.1 gives it back
14:45
<alkisg>
Ah maybe it's the opposite, let me see
14:45
<BuddyButterfly>
;; ANSWER SECTION:
14:45
www.google.com. 262 IN A 172.217.22.68
14:46
but that host 192.168.1.1 does not work.
14:46
<alkisg>
Yeah it's: host www.google.com 192.168.1.1
14:46
<BuddyButterfly>
yep, works.
14:46
<alkisg>
What about the other 2?
14:47
(05:42:31 PM) alkisg: systemd-resolve --status => DNS server there?
14:47
(05:43:18 PM) alkisg: And, dpkg -l resolvconf
14:47
<BuddyButterfly>
moment...
14:47
ii resolvconf 1.79ubuntu10.1 all name server information handler
14:47
<alkisg>
OK, this is probably what breaks it
14:48
Remove it from the chroot or the server if you're using chrootless, and update image
14:48
<BuddyButterfly>
okey...?
14:48
ok, will do....
14:48
hang on... ;-)
14:48
<alkisg>
Ubuntu dropped resolvconf after 16.04 or maybe even earlier
14:48
They change the DNS stuff on every release :D
14:49
<BuddyButterfly>
yes, true! I have already started to move some systems to debian....
14:49
away from ubuntu...
14:50
<alkisg>
Now with the new ltsp19 it'll be very very easy to test all .deb based distributions
14:50
And desktop environments
14:50
I'll try to support most of them, so that people can easily switch between them
14:50
I'll probably switch a couple of schools to buster + ltsp19 in september too
14:51
<BuddyButterfly>
alkisg: yes, wise decision. have also moved some systems to buster.
14:51
debian is not that erratic in its changes and more stable in recent times.
14:51
<alkisg>
I'm sure it'll require a few months of fine-tuning, but it might be worth it
14:55
<BuddyButterfly>
alkisg: so, image is being created. removed resolvconf from server.
14:55
<alkisg>
Are you using chrootless ltsp?
14:55
<BuddyButterfly>
needs some time ;-)
14:55
yes, pnp...
14:56
<alkisg>
OK; does dns work on the server after it was removed?
14:56
Maybe you need to do a couple of manual steps...
14:56
<BuddyButterfly>
yes, checked, that ;-)
14:56
<alkisg>
Maybe it'll break after reboot :P
14:56
<BuddyButterfly>
also rebooted ;-)
14:57
it gives explicit notice that reboot is required.
14:57
after deinstallation.
15:00
alkisg: it is nice to have the ltsp server running in a vm. so I am very comfortable with testing.... can alway revert back to old vm. Just cloned old one and made the upgrade... worked flawlessly.
15:00
then I also have 2 vm clients to the ltsp server where I can do real quick tests...
15:02
<alkisg>
BuddyButterfly: the opposite is also nice, to have the "template client" in a vm itself, so that you can test without even running ltsp-update-image... https://ltsp.github.io/docs/ltsp-image/#VM-IMAGES
15:02
(that's from the new ltsp19)
15:03
E.g. I have 20 VMs and 20 live cds, and I can ltsp-boot any one of them
15:03
And I'm not even using -pnp
15:05
<BuddyButterfly>
oh my good
15:05
that is so cool!
15:05
wow, I will definitely look into this also, as I have also a few vms that could be used as templates.
15:06
<alkisg>
It'll be ready for testing in a couple of weeks
15:06
It's also doable in ltsp5, but I don't have any documentation for it
15:06
<BuddyButterfly>
where do I see the exact version I am using?
15:07
image finished...
15:07
<alkisg>
Everyone is using ltsp5; while I'm currently developing ltsp19 and it'll be ready for beta testing in 2 weeks
15:07
<BuddyButterfly>
thumbs up...
15:09
Chacka!!!! That cooked it!
15:09
will you vm templating also support qcow2 sparse images?
15:09
which is the default I am using.
15:10
cause I am running on kvm (proxmox server).
15:10
<alkisg>
No
15:10
initramfs can't boot qcow2
15:10
So it needs to be fixed size image
15:11
<BuddyButterfly>
ok, can be easily converted for that templates.
15:11
<alkisg>
I'm sure all virtualization applications support fixed size, right?
15:11* markit hopes alkisg with ltsp19 will support Kubuntu too...
15:11
<BuddyButterfly>
yep
15:11
<alkisg>
markit: I've booted kubuntu 18.04 with ltsp19, I didn't notice any big delays
15:12
<BuddyButterfly>
alkisg: thanks again for you perfect and precise help!
15:12
unbeatable...
15:12
<alkisg>
np
15:12
<BuddyButterfly>
there is one thing left, where I probably would need advice.
15:13
but I will test first.... (it is mounting cifs via fstab, which does not work as expected). But I would like to have more data on what exactly happens).
15:14
especially I would like to test this in the version (bionic)...
15:22
<alkisg>
!install | markit:
15:22
<ltsp>
Error: "markit:" is not a valid command.
15:22
<alkisg>
!install | echo markit:
15:22
<ltsp>
markit: install: http://wiki.ltsp.org/wiki/Installation/Ubuntu for Ubuntu, or http://wiki.ltsp.org/wiki/Installation for other distributions
15:22archundial has joined IRC (archundial!bbbdd62b@fixed-187-189-214-43.totalplay.net)
15:23
<archundial>
Hi, i installed my ltsp server, congratullations, now its so easy but a thin client, but i cant admin my users, how can i do it? Sorry for my easy question
15:24
boot* a thin client
15:24
<alkisg>
What does "admin my users" mean?
15:24
Why are you using thin clients instead of fat?
15:24
!fatclients
15:24
<ltsp>
fatclients: Nowadays LTSP supports thin and fat clients. They are both diskless and netbooted from the same LTSP chroot, but while thin clients run the session on the server and transfer the screen, fat clients run the session locally with their own CPU/RAM, thus performing amazingly better. See also !ltsp-pnp and https://help.ubuntu.com/community/UbuntuLTSP/FatClients
15:24
<archundial>
fat
15:25
<alkisg>
Do you mean that you cannot run "sudo" on fat clients?
15:25
<archundial>
but i cant log in my clients
15:25
<alkisg>
Your fat clients boot, but you can't login to them?
15:25
<archundial>
yes
15:25
<alkisg>
Do you have epoptes installed?
15:25
!epoptes
15:25
<ltsp>
epoptes: Epoptes is a computer lab administration and monitoring tool. It works on Ubuntu and Debian based labs with LTSP or non-LTSP servers, thin and fat clients, standalone workstations, NX clients etc. More info: http://www.epoptes.org
15:25
<archundial>
ye
15:25
yes
15:25
<alkisg>
I can take a quick look over vnc, if you want
15:25
!vnc-edide
15:25
<ltsp>
vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
15:26
<alkisg>
From the server
15:26
<archundial>
i saw my computers turnned on
15:30shored has left IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi, Read error: Connection reset by peer)
15:30shored has joined IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi)
15:33
<alkisg>
archundial: it seems like a problem with gnome and 19.04
15:34
Better use mate and 18.04 instead
15:34
!install
15:34
<ltsp>
install: http://wiki.ltsp.org/wiki/Installation/Ubuntu for Ubuntu, or http://wiki.ltsp.org/wiki/Installation for other distributions
15:34
<alkisg>
I.e. this one ^
15:42
<archundial>
Its done, then?
15:45
i need to reinstall all, right?
15:49
i'll do it, i'm so thankfully
15:56archundial has left IRC (archundial!bbbdd62b@fixed-187-189-214-43.totalplay.net, Remote host closed the connection)
16:47BuddyButterfly has left IRC (BuddyButterfly!~BuddyButt@h2216388.stratoserver.net, Quit: Leaving.)
17:18statler has left IRC (statler!~Georg@gwrz3.lohn24.de, Remote host closed the connection)
17:27
<markit>
alkisg: I've installed in pnp (chrootless) mode, but I've god a mate/gnome interface, did not keept the KDE "host" one, any parameter I'm missing?
17:29BuddyButterfly has joined IRC (BuddyButterfly!~BuddyButt@h2216388.stratoserver.net)
17:30BuddyButterfly has left IRC (BuddyButterfly!~BuddyButt@h2216388.stratoserver.net, Client Quit)
17:34
<markit>
ops, my foult, I just copy/pasted the commands "ltsp-chroot -m apt install ubuntu-mate-desktop"
17:34
I thought that with pnp always the SAME desktop would have been installed, and I did not noticed that command, sigh
17:38
mm what a mess, I've mixed pnp and not pnp installation, too distraction (phone, clients, family...)
17:41woernie has joined IRC (woernie!~werner@p57A0EC92.dip0.t-ipconnect.de)
17:46
<markit>
mmmm "apt install --yes --install-recommends ltsp-server-standalone ltsp-client epoptes" installs "mate" desktop, how can I avoit id?
17:47
brb
17:50markit has left IRC (markit!~marco@78-134-22-223.v4.ngi.it, )
19:10spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Ping timeout: 244 seconds)
19:24vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
19:51woernie has left IRC (woernie!~werner@p57A0EC92.dip0.t-ipconnect.de, Remote host closed the connection)
20:03section1 has left IRC (section1!~section1@178.33.109.106, Quit: Leaving)
20:29vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
20:44Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
21:14jgee has left IRC (jgee!~jgee@190.159.118.121, Remote host closed the connection)
21:46jgee has joined IRC (jgee!~jgee@190.159.118.121)
22:56adrianorg has joined IRC (adrianorg!~adrianorg@186.215.17.155)
22:59adrianor1 has left IRC (adrianor1!~adrianorg@187.113.247.112, Ping timeout: 268 seconds)