IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 18 February 2021 (all times are UTC)
| 00:49 | Vercas has joined IRC (Vercas!~Vercas@unaffiliated/vercas) | |
| 01:11 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
| 03:26 | GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Ping timeout: 240 seconds) | |
| 04:07 | GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net) | |
| 04:23 | GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Ping timeout: 260 seconds) | |
| 07:09 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 08:06 | RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro) | |
| 08:52 | <Hyperbyte> Good morning alkisg. :-) I'm still having issues with the new LTSP on Ubuntu 20.04 that do seem to be LTSP related. The user reported error is "sound is not working".
| |
| 08:52 | When looking into it, I found out pulseaudio is not started, when I try to start it using systemctl --user start pulseaudio.service, I get the following error: "Process org.freedesktop.systemd1 exited with status 1"
| |
| 08:53 | <fiesh> maybe do a journalctl -xe to see what's up
| |
| 08:53 | or a systemctl status pulseaudio
| |
| 08:53 | the message alone doesn't say much
| |
| 08:53 | <Hyperbyte> In fact, when I try to execute any systemctl --user command, it spits out that error. It doesn't always happen, maybe 50/50 chance. I've also noticed that when it happens, /run/user/ folder is empty
| |
| 08:53 | <alkisg> Morning guys. Additionally, try with a live cd and see if sound works there
| |
| 08:53 | Ah
| |
| 08:53 | If /run/user/ is empty, that's a serious problem
| |
| 08:53 | Do you have customized PAM?
| |
| 08:54 | <Hyperbyte> Not as far as I know? Could be LDAP related maybe?
| |
| 08:54 | <alkisg> How did you configure LDAP on the clients?
| |
| 08:54 | (yeah that's the customized PAM that I was asking for)
| |
| 08:55 | <Hyperbyte> I configured it on the server. /etc/ldap.conf
| |
| 08:55 | <alkisg> And then? Chrootless?
| |
| 08:55 | <Hyperbyte> The new LTSP setup you recommended, chrootless
| |
| 08:55 | <alkisg> Than means that you have configured ldap on the clients as well, as it is a clone of the server
| |
| 08:56 | <Hyperbyte> ltsp 21.01
| |
| 08:56 | <alkisg> Now, I would expect to see the sound problem on the server itself as well
| |
| 08:56 | <Hyperbyte> I don't think sound is the actual problem. Maybe I shouldn't have mentioned it.
| |
| 08:56 | <alkisg> The actual problem is /run/user not being mounted after a user has logged in
| |
| 08:56 | <Hyperbyte> It seems that nothing systemd related in userspace is started. systemctl --user status pulseaudio.service results in the same error
| |
| 08:56 | Right
| |
| 08:57 | <alkisg> systemd-pam should have ensured that it's always there
| |
| 08:57 | That means that you manually changed /etc/pam.d to add ldap, and you did something wrong, that introduced a race condition, unrelated to ltsp
| |
| 08:58 | <Hyperbyte> Could be. This is a 16.04 install upgraded all the way to 20.04, so I don't recall exactly what's happened to the pam config :-)
| |
| 08:58 | I've been considering ditching LDAP. Maybe this is the time... probably easiest solution.
| |
| 08:59 | We used to share accounts between 4 servers, now LTSP is actually the only thing using LDAP still as the other 3 servers have moved to different account management.
| |
| 08:59 | <alkisg> https://github.com/ltsp/ltsp/issues/338#issuecomment-735230997
| |
| 08:59 | This ^ link describes a very easy way to setup SSSD, which is an LDAP client, without manually messing with PAM
| |
| 08:59 | PAM is supposed to be handled by packages, not by the user. By update-pam-auth etc.
| |
| 09:00 | <Hyperbyte> I agree. I remember I tried sssd but had some problems with it that I couldn't resolve.
| |
| 09:00 | I think I'm just going to ditch LDAP and reset the entire pam config
| |
| 09:01 | <alkisg> I haven't tried SSSD in the distant past, but last year that I did, it was super smooth and automatic
| |
| 09:01 | apt install + a tiny config => ready
| |
| 09:01 | It even supports caching out of the box, for the case where ldap gets rebooted
| |
| 09:02 | <sebd_> alkisg: Debian removed support for PRINTER_LIST in cups on Fri, 14 Dec 2018 (cups 2.2.10-3) because the patch was refused for upstream integration
| |
| 09:02 | <Hyperbyte> Yeah, I'm sure it's good. It worked beautifully on Fedora. On Ubuntu I had some problems where it didn't like my server. I think at this point easiest is to just ditch LDAP. Frees up some VM resources as well.
| |
| 09:02 | <alkisg> sebd_: yeah, I can't say I liked ltsp-specific patches in ltsp5, so I haven't used them at all in ltsp20+
| |
| 09:03 | <Hyperbyte> Anyway, thanks for helping me trace this down. :-)
| |
| 09:03 | <alkisg> Hyperbyte: sure; note though that in this case, when you add user accounts, you'll need to reboot the clients
| |
| 09:03 | While no reboot is needed for password changes or account removals
| |
| 09:03 | np
| |
| 09:04 | sebd_, I even filed bugs in isc-dhcp and in cups to remove the ltsp-specific patches :)
| |
| 09:09 | <sebd_> alkisg: we are trying to empty printers.conf and generate cups-browsed.conf and lpoptions at client boot now
| |
| 09:09 | <alkisg> sebd_, cups has its own settings and methods to set default printers; did you read about them?
| |
| 09:10 | <sebd_> cups-browsed.conf has BrowseFilter, which can be used to mask the server's printer queues on their names, that's what we are attempting to use
| |
| 09:11 | and lpoptions can contain Default NameOfTheDefautPrinterQueue
| |
| 13:14 | gvy has joined IRC (gvy!~mike@altlinux/developer/mike) | |
| 15:10 | RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Quit: Please remember your own message. It'll be read as soon as possible.) | |
| 15:52 | GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net) | |
| 16:36 | GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Ping timeout: 246 seconds) | |
| 16:54 | alequint8912 has joined IRC (alequint8912!be5c7f0f@190.92.127.15) | |
| 16:54 | GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net) | |
| 17:00 | <alequint8912> Hi. I install Ubuntu desktop 20.04 in a Proxmox enviroment, so when I install dnsmasq service in the ubuntu, it say that the 53 port is in use by this process
| |
| 17:00 | tcp 0 0 127.0.0.53:53 0.0.0.0:* ESCUCHAR - apagado (0.00/0/0)
| |
| 17:00 | tcp 0 0 0.0.0.0:36539 0.0.0.0:* ESCUCHAR - apagado (0.00/0/0)
| |
| 17:00 | tcp6 0 0 :::35325 :::* ESCUCHAR - apagado (0.00/0/0)
| |
| 17:00 | udp 0 0 0.0.0.0:53275 0.0.0.0:* - apagado (0.00/0/0)
| |
| 17:00 | udp 0 0 127.0.0.53:53 0.0.0.0:* - apagado (0.00/0/0)
| |
| 17:00 | udp 0 0 0.0.0.0:5353 0.0.0.0:* - apagado (0.00/0/0)
| |
| 17:00 | udp6 0 0 :::5353 :::* - apagado (0.00/0/0)
| |
| 17:01 | Can I configure the dnsmasq service to use another port?
| |
| 17:01 | <mwalters> Why would you want to?
| |
| 17:02 | Oh, you don't have dnsmasq installed and something else is using the port
| |
| 17:02 | are you installing ltsp?
| |
| 17:03 | <alequint8912> yes I run the command
| |
| 17:03 | apt install --install-recommends ltsp ltsp-binaries dnsmasq nfs-kernel-server openssh-server squashfs-tools ethtool net-tools epoptes
| |
| 17:03 | but dnsmasq fails because port 53 is in use
| |
| 17:04 | <mwalters> a quick google shows that it might be systemd-resolved
| |
| 17:05 | <alequint8912> Yes it is. I don't have much experience in linux but I couldn't stop that service. What I can do?
| |
| 17:07 | <mwalters> I'm going to refrain from giving suggestions... I don't know what could happen if you put that service on a different port. Either wait for someone else, or maybe ask in #ubuntu
| |
| 17:07 | <alequint8912> ok thanks
| |
| 17:08 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
| 18:11 | <alkisg> alequint8912: just run the next step, `ltsp dnsmasq` and it will solve the problem
| |
| 18:12 | In a default debian or ubuntu installation, dnsmasq conflicts with systemd-resolved; then ltsp steps in with a configuration file and solves the problem
| |
| 18:14 | <mwalters> "The process failed successfully" ;)
| |
| 18:21 | <alequint8912> alkisg thanks you very much, the service is up
| |
| 18:22 | <alkisg> np
| |
| 18:22 | GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Ping timeout: 260 seconds) | |
| 18:25 | <alequint8912> alkisg If I build the image on another pc, could I use that image in this new installation?
| |
| 18:30 | <alkisg> Sure
| |
| 18:32 | <alequint8912> good, ok thanks
| |
| 20:44 | <Hyperbyte> Oh alkisg, just FYI. when I rebuild the ltsp image, I get an error about not being able to delete /tmp/tmp.OgPViFMrY7/tmpfs/, folder not empty.
| |
| 20:45 | It leaves a folder '0' with looproot, up, work in it. No actual files.
| |
| 20:56 | <alkisg> Hyperbyte: it doesn't affect any other ltsp users, so if it's just "FYI", np; if you need to resolve it, I'll need more details about your setup
| |
| 20:59 | alequint8912 has left IRC (alequint8912!be5c7f0f@190.92.127.15, Quit: Connection closed) | |
| 21:02 | <alkisg> Especially, if it happens after reboot, and what your mounts are
| |
| 22:35 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
| 23:00 | <Hyperbyte> Doesn't bother me, but if you want to debug for me or possibly others then I've sent you a PM with the mounts. It does happen consistently after reboots.
| |
| 23:01 | But it's just an error and it leaves some errant empty folders in /tmp, so definitely nothing I worry about.
| |
| 23:01 | :-)
| |
| 23:01 | G'night
| |