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


Channel log from 9 October 2020   (all times are UTC)

01:37jgee has left IRC (jgee!~jgee@190.159.118.121, Read error: Connection reset by peer)
01:37jgee7 has joined IRC (jgee7!~jgee@190.159.118.121)
05:36RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro)
07:11woernie has joined IRC (woernie!~werner@pd9f60c02.dip0.t-ipconnect.de)
08:52eu^cgn-213-196-2 has joined IRC (eu^cgn-213-196-2!d5c4d36d@cgn-213-196-211-109.nc.de)
08:52eu^cgn-213-196-2 has left IRC (eu^cgn-213-196-2!d5c4d36d@cgn-213-196-211-109.nc.de, Remote host closed the connection)
08:58woernie has left IRC (woernie!~werner@pd9f60c02.dip0.t-ipconnect.de, Ping timeout: 240 seconds)
09:24Aison0 has joined IRC (Aison0!~Asion0@2a02:168:200f:110:1dfa:baf4:9142:6399)
11:02uumas has left IRC (uumas!uumaskapsi@gateway/shell/matrix.org/x-avicbavzxdnwltgm, Quit: killed)
11:09uumas has joined IRC (uumas!uumaskapsi@gateway/shell/matrix.org/x-zfuviwsnaeidbcbs)
11:34jgee7 has left IRC (jgee7!~jgee@190.159.118.121, *.net *.split)
11:34bcg has left IRC (bcg!~b@dg4ybwyyyyyyyyyyyyyyt-3.rev.dnainternet.fi, *.net *.split)
11:34jgee77 has joined IRC (jgee77!~jgee@190.159.118.121)
11:40bcg has joined IRC (bcg!~b@dg4ybwyyyyyyyyyyyyyyt-3.rev.dnainternet.fi)
12:20woernie has joined IRC (woernie!~werner@p200300e3bf02ef2768a0b81ad93dcc4f.dip0.t-ipconnect.de)
12:27Aison0 is now known as Jumper
12:56woernie has left IRC (woernie!~werner@p200300e3bf02ef2768a0b81ad93dcc4f.dip0.t-ipconnect.de, Ping timeout: 260 seconds)
15:15gvy has joined IRC (gvy!~mike@altlinux/developer/mike)
15:15Jumper has left IRC (Jumper!~Asion0@2a02:168:200f:110:1dfa:baf4:9142:6399, Ping timeout: 272 seconds)
15:15Jumper has joined IRC (Jumper!~Asion0@2a02:168:200f:110:1dfa:baf4:9142:6399)
15:22Talikka has joined IRC (Talikka!uid18862@gateway/web/irccloud.com/x-qribzleeuitvxvzd)
15:50woernie has joined IRC (woernie!~werner@p200300e3bf02ef2768a0b81ad93dcc4f.dip0.t-ipconnect.de)
16:23gvy has left IRC (gvy!~mike@altlinux/developer/mike, Remote host closed the connection)
18:42eu^static2372472 has joined IRC (eu^static2372472!52d5f7ed@82.213.247.237)
18:43
<eu^static2372472>
hi
18:43
<alkisg>
Hello
18:44
<eu^static2372472>
I'm looking at ltsp19 coming from previous ltsp5 and I'm a bit lost
18:44
<alkisg>
ltsp20? lost, how?
18:44
<eu^static2372472>
how do you see a list of current clients?
18:44
in old ltsp you simply check ltsp.conf and dhcp.conf to see all clients with static ip
18:45
with current version I don't see ltsp.conf in any place and dhcp.conf seems to be assigning ip's dinamically
18:45
<alkisg>
If you declare the clients in ltsp.conf, this hasn't changed, they're there now too
18:45
!ltsp.conf
18:45
<ltspbot>
ltsp.conf: Configuration file for LTSP: https://ltsp.org/man/ltsp.conf/
18:45
<alkisg>
Read the first paragraph there, "creation"
18:47
<eu^static2372472>
ok, but this paragraph says: "install -m 0660 -g sudo /usr/share/ltsp/common/ltsp/ltsp.conf /etc/ltsp/ltsp.conf"
18:48
so it seems resulting ltsp is created in /etc/ltsp/ltsp.conf
18:48
but I don't have that file
18:48
<alkisg>
You ran that command and it didn't create a file?
18:48
<eu^static2372472>
I don't have /usr/share/ltsp/common/ltsp/ltsp.conf neither
18:48
<alkisg>
Did you actually install ltsp?
18:48
What's the output of this command? dpkg -l | grep ltsp
18:48
<eu^static2372472>
my ltsp installion is an already installed one, I didn't install it
18:49
<alkisg>
!pastebin
18:49
<ltspbot>
pastebin: see !paste
18:49
<alkisg>
!paste
18:49
<ltspbot>
paste: To avoid channel flooding, please upload text longer than 3 lines to http://paste.debian.net. Don't forget to paste the resulting URL here.
18:49
<eu^static2372472>
ii ltsp-client 5.18.12+t201905250652~ubuntu18.04.1 amd64 complete LTSP client environment
18:49
5.18.12+t201905250652~ubuntu18.04.1 all basic LTSP server environment
18:49
based remote filesystem for LTSP thin clients
18:49
daemon for LTSP thin clients
18:49
<alkisg>
See that's not ltsp20
18:49
It's ltsp5
18:49
<eu^static2372472>
sorry, i pasted it before read your advise
18:51
oh, ok, I've been told its new ltsp
18:51
<alkisg>
Btw where did you run that command, in an ltsp client?
18:53
<eu^static2372472>
in that case sorry for the inconvenience
18:53
<alkisg>
No worries, this is also the channel for ltsp5 :)
18:53
<eu^static2372472>
yes, a ltsp client
18:53
as I've been told this is a new ltsp (i see it is not) running with fat clients only
18:54
<alkisg>
This sounds like an old ltsp running with fat clients only
18:54
<eu^static2372472>
from the client I ssh to the server
18:54
and there I look for ltsp config files or whatever
18:55
I can get root access to the server
18:55
<alkisg>
They're in /var/lib/tftpboot/ltsp
18:55
(in ltsp5)
18:55
And some of them might be in /etc/ltsp
18:56
<eu^static2372472>
in /etc/ltsp I only have 3 files: dhcpd.conf ltsp-update-image.excludes update-kernels.conf
18:57
<alkisg>
Yes
18:57
<eu^static2372472>
and dhcpd.con does not list the cients
18:57
<alkisg>
(09:44:56 PM) eu^static2372472: in old ltsp you simply check ltsp.conf and dhcp.conf to see all clients with static ip
18:57
Didn't you say that? :)
18:57
Are you sure your clients have a static ip?
18:57
<eu^static2372472>
yes I said that
18:58
<alkisg>
What are you trying to find, the running clients?
18:58
The ones the have logged in? The ones that have a static ip?
18:58
<eu^static2372472>
that is the usual way I config the clients
18:58
<alkisg>
These 3 are different things
18:59
<eu^static2372472>
but this installation uses dynamic ip, in dhcp.conf I can see: range 192.168.67.20 192.168.67.250;
18:59
<alkisg>
Can you start with your goal?
18:59
<eu^static2372472>
I want to see how many clients are in my ltsp network
18:59
<alkisg>
What are you trying to do eventually?
18:59
<eu^static2372472>
then want to know the actual ip of every client
18:59
<alkisg>
The ones that are booted, or the ones that are closed as well?
18:59
*powered off
19:00
!list
19:00
<ltspbot>
Admin, Channel, ChannelLogger, Config, Factoids, Misc, Owner, RSS, Seen, Status, Time, User, and Utilities
19:00
<alkisg>
!client-list
19:00
<ltspbot>
client-list: to get a list of all nbd-clients (which sometimes is the same as ltsp clients), run: ss -n | sed -n 's/.*:10809 *\([0-9.]*\):.*/\1/p' | sort -Vu
19:00
<alkisg>
This is the list of the running clients
19:00
<eu^static2372472>
all clients, booted (on or active) and inactive (off or powered off)
19:00
<alkisg>
If you're using nbd, which is the default in ltsp5
19:00
You CANNOT get a list of powered off clients if you're using dynamic ips
19:01
<eu^static2372472>
so ltsp did not maintain an internal list of clients?
19:01
<alkisg>
No
19:01
<eu^static2372472>
for example, a history of all connected clients
19:01
<alkisg>
No
19:01
There is a history of log ins or authentication requests etc etc in your syslog
19:02
<eu^static2372472>
ok
19:02
<alkisg>
You could write a script to parse your syslog, depending on which programs you use and what they write in syslog
19:03
<eu^static2372472>
ok, and the ss commend sugested by the bot I assume is only valid for active connected clients
19:03
<alkisg>
Yes I wrote that command to detect the currently booted nbd clients
19:04
<eu^static2372472>
the messages in syslog follow the same pattern? I mean sed -n 's/.*:10809 *\([0-9.]*\):.*/\1/p' |
19:05
<alkisg>
No. Use `cat /var/log/syslog` and see if you can find any information there
19:05
It's not certain that you'll find connection logs
19:05
For example, dnsmasq logs information there by default, but isc-dhcp doesn't
19:06
It depends on which programs you use; you'll just have to read syslog to see
19:06
<eu^static2372472>
I'm searching for ltsp strings in syslog but nothing found
19:07
<alkisg>
Don't search for ltsp
19:07
Search for dhcp and nbd
19:07
Or tftp
19:07
Or boot a client now and see if it produces any new logs with its ip
19:07
<eu^static2372472>
but I see there're several dirs under /var/log named with a ltsp pattern suchs as /var/log/ltsp118.xdom.com
19:08
<alkisg>
Are you searching on the server or the client?
19:09
<eu^static2372472>
and inside it there're a lot of log files of different programs and services such as cron dbus epoptes-client sh ...
19:09
<alkisg>
It's possible that your predecessor had enabled ltsp client syslog forwarding to the server
19:09
If so, you can just ls /var/log/ltsp*
19:09
Can't you just ask him?
19:10
<eu^static2372472>
nothing of dhcp or ndd but I see some entries of tftp
19:10
<alkisg>
Also old epoptes logged connections in /var/log/epoptes
19:10
<eu^static2372472>
I will follow that path, thanks!
19:11
no, my predecesor is not available, sadly
19:13
there's no file like /var/log/epoptes or /bar/log/ltsp*
19:13
but there're several /var/log/ltsp* directories
19:14
<alkisg>
I'd say just boot a client and grep -r its mac/ip under /var/log
19:14
<eu^static2372472>
inside them there's a epoptes-client.log
19:14
but no info about IPs
19:14
<alkisg>
Don't waste time in searching one by one. Do it with example
19:15
Or grep the subnet, e.g. grep -r 192.168.67 /var/log
19:20
<eu^static2372472>
it takes a bit...
19:20
nothing found
19:21vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
19:22
<alkisg>
Heya vagrantc; I applied for the new "github discussions beta" program: https://github.community/t/can-one-apply-for-github-discussions-beta/121120/295
19:22
I'm thinking of migrating https://github.com/ltsp/community/issues to https://github.com/ltsp/ltsp/discussions, when they're up
19:22woernie has left IRC (woernie!~werner@p200300e3bf02ef2768a0b81ad93dcc4f.dip0.t-ipconnect.de, Remote host closed the connection)
19:24
<vagrantc>
alkisg: ok. no strong opinions here. worst case, can always move it back?
19:24
<alkisg>
I think I'll have to move 100+ discussions manually, click move, click next...
19:24
So I'd like to avoid doing it twice :D
19:24
<vagrantc>
ouch!
19:24
<eu^static2372472>
ok, thanks for your help, anyway
19:25
<alkisg>
eu^static2372472: np; you might be searching for the wrong subnet there; in any case it's just grepping, not ltsp related
19:25
ltsp by itself doesn't keep any logs
19:26
vagrantc: example discussions: https://github.com/nhibernate/nhibernate-core/discussions
19:27
I think they're going to be used a lot in projects from now on
19:27
So I guess github users will get used to them, and expect them to be there
19:31Talikka has left IRC (Talikka!uid18862@gateway/web/irccloud.com/x-qribzleeuitvxvzd, Quit: Connection closed for inactivity)
19:34
<eu^static2372472>
I'm looking for the right subnet, taked from dhcp.conf
19:35
<alkisg>
eu^static2372472: what's the output of `ip a` on the server?
19:35
<eu^static2372472>
but really thanks for your help and focusing me to the right path
19:35
<alkisg>
Because if it doesn't have 192.168.67.x, then it's not the right subnet
19:36
Anyway just boot a client and see
19:36
<eu^static2372472>
good point
19:36
tanks, I'll do what you say
19:36
<vagrantc>
alkisg: i won't likely be much of a participant, but i'm not the target audience
19:36
<alkisg>
The existance of /etc/ltsp/dhcpd.conf doesn't mean that dhcp is in use
19:36
<eu^static2372472>
thanks a lot
19:36
<alkisg>
You might still be using dnsmasq
19:36
eu^static2372472: np, bye
19:37
<eu^static2372472>
I see this group is really useful and nice
19:37
thankyou
19:41
just one more question
19:41
in the ss command the port 10809 is fixed in LTSP connections?
19:41
<alkisg>
10809 is the nbd protocol
19:42
<eu^static2372472>
ok
19:43
thank you alkisg
19:43
<alkisg>
np
19:45
<eu^static2372472>
bye!
19:45eu^static2372472 has left IRC (eu^static2372472!52d5f7ed@82.213.247.237, Remote host closed the connection)
20:25RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.)
22:16Jumper has left IRC (Jumper!~Asion0@2a02:168:200f:110:1dfa:baf4:9142:6399, Remote host closed the connection)
22:36vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)