Config Log issue on multisites

Created on 19 December 2024, 4 months ago

Problem/Motivation

I'm using the config log module in Drupal 10 multisites. It's enabled and configured for all 13 Drupal 10 multisites. On a few multisites, it's not sending email notifications when there are config changes. The config log reports page at /admin/reports/config-log is also missing.

Attached is a screenshot of what is missing for a few of a multisites.

Steps to reproduce

1) Enable the module via drush for all multisites
2) Configure the module for each multisite at admin/config/development/config_log
3) Enable log destination, custom table, default logging system, mail notification, and mail notification email for each multisite
4) Make a config change.
5) Confirm there is a config change using Drush or Drupal UI
6) Uninstall and re-install the module.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Active

Version

4.0

Component

Code

Created by

πŸ‡¦πŸ‡½Γ…land Islands albertho425 Seattle, WA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @albertho425
  • πŸ‡­πŸ‡ΊHungary nagy.balint

    Hi!

    If I understand correctly, all the sites have the same configuration, but different database.

    Is the (drush cim) show nothing to synchronize for all sites?

  • πŸ‡¦πŸ‡½Γ…land Islands albertho425 Seattle, WA

    Hello @nagy.balint,

    Yes all multiisites have the same configuration and different database.

    Drush cim and the Configuration Log module as well as shell scripts are not showing anything to synchronize.

    Thanks.

  • πŸ‡­πŸ‡ΊHungary nagy.balint

    I would guess if
    - code is the same
    - config is the same and nothing to synchronize
    - some sites do send mail

    then the only thing that could be different is perhaps mail sending configuration (perhaps site email, or any related config in settings.php overriden, or in config split or gitignore or config ignore)
    because if the mail sending is different, perhaps also due to domain differences, then maybe the mail is rejected by the mail server.

    There might be some dblog messages on the affected sites on config change about mail sending.

  • πŸ‡¦πŸ‡½Γ…land Islands albertho425 Seattle, WA

    I checked the following

    - settings.php is same for all 10+ multisites except for the database table name, username, and password
    - I have a shell script for all multisites that emails site information on-demand and automatically, so the email is working
    - I also have a shell script that checks for config changes and emails from each multisite which is working

    On the 2 where I am experiencing an issue
    - /admin/reports/config-log is also missing for those sites
    - emails are not being sent when a config change occurs, but is sending through my shell scripts

    Is there something I can check in the database?

    Thanks.

  • πŸ‡­πŸ‡ΊHungary nagy.balint

    The admin/reports/config-log is simply a views where the config is installed from the config_log_views submodule.
    So if it is not there, then it is likely that config_log_views is not enabled in that database, and or that the config differs.

    Apart from that, only the emails are not sent?
    If you enable "Default logging system" in admin/config/development/config_log then it should log config changes in the dblog (admin/reports/dblog) Recent Log Messages.

  • πŸ‡¦πŸ‡½Γ…land Islands albertho425 Seattle, WA

    Configurations on 2 affected sites
    - Configuration Log and Configuration Log Views are installed
    - Custom table, Default logging system, and mail notification are checked
    - Ignore logging on config import and ignore logging if there are no changes to the configuration are also checked

    What's not working
    -Emails not sending
    -Can't access the view
    -Can't see the config change in dblog

    Thank you.

  • πŸ‡­πŸ‡ΊHungary nagy.balint

    I guess you cannot give me any access to look around, if I had access to the server I could probably figure it out.

    So far based on the information I could only conclude that the issue is likely not with the module, but how it was installed.
    Or maybe if it was an old installation and the upgrade somehow failed, but even then the dblog logger has no dependency so that should work no matter what.
    Because what you are describing is that the module is installed but Drupal simply ignores everything the module defined, which is normally unlikely.

  • πŸ‡­πŸ‡ΊHungary nagy.balint

    You can turn off the two ignore settings as a test just in case they interfere with something.

  • πŸ‡¦πŸ‡½Γ…land Islands albertho425 Seattle, WA

    Sorry. Correction to my statement.

    On the 2 affected sites, email is sending correctly. I just can't access the view and I can't see the config change in dblog. Unfortunately, I can't give access to the server. I tried uninstalling and re-installing. I also tried turning off the two ignore settings. Still the same. In case it was an old installation and failed, do you have instructions on how I can do a clean uninstall?

    Thanks.

  • πŸ‡­πŸ‡ΊHungary nagy.balint

    Hi!

    • Can you provide screenshot of the admin/config/development/config_log form on the affected site?
    • Can you check if the config_log_views is enabled in the extend page? (admin/modules)
    • Are you using the admin user? or have administer site configuration permission?
  • πŸ‡¦πŸ‡½Γ…land Islands albertho425 Seattle, WA

    Hello @nagy.balint

    Sorry for the late reply. I am using admin user and the config_log_views is enabled in the extend page.

    On the 2 sites where config_log_views is enabled but the URL /admin/reports/config-log is missing, I exported the YML file of a config_log_view of a site that is fully working and imported the YML file to the 2 sites where /admin/reports/config-log is missing. I'll closely monitor for the next few days but it looks like exporting/importing the specific config_log_views using drush resolves the issue. Thank you.

Production build 0.71.5 2024