Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Wolff Felix (ETAS-SEC/ECT-Be)" <Felix.Wolff@escrypt.com>
To: "Linux-audit@redhat.com" <Linux-audit@redhat.com>
Subject: Error starting auditd
Date: Thu, 16 May 2019 10:47:05 +0000	[thread overview]
Message-ID: <3dc64aea26e94e68818b81289f1a713b@escrypt.com> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 945 bytes --]

Hello,

I am currently porting auditd to a new platform. When starting it using `auditd -f`, I get the following error:

"Error setting audit daemon pid (File exists)"

It occurs during the call to `audit_set_pid(fd, getpid(), WAIT_YES);` in auditd.c. If I understand correctly, this call registers auditd with the kernel, is that correct? fd looks like a valid file descriptor, at least its >0. Especially the "file exists" part confuses me. In which direction can I investigate that error?

Thank you and greets,
Felix



--
Mit freundlichen Grüßen/Best regards
Felix Wolff
Software Engineer
[ESCRYPT-Logo_RGB]
ESCRYPT GmbH
Wittener Straße 45
44789 Bochum, Germany
Email:        felix.wolff@escrypt.com
Phone:      +49 30 403 691 957
Mobile:     +49 1525 6953 720
www.escrypt.com

Managing directors: Christopher White, Dr.-Ing. Thomas Wollinger
Registered office and court of registry: Bochum, Germany, HRB 7877


[-- Attachment #1.1.2: Type: text/html, Size: 7386 bytes --]

[-- Attachment #1.2: image003.png --]
[-- Type: image/png, Size: 6498 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



             reply	other threads:[~2019-05-16 10:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16 10:47 Wolff Felix (ETAS-SEC/ECT-Be) [this message]
2019-05-16 13:56 ` Error starting auditd Richard Guy Briggs
2019-05-16 14:11   ` AW: " Wolff Felix (ETAS-SEC/ECT-Be)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3dc64aea26e94e68818b81289f1a713b@escrypt.com \
    --to=felix.wolff@escrypt.com \
    --cc=Linux-audit@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox