I’ve read Cockpit help for not starting with no conclusion. So, hoping someone may have it working by now. Here is my problem status:
nasheayahu@kvmserver:~> systemctl status cockpit.socket
○ cockpit.socket - Cockpit Web Service Socket
Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; disabled; preset: disabled)
Active: inactive (dead)
Triggers: ● cockpit.service
Docs: man:cockpit-ws(8)
Listen: [::]:9090 (Stream)
nasheayahu@kvmserver:~> systemctl enable cockpit.socket --now
Created symlink /etc/systemd/system/sockets.target.wants/cockpit.socket → /usr/lib/systemd/system/cockpit.socket.
nasheayahu@kvmserver:~> systemctl status cockpit.socket
● cockpit.socket - Cockpit Web Service Socket
Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; enabled; preset: disabled)
Active: active (listening) since Thu 2024-11-28 20:39:58 MST; 4s ago
Triggers: ● cockpit.service
Docs: man:cockpit-ws(8)
Listen: [::]:9090 (Stream)
Process: 25132 ExecStartPost=/usr/share/cockpit/motd/update-motd localhost (code=exited, status=1/FAILURE)
Process: 25140 ExecStartPost=/bin/ln -snf active.motd /run/cockpit/motd (code=exited, status=1/FAILURE)
Tasks: 0 (limit: 4915)
CPU: 11ms
CGroup: /system.slice/cockpit.socket
Nov 28 20:39:57 kvmserver systemd[1]: Starting Cockpit Web Service Socket…
Nov 28 20:39:58 kvmserver update-motd[25132]: /usr/share/cockpit/motd/update-motd: line 24: /run/cockpit/active.motd: No such file or directory
Nov 28 20:39:58 kvmserver ln[25140]: /bin/ln: failed to create symbolic link ‘/run/cockpit/motd’: No such file or directory
Nov 28 20:39:58 kvmserver systemd[1]: Listening on Cockpit Web Service Socket.
nasheayahu@kvmserver:~> systemctl status cockpit
○ cockpit.service - Cockpit Web Service
Loaded: loaded (/usr/lib/systemd/system/cockpit.service; static)
Active: inactive (dead)
TriggeredBy: ● cockpit.socket
Docs: man:cockpit-ws(8)
nasheayahu@kvmserver:~> systemctl enable cockpit
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 this kind 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.
nasheayahu@kvmserver:~> journalctl -u cockpit.socket
Nov 28 20:39:57 kvmserver systemd[1]: Starting Cockpit Web Service Socket…
Nov 28 20:39:58 kvmserver update-motd[25132]: /usr/share/cockpit/motd/update-motd: line 24: /run/cockpit/active.motd: No such file or directory
Nov 28 20:39:58 kvmserver ln[25140]: /bin/ln: failed to create symbolic link ‘/run/cockpit/motd’: No such file or directory
Nov 28 20:39:58 kvmserver systemd[1]: Listening on Cockpit Web Service Socket.
asheayahu@kvmserver:~> journalctl -u cockpit.service
– No entries –
nasheayahu@kvmserver:~> journalctl -u cockpit
– No entries –
By these outputs, what is there I need to do to get this working?
Thanks!..