Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved Errors in the Moodle logs

    Moodle
    5
    6
    171
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • robi
      robi last edited by

       Installation completed successfully.
      Oct 08 07:35:27 ==> Done.
      Oct 08 07:35:31 AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.18.0.26. Set the 'ServerName' directive globally to suppress this message
      

      I only looked because I had 0.3.0 installed and it was unresponsive. I did an upgrade to 0.4.0 and it was still unresponsive.
      Uninstall / Reinstall got it working while watching the logs, where this popped up.

      Life of Advanced Technology

      jdaviescoates 1 Reply Last reply Reply Quote 1
      • jdaviescoates
        jdaviescoates @robi last edited by

        @robi said in Errors in the Moodle logs:

        I only looked because I had 0.3.0 installed and it was unresponsive. I did an upgrade to 0.4.0 and it was still unresponsive.
        Uninstall / Reinstall got it working

        I had exactly the same experience. I guess it's to be expected when apps are still unstable.

        I didn't actually check the logs though!

        I use Cloudron with Gandi & Hetzner

        1 Reply Last reply Reply Quote 0
        • nebulon
          nebulon Staff last edited by

          The apache warning is to be expected. I guess we should set the server name explicitly in the configs, but it is not a failure reason.

          Still looks like there is some other bug lurking somewhere. If you hit that situation please check the logs further.

          1 Reply Last reply Reply Quote 0
          • girish
            girish Staff last edited by

            Yes, @atrilahiji and I made several breaking changes. First, we switched db from mysql to postgres. Then we changed the whole code base to be non-read only. We didn't bother with proper updates since it is still unstable, sorry about that!

            1 Reply Last reply Reply Quote 1
            • ?
              A Former User last edited by A Former User

              Yeah. The way Moodle handles plugins required moving the whole thing to /app/data. The PostgreSQL change was to align it with Moodle's recommendations.\

              fingers crossed we wont need to make any more breaking changes.

              1 Reply Last reply Reply Quote 1
              • robi
                robi last edited by

                no worries, just reporting in case it was relevant.

                Life of Advanced Technology

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Powered by NodeBB