Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-51111

MUC config.php random reset

    XMLWordPrintable

Details

    • MOODLE_28_STABLE, MOODLE_30_STABLE, MOODLE_310_STABLE, MOODLE_39_STABLE
    • MOODLE_310_STABLE, MOODLE_39_STABLE
    • MDL-51111-muc-reset
    • Hide

      1) Find the site data run

      tail -F muc/config.php

      2) As an anon user visit /admin/index.php?cache=0 or run

      curl -I http://moodle.local/admin/index.php?cache=0

      3) Confirm the tail above was empty, or if it did write (eg right after upgrade) then it was empty on subsequent runs

       

      Show
      1) Find the site data run tail -F muc/config.php 2) As an anon user visit /admin/index.php?cache=0 or run curl -I http://moodle.local/admin/index.php?cache=0 3) Confirm the tail above was empty, or if it did write (eg right after upgrade) then it was empty on subsequent runs  

    Description

      Now and then the file-based MUC settings seems to be reset.

      We have added an external memcached store and sometimes the config.php is reset to default settings. That means we have to reconfigure the memcached instance everytime and edit the store mappings when this happens.

      This MUC config file resides in our NFS shared moodledata: /moodledata/moodle/muc/config.php

      I have not yet figured out how to trigger this behaviour and currently it occurs randomly like once a week or once per two or three weeks. We have also had times when it occured more often.

      There are also others experiencing this:
      https://moodle.org/mod/forum/discuss.php?d=274344

      Attachments

        Issue Links

          Activity

            People

              brendanheywood Brendan Heywood
              rien0700 Rikard E
              Peter Burnett Peter Burnett
              Victor Déniz Falcón Victor Déniz Falcón
              Mathew May Mathew May
              Votes:
              23 Vote for this issue
              Watchers:
              32 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 hours, 45 minutes
                  4h 45m

                  Clockify

                    Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.