Uploaded image for project: 'Moodle Community Sites'
  1. Moodle Community Sites
  2. MDLSITE-5245

worker01.test.in.moodle.com startup

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: Integration
    • Labels:
      None

      Description

      Some hours ago a number of jobs (chains) failed @ nightly. The problem were database connectivity @ worker01.test.in.moodle.com.

      Connected, there were no containers running and it seems the server was rebooted 19h ago:

      $ docker ps 
      CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
      -----
       
      $ uptime
       00:00:34 up 19:25,  1 user,  load average: 0.09, 0.05, 0.01
      

      So I've proceeded manually to kill exited (old) containers and start all the databases, using /store/scripts/dockercleaner.sh and /store/scripts/dockerdb.sh mysql|pgsql|mariadb|oracle|sqlsrv.

      This issue is about to ensure that the scripts above are executed on startup to get everything ready or start (and maybe also to understand why the server was rebooted 19h ago).

      Ciao

        Attachments

          Activity

            People

            • Assignee:
              dobedobedoh Andrew Nicols
              Reporter:
              stronk7 Eloy Lafuente (stronk7)
              Tester:
              Eloy Lafuente (stronk7)
              Participants:
              Component watchers:
              Eloy Lafuente (stronk7)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: