IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 12 August 2019 (all times are UTC)
| 01:19 | mmarconm has left IRC (mmarconm!~mmarconm@unaffiliated/mmarconm, Remote host closed the connection) | |
| 01:19 | mmarconm has joined IRC (mmarconm!~mmarconm@200.140.189.122) | |
| 01:19 | mmarconm has joined IRC (mmarconm!~mmarconm@unaffiliated/mmarconm) | |
| 02:53 | shored has left IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi, Read error: Connection reset by peer) | |
| 02:53 | shored has joined IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi) | |
| 04:00 | shored has left IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi, Read error: Connection reset by peer) | |
| 04:00 | shored has joined IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi) | |
| 05:46 | statler has joined IRC (statler!~Georg@p548978DB.dip0.t-ipconnect.de) | |
| 05:51 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 05:54 | adrianor1 has joined IRC (adrianor1!~adrianorg@177.134.57.16) | |
| 05:57 | adrianorg has left IRC (adrianorg!~adrianorg@186.213.156.16, Ping timeout: 246 seconds) | |
| 06:23 | pavars has joined IRC (pavars!~pavars@85.9.219.78) | |
| 06:25 | yanu has joined IRC (yanu!~yanu@178-116-55-218.access.telenet.be) | |
| 06:38 | pavars_ has joined IRC (pavars_!~pavars@213.226.141.164) | |
| 06:41 | pavars has left IRC (pavars!~pavars@85.9.219.78, Ping timeout: 268 seconds) | |
| 06:56 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 08:31 | kjackal has joined IRC (kjackal!~quassel@ppp-94-66-223-142.home.otenet.gr) | |
| 08:38 | statler has left IRC (statler!~Georg@p548978DB.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 08:40 | pavars_ has left IRC (pavars_!~pavars@213.226.141.164, Remote host closed the connection) | |
| 08:47 | pavars has joined IRC (pavars!~pavars@213.226.141.164) | |
| 08:48 | pavars_ has joined IRC (pavars_!~pavars@213.226.141.164) | |
| 08:51 | pavars__ has joined IRC (pavars__!~pavars@85.9.219.78) | |
| 08:51 | pavars has left IRC (pavars!~pavars@213.226.141.164, Ping timeout: 248 seconds) | |
| 08:54 | pavars_ has left IRC (pavars_!~pavars@213.226.141.164, Ping timeout: 258 seconds) | |
| 09:26 | statler has joined IRC (statler!~Georg@gwrz3.lohn24.de) | |
| 09:55 | <pavars__> Hi, just tested now and found what was the issue for getting -bash -fork: resource temporarily unavailable
| |
| 09:55 | I raised both of these limits to 20k and 25k
| |
| 09:55 | Additional information for modern (systemd) linux systems.
| |
| 09:55 | There are many resources about this of values that may need tweaking (the other answer is a good source for most of them); however a new limit is imposed by way of the systemd "TasksMax" limit which sets pids.max on the cgroup.
| |
| 09:55 | For login sessions the UserTasksMax default is 33% of the kernel limit pids_max (usually 12,288) and can be override in /etc/systemd/logind.conf.
| |
| 09:55 | For services the DefaultTasksMax default is 15% of the kernel limit pids_max (usually 4,915). You can override it for the service by setting TasksMax in "systemctl edit" or update DefaultTasksMax in /etc/systemd/system.conf
| |
| 09:56 | before that the thread count didn't go above ~5k
| |
| 09:56 | # ps -elfT | wc -l
| |
| 09:56 | 5286
| |
| 09:56 | now it goes to 15k
| |
| 09:57 | <alkisg> Are you the one that had issues logging in more than 10 thin client users or so, and this solves it?
| |
| 09:57 | <pavars__> no issues with 21 user thus far, only application issues
| |
| 09:57 | @alkisg yes
| |
| 09:57 | <alkisg> Great; ltsp19 doesn't support thin clients, but ltsp5 users might find that useful
| |
| 09:57 | It might also apply for ltsp19 + x2go or xrdp users
| |
| 09:57 | <pavars__> because everything is running under ssh.service and it hits the limit at some point but it's not logged anywhere
| |
| 09:58 | what's the plan for ltsp19 and when is it coming out?
| |
| 09:59 | <alkisg> I have the first .deb package ready; it's in alpha; I guess I'll call it "releasable" by the end of the month...
| |
| 09:59 | <pavars__> we will be upgrading to fujitsu s720 do you think they could handle "FAT" client?
| |
| 09:59 | <alkisg> I think you said you tried them as fat and they were slow?
| |
| 09:59 | <pavars__> we tried with s550
| |
| 10:00 | <alkisg> Acceptable browsing is around 1000 cpu score in cpubenchmark.ne
| |
| 10:00 | *net
| |
| 10:00 | <pavars__> s720 is newer model https://www.fujitsu.com/fts/products/computing/pc/thin-clients/FUTRO-S720/
| |
| 10:00 | <alkisg> So check the exact cpu model there, and tell us the score
| |
| 10:00 | E.g. my laptop has 12447 score: https://www.cpubenchmark.net/cpu.php?cpu=Intel+Core+i7-8750H+%40+2.20GHz&id=3237
| |
| 10:01 | so it's around 50 times faster than your old clients :P
| |
| 10:01 | <pavars__> AMD G-Series GX-222GC has 1255
| |
| 10:01 | <alkisg> 1255 is acceptable browsing
| |
| 10:01 | Definitively should be fat, not thin
| |
| 10:02 | *definitely
| |
| 10:03 | <pavars__> I have the same cpu for my laptop :p
| |
| 10:17 | adrianorg has joined IRC (adrianorg!~adrianorg@201.22.230.149) | |
| 10:20 | adrianor1 has left IRC (adrianor1!~adrianorg@177.134.57.16, Ping timeout: 268 seconds) | |
| 10:41 | kjackal has left IRC (kjackal!~quassel@ppp-94-66-223-142.home.otenet.gr, Ping timeout: 272 seconds) | |
| 10:52 | kjackal has joined IRC (kjackal!~quassel@2a02:587:9a0a:ed00:e84a:a70b:c1c6:37d5) | |
| 10:54 | pavars__ has left IRC (pavars__!~pavars@85.9.219.78, Remote host closed the connection) | |
| 11:32 | pavars has joined IRC (pavars!~pavars@85.9.219.78) | |
| 11:37 | pavars has left IRC (pavars!~pavars@85.9.219.78, Ping timeout: 245 seconds) | |
| 11:45 | pavars has joined IRC (pavars!~pavars@85.9.219.78) | |
| 11:58 | Faith has joined IRC (Faith!~Paty_@unaffiliated/faith) | |
| 12:01 | <pavars> will ltsp19 be majorly different from ltsp5 ?
| |
| 12:03 | kjackal has left IRC (kjackal!~quassel@2a02:587:9a0a:ed00:e84a:a70b:c1c6:37d5, Remote host closed the connection) | |
| 12:05 | kjackal has joined IRC (kjackal!~quassel@2a02:587:9a0a:ed00:dd6:937d:17e9:5d61) | |
| 12:08 | <alkisg> !migration
| |
| 12:08 | <ltsp> migration: https://github.com/ltsp/ltsp/wiki/migration may help LTSP5 users get oriented in the new LTSP concepts
| |
| 12:08 | <alkisg> pavars: read that one ^
| |
| 12:08 | <pavars> :)
| |
| 12:08 | <alkisg> (and tell me if it needs fixes/clarifications)
| |
| 12:10 | Btw, the first build is ready, for advanced users that have a VM or a spare server to test ltsp19 in...
| |
| 12:10 | !installation
| |
| 12:10 | <ltsp> Error: "installation" is not a valid command.
| |
| 12:10 | <alkisg> !install
| |
| 12:10 | <ltsp> install: To install LTSP19+: https://github.com/ltsp/ltsp/wiki/installation. To install LTSP5: http://wiki.ltsp.org/wiki/Installation/Ubuntu for Ubuntu, or http://wiki.ltsp.org/wiki/Installation for other distributions
| |
| 12:11 | <alkisg> !learn installation as To install the new LTSP, start there: https://github.com/ltsp/ltsp/wiki/installation
| |
| 12:11 | <ltsp> The operation succeeded.
| |
| 12:11 | <pavars> I'm not sure if I understand completely "But you can still netboot clients up to the login screen, and then set up a session that uses xfreerdp, x2go or vnc to access the server in a manner similar to thin clients." does it mean that the thinclients will need an OS to be able to connect to ltsp or is it still network boot?
| |
| 12:11 | <alkisg> It is still network boot
| |
| 12:11 | <pavars> so xrdp/ x2go are optional
| |
| 12:11 | <alkisg> But the "remote desktop" part is now handled by x2go/xfreerdp etc, not by ltsp
| |
| 12:12 | x2go/xrdp are what will create a "thin session" instead of the default "fat session" of ltsp19+
| |
| 12:12 | <pavars> ohh, so fat clients won't need x2go/ xrdp
| |
| 12:12 | <alkisg> Right
| |
| 12:12 | <pavars> all clear
| |
| 12:12 | <alkisg> Ouch, I guess I wasn't very clear in the wiki :D
| |
| 12:13 | <pavars> ¯\_(ツ)_/¯
| |
| 12:15 | ok, but with the user limit issue resolved there are still two annoying issues - 1) sometimes the clients boot up to a black screen and takes several reboots until it shows ubuntu login screen
| |
| 12:15 | <alkisg> Do you have epoptes installed?
| |
| 12:16 | <pavars> 2) sometimes for some users it shows Ubuntu is updating (or something) system will reboot in 10, 9 ...
| |
| 12:16 | and they need to click cancel
| |
| 12:16 | yes, epoptes is installed
| |
| 12:16 | <alkisg> !checkupdate
| |
| 12:16 | <ltsp> I do not know about 'checkupdate', but I do know about these similar topics: 'nbd-checkupdate'
| |
| 12:16 | <alkisg> !nbd-checkupdate
| |
| 12:16 | <ltsp> nbd-checkupdate: To avoid bug https://github.com/NetworkBlockDevice/nbd/issues/59, put this in lts.conf: INIT_COMMAND_RM_NBD_CHECKUPDATE="rm -rf /usr/share/ldm/rc.d/I01-nbd-checkupdate"
| |
| 12:16 | <alkisg> You can solve (2) with that ^
| |
| 12:16 | About (1), when it happens, ping me to see it via epoptes
| |
| 12:17 | <pavars> we have stopped the user testing for now, as this server will be shipped to a different location
| |
| 12:17 | I will try to get the black screen in the evening
| |
| 12:21 | section1 has joined IRC (section1!~section1@178.33.109.106) | |
| 13:14 | pavars has left IRC (pavars!~pavars@85.9.219.78, Remote host closed the connection) | |
| 13:23 | pavars has joined IRC (pavars!~pavars@85.9.219.78) | |
| 14:03 | pavars has left IRC (pavars!~pavars@85.9.219.78, Remote host closed the connection) | |
| 14:07 | pavars has joined IRC (pavars!~pavars@85.9.219.78) | |
| 14:30 | shored has left IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi, Read error: Connection reset by peer) | |
| 14:31 | shored has joined IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi) | |
| 14:31 | pavars_ has joined IRC (pavars_!~pavars@85.9.219.78) | |
| 14:31 | pavars has left IRC (pavars!~pavars@85.9.219.78, Read error: Connection reset by peer) | |
| 14:33 | pavars_ has left IRC (pavars_!~pavars@85.9.219.78, Remote host closed the connection) | |
| 14:38 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 14:40 | ZAJDAN has joined IRC (ZAJDAN!~zdenek@77.48.149.75) | |
| 15:18 | <alkisg> !ppa
| |
| 15:18 | <ltsp> ppa: https://github.com/ltsp/ltsp/wiki/ppa describes how Debian and Ubuntu users may add the upstream LTSP PPA to their sources, to be able to install LTSP
| |
| 15:51 | ZAJDAN has left IRC (ZAJDAN!~zdenek@77.48.149.75, Remote host closed the connection) | |
| 15:51 | ZAJDAN has joined IRC (ZAJDAN!~zdenek@77.48.149.75) | |
| 15:53 | shored has left IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi, Read error: Connection reset by peer) | |
| 15:53 | shored has joined IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi) | |
| 16:27 | kjackal has left IRC (kjackal!~quassel@2a02:587:9a0a:ed00:dd6:937d:17e9:5d61, Ping timeout: 252 seconds) | |
| 16:30 | statler has left IRC (statler!~Georg@gwrz3.lohn24.de, Read error: Connection reset by peer) | |
| 17:08 | adrianor1 has joined IRC (adrianor1!~adrianorg@187.113.251.237) | |
| 17:10 | adrianorg has left IRC (adrianorg!~adrianorg@201.22.230.149, Ping timeout: 248 seconds) | |
| 17:44 | kjackal has joined IRC (kjackal!~quassel@2a02:587:9a0a:ed00:dd6:937d:17e9:5d61) | |
| 17:53 | adrianorg has joined IRC (adrianorg!~adrianorg@177.156.61.113) | |
| 17:55 | adrianor1 has left IRC (adrianor1!~adrianorg@187.113.251.237, Ping timeout: 272 seconds) | |
| 17:56 | kjackal has left IRC (kjackal!~quassel@2a02:587:9a0a:ed00:dd6:937d:17e9:5d61, Ping timeout: 252 seconds) | |
| 18:03 | adrianorg has left IRC (adrianorg!~adrianorg@177.156.61.113, Ping timeout: 245 seconds) | |
| 18:23 | adrianorg has joined IRC (adrianorg!~adrianorg@177.132.221.50) | |
| 19:17 | shored has left IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi, Read error: Connection reset by peer) | |
| 19:17 | shored has joined IRC (shored!~shored@87-92-64-8.bb.dnainternet.fi) | |
| 19:41 | Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving) | |
| 19:56 | section1 has left IRC (section1!~section1@178.33.109.106, Quit: Leaving) | |
| 20:28 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 20:34 | kjackal has joined IRC (kjackal!~quassel@2a02:587:9a0a:ed00:dd6:937d:17e9:5d61) | |
| 22:22 | adrianor1 has joined IRC (adrianor1!~adrianorg@177.156.227.166) | |
| 22:25 | adrianorg has left IRC (adrianorg!~adrianorg@177.132.221.50, Ping timeout: 246 seconds) | |
| 23:28 | kjackal has left IRC (kjackal!~quassel@2a02:587:9a0a:ed00:dd6:937d:17e9:5d61, Ping timeout: 252 seconds) | |