05:22 | woernie has joined IRC (woernie!~werner@p5ddedeef.dip0.t-ipconnect.de) | |
07:35 | woernie has left IRC (woernie!~werner@p5ddedeef.dip0.t-ipconnect.de, Ping timeout: 252 seconds) | |
07:35 | woernie has joined IRC (woernie!~werner@www.velometrik.eu) | |
09:53 | woernie has left IRC (woernie!~werner@www.velometrik.eu, Ping timeout: 245 seconds) | |
09:53 | woernie has joined IRC (woernie!~werner@p5ddedeef.dip0.t-ipconnect.de) | |
10:25 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
15:16 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:50) | |
16:52 | woernie has left IRC (woernie!~werner@p5ddedeef.dip0.t-ipconnect.de, Remote host closed the connection) | |
18:42 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
20:34 | mac has joined IRC (mac!~mac@2600:8807:3d07:9100:c851:1d0d:df86:6f77) | |
20:38 | <mac> where do i find the ltsp logs of thin clients on the ltsp server? I have a thin client that freezes up and when its power cycled it starts working again, i would like to dig into the logs but cant find them at /var/log/ltsp
| |
20:39 | <quinox> thin clients are from the older LTSP, the one from the last few years only supports fat clients
| |
20:40 | there are no such logs since LTSP is basically really clever glue between standard linux tools
| |
20:40 | you probably want /var/log/dmesg
| |
20:40 | if the machine is locking up you might not be able to access it; you can set up remote logging which might or might not help you
| |
20:41 | something like rsyslog or systemd-journal-remote
| |
20:41 | those are standard linux tools, not LTSP specific. See their manual pages for what to do
| |
20:42 | <mac> quinox sorry meant the FAT clients. Oh okay, the other clients are working just fine, so i just wanted to check whats happening to the others.
| |
20:42 | Thought logs would help, where i can see when it connects, receive the image and the what happens after that.
| |
20:44 | <quinox> on the server in /var/log/syslog , grep for dnsmasq: that's the process that should normally respond to the DHCP boot sequence + the mounting of the first filesystem over TFTP
| |
20:47 | depending on your setup /home is mounted over either ssh or something like NFS; for ssh you can check /var/log/auth.log, NFS by default is rather silent IIRC so you'll have to google a bit to see how to look at the logs
| |
20:50 | I'm off to bed now, feel free to hang around and ask questions: other people might show up eventually
| |
20:51 | <mac> Thanks for your help. I appreaciate it. Thanks alot. have a good night.
| |
21:01 | mac has left IRC (mac!~mac@2600:8807:3d07:9100:c851:1d0d:df86:6f77, Quit: Client closed) | |
22:36 | Vercas4 has joined IRC (Vercas4!~Vercas@gateway/tor-sasl/vercas) | |
22:37 | Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds)) | |
22:37 | Vercas4 is now known as Vercas | |