search

Ultramarine-Linux / triage

If you're unsure where an issue should go, but are sure it belongs to Ultramarine, you can report it here.
49 stars 1 forks source link

[BUG] Failed to start auditd.service - Security Auditing Service. #36

Closed alexanderlavrenko closed 6 months ago

alexanderlavrenko commented 6 months ago

Here's what I get after boot and type sudo journalctl -p 3 -xb:

Feb 19 10:26:49 ultramarine kernel: x86/cpu: SGX disabled by BIOS. Feb 19 10:26:49 ultramarine systemd-vconsole-setup[261]: /usr/bin/setfont fai> Feb 19 10:26:51 ultramarine systemd-vconsole-setup[566]: /usr/bin/setfont fai> Feb 19 10:27:06 ultramarine auditd[1190]: Could not open dir /var/log/audit (> Feb 19 10:27:06 ultramarine systemd[1]: Failed to start auditd.service - Secu> ░░ Subject: A start job for unit auditd.service has failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit auditd.service has finished with a failure. ░░ ░░ The job identifier is 320 and the job result is failed. Feb 19 10:27:06 ultramarine auditd[1201]: Could not open dir /var/log/audit (> Feb 19 10:27:06 ultramarine systemd[1]: Failed to start auditd.service - Secu> ░░ Subject: A start job for unit auditd.service has failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit auditd.service has finished with a failure. ░░ ░░ The job identifier is 445 and the job result is failed. Feb 19 10:27:06 ultramarine auditd[1204]: Could not open dir /var/log/audit (> Feb 19 10:27:06 ultramarine systemd[1]: Failed to start auditd.service - Secu> ░░ Subject: A start job for unit auditd.service has failed ░░ Defined-By: systemd lines 1-25...skipping... Feb 19 10:26:49 ultramarine kernel: x86/cpu: SGX disabled by BIOS. Feb 19 10:26:49 ultramarine systemd-vconsole-setup[261]: /usr/bin/setfont failed with exit status 71. Feb 19 10:26:51 ultramarine systemd-vconsole-setup[566]: /usr/bin/setfont failed with exit status 71. Feb 19 10:27:06 ultramarine auditd[1190]: Could not open dir /var/log/audit (No such file or directory) Feb 19 10:27:06 ultramarine systemd[1]: Failed to start auditd.service - Security Auditing Service. ░░ Subject: A start job for unit auditd.service has failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit auditd.service has finished with a failure. ░░ ░░ The job identifier is 320 and the job result is failed. Feb 19 10:27:06 ultramarine auditd[1201]: Could not open dir /var/log/audit (No such file or directory) Feb 19 10:27:06 ultramarine systemd[1]: Failed to start auditd.service - Security Auditing Service. ░░ Subject: A start job for unit auditd.service has failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit auditd.service has finished with a failure. ░░ ░░ The job identifier is 445 and the job result is failed. Feb 19 10:27:06 ultramarine auditd[1204]: Could not open dir /var/log/audit (No such file or directory) Feb 19 10:27:06 ultramarine systemd[1]: Failed to start auditd.service - Security Auditing Service. ░░ Subject: A start job for unit auditd.service has failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit auditd.service has finished with a failure. ░░ ░░ The job identifier is 449 and the job result is failed. Feb 19 10:27:06 ultramarine auditd[1247]: Could not open dir /var/log/audit (No such file or directory) Feb 19 10:27:07 ultramarine systemd[1]: Failed to start auditd.service - Security Auditing Service. ░░ Subject: A start job for unit auditd.service has failed ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit auditd.service has finished with a failure. ░░ ░░ The job identifier is 565 and the job result is failed. Feb 19 10:27:07 ultramarine auditd[1445]: Could not open dir /var/log/audit (No such file or directory) Feb 19 10:27:07 ultramarine systemd[1]: Failed to start auditd.service - Security Auditing Service. ░░ Subject: A start job for unit auditd.service has failed ░░ Defined-By: systemd

so the problem is that auditd.service is not working

Steps that DID NOT help:

Any idea why does it fail to start auditd.service and how to fix it?

Desktop (please complete the following information):

Additional context It happens regardless of KDE and I spotted this on Hyprland. Both when I boot into KDE or Hyprland then I get this message.

madonuko commented 6 months ago

Please complete the information on the GitHub issue template, including but not limited to your Desktop information.

Also, do you happen to be on Immutable/Atomic versions of Ultramarine Linux? If you don't know what I'm talking about here, then you're probably not on Atomic.

alexanderlavrenko commented 6 months ago

Please complete the information on the GitHub issue template, including but not limited to your Desktop information.

Also, do you happen to be on Immutable/Atomic versions of Ultramarine Linux? If you don't know what I'm talking about here, then you're probably not on Atomic.

What kind of additional information could help?

I don't know what you mean by Immutable/Atomic versions, I've downloaded Ultramarine Linux (KDE Edition) ISO from official website.

I can tell though that I've installed Ultramarine alongside Ubuntu (which was installed by pretty advanced encrypted installation) and in the process forgot to make it use Swap partition and make it unlock encrypted Home partition from Ubuntu, as a result I see there are problems with /etc/fstab, so I'm looking forward to make complete re-installation to leave just Ultramarine Linux. I see it runs really well, and I'm pretty sure it will be better without Ubuntu.

Also can give little feedback on KDE if somebody's interested. I don't know what's the problem with it but dark themes here are nightmare, I've installed some dark themes from Settings and pretty much all of them don't change font color accordingly on QT apps.

UPDATE: To everyone who read my "nightmare" quote, I want to apologize. It turns out it was actually me but I had no idea at first. The reason for this was this line in the .profile:

Qt 5

export QT_QPA_PLATFORMTHEME=qt5ct

The thing is one Ubuntu I didn't see this affecting KDE but here on Ultramarine, it does affect it for some reason, and as a result I've seen dark themes were looking inadequately. This line was added for Xmonad tiling window manager specifically to make QT apps look dark on Ubuntu, and it did work just fine.

madonuko commented 6 months ago

image You need to provide your edition (which I know is KDE from other text) and your release version (which I don't know)

The latest release version as of now is 39. You can check which release version you are on by going to KDE System Settings → System Administration → About this System.

I'm personally on Ultramarine 39 KDE and I cannot reproduce this issue.

madonuko commented 6 months ago

Also, to change the theme, go to KDE System Settings → Appearance → Global Theme / Plasma Style / Colors.

If you are having issues with theming GTK apps, go to System Settings → Appearance → Application Style → click the button "Configure GNOME/GTK Application Style…".

alexanderlavrenko commented 6 months ago

image You need to provide your edition (which I know is KDE from other text) and your release version (which I don't know)

The latest release version as of now is 39. You can check which release version you are on by going to KDE System Settings → System Administration → About this System.

I'm personally on Ultramarine 39 KDE and I cannot reproduce this issue.

I'm on Ultramarine 39 KDE as well, and it's up to date. I see it just after boot in journalctl.

Maybe it has something to do with my installation but it doesn't seem relevant but I hope so.

I'll do complete re-install next week probably, and then will tell if I found it again.

alexanderlavrenko commented 6 months ago

Also, to change the theme, go to KDE System Settings → Appearance → Global Theme / Plasma Style / Colors.

If you are having issues with theming GTK apps, go to System Settings → Appearance → Application Style → click the button "Configure GNOME/GTK Application Style…".

Right, but as a user when you choose dark theme you'd expect fonts to be white and everything look right and clear without having to manually change certain colors. Thank you anyway.

madonuko commented 6 months ago

Fonts are white and everything looks right and clear without having to manually change certain colours. At least supposedly!

We've tested our ISOs for these kinds of theme customisations before release and they worked fine.

Without any further information I'm afraid the theme issue and the auditd issue can't be reproduced easily… I reckon this is an issue specific to your installation somehow (maybe you messed up something unorthodox / peculiar, who knows?), so you probably will fancy a reinstallation.

Don't worry, I'll keep this issue open, you may hit us at any time once you reinstalled; hope everything goes well!

alexanderlavrenko commented 6 months ago

Fonts are white and everything looks right and clear without having to manually change certain colours. At least supposedly!

We've tested our ISOs for these kinds of theme customisations before release and they worked fine.

Without any further information I'm afraid the theme issue and the auditd issue can't be reproduced easily… I reckon this is an issue specific to your installation somehow (maybe you messed up something unorthodox / peculiar, who knows?), so you probably will fancy a reinstallation.

Don't worry, I'll keep this issue open, you may hit us at any time once you reinstalled; hope everything goes well!

Check my explanation about dark theme effect above, there's no problem with KDE itself. audit problem is a mystery for now but I'll tell if it's there after re-installation. Thanks.