Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fatal errors in log during Anaconda installation: "CRIT sss_cache:No domains configured, fatal error!" #6387

Closed
pbrezina opened this issue Oct 11, 2022 · 2 comments
Closed

Fatal errors in log during Anaconda installation: "CRIT sss_cache:No domains configured, fatal error!" #6387

pbrezina opened this issue Oct 11, 2022 · 2 comments
Assignees
@pbrezina
Labels
Bugzilla Closed: Fixed Issue was closed as fixed.

Comments

@pbrezina
Copy link
Member

https://bugzilla.redhat.com/show_bug.cgi?id=2133437

Created [attachment 1917056](https://bugzilla.redhat.com/attachment.cgi?id=1917056) [[details]](https://bugzilla.redhat.com/attachment.cgi?id=1917056&action=edit)
/tmp/syslog from installer environment

Description of problem:

We have new CRIT error messages appearing in kickstart during root password setup in chroot (and also in one other place):

09:32:55,063 WARNING org.fedoraproject.Anaconda.Modules.Users:INFO:anaconda.modules.common.task.task:Configure root password
09:32:55,136 WARNING org.fedoraproject.Anaconda.Modules.Users:INFO:program:Running... chpasswd -R /mnt/sysroot -e
09:32:55,267 CRIT sss_cache:No domains configured, fatal error!
09:32:55,317 CRIT sss_cache:No domains configured, fatal error!
09:32:55,328 WARNING org.fedoraproject.Anaconda.Modules.Users:INFO:program:Running... chage -R /mnt/sysroot -d  root
09:32:55,402 NOTICE audit:USER_MGMT pid=20479 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:kernel_t:s0 msg='op=change-last-change-date id=0 exe="/usr/bin/chage" hostname=? addr=? terminal=? res=success'
09:32:55,499 CRIT sss_cache:No domains configured, fatal error!
09:32:55,515 WARNING org.fedoraproject.Anaconda.Modules.Users:INFO:program:[sss_cache] [confdb_get_domains] (0x0010): No domains configured, fatal error!
09:32:55,515 WARNING org.fedoraproject.Anaconda.Modules.Users:DEBUG:program:Return code: 0


Version-Release number of selected component (if applicable):

https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/COMPOSE_ID:
Fedora-Rawhide-20221009.n.0

It seems to start happening when 
sssd-2.8.0-1 replaced sssd-2.7.4-1.

Are we missing some configuration in installation environment?

How reproducible:

Do Fedora Server installation with latest development rawhide

Steps to Reproduce:
1.
2.
3.

Actual results:

Error messages in the log, but installation seems to finish without issues.

Expected results:

No CRIT error messages by sss in the logs.

Additional info:

The CRIT messages make Anaconda kickstart test fail. We can put them on a ignore list but we should try to fix the origin of the messages first.
@pbrezina pbrezina self-assigned this Oct 11, 2022
pbrezina added a commit to pbrezina/sssd that referenced this issue Oct 11, 2022
@pbrezina
confdb: avoid syslog message when no domains are enabled
eeac2d5 
This syslog message would also appear when calling other tools like
sss_cache which is confusing. We return specific error code instead
and let the error be syslogged in the monitor in monitor.c:main (this
is already implemented).

Resolves: SSSD#6387
@pbrezina pbrezina mentioned this issue Oct 11, 2022
Closed
@pbrezina
Copy link
Member Author

This is a regression introduced in #6182

pbrezina added a commit to pbrezina/sssd that referenced this issue Oct 12, 2022
@pbrezina
confdb: chande debug level when no domain are found in confdb_get_dom…
6316174 
…ains

We print the error as fatal error in the monitor to make sure the
message is correctly visible. However, the error is not fatal for tools
like sss_cache and it should not be printed there by default.

Since the tools have default debug level set to SSSDBG_FATAL_FAILURE, it
is sufficient to just drop the level to critical.

Resolves: SSSD#6387
pbrezina added a commit to pbrezina/sssd that referenced this issue Oct 13, 2022
@pbrezina
confdb: avoid syslog message when no domains are enabled
cc87838 
This syslog message would also appear when calling other tools like
sss_cache which is confusing. We return specific error code instead
and let the error be syslogged in the monitor in monitor.c:main (this
is already implemented).

Resolves: SSSD#6387

:fixes: A regression when running sss_cache when no SSSD domain is
  enabled would produce a syslog critical message was fixed.
pbrezina added a commit to pbrezina/sssd that referenced this issue Oct 13, 2022
@pbrezina
confdb: chande debug level when no domain are found in confdb_get_dom…
22704f1 
…ains

We print the error as fatal error in the monitor to make sure the
message is correctly visible. However, the error is not fatal for tools
like sss_cache and it should not be printed there by default.

Since the tools have default debug level set to SSSDBG_FATAL_FAILURE, it
is sufficient to just drop the level to critical.

Resolves: SSSD#6387
pbrezina added a commit that referenced this issue Oct 13, 2022
@pbrezina
confdb: chande debug level when no domain are found in confdb_get_dom…
df55b1f 
…ains

We print the error as fatal error in the monitor to make sure the
message is correctly visible. However, the error is not fatal for tools
like sss_cache and it should not be printed there by default.

Since the tools have default debug level set to SSSDBG_FATAL_FAILURE, it
is sufficient to just drop the level to critical.

Resolves: #6387

Reviewed-by: Alejandro López <allopez@redhat.com>
Reviewed-by: Sumit Bose <sbose@redhat.com>
pbrezina added a commit that referenced this issue Oct 13, 2022
@pbrezina
confdb: avoid syslog message when no domains are enabled
a6d5214 
This syslog message would also appear when calling other tools like
sss_cache which is confusing. We return specific error code instead
and let the error be syslogged in the monitor in monitor.c:main (this
is already implemented).

Resolves: #6387

:fixes: A regression when running sss_cache when no SSSD domain is
  enabled would produce a syslog critical message was fixed.

Reviewed-by: Alejandro López <allopez@redhat.com>
Reviewed-by: Sumit Bose <sbose@redhat.com>
(cherry picked from commit b38fdc8)
pbrezina added a commit that referenced this issue Oct 13, 2022
@pbrezina
confdb: chande debug level when no domain are found in confdb_get_dom…
ab7cbb5 
…ains

We print the error as fatal error in the monitor to make sure the
message is correctly visible. However, the error is not fatal for tools
like sss_cache and it should not be printed there by default.

Since the tools have default debug level set to SSSDBG_FATAL_FAILURE, it
is sufficient to just drop the level to critical.

Resolves: #6387

Reviewed-by: Alejandro López <allopez@redhat.com>
Reviewed-by: Sumit Bose <sbose@redhat.com>
(cherry picked from commit df55b1f)
@pbrezina
Copy link
Member Author

Pushed PR: #6388

  • master
    • df55b1f - confdb: chande debug level when no domain are found in confdb_get_domains
    • 64c22dd - sss_cache: use ERR_NO_DOMAIN_ENABLED instead of ENOENT
    • 4da8613 - monitor: read all enabled domains in add_implicit_services
    • b38fdc8 - confdb: avoid syslog message when no domains are enabled
  • sssd-2-8
    • ab7cbb5 - confdb: chande debug level when no domain are found in confdb_get_domains
    • a6312c4 - sss_cache: use ERR_NO_DOMAIN_ENABLED instead of ENOENT
    • 1df0294 - monitor: read all enabled domains in add_implicit_services
    • a6d5214 - confdb: avoid syslog message when no domains are enabled

@pbrezina pbrezina added the Closed: Fixed Issue was closed as fixed. label Oct 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pbrezina pbrezina

Labels
Bugzilla Closed: Fixed Issue was closed as fixed.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

confdb: avoid syslog message when no domains are enabled pbrezina/sssd
1 participant
@pbrezina