Show startup errors #7
Description
If the "systemctl start openafs-client" command fails on the command line, the user at least gets an error message to see something when wrong, for example.
openafs-client.service - OpenAFS Client Service
Loaded: loaded (/etc/systemd/system/openafs-client.service; disabled; preset: enabled)
Active: failed (Result: exit-code) since Thu 2025-07-31 09:09:32 EDT; 34s ago
Process: 4835 ExecStart=/opt/openafs/sbin/openafs-client-systemd-helper.sh ExecStart (code=exited, status=1/FAILURE)
Process: 4844 ExecStopPost=/opt/openafs/sbin/openafs-client-systemd-helper.sh ExecStopPost (code=exited, status=0/S>
CPU: 82ms
Jul 31 09:09:31 lana systemd[1]: Starting openafs-client.service - OpenAFS Client Service...
Jul 31 09:09:31 lana openafs-client-systemd-helper.sh[4842]: modprobe: FATAL: Module openafs not found in directory /li>
In this case, the modprode failed because the module is missing, which can happen when DKMS fails to build a new version for some reason or the new kernel version is not supported by OpenAFS yet.
When using the extension, it's currently not possible to see the "start openafs client" selection fails. It just looks like it is stopped. Can we make it more clear we are in an error state and give some message to the user the start failed?
Thanks,
Mike