[BUG] Error messages to find and fix

[chewitt]

The following error messages are observed during boot. All appear to be completely harmless, but clean logs are prettier :)

Sep 17 16:00:40 N2PLUS systemd-udevd[452]: /usr/lib/udev/rules.d/50-udev-default.rules:13 Unknown group 'clock', ignoring.
Sep 17 16:00:40 N2PLUS systemd-udevd[452]: /usr/lib/udev/rules.d/50-udev-default.rules:34 Unknown group 'clock', ignoring.

Sep 17 16:00:41 N2PLUS (udev-worker)[508]: controlC0: /usr/lib/udev/rules.d/90-alsa-restore.rules:5 NAME="snd/%k": Only network interfaces can be renamed, ignoring.

Sep 29 17:18:56 N2PLUS pulseaudio[467]: W: [pulseaudio] authkey.c: Failed to open cookie file '/var/run/pulse/.config/pulse/cookie': No such file or directory
Sep 29 17:18:56 N2PLUS pulseaudio[467]: W: [pulseaudio] authkey.c: Failed to load authentication key '/var/run/pulse/.config/pulse/cookie': No such file or directory
Sep 29 17:18:56 N2PLUS pulseaudio[467]: W: [pulseaudio] authkey.c: Failed to open cookie file '/var/run/pulse/.pulse-cookie': No such file or directory
Sep 29 17:18:56 N2PLUS pulseaudio[467]: W: [pulseaudio] authkey.c: Failed to load authentication key '/var/run/pulse/.pulse-cookie': No such file or directory

Sep 29 17:18:56 N2PLUS pulseaudio[467]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.

[chewitt]

Another one:

Sep 17 16:00:40 LibreELEC systemd-tmpfiles[365]: Failed to create directory or subvolume "/root", ignoring: Read-only file system
Sep 17 16:00:40 LibreELEC systemd-tmpfiles[365]: Failed to open path '/root', ignoring: No such file or directory

[HiassofT]

I think it's safe to ignore the pulseaudio cookie warnings, they are expected after system start.

Checking with gdb they originate from the pa_auth_cookie_get calls in pa_native_options_parse lines 5547 and 5552 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/blob/1f020889c9aa44ea0f63d7222e8c2b62c3f45f68/src/pulsecore/protocol-native.c#L5547-5558

            o->auth_cookie = pa_auth_cookie_get(c, PA_NATIVE_COOKIE_FILE, false, PA_NATIVE_COOKIE_LENGTH);
            if (!o->auth_cookie) {
                char *fallback_path;
                if (pa_append_to_home_dir(PA_NATIVE_COOKIE_FILE_FALLBACK, &fallback_path) >= 0) {
                    o->auth_cookie = pa_auth_cookie_get(c, fallback_path, false, PA_NATIVE_COOKIE_LENGTH);
                    pa_xfree(fallback_path);
                }
                if (!o->auth_cookie)
                    o->auth_cookie = pa_auth_cookie_get(c, PA_NATIVE_COOKIE_FILE, true, PA_NATIVE_COOKIE_LENGTH);
            }

First PA tries to read the cookie and then the fallback .pulse-cookie files, which don't exist after startup (as /run is volatile), which each result in a cookie and authkey warning.

Then in line 5557 pa_auth_cookie_get is called with the tird ("create") arg set to true, which will then create the cookie file

rpi5:~ # ls -la /var/run/pulse/.config/pulse/cookie 
-rw-------    1 root     root           256 Sep 30 19:00 /var/run/pulse/.config/pulse/cookie

When restarting pulseaudio the cookie file is present right from the start and no warnings are logged.

[chewitt]

First PA tries to read the cookie and then the fallback .pulse-cookie files, which don't exist after startup (as /run is volatile), which each result in a cookie and authkey warning.

Can we define the /path/to/cookie in build config and then persist is somewhere under /storage/.cache?