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

unable to run on ubuntu 20.04

Scheduled Pinned Locked Moved Solved Support
install
8 Posts 4 Posters 422 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.
  • moussanM Offline
    moussanM Offline
    moussan
    wrote on last edited by girish
    #1

    i cant seem to get cloudron to function correctly.
    i go through the installation process but get a notice to check the installation log.

    see below, where is the issue.
    when i go to the installation ip, i see an nginx page stating it is installed but probably not configured correctly.

    can anyone help please.

    root@server:~# nano /var/log/cloudron-setup.log


    link text


    did the installation process not finish?

    nebulonN 1 Reply Last reply
    0
  • nebulonN Offline
    nebulonN Offline
    nebulon Staff
    replied to moussan on last edited by
    #2

    @moussan indeed it looks like the journald config step is failing with:

    2021-10-12T14:25:53 ==> start: Configuring journald
    setfacl: /var/log/journal/*/system.journal: No such file or directory
    

    Which VPS provider is this?

    1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    wrote on last edited by girish
    #3

    I fixed this exact issue in https://git.cloudron.io/cloudron/box/-/commit/73315a42fef03bc144fdfd707b8a6d5905733109 since it was failing in time4vps servers.

    Workaround: mkdir -p /var/log/journal/foo && touch /var/log/journal/*/system.journal . Then run the setup script again.

    M 1 Reply Last reply
    0
  • M Offline
    M Offline
    msbt App Dev
    replied to girish on last edited by
    #4

    @girish isn't that bit supposed to be outside of the if?

    girishG 1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    replied to msbt on last edited by
    #5

    @msbt i removed the setfacl entirely. is that what you are asking?

    M 1 Reply Last reply
    0
  • M Offline
    M Offline
    msbt App Dev
    replied to girish on last edited by
    #6

    @girish no, the line with chown root:systemd-journal /var/log/journal, that was always running before, now only in the if condition, not sure if it's required though 😉

    girishG 1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    replied to msbt on last edited by
    #7

    @msbt ah, got it. The if block should ideally never run. It should only run on distros which do not have /var/log/journal (I don't understand why it's not there on some specific VPS, some ubuntu or provider flakiness).

    M 1 Reply Last reply
    0
  • M Offline
    M Offline
    msbt App Dev
    replied to girish on last edited by
    #8

    @girish that's what I meant, the cmd ran always before, but now only in the rare case the directory isn't there

    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