At first, update-motd fails to create a symbolic link (“polluting” the log, just a bit), but it’s created later on. This might be an upstream bug or even not a bug.
Jun 28 20:43:16 local esmith::event[4165]: expanding /etc/motd
Jun 28 20:44:39 local update-motd: /usr/share/cockpit/motd/update-motd: line 24: /run/cockpit/active.motd: No such file or directory
Jun 28 20:44:39 local ln: /bin/ln: failed to create symbolic link ‘/run/cockpit/motd’: No such file or directory
Jun 28 20:44:39 local systemd: Starting Cockpit motd updater service...
Jun 28 20:44:39 local update-motd: /usr/share/cockpit/motd/update-motd: line 24: /run/cockpit/active.motd: No such file or directory
Jun 28 20:44:39 local systemd: Started Cockpit motd updater service.
Packages:
- cockpit-183-1.el7.x86_64
- cockpit-bridge-183-1.el7.x86_64
- cockpit-packagekit-183-1.el7.noarch
- cockpit-storaged-183-1.el7.noarch
- cockpit-system-183-1.el7.noarch
- cockpit-ws-183-1.el7.x86_64
- nethserver-cockpit-0.9.2-1.9.g630e292.ns7.noarch
- nethserver-cockpit-lib-0.9.2-1.9.g630e292.ns7.noarch