Open kiarn opened 2 years ago
That's really strange... I thought, that this should be solved by this line: https://github.com/linuxmuster/linuxmuster-linuxclient7/blob/3d7cb5fbefc06603febbd3fb17773e03a1385fda/usr/share/linuxmuster-linuxclient7/templates/linuxmuster-linuxclient7.service#L8
Is it a laptop?
No, they are all workstations, wired with ethernet, and the problem appear in random mode : I'm not able to reproduce it on the same computer again. That's why it's pretty complicated for debugging.
I will try to disable NetworkManager-wait-online.service and see if it's better.
Hello @dorianim
I did not forget this, but it's difficult to find the reason. But I think I was searching in the wrong direction. I assumed that the client was trying to mount sysvol without network, and maybe the problem is that the client is trying to mount it with network, but without resolver. If systemd-resolver does not start before linuxmuster-linuxclient7, then the client has no chance to mount \\dfgserver.linuxmuster.lan
even if it's written in /etc/hosts
. I will do further searchs ...
Arnaud
That's an intresing idea... maybe we need to add systemd-resolved to the service unit file as a dependency?
Maybe, it should also be after sssd.service instead of before ...
systemd-resolved needs nss-lookup which comes after sssd, as you already found out.
Well then, that's definetly a problem. Might be solved by just placing sssd.service in after
We just tested to use sssd in After and it seems to work much better than before. Since sssd needs network-online we just use that one line in /etc/systemd/system/linuxmuster-linuxclient7.service:
After=sssd.service
All our testcases worked (and boot was a bit faster than before). We tested LAN, NoNetwork, School Wifi and Hotspot. In all cases boot was quick and Proxy autoconfig worked. The hookscripts where all executed (checked by greping for 00_example.sh in journactl -b0).
Hallo!
Ich habe das jetzt auch mal bei uns an der Schule mit /etc/systemd/system/linuxmuster-linuxclient7.service auf dem Ubuntu-22.04-Client getestet.
Mit:
[Unit]
Description=linuxmuster: switch local and remote home depending on ad server connection
After=network-online.target
Before=sssd.service
funktioniert die Anmeldung (mit dem Problem der laaaangen Wartezeit beim Booten in einem fremden Netz).
Mit:
[Unit]
Description=linuxmuster: switch local and remote home depending on ad server connection
After=sssd.service
funktioniert KEINE Anmeldung.
Was ist bei euch noch besonders, dass es funktioniert? (Bei mir wüsste ich diesbezüglich keine Abweichung von Standard.)
Gruß - Rainer
Hi,
I made the tests as Rainer 2 weeks ago with the same result: sssd
service was not active.
Arnaud
Hello, we have the problem that occasionally the drives are not mounted even though the login is successful. The problem is that I cannot reproduce it. Could it be the same problem or related?
Hard to say without any logs. Could also be a network issue. The login works offline when the user was logged in on the workstation before.
Hello,
I'm experiencing the following ; about 1/3 of the computers are not able to mount sysvol at boot. As a consequence, the sysstart scripts can not be launched, but it does not block the login afterwards. Maybe that's why it's not really observed.
It seems that the network is not started when linuxclient tries to mount sysvol :
And then 15s later :
So it's pretty obvious that the network is down when linuxclient starts.
I tried to find a reason in the systemd direction and found this : https://github.com/systemd/systemd/issues/22360#issuecomment-1028665992
So I add :
in
/etc/systemd/system/linuxmuster-linuxclient7.service
and then reload systemd, but it doesn't seem to sufficient, because I still have the problem.It's not really an issue in linuxclient, more a convention problem of what "online" means for the network, but I think it's important to mention it here. I will update this topic if I find some hints.
Arnaud