IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 28 November 2022 (all times are UTC)
| 00:08 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds)) | |
| 00:23 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 00:37 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving) | |
| 00:49 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection) | |
| 01:02 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 02:30 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds)) | |
| 02:45 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 03:26 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 03:36 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 255 seconds) | |
| 03:46 | Vercas6 has joined IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas) | |
| 03:53 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving) | |
| 05:00 | Vercas6 has left IRC (Vercas6!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 255 seconds) | |
| 06:44 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 07:21 | woernie has joined IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de) | |
| 07:27 | woernie has left IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 07:28 | woernie has joined IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de) | |
| 08:29 | Ted468 has joined IRC (Ted468!~Ted468@195.123.111.204.dynamic-pppoe.dt.ipv4.wtnet.de) | |
| 08:32 | <Ted468> Hi there, what reasons could there be that an ltsp server is having breakups? Sometimes programs freeze for 10sec up to 1min - e.g. Browser or explorer. After everything works normally. Its a small local network - a qnap nas runs the ltsp-server as virtual machine - and a thin client is connected via lan. When i boot the "normal" operating system
| |
| 08:32 | no connection problems occur.
| |
| 08:33 | <alkisg1> Ted468: is it a thin client or a fat client? Which ltsp version?
| |
| 08:33 | (thin client means the processes run on the server, not with the client CPU)
| |
| 08:48 | <Ted468> LTSP Version is ltsp 22.01-1~ubuntu20.04.1 , and yes - its a fat client (i "simply" followed the instructions at https://ltsp.org/docs/installation/ for a chrootless installation (kubuntu 20.04)
| |
| 08:49 | <alkisg1> An LTSP server "operating system" is a "normal" operating system, as long as no LTSP client has booted; then it's a "server" because it provides some resources to its clients
| |
| 08:50 | So you're reporting that "kubuntu ltsp" on the server lags, while "kubuntu without ltsp" doesn't lag? That doesn't make any sense, ltsp isn't running any heavy services...
| |
| 08:51 | I would check top and free for CPU and memory shortcomings, and dmesg / journalctl for system errors
| |
| 08:52 | Does the problem happen on the server even when no client has been booted from it?
| |
| 08:54 | <Ted468> k -will do so. I only "see" the problems when using a pc that booted from the ltsp server - like right now. At 9:52 the browser froze and i couldnt type anything into the chat field for about 30sec.
| |
| 08:54 | thx a lot - i will have a look at the journals
| |
| 08:55 | <alkisg1> Ted468: also check the nas journals, in case there are any bad sectors in the disk, and the client happens to be reading these, so that nap stalls, and with it, all VMs
| |
| 08:55 | <Ted468> will do. Thx a lot for your help. (y)
| |
| 09:12 | Ted468 has left IRC (Ted468!~Ted468@195.123.111.204.dynamic-pppoe.dt.ipv4.wtnet.de, Quit: Client closed) | |
| 11:00 | woernie has left IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 12:06 | woernie has joined IRC (woernie!~werner@p200300cf07170600a560e4446cf0544a.dip0.t-ipconnect.de) | |
| 14:24 | oh207_ has joined IRC (oh207_!~oh207@pool-72-69-11-48.nycmny.fios.verizon.net) | |
| 14:27 | oh207_ has left IRC (oh207_!~oh207@pool-72-69-11-48.nycmny.fios.verizon.net, Client Quit) | |
| 14:28 | oh207 has joined IRC (oh207!~oh207@pool-72-69-11-48.nycmny.fios.verizon.net) | |
| 15:15 | woernie has left IRC (woernie!~werner@p200300cf07170600a560e4446cf0544a.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 16:56 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Ping timeout: 264 seconds) | |
| 17:12 | woernie has joined IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de) | |
| 17:33 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 18:34 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 18:53 | woernie has left IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de, Quit: No Ping reply in 180 seconds.) | |
| 18:53 | woernie has joined IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de) | |
| 20:17 | oh207 has left IRC (oh207!~oh207@pool-72-69-11-48.nycmny.fios.verizon.net, Ping timeout: 252 seconds) | |
| 21:26 | woernie has left IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de, Remote host closed the connection) | |
| 21:40 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 22:39 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving) | |
| 22:48 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:40) | |