Installing cisco-secure-client 5.1.6.103-1 onto a new (refurbished) Thinkpad, I'm getting an message ...
Connect capability is unavailable because the VPN service is unavailable.
On an older Thinkpad, I have Cisco AnyConnect 4.10.08029 working just fine, so it's not the destination network.
I found a similar error at https://forum.manjaro.org/t/anyconnect-connection-attempt-has-failed/155171/6 that pointed to https://bbs.archlinux.org/viewtopic.php?pid=2141236#p2141236 as a solution. I've mostly tried to follow that. (There are some spelling mistakes there, so I've done my best to adjust).
I'm still having iusses with vpnagentd.
sudo systemctl enable --now vpnagentd.service
[sudo] password for daviding:
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having these kinds of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/, .requires/, or .upholds/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some instance name specified. Failed to start vpnagentd.service: Unit vpnagentd.service has a bad unit file setting. See system logs and 'systemctl status vpnagentd.service' for details.
Please let me know if I can provide any additional information for diagnosis.
Pinned Comments
dmsh commented on 2024-03-23 17:24 (UTC) (edited on 2024-03-23 17:25 (UTC) by dmsh)
After package installation,
vpnagentd
service must be enabled:sudo systemctl enable --now vpnagentd.service; sudo systemctl status vpnagentd.service