From jonathan.buzzard at strath.ac.uk Wed Jun 2 20:27:52 2021 From: jonathan.buzzard at strath.ac.uk (Jonathan Buzzard) Date: Wed, 2 Jun 2021 19:27:52 +0100 Subject: [ThinLinc-technical] systemd unit file bugs Message-ID: First off the vsmagent.service file is being installed with execute permissions, so I see things like this in my log files systemd: Configuration file /usr/lib/systemd/system/vsmagent.service is marked executable. Please remove executable permission bits. Proceeding anyway. You can use "systemctl daemon-reload" to trigger it. Second the way the unit file is written the service agent will fail to start in many circumstances. So you have the following [Unit] Description=ThinLinc VSM agent After=network.target Basically using "After=network.target" is about as much use as a chocolate teapot. What I am seeing on a system where the network interface is a 802.ad bond is the following 2021-06-01 20:44:29 WARNING vsmagent: Couldn't lookup host vsmserver.mycorp.com: [Errno -2] Name or service not known That's because network.target only indicates that the network management stack is up, it doesn't mean there is a useable network connection. It takes a handful of seconds after the 802.3ad LAG is started for it to actually be able to handle traffic. In that time the vsmagent starts can't lookup the vsmserver hostname and unhelpfully fails. You may well see the same if the server is doing DHCP to obtain it's IP address. What you want is to use the following in your unit file After=network-online.target Wants=network-online.target Though to avoid slowing down the boot, you should probably be watching rtnetlink and retrying when network reconfigurations happen. The above modification is basically having systemd working around broken behaviour in the vsmagent demon. Note depending on your circumstances you might want to do something like the following to make the vsmagent wait till any remote file systems are mounted. For example if users home directories are on an NFS share. mkdir -p /etc/systemd/system/vsmagent.service.d echo -e "[Unit]\nAfter=network-online.target remote-fs.target" > /etc/systemd/system/vsmagent.service.d/waitforremotefs.conf systemctl daemon-reload JAB. -- Jonathan A. Buzzard Tel: +44141-5483420 HPC System Administrator, ARCHIE-WeSt. University of Strathclyde, John Anderson Building, Glasgow. G4 0NG From ossman at cendio.se Thu Jun 24 12:20:03 2021 From: ossman at cendio.se (Pierre Ossman) Date: Thu, 24 Jun 2021 12:20:03 +0200 Subject: [ThinLinc-technical] systemd unit file bugs In-Reply-To: References: Message-ID: Hi Jonathan, I'm guessing you are running ThinLinc 4.12.0? The issues you mentioned should be addressed in the bug fix release 4.12.1, so please give that a try and see if there is still anything giving you problems. Regards -- Pierre Ossman Software Development Cendio AB https://cendio.com Teknikringen 8 https://twitter.com/ThinLinc 583 30 Link?ping https://facebook.com/ThinLinc Phone: +46-13-214600 A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? From Thomas.Doczkal at eu.socionext.com Fri Jun 25 09:22:32 2021 From: Thomas.Doczkal at eu.socionext.com (Doczkal, Thomas) Date: Fri, 25 Jun 2021 07:22:32 +0000 Subject: [ThinLinc-technical] systemd unit file bugs In-Reply-To: References: , Message-ID: ________________________________________ From: ThinLinc-technical on behalf of Pierre Ossman Sent: Thursday, June 24, 2021 12:20 PM To: Jonathan Buzzard; thinlinc-technical at lists.cendio.se Subject: Re: [ThinLinc-technical] systemd unit file bugs Hi Jonathan, I'm guessing you are running ThinLinc 4.12.0? The issues you mentioned should be addressed in the bug fix release 4.12.1, so please give that a try and see if there is still anything giving you problems. ________________________________________ Hi, 4.12.1 has bugs that prevent using kerberos as Login method. Issue: [issue29057] Appcrash - ssh.exe stopped working When do you expect to release a new version with this fixed? Otherwise you just change one bug with another. For us kerberos (during runtime) is more bugging then the failed startup. Once the service is up and running 4.12.0 is stable. Thanks. Regards, Thomas From ossman at cendio.se Tue Jun 29 12:58:36 2021 From: ossman at cendio.se (Pierre Ossman) Date: Tue, 29 Jun 2021 12:58:36 +0200 Subject: [ThinLinc-technical] systemd unit file bugs In-Reply-To: References:

Message-ID: On 25/06/2021 09:22, Doczkal, Thomas wrote: > Hi, > > 4.12.1 has bugs that prevent using kerberos as Login method. > > Issue: [issue29057] Appcrash - ssh.exe stopped working > > When do you expect to release a new version with this fixed? I'm hoping in a few weeks. We are finishing up the last parts now and I hope they won't give us any trouble. > Otherwise you just change one bug with another. For us kerberos (during runtime) is more bugging then the failed startup. Once the service is up and running 4.12.0 is stable. > Fortunately the Kerberos issue is entirely in the client, and the systemd unit issues are entirely on the server. So using the 4.12.0 client with a 4.12.1 server will avoid all of the problems. Regards -- Pierre Ossman Software Development Cendio AB https://cendio.com Teknikringen 8 https://twitter.com/ThinLinc 583 30 Link?ping https://facebook.com/ThinLinc Phone: +46-13-214600 A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?