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


Channel log from 3 July 2019   (all times are UTC)

00:03josefig has left IRC (josefig!~josefig@unaffiliated/josefig, Quit: Ping timeout (120 seconds))
00:05josefig has joined IRC (josefig!~josefig@unaffiliated/josefig)
03:31adrianor1 has joined IRC (adrianor1!~adrianorg@177.18.175.32)
03:34adrianorg has left IRC (adrianorg!~adrianorg@177.156.225.9, Ping timeout: 244 seconds)
04:35kjackal has joined IRC (kjackal!~quassel@2a02:587:9a03:2100:10f5:22c9:80be:6fd9)
05:30kjackal has left IRC (kjackal!~quassel@2a02:587:9a03:2100:10f5:22c9:80be:6fd9, Ping timeout: 250 seconds)
05:57ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:11kjackal has joined IRC (kjackal!~quassel@ppp-94-66-223-46.home.otenet.gr)
06:34bluejaypop has joined IRC (bluejaypop!~BlueJay@201.175.203.114)
06:41stellasolitaria has joined IRC (stellasolitaria!~jhonny5@159.213.93.166)
07:19gdi2k has left IRC (gdi2k!~gdi2k@58.69.160.28, Read error: Connection reset by peer)
07:36gdi2k has joined IRC (gdi2k!~gdi2k@58.69.160.28)
07:48bluejaypop has left IRC (bluejaypop!~BlueJay@201.175.203.114, Ping timeout: 246 seconds)
07:50kaktux has joined IRC (kaktux!58825afb@mue-88-130-90-251.dsl.tropolys.de)
08:00
<kaktux>
hi there, i am totally new to ltsp and read all i could find for installing a ltsp-server fat-client on Ubuntu - which is what i plan to achieve (create a Lubuntu 19.04 LTSP-Server for fat-clients) for the small company i work for. But all the (mostly outdated by 5+ years) infos i could find left me with some general questions.
08:01
<alkisg>
!install
08:01
<ltsp`>
install: http://wiki.ltsp.org/wiki/Installation/Ubuntu for Ubuntu, or http://wiki.ltsp.org/wiki/Installation for other distributions
08:01
<alkisg>
kaktux: follow this ^ one EXACTLY and you should be ready in 30 mins :)
08:04
<kaktux>
ok - i have these on my list already and read them (but not tried out till now). But i would like to ask the general questions as some tutorials on the net told to do some things before installing ltsp-packages. Which made me asked: why? Doesnt it work after? So the things i asked myself are about the functions of ltsp in general.
08:04
1. Possible to add programs after installation?2. Possible to add programs not included in the disstributions repository (like java programs)?3. Possible to add decives after installation (Printer, Card-Reader)?4. Possible to add users after installation?5. Possible to add bookmarks for all users in a file explorer (Dolphin, Nautilus...)?6. Possibl
08:04
e to add network connections (VPN) for all?7. Possible to add bookmarks/browser addons in Firefox for all?
08:04
<alkisg>
1) Yes 2) Yes 3) Yes 4) Yes 5) Yes 6) Yes 7) Yes
08:05
Note that "adding bookmarks for all users" etc is not related to ltsp. You can do it by following the mozilla documentation.
08:05
"doing things for all users" is the same if you just have a home pc with 3 accounts for your kids; again, you follow the mozilla documentation there and it works
08:07
<kaktux>
ok thx ;) thats what i was hoping for. I will just give a virtual machine installation a try and see what happens. Thx for your input. And another short one: i read a lot about "failed" lubuntu ltsp attempts. As most successfull users dont ask questions in forums: do you know about anyone using current lubuntu with ltsp?
08:07
<alkisg>
I think I heard a couple of people using it, yes. I don't know of any known issues with lubuntu.
08:07
More people use mate, as it's just as light and more full-featured, but lubuntu should also work fine
08:07
Ah
08:08
Also, DONT use 19.04
08:08
Use 18.04
08:08
Non LTS Ubuntu releases aren't tested at all by ltsp developers
08:08
<kaktux>
ok thx a lot. I wanted to use lubuntu current one - as the lts (18.04) uses a different desktop environment. They switched to lxqt starting 18.10 - thats why
08:09
in the long run i plan to use lts version
08:09
<alkisg>
OK that makes sense
08:09
Although 19.04 doesn't work for i386 clients
08:10
<kaktux>
anyway - i will just try out via virtual machine and go from there. Thx for all your input
08:10
<alkisg>
Also note that I'm currently rewritting ltsp from scratch,
08:10
so the new version that will be released in september will be completely different to the current one
08:11
<kaktux>
"will be released in september" doesnt sound like open source development to me ;) - im more used to "done when its done" - without sure dates
08:11
<alkisg>
Haha
08:11
Some times dates are used; e.g. in Ubuntu releases or GSoC projects ;)
08:12
<kaktux>
your right about that. Will the new version be included in upcoming ubuntu releases?
08:12
if so i will make a "test phase" for the 3 months
08:12
<alkisg>
I'm not sure if I'll release it for 20.04 or 20.10, but it will surely be there from 20.10 and on
08:13
<kaktux>
ok. sounds good
08:13
<alkisg>
If people ask for the old ltsp to be around for 20.04, we might keep it to make migration easier for them
08:15
<kaktux>
before migration i will try installation ;) thx for all you help. I will tryout a vm-installation (in general thats the plan: running it on a nas (qnap virtualization station)).
08:16
<alkisg>
Sure; remember to use a bridged adapter
08:16
<kaktux>
yeah - i know that problem already from other virtual machines i transfered from my local virtual box to the nas ;) thx a lot - you cleared my doubts about ltsp. have a nice day
08:17
<alkisg>
You too
08:17kaktux has left IRC (kaktux!58825afb@mue-88-130-90-251.dsl.tropolys.de, Remote host closed the connection)
08:24kaktu has joined IRC (kaktu!58825afb@mue-88-130-90-251.dsl.tropolys.de)
08:26
<kaktu>
hi there (once again) - the usual happend: as i closed the window another question entered my mind. As you mentioned the new release. On the ltsp wiki it says: "The Greek schools PPA is maintained by LTSP developers and offers new LTSP releases that are a lot more stable than those in the Ubuntu repositories. To add it to your sources [...]. Is thi
08:26
s still accurate? Meaning - if so - this may or may not have the new september version available before it is added as official ubuntu package. So this may be the fastest way to try it out once available.
08:28ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
08:29ogra has joined IRC (ogra!~ogra_@ubuntu/member/ogra)
08:33
<alkisg>
kaktu: I maintain the greek schools ppa; but I never upload ltsp for non-lts ubuntu releases there, so don't add it to your sources,
08:34
wrt ltsp5 (the current) vs ltsp19 (the next one), I'm thinking if I should have ltsp5 in ubuntu 20.04, and ltsp19 in the ppa, and then ltsp19 in ubuntu 20.10
08:34
(or... ltsp19 in ubuntu 20.04 directly)
08:35
<kaktu>
ok thx. good to know. btw. the ltsp wiki is quite spammed ;) - searching for fat client gives me some result about fat loss - not a big problem - but just in case you didnt know. Now i wont bother you from you work anymore. All is answered. Thx again
08:36
<alkisg>
kaktu: yeah ltsp.org is unmaintained, fortunately the domain owners agreed to move it to github.com/ltsp when I get that ready
08:37
<kaktu>
dont worry about it - the main info is still easily accesible for a human who can think. So no pressure. Have a nice day
08:37
<alkisg>
You too again :)
08:38kaktu has left IRC (kaktu!58825afb@mue-88-130-90-251.dsl.tropolys.de, Remote host closed the connection)
08:57nr0 has joined IRC (nr0!~nr0@217.118.78.84)
09:12nr0 has left IRC (nr0!~nr0@217.118.78.84, )
09:13pavars has joined IRC (pavars!5509db4e@85.9.219.78)
09:13
<pavars>
Hi, I'm new here and recently set up LTSP with ubuntu-mate
09:14
I wanted to ask if anyone has some info on how to customize the mate GUI for users system-wide, so I don't have to do it per user basis
09:15
like changing background, menu icon, menu theme etc. I did adjust /etc/skel but that only works for desktop iicons
09:15
like changing background, menu icon, menu theme etc. I did adjust /etc/skel but that only works for desktop icons
09:15
clients are running as thinclients
09:17
any advice would be greatly appreciated :)
09:29
<alkisg>
pavars: this question isn't related to ltsp; you can ask in #mate; that said, here's the answer: https://wiki.gnome.org/Projects/dconf/SystemAdministrators
09:43
<pavars>
thanks, figured it out on my own... the .files weren't properly copied to /etc/skel
10:00
<alkisg>
/etc/skel is the wrong way to do it; but ok whatever works for you
10:01
It'll only affect new users, and it can't support different /home/username paths per user
10:07pavars has left IRC (pavars!5509db4e@85.9.219.78, Ping timeout: 260 seconds)
10:33kjackal has left IRC (kjackal!~quassel@ppp-94-66-223-46.home.otenet.gr, Ping timeout: 248 seconds)
11:01kjackal has joined IRC (kjackal!~quassel@2a02:587:9a03:2100:10f5:22c9:80be:6fd9)
11:26statler has joined IRC (statler!~Georg@gwrz.lohn24.de)
11:35pavars has joined IRC (pavars!5509db4e@85.9.219.78)
11:37
<pavars>
Ok thanks, I'll have a look at it. We have user management via LDAP so there won't be different /home/username paths per user. And currently I only need it to be created when a new user logs in
12:11Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
12:19adrianorg has joined IRC (adrianorg!~adrianorg@191.32.103.186)
12:20woernie has joined IRC (woernie!~werner@p57A0EC92.dip0.t-ipconnect.de)
12:22adrianor1 has left IRC (adrianor1!~adrianorg@177.18.175.32, Ping timeout: 272 seconds)
12:27adrianorg has left IRC (adrianorg!~adrianorg@191.32.103.186, Ping timeout: 246 seconds)
12:42stellasolitaria has left IRC (stellasolitaria!~jhonny5@159.213.93.166, Ping timeout: 248 seconds)
12:49adrianorg has joined IRC (adrianorg!~adrianorg@187.113.246.225)
13:24jvss has joined IRC (jvss!c8118d03@aruana.ufs.br)
13:26
<jvss>
Hello, someone already used LTSP with Odroids as clients?
13:26
I need help
13:34
<mwalters>
I haven't heard of anyone using odroids, but I think there are a few raspi users (or used to be)
13:34
!ask
13:34
<ltsp`>
ask: Don't ask to ask a question, simply ask it, and if someone knows the answer, they'll respond. Please hang around for at least a full hour after asking a question, as not everybody constantly monitors the channel.
13:37
<alkisg>
jvss: I think vagrantc has used odroids some time in the past, why?
13:39adrianor1 has joined IRC (adrianor1!~adrianorg@177.156.58.97)
13:40adrianorg has left IRC (adrianorg!~adrianorg@187.113.246.225, Ping timeout: 245 seconds)
13:50
<jvss>
Because i m trying to use Odroids XU4 as clients, but I m with troubles to network boot
13:55mnevans has joined IRC (mnevans!8008b09d@zero.geol.umd.edu)
13:57
<mnevans>
Hello LTSP World. I am running a Debian 9.9 system. Yesterday updated it, and apparently with kernel 4.9.0-9-amd64, keyboard and mouse do not work under ltsp.
13:58
Booting with kernel 4.9.0-8-amd64 fixes that, but I think I need to make ltsp installation boot that kernel as well.
13:59
It currently tries to boot 4.9.0-9 and that doesn't work b/c it seems ltsp kernel and system kernel must match.
14:00
I tried to set update-kernels.conf in /opt/ltsp/amd64/etc/ltsp to show menu so I could choose the correct kernel
14:00
but this doesn't seem to work.
14:00
Suggestions? Thanks in advance.
14:01
I am pretty sure I am using nbd, but am not entirely certain!
14:01
Such is the case with ltsp - it works so well 99.9% of the time, I forget how to debug things...
14:03adrianor1 has left IRC (adrianor1!~adrianorg@177.156.58.97, Ping timeout: 245 seconds)
14:05
<mnevans>
Is there any more documentation besides https://wiki.debian.org/LTSP/Howto or http://wiki.ltsp.org/wiki/LTSPedia I should check?
14:09adrianorg has joined IRC (adrianorg!~adrianorg@187.115.105.2)
14:11jvss has left IRC (jvss!c8118d03@aruana.ufs.br, Remote host closed the connection)
14:14
<mwalters>
`ltsp-update-kernels` should update the kernels in tftproot
14:14
and the pxelinux conf
14:14
oh, you want to roll back
14:15
not sure about debian, but pxelinux stuff is found in /var/lib/tftpboot/ltsp on ubuntu
14:17
<alkisg>
mnevans: this sounds like you are booting a kernel that is not available in the chroot
14:17
What's is the output of these commands on the client? uname -a; ls /lib/modules
14:19
<mnevans>
Thanks, Yes. I can't boot the client, but server is running kernel 4.9.0-8-amd64. Client, I think, is trying to boot 4.9.0-9-amd64 which is the latest. I haven't succeeded in getting a client menu to be able to choose 4.9.0-8.
14:21
I also might have fungooled things trying booting with ntfs... trying to fix that now.
14:22
<alkisg>
I thought the client did boot but without mouse/keyb
14:23
<mnevans>
That was then, this is now...
14:23
<alkisg>
:)
14:23
<mnevans>
:|
14:23
<alkisg>
Also note that some times people end up with multiple tftp dirs
14:23
<mnevans>
Now I get from the client only : "a bootable device has not been detected.'
14:24
<alkisg>
And they try modifying one of them, while the real one is the other one
14:24
<mnevans>
I think it is trying to use ntfs now, not sure why. I did run ltsp-update-image and this behavior appeared afterward.
14:25
<alkisg>
nfs or nbd is a lot later than "bootable device not detected"
14:25
Up until the kernel/initrd is loaded, it's always tftp
14:25
<mnevans>
I have some copies of tftp directories, but they were copies from a previous troubleshooting for which I can't recall or find docs for problem or solution (my bad).
14:26
<alkisg>
If you have a vbox client, I could have a quick look over vnc
14:26
<mnevans>
ltsp-update-kernels is updating all of them.
14:27
Ihave used vbox in the past, but it has been reaaaaalllly slllloooooowwwww for even simple things.
14:28
<alkisg>
This isn't normal, maybe you didn't enable vt-d in the bios settings
14:28adrianorg has left IRC (adrianorg!~adrianorg@187.115.105.2, Ping timeout: 272 seconds)
14:28
<mnevans>
on the server? Possibly, I would have to check. Old server with lots of computning nodes, but low power/slow on each.
14:29
<alkisg>
Yeah, it's handy to be able to detect client problems with vnc
14:29
E.g. schools say "clients don't boot", I use a vbox fat client to test, and solve the issue
14:30
<mnevans>
How would I be sure that I am running with nbd and having set up (mistakenly) to boot with ntfs? Another client is saying 'nfs over tcp not available and then dropping to a busybox prompt. Can we work with that?
14:31
<alkisg>
cat /proc/cmdline on busybox
14:31
If you see nbd, it's nbd, etc etc
14:32
<mnevans>
Thanks, yes, its set to nfs. So how can I set it to boot using nbd, and then how to get the menu on the client to come up so I could choose the right kernel?
14:33
In /opt/ltsp/amd64/etc/ltsp/update-kernels.conf?
14:34
<alkisg>
Eeeh that requires writing around 15 lines, search for it, I answered it a few times both in irclogs.ltsp.organd the mailing list
14:34bluejaypop has joined IRC (bluejaypop!~BlueJay@201.175.203.114)
14:34
<alkisg>
!ltsp-discuss
14:34
<ltsp`>
ltsp-discuss: at https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
14:34
<mnevans>
I have tried setting PXELINUX_DEFAULT=menu, then running ltspo-update-kernels, then rebooting client, no luck.
14:39adrianorg has joined IRC (adrianorg!~adrianorg@177.132.220.63)
14:40
<mnevans>
Ah, sorry - thanks - will look there. keywords to search = nbd and boot and ?
14:45vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
14:46adrianorg has left IRC (adrianorg!~adrianorg@177.132.220.63, Ping timeout: 258 seconds)
14:47
<mnevans>
https://sourceforge.net/p/ltsp/mailman/message/36669125/
14:47
?
14:47mmarconm has joined IRC (mmarconm!~mmarconm@unaffiliated/mmarconm)
14:59
<mnevans>
Alkisg, Following these instructions seemed to help me boot one thin client:
14:59
https://sourceforge.net/p/ltsp/mailman/message/36669125/
15:00
Still can't boot another. But a client that was not rebooted since before the server upgrade is still running(!) That might help me figure things out.
15:00
<alkisg>
mnevans: heh, just one?
15:01
!vnc-dide
15:01
<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.
15:01
<alkisg>
Anyway, try this, I have a few minutes free just onw
15:01
<mnevans>
Ha ha. Just one. But the client that came up now with nfs boot is not accepting my password(!)
15:02
Alkis, this is on the server, correct?
15:02
or client?
15:02
<alkisg>
Right, and it requires running xorg
15:02
Server
15:04mmarconm has left IRC (mmarconm!~mmarconm@unaffiliated/mmarconm, Quit: Konversation terminated!)
15:06
<alkisg>
mnevans: so, you're using /srv/tftp
15:06
<mnevans>
OK
15:06
Is that good or bad?
15:06
:)
15:06
<alkisg>
You should delete /var/lib/tftpboot/ltsp, after getting backups of lts.conf etc, so that you don't get confused
15:06
It's not a problem as long as you know it :)
15:07
<mnevans>
There is lts.conf
15:07
Can I point it out?
15:09adrianorg has joined IRC (adrianorg!~adrianorg@177.156.227.240)
15:10bluejaypop has left IRC (bluejaypop!~BlueJay@201.175.203.114, Quit: Leaving)
15:16
<alkisg>
"bootable device has not been detected on my desktop client..." ==> I didn't see an IP request there
15:17
Now I do see 2 ips, and tftp requests
15:17
This is now using the default nbd setup
15:18
<mnevans>
That's two other thin clients I think.
15:18
I see boot menu; choose boot using ntfs?
15:18
<alkisg>
No
15:18
The default, nbd
15:18
<mnevans>
OK. I am really confused now.
15:18
:)
15:18
<alkisg>
You didn't set up nfs like I write in the mailing list
15:18
You tried to use the broken nfs of debian
15:19
I was advising "single file over nfs"; you tried to use "chroot over nfs"
15:19
Let's not make things complex; you were using nbd; continue to use it
15:19
<mnevans>
OK. Sorry I misundersl epoptes
15:20
<alkisg>
Did the clients boot? Can't see, you don't have epoptes
15:21
<mnevans>
No - message is 'gave up waiting for root file device'
15:21
Can install epoptes...
15:22
other client also didn't boot - 'bootable device has not been detected'.
15:22
Might be something with the client bios.
15:22
<alkisg>
Yeah ignore those they're in the wrong subnet or have wrong bios settings
15:22
They don't ask for an ip
15:22
What's the output of `cat /proc/cmdline` on the other ones, that give up on root device?
15:24
<mnevans>
root=/dev//dnev/nbdbd000
15:24* vagrantc blinks
15:24
<alkisg>
what, that's all?
15:24
Heya vagrantc
15:24
<mnevans>
No, hang on, I'll write it down and transcribe....
15:24
<alkisg>
I see your pings hours after you're gone! Can't seem to catch up with you lately :)
15:25
mnevans: you do have virtualization enabled in your processors, so virtualbox should run fine
15:25
<vagrantc>
alkisg: clearly it's not me catching up with *you* :)
15:25* vagrantc hasn't done any ltsp stuff worth catching up with :)
15:26
<mnevans>
re: virtualization, yes, then it must be slow processors
15:26
here is /cat/proc/cmdline output
15:27
<alkisg>
I relaxed a bit last week so I didn't do much. Separated the code into ltsp/{server, client, common}, and now I'll make it possible so that ltsp-client is, or is not, installed in the client image; the benefit when it is, is that it saves ram, as rsync/cp will see that the client code is already there
15:27pavars has left IRC (pavars!5509db4e@85.9.219.78, Ping timeout: 260 seconds)
15:28
<mnevans>
BOOT_IMAGE=vmlinuz-4.9.0-9-amd64 ro initrd=initrd.img-4.9.0-9-amd64 init=/sbin/init-ltsp quiet root=/dev/nbd0 BOOTIF=01-00-01-2e-40-8b-**
15:28
kernel is wrong. Server is running 4.9.0-8-amd64
15:28
<alkisg>
mnevans: it's fine; it's what the chroot has
15:28
<mnevans>
?
15:28
<alkisg>
You're using chroots, so the server kernel doesn't matter at all
15:28
Your client kernel is at /opt/ltsp/amd64/boot
15:29
Not at /boot
15:29
!nbd-client
15:29
<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
15:29
<alkisg>
Try this command , using the correct ip there, and amd64
15:29
<mnevans>
Ah, I thought what was preventing client coming up was different kernel: server and client.
15:29
<alkisg>
No, you can have 3.x kernel on the server and 5.x on the client, no problems there
15:33
<mnevans>
So mouting the NBD image from the client initramfs: no response to command, like it is waiting on connecting.
15:33
<alkisg>
And did you use the correct ip?
15:34
Do you have firewall or something?
15:34
<mnevans>
yes. ifconfig to confirm. No firewall between server and client.
15:39
<alkisg>
mnevans: I'm not looking at vnc, if you wrote something, I lost it
15:40
nbd-server.allow does not exist by default
15:40
<mnevans>
Ah - I had created nbd-server.allow because one of the errors I got on trying to boot a client was that this config file was missing
15:40
Should I delete it?
15:41
<alkisg>
!nbd-client
15:41
<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
15:41
<alkisg>
mnevans: try again this on the client
15:42
<mnevans>
OK
15:43
Same result - on its way to timeout I think.
15:43
reboot it and try again?
15:44
previo the error was : socket failed
15:45
<alkisg>
The message about nbd.allow is fine, it's just a warning
15:45
The problem is that the client doesn't ask for an nbd connection at all
15:45
Try rebooting the client, as you might be typing the command wrong
15:45
If it still fails, we'll see
15:46
<mnevans>
ok rebooting
15:48
At menu, selected LTSP, using NBD
15:48
some boot messages, then blank screen
15:48
should be client *.40
15:49
<alkisg>
I think this got past the nbd issue
15:49
It says "starting to serve"
15:49
Black screen seems unrelated
15:50
Btw I see a lot of ata errors, check your disk
15:50
<mnevans>
Yeah, that is worrisome! and new. Not found when rebooting server and disk check last night.
15:51gdi2k has left IRC (gdi2k!~gdi2k@58.69.160.28, Read error: Connection reset by peer)
15:52
<mnevans>
Is client booting kernel 4.9.0-9 or *-8?
15:52
*-9 gave keyboard/mouse unresponsive problem
15:52
<alkisg>
That would be because it was missing from the chroot
15:52
It shouldn't be an issue now
15:52
Try other options from the menu if you want, previous kernels etc
15:53
<mnevans>
No response from client *40. Blank screen only.
15:54
can't boot client *.45
15:54
I will try the previous kernel!
15:55gdi2k has joined IRC (gdi2k!~gdi2k@58.69.160.28)
15:56
<mnevans>
OK - client *40 came up with login. But returns to login on entering correct password. That problem looks familiar - but I don''t remember how to solve it.
15:58
syslog says password ok, then started session, then 3 errors:
15:59
udev-acl.ck[28819]: g_slice_set_config: assertion 'sys_page_size == 0' failed
15:59
console-kit-daemon[2134]: missing action
15:59
then
15:59
Received disconnect from 192.168.0.40 port 55852:11: disconnected by user
15:59
then
15:59
Disconnected from 192.168.0.40 port 55852'
16:00
pam_unix(sshd:session): session closed for user mnevans
16:08
Looks like I need to run ltsp-update-sshkeys, then ltsp-update-kernels?
16:09
Alkis, is that going to break anything we just did?
16:09
<alkisg>
(06:58:45 PM) mnevans: syslog says password ok, then started session, then 3 errors: ==> this means no ssh keys needed
16:13
<mnevans>
I think it is using default authentication - what is this? If not an ssh problem, any idea what could be happening here?
16:13
<alkisg>
try the failsafe xterm session
16:14
Also, your disk might be broken
16:17
<mnevans>
I get a spinning wheel cursor; and a login prompt but can't type anything there on the client.
16:18
<alkisg>
You need to move the mouse over the xterm to type
16:18
To the top left of the screen
16:18
If xterm works and normal session doesn't, it's not an authentication issue, it's xorg or broken disk or compositing etc
16:19
<mnevans>
Sorry - yep - that works.
16:20
So I can safely ltsp-update-kernels if need be?
16:20
I think I should diagnose these disk errors!
16:20
Thank you for your help!
16:21
Is there some way I can make a donation to the ltsp effort, to say thank you?
16:22
what did you mean by " or compositing etc?"
16:23
<mwalters>
"stuff that renders the desktop"
16:26
<mnevans>
Ah, thank you!
16:28
<alkisg>
mnevans: there's no entity behind ltsp that can accept donations etc; you may pay individual developers if they help you and if you want to, but there's no obligation...
16:28
Personally I give free help here when I have the time for it, and I'm also available for hire, for more time-consuming issues
16:29
<mnevans>
So I could send you monetary donation by paypal?
16:29
Or offer testing help for the upcoming release?
16:29
<alkisg>
Sure, if you want to; but I usually prefer to charge 30€ per hour for tasks that I do for the person that needs help
16:30
This way both are benefited
16:30
Re: testing, sure, that's welcome, but I'll deploy it to many schools in September, so that it'll be more tested when other end-users get it
16:31
If you need help with logging in, I'd need either epoptes or virtualbox, in order to help efficiently
16:36
<mnevans>
OK. Would like to send you 30 euros for the help today.
16:36
<alkisg>
Thank you; it's alkisg at gmail dot com
16:36* alkisg waves; jogging time; bb in a couple of hours
16:37
<mnevans>
Have just installed epoptes but was not able to run epoptes-client -c : there is nothing in /etc/epoptes/server.crt, failed to fetch certificate from server:789
17:04kjackal has left IRC (kjackal!~quassel@2a02:587:9a03:2100:10f5:22c9:80be:6fd9, Ping timeout: 252 seconds)
17:19mnevans has left IRC (mnevans!8008b09d@zero.geol.umd.edu, Remote host closed the connection)
18:05
<alkisg>
mnevans: back, if you watch irclogs :)
18:08Julien has joined IRC (Julien!8d8ab4a2@141.138.180.162)
18:08
<Julien>
Hello Everyone, I'm in an urgent need of help
18:08Julien is now known as Guest92384
18:08
<alkisg>
Guest92384: specifically?
18:09
<Guest92384>
I've been running ltsp server for quite some time now and I just ran an apt-get update then upgrade on the ltsp server (chrootless config)
18:09
after that, the clients froze and I'm unable to start them now
18:09
<alkisg>
What's the output of this command? sudo ltsp-info | nc termbin.com 9999
18:10
<Guest92384>
on the server ?
18:10
<alkisg>
Yes
18:10
And also, what is the error message when the clients won't start?
18:10
<Guest92384>
No LSB modules are available.https://termbin.com/14fu
18:10
On the client it outputs:
18:10
Error: Socket failed: Connection timed out
18:10
<alkisg>
sounds like nbd issues
18:11
<Guest92384>
yes indeed
18:11
after a long time it fails to Busybox
18:11
and I try to issue nbd-client commands
18:11
but they timeout
18:11
like nbd-client x.x.x.x -l won't work
18:11
whereas on the server it returns
18:11
E: listing not allowed by server.
18:13mnevans has joined IRC (mnevans!8008b09d@zero.geol.umd.edu)
18:15
<Guest92384>
I double checked the ndb-server configuration
18:15
and it seems all good
18:16
so I'm not sure if the issue is from nbd itself or if it's a network issue
18:18
<mnevans>
Hello Alkis - just wanted to report that I rebooted my server and performed a disk check on all disks - somehow came back clean. Then rebooted a client - OK and can login. In fact all clients seem to be back.
18:18
No idea exactly why.
18:18
:)
18:22
<Guest92384>
alkisg is there an easy way in busybox mode to check network configs ?
18:23
asking because I also see the following error (but not sure it is related)
18:23
no search or nameservers found in /run/net-eno1.conf ...
18:24
when I cat /run/net-eno1.conf on the client I see the following values
18:24
device='eno1'
18:25
IPV4ADDR='10.0.1.57' which is correct
18:25
IPV4NETMASK='255.255.255.0'
18:25
IPV4GATEWAY='10.0.1.1' which is correct
18:25
ROOTSERVER='10.0.1.31' which is the IP of the ltsp server
18:26
ROOTPATH='/opt/ltsp/amd64' which is the name of the ndb-server export
18:26
other values are here but empty
18:27kjackal has joined IRC (kjackal!~quassel@2a02:587:9a03:2100:10f5:22c9:80be:6fd9)
18:28
<alkisg>
mnevans: great! maybe it was disk/fsck related
18:29
Guest92384: try this
18:29
!nbd-client
18:29
<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:30
<Guest92384>
sure
18:30
<alkisg>
mnevans: do you need help with epoptes setup? It should be rather easy...
18:31
<Guest92384>
it seems not to be working, but my chrootless is an amd64 so is it normal to be using an i386 one ?
18:31
<alkisg>
No, replace the ip and i386 in that command
18:32
<Guest92384>
ohh for the IP you want me to use the IP of the ltsp server ?
18:32
<alkisg>
yes
18:32
<Guest92384>
I tried this already, it did not work either
18:32
<alkisg>
What was the error message?
18:32
<Guest92384>
Error: Socket failed: Connection timed out
18:33
<alkisg>
And you did use the correct ip?
18:33
<Guest92384>
yes
18:33
<alkisg>
OK, can you vnc to me?
18:33
!vnc-dide
18:33
<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.
18:33
<Guest92384>
this is the command I tried: nbd-client 10.0.1.31 -N /opt/ltsp/amd64 /dev/nbd0
18:33
<alkisg>
From the client initramfs, right?
18:33
Sounds correct
18:33
<Guest92384>
you want me to run this on the server or the client ?
18:33
<alkisg>
On the server
18:34
<Guest92384>
from the client initramfs yes
18:34
<alkisg>
It'll share your server screen with me
18:34
Like quick teamviewer
18:35
<Guest92384>
can't I give you access through Epoptes ?
18:35
<alkisg>
!vnc-edide
18:35
<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
18:35
<alkisg>
Sure, it's the same
18:36kjackal has left IRC (kjackal!~quassel@2a02:587:9a03:2100:10f5:22c9:80be:6fd9, Ping timeout: 252 seconds)
18:40
<alkisg>
Guest92384: boot a client
18:40
<Guest92384>
ok trying now
18:41
it seems to be doing the same
18:41
<alkisg>
I don't see an nbd request though
18:42
<Guest92384>
yes I did try this too and noticed the same
18:42
as if the networks configuration has been altered
18:42
<alkisg>
OK we'll wait until it drops to initramfs
18:42
then you'll try again the nbd-client command
18:42
so that i see if it says version mismatch or anything
18:42
You don't have a firewall, do you?
18:43
<Guest92384>
nop not in my local network
18:43
plus nothing I modified today
18:44
<alkisg>
Did the client reach the initramfs prompt?
18:44
<Guest92384>
it just did
18:44
I issued the nbd-client comment just now
18:44
<alkisg>
can you ping 10.0.1.31?
18:45
<Guest92384>
well I tried but it seems that the ping command is not available in the initramfs
18:45
<alkisg>
Hm right
18:45
<Guest92384>
though the initial image is being loaded through tftp
18:45
so network wise (mean hardware equipement and config) it is working
18:45
<alkisg>
try:
18:45
wget 10.0.1.31:8000/lts.conf
18:46
Does that work, from the client?
18:46
<Guest92384>
I will try as soon as the nbd-client command times out
18:46
<alkisg>
Ouch :D
18:46
openvt bash -l => gives you vt2, for another time
18:46
<Guest92384>
ok
18:46
tryed the wget
18:47
it is hanging on the Connecting to 10.0.1.31:8000 line
18:47
and nothing happens
18:47
so it seems like a network configuration on the ltsp client level ?
18:47
<alkisg>
So the client networking seems broken, yes; or... firewall
18:47
If you get a shell, try `ip a`
18:47
See what ip/gateway it has etc
18:48
<Guest92384>
the wget is not timing out :-(
18:48
<alkisg>
reboot... and openvt
18:48
<Guest92384>
ok
18:52
<alkisg>
sudo ltsp-update-image -r / ==> reverts to the previous image, in a few secs
18:53
So that you verify it's image-related
18:54
<Guest92384>
ok the reboot finished
18:54
so the ip a
18:54
gives me an inet value that looks legit
18:54
10.0.1.57
18:54
do you want me to look at something else ?
18:57
I'm rebooting with the reverted image
18:57
but I don't think it's image related, as when the problem occured, one person tried to reboot multiple times before I created the new image and it wasn't working
18:57
trying though
18:58
same problem
18:58
if I revert again it will put back the new image ?
19:01
<alkisg>
yes
19:01
<Guest92384>
ok
19:02
I'm running out of ideas here...
19:02
wondering one thing though
19:02Guest92384 has left IRC (Guest92384!8d8ab4a2@141.138.180.162, Remote host closed the connection)
19:03Julien has joined IRC (Julien!8d8ab4a2@141.138.180.162)
19:03
<Julien>
if tftp worked to load the image, doesn't this mean that Network level things are OK ?
19:03Julien is now known as Guest82753
19:03Guest82753 is now known as ewJulien
19:10
<alkisg>
ewJulien: not necessarily; e.g. tftp might work at 100 mbps (bios) while later on kernel at gigabit, with broken cables
19:10
I would test with a virtualbox client next
19:11
<ewJulien>
well what drives me crazy is that it was working well.. during the update of the server, stations froze and couldn't reboot
19:11
as if the nbd disk failed and is now unable to reconnect
19:11
<alkisg>
and wget too? :)
19:12
nope, that doesn't sound right
19:16
<ewJulien>
you suspect a network hardware failure or misconfiguration ?
19:18ewJulien has left IRC (ewJulien!8d8ab4a2@141.138.180.162, Remote host closed the connection)
19:28statler has left IRC (statler!~Georg@gwrz.lohn24.de, Remote host closed the connection)
19:34ewJulien has joined IRC (ewJulien!8d8ab4a2@141.138.180.162)
19:35
<ewJulien>
alkisg I got a connection issue apparently
19:35
well your suspicion made me think, I restarted one of the switches...
19:35
and it worked again!
19:35
<alkisg>
:)
19:35
<ewJulien>
Thank you a lot for your help
19:36
is there anything we shall undo before I disconect the remote assistance session ?
19:36
<alkisg>
No I wasn't monitoring it :)
19:36
Just close it!
19:36
<ewJulien>
ok
19:36
and for the terminal windows you opened ?
19:41
<alkisg>
close all of them , sure
19:45ewJulien has left IRC (ewJulien!8d8ab4a2@141.138.180.162, Ping timeout: 260 seconds)
19:50mnevans has left IRC (mnevans!8008b09d@zero.geol.umd.edu, Remote host closed the connection)
20:15kjackal has joined IRC (kjackal!~quassel@2a02:587:9a03:2100:10f5:22c9:80be:6fd9)
20:16ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
20:39GodFather has joined IRC (GodFather!~rcc@d53-64-7-141.nap.wideopenwest.com)
20:50Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
21:00kjackal has left IRC (kjackal!~quassel@2a02:587:9a03:2100:10f5:22c9:80be:6fd9, Ping timeout: 252 seconds)
23:59spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Quit: Leaving)