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.

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

systemd: Ignore exit code of [email protected] instantiations #199

Merged
merged 2 commits into from
Oct 9, 2024

Conversation

TwizzyDizzy
Copy link
Contributor

@TwizzyDizzy TwizzyDizzy commented Sep 13, 2024

Recently, the support for systemd based status checking has been implemented.

Due to the way MariaDB Community Edition implements the locking during a mariabackup in comparison to MariaDB Enterprise Edition, it is possible, that during a mariabackup some instantiations of [email protected] will fail because the check for wsrep_ready briefly reports OFF.

This leads to the units failing and impeding the overall system state as seen by systemctl status:

● HOSTNAME
    State: degraded
    Units: 331 loaded (incl. loaded aliases)
     Jobs: 0 queued
   Failed: 1 units
    Since: Thu 2024-08-15 16:25:35 CEST; 4 weeks 1 day ago
  systemd: 252-32.el9_4.6
  Tainted: local-hwclock
   CGroup: /

and

root@HOSTNAME / # systemctl --failed
  UNIT                                                            LOAD   ACTIVE SUB    DESCRIPTION                            
● [email protected]:9220-192.168.0.0:34154.service loaded failed failed mysqlchk service (192.168.0.0:34154)

We therefore propose to not honor the exit code of the instantiations of [email protected].

Cheers Thomas

@TwizzyDizzy TwizzyDizzy marked this pull request as ready for review September 13, 2024 16:26
@TwizzyDizzy TwizzyDizzy changed the title systemd: Reset failed check units to not impede overall system state systemd: Ignore exit code of [email protected] instantiations Sep 13, 2024
@fraenki fraenki merged commit 064f715 into markt-de:main Oct 9, 2024
18 of 19 checks passed
@fraenki
Copy link
Member

fraenki commented Oct 9, 2024

Merged, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants