My MOTD is not getting updated for an enabled cockpit.socket.

[supakeen]

Explain what happens

I have cockpit installed:

# dnf list --installed | grep cockpit
cockpit.aarch64                         316-1.fc40                 @updates

On a Fedora 40:

# hostnamectl
     Static hostname: zmeya.home.arpa
           Icon name: computer-desktop
             Chassis: desktop 🖥️
          Machine ID: d93ad37cec7443ff9a1d37f441214b11
             Boot ID: 977ec5d143a445bba4233132560529c3
    Operating System: Fedora Linux 40 (Forty)
         CPE OS Name: cpe:/o:fedoraproject:fedora:40
      OS Support End: Tue 2025-05-13
OS Support Remaining: 1y 4d
              Kernel: Linux 6.8.7-300.fc40.aarch64
        Architecture: arm64
     Hardware Vendor: raspberrypi
      Hardware Model: Raspberry Pi 4 Model B Rev 1.2
    Firmware Version: 2024.04-rc4
       Firmware Date: Mon 2024-04-01
        Firmware Age: 1month 1w

The MOTD keeps showing me to enable cockpit.socket.

# cat /etc/issue.d/cockpit.issue
Activate the web console with: systemctl enable --now cockpit.socket
# cat /etc/motd.d/cockpit
Activate the web console with: systemctl enable --now cockpit.socket
# find /run -name cockpit.issue
#

But it is enabled:

# 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 Fri 2024-03-01 00:00:32 UTC; 2 months 7 days ago
   Triggers: ● cockpit.service
       Docs: man:cockpit-ws(8)
     Listen: [::]:9090 (Stream)
      Tasks: 0 (limit: 4062)
     Memory: 1.2M (peak: 2.3M)
        CPU: 96ms
     CGroup: /system.slice/cockpit.socket

Mar 01 00:00:32 zmeya.home.arpa systemd[1]: Starting cockpit.socket - Cockpit Web Service Socket...
Mar 01 00:00:32 zmeya.home.arpa systemd[1]: Listening on cockpit.socket - Cockpit Web Service Socket.

I see this issue on 4 machines; all Fedora 40 on arm64.

Version of Cockpit

316

Where is the problem in Cockpit?

Unknown or not applicable

Server operating system

Fedora

Server operating system version

40

What browsers are you using?

No response

System log

No response

[martinpitt]

Can you please check ls -l /run/cockpit/motd? I suppose it still points to inactive.motd.

This is done by cockpit.socket's

ExecStartPost=-/bin/ln -snf active.motd /run/cockpit/motd

which is usually quite robust. Can you please check sudo systemctl status cockpit.socket? Any error there?