How to find the source of "Got unexpected auxiliary data with level=1 and type=2"

I see many entries of "Got unexpected auxiliary data with level=1 and type=2" in journalctl, but there is no hint where these are generated. The number of log entries is high. I cannot brain-link these entries with specific services.

How can I find out which service generates the "Got unexpected auxiliary data with level=1 and type=2" messages?

Asked By: Thomas

||

This might be somewhat brute-force but you can list all enabled services with

systemctl list-unit-files | grep enabled

You can likely disregard most of the services listed as being fairly vanilla. For the ones you want to take a look at, use

journalctl -u *servicename*

Tedious but it should work. Might be better to use a loop to examine each service and grep for your error message.

Answered By: doneal24

After more tests we found that with debug logging enabled, every service restart where systemctl is involved leads to exactly three "Got unexpected auxiliary data with level=1 and type=2" entries in the journal. This is also true on fresh operating system installs of CentOS and Alma Linux. It is still unclear why these entries are logged, but they seem to be totally normal and expected.

Answered By: Thomas
Categories: Answers Tags:
Answers are sorted by their score. The answer accepted by the question owner as the best is marked with
at the top-right corner.