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


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Cloudron Forum

Apps | Demo | Docs | Install

Errors in the Moodle logs

Scheduled Pinned Locked Moved Solved Moodle
6 Posts 5 Posters 207 Views
    • 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.
  • robiR Offline
    robiR Offline
    robi
    wrote on last edited by
    #1
     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 sky tech

    jdaviescoatesJ 1 Reply Last reply
    1
  • jdaviescoatesJ Online
    jdaviescoatesJ Online
    jdaviescoates
    replied to robi on last edited by
    #2

    @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
    0
  • nebulonN Online
    nebulonN Online
    nebulon Staff
    wrote on last edited by
    #3

    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
    0
  • girishG Offline
    girishG Offline
    girish Staff
    wrote on last edited by
    #4

    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
    1
  • ? Offline
    ? Offline
    A Former User
    wrote on last edited by A Former User
    #5

    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
    1
  • robiR Offline
    robiR Offline
    robi
    wrote on last edited by
    #6

    no worries, just reporting in case it was relevant.

    Life of sky tech

    1 Reply Last reply
    0

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Login

  • Don't have an account? Register

  • Login or register to search.