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


Channel log from 25 October 2022   (all times are UTC)

00:10we6jbo has joined IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-4c9b-4f3c-15a3-408b.res6.spectrum.com)
00:23vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20)
00:56we6jbo has left IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-4c9b-4f3c-15a3-408b.res6.spectrum.com, Ping timeout: 250 seconds)
01:10book` has left IRC (book`!~book`@static.38.6.217.95.clients.your-server.de, K-Lined)
01:15book` has joined IRC (book`!~book`@static.38.6.217.95.clients.your-server.de)
01:16vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving)
01:17we6jbo has joined IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-9365-7c17-4f42-3551.res6.spectrum.com)
04:30Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Quit: buh bye)
04:31Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas)
04:35Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Client Quit)
04:35Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas)
04:40Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Client Quit)
04:40Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas)
04:44Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Client Quit)
04:45Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas)
04:53we6jbo has left IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-9365-7c17-4f42-3551.res6.spectrum.com, Remote host closed the connection)
05:14alkisg_web has joined IRC (alkisg_web!~alkisg_we@2a02:587:7458:8100:c24a:ff:fe02:bc1e)
05:38ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:24woernie has joined IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de)
07:31Krisz has joined IRC (Krisz!~Krisz@563B972C.catv.pool.telekom.hu)
07:32
<Krisz>
Hello everyone :)
07:37
I am new in ltsp, I am trying to configure my first server + clients, but I am stuck with an issue
07:37
do you know where I can get a little help?
07:37
thank you
07:37
<alkisg>
Krisz: here is fine, what issue?
07:45
<Krisz>
thank you
07:45
I have created an ltsp server, following the steps http://ltsp.org/docs/installation/
07:45
I want to create with chroot method for the clients with debian bullseye image
07:45
the image is located under /srv/ltsp/images but when booting the client I get an error like:
07:45
running /sbin/ltsp initrd-bottom
07:45
image doesn't exist: /root/images/bullseye.img
07:45
LTSP command failed: mount_img_src /root/images/bullseye.img /root /run/initramfs/ltsp
07:45
Aborting ltsp
07:46
<alkisg>
The chrootless method is the easiest one for first installations
07:46
Chroots should go to /srv/ltsp/bullseye/
07:46
Then you may run `sudo ltsp image bullseye` to generate /srv/ltsp/images/bullseye.img
07:47
And then `sudo ltsp ipxe` to update the ipxe menu
07:47
And then you can boot the clients
07:47
If you only have an image, rename it from bullseye to x86_64 so that it's the default name and you don't need to type it all the time
07:52
<Krisz>
my chroots are here: /srv/ltsp/bullseye
07:52
I have ran ltsp image bullseye with root privilages then was bullseye.img created
07:52
after ran 'ltsp initrd' to create ltsp.img under /srv/tftp/ltsp after this I ran 'ltsp ipxe'
07:52
but I still have this issue
07:53
<alkisg>
Krisz: do you mind sharing your server screen so that we can troubleshoot this faster?
07:54
<Krisz>
no, I do not mind
07:54
how can I do that?
07:54
<alkisg>
Are you using xorg, wayland or ssh/terminal?
07:54
(to access the server)
07:54
<Krisz>
ssh
07:55
<alkisg>
And your own PC is using xorg, wayland or windows?
07:56
Anyway run this via ssh on the server:
07:56
sudo apt install --no-install-recommends epoptes-client
07:56
/usr/share/epoptes-client/share-terminal 81.186.20.0
07:56
These will share just that terminal with me
07:58
<Krisz>
thank you :)
08:00
<alkisg>
Krisz: if it fails with the same message, take a photo
08:00
!photo
08:00
<ltspbot`>
I do not know about 'photo', but I do know about these similar topics: 'paste'
08:01
<alkisg>
!screenshot
08:01
<ltspbot`>
screenshot: to upload a screenshot use a site like https://prnt.sc/ or https://snag.gy/ and then paste the URL here
08:02
<alkisg>
Btw, try to boot "bullseye.img" (the image), not "bullseye" (the chroot), ok?
08:03
<Krisz>
this was bullseye.img so the first option from the menü
08:04
I will upload  the screenshot right away
08:07
https://snipboard.io/AqKBtm.jpg
08:13
<alkisg>
Krisz: press ctrl+c in our shared terminal
08:13
<Krisz>
done
08:15
<alkisg>
Krisz: it seems our terminal sharing no longer works, can you exit it and then re-run the command?
08:18
Krisz: try once more to reboot the client
08:18
<Krisz>
ok, just a sec
08:20
same error
08:22
<alkisg>
Krisz: try once more
08:23
<Krisz>
same error once again, sorry
08:24
<alkisg>
Krisz: and once more
08:25
<Krisz>
some error, but now I have debug shell
08:25Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds))
08:26
<alkisg>
Krisz: once more
08:27
<Krisz>
same again
08:28
<alkisg>
OK then you'll need to boot a VM client, not a real client, and share that VM screen with me so that I can look around
08:28Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas)
08:28
<alkisg>
Something is wrong but I can't pinpoint what
08:28
Ah btw, what's the output of:
08:28
ls /root
08:28
While on that debug shell
08:33
<Krisz>
this is very intersting
08:33
if I type exit to debug console the clients starts
08:33
but I will upload the screenshot of /root just a sec
08:35
https://snipboard.io/kzcIlF.jpg
08:39
but now, that I have a running client
08:39
I can share its terminal with you if you need it
08:39
or should I create VM client?
08:51
<alkisg>
Krisz: a VM client will be needed, but let's postpone that for another time as I got too much work currently; unfortunately you'll need to make do with the "exit" workaround till then :)
08:52
<Krisz>
ok, I am very happy now
08:52
and very gretefull for your help
08:56
<alkisg>
👍️
09:34Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds))
09:35Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas)
09:51Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds))
10:18Krisz has left IRC (Krisz!~Krisz@563B972C.catv.pool.telekom.hu, Ping timeout: 244 seconds)
10:35woernie has left IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de, Ping timeout: 240 seconds)
11:00Krisz has joined IRC (Krisz!~Krisz@563B972C.catv.pool.telekom.hu)
11:08eu^86-181-20-212 has joined IRC (eu^86-181-20-212!~eu^86-181@86-181-20-212.revers.globvill.de)
11:28eu^86-181-20-212 has left IRC (eu^86-181-20-212!~eu^86-181@86-181-20-212.revers.globvill.de, Quit: Client closed)
12:42woernie has joined IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de)
13:38we6jbo has joined IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-4d5c-0b64-fa0d-5f0a.res6.spectrum.com)
13:55we6jbo has left IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-4d5c-0b64-fa0d-5f0a.res6.spectrum.com, Remote host closed the connection)
14:19Krisz has left IRC (Krisz!~Krisz@563B972C.catv.pool.telekom.hu, Quit: Client closed)
14:27oh207 has joined IRC (oh207!~oh207@pool-72-69-11-48.nycmny.fios.verizon.net)
14:39vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20)
16:30woernie has left IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de, Ping timeout: 272 seconds)
16:45woernie has joined IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de)
17:21alkisg_web has left IRC (alkisg_web!~alkisg_we@2a02:587:7458:8100:c24a:ff:fe02:bc1e, Quit: Client closed)
17:42hhttseee[m] has left IRC (hhttseee[m]!~thisis271@2001:470:69fc:105::2:5463)
19:58Lantizia has left IRC (Lantizia!~Lantizia@195.62.201.126, Read error: Connection reset by peer)
19:59Lantizia has joined IRC (Lantizia!~Lantizia@195.62.201.126)
20:45ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
21:32woernie has left IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de, Remote host closed the connection)
23:49we6jbo has joined IRC (we6jbo!~we6jbo@2603-8001-5b43-4000-63e8-0cc5-7ae5-f046.res6.spectrum.com)