Comment 3 for bug 1873627
Revision history for this message
| Trey Schisser (treys) wrote Re: [Bug 1873627] Re: auditd fails after moving /var it a new filesystem and turning /var/run into a symlink to /run | #3 |
Alright, close the bug, I have built two different machines and tried to
reproduce the problem several different ways, but have been unable to do
so. Sorry to bother you with this.
Trey Schisser
Waveland Technologies - https:/
Director of Security Operations and IT Infrastructure
<email address hidden>
*mobile* 512-496-6660
Never send passwords, regulated data, or confidential information via
unencrypted email.
Please use Signal (https:/
(512-496-6660)
Or PGP to send encrypted messages via email (See attached public key)
PGP Public key for <email address hidden>: F056 40E6 AEE2 EB92
-----BEGIN PGP PUBLIC KEY BLOCK-----Version: FlowCrypt 7.6.0 Gmail Encryption
Comment: Seamlessly send and receive encrypted
emailxjMEXmbFHh
NCWvClyafb3NKVR
bS5jb20+
AAoJEPBWQOau4uu
1uYBAP4/
CisGAQQBl1UBBQE
GAMBCAfCYQQYFgg
nk5fIpKG23eLrZO
4pxkHA1GaPmQwKr
=fqR7
-----END PGP PUBLIC KEY BLOCK-----
On Mon, Apr 20, 2020 at 4:40 PM Seth Arnold <email address hidden>
wrote:
> Running under strace may change the execution environment enough that
> it's not reflective of the actual error, but it's still worth a shot --
> can you pastebin the whole auditd strace logs? That openat() line is
> actually a success -- the error we're looking for will come from the
> audit_set_pid(3) function, which uses netlink, which is an incredibly
> complicated protocol. The error may not look like an error in strace
> output.
>
> Is there any chance the kernel has logged whatever the failure was in
> dmesg output?
>
> Thanks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> auditd fails after moving /var it a new filesystem and turning
> /var/run into a symlink to /run
>
> Status in audit package in Ubuntu:
> New
>
> Bug description:
> Auditd was working on my system (Ubuntu 18.04LTS, kernel
> 4.15.0-1065-aws) until recently. But after splitting off /var into a
> new filesystem it fails to launch.
>
> running '/sbin/auditd -f' as root indicates a problem writing the pid
> file (no file exists even when it says one does) Post config load command
> output:
> Started dispatcher: /sbin/audispd pid: 16927
> type=DAEMON_START msg=audit(
> format=raw kernel=
> subj=unconfined res=success
> config_manager init complete
> Error setting audit daemon pid (File exists)
> type=DAEMON_ABORT msg=audit(
> auid=878601141 pid=16925 uid=0 ses=24 subj=unconfined res=failed
> Unable to set audit pid, exiting
> The audit daemon is exiting.
> Error setting audit daemon pid (Permission denied)
>
> /var/run is a symlink to /run
> /var/run permissions are 777 root:root
> /run permissions are 755f root:root
> no /run/auditd.pid and subsiquently no /var/run/auditd.pid exists (even
> though the error incorrectly reports otherwise.
>
> /var/log/
> type=DAEMON_START msg=audit(
> format=raw kernel=
> ses=4294967295 subj=unconf
> ined res=success
> type=DAEMON_ABORT msg=audit(
> auid=4294967295 pid=7529 uid=0 ses=4294967295 subj=unconfined res=failed
>
> I have been pulling my hair out over this one. So I ran 'strace
> /sbin/auditd -f' and found the following line in the output.
> "openat(AT_FDCWD, "/var/run/
> O_WRONLY|
> I am grasping at straws, but suspect that the O_NOFOLLOW option is
> causing a failure in creating the pid file since /var/run is a symlink. I
> could be wrong but I can't find anything else to suspect.
>
> Since it is best practice to split/var into a separate file system to
> prevent filling the root filesystem in case of an unexpected increase
> in log collection I suspect this is a bug. So either the system needs
> to be able to follow symlinks or an option such as pid_file=[filepath]
> needs to be available in /etc/audit/
>
> To manage notifications about this bug go to:
> https:/
>