#8436 List of Supported Distros?

unreleased
open
nobody
None
General
nobody
2022-06-11
2022-06-05
jmclean
No

Is it possible we could get a list of distros that Allura is supported on? I tried following the Docker install steps and it failed on both Ubuntu 22.04 (Current) and 20.04. The steps did work correctly on 18.04, but that version is now out of support.

Version: 1.13.0
Steps I followed: https://forge-allura.apache.org/docs/getting_started/installation.html

Discussion

  • Dave Brondsema

    Dave Brondsema - 2022-06-06

    What errors did you get? [#8406] has another user's error messages with Ubuntu, if your error matches one of those perhaps that will help.

    We are way overdue for making a release, you could try installing from latest git instead of 1.13.0. It should be stable and has quite a few fixes & improvements.

     

    Related

    Tickets: #8406

  • jmclean

    jmclean - 2022-06-08

    Thanks for the reply. I didn't see any obvious errors when following the Docker steps, but upon spinning up the containers I couldn't connect to the web interface on port 8080. Though oddly I could get to the SOLR web interface and MongoDB responded when I poked it with a web browser.

    I would eventually get a time out on 8080. Sometimes I would get redirected to the 'neighborhoods' URL if I waited long enough, but still no page.

    I did run across ticket 8406 while I was Googling for an answer. It didn't seem to help me at the time, but I can re-check.

    I'm happy to follow any troubleshooting or log gathering steps you suggest.

     
  • Dave Brondsema

    Dave Brondsema - 2022-06-08

    Interesting you can get to some services, and even getting redirected to the 'neighborhoods' URL sometimes.

    Does docker-compose ps say the "web" container is up?

    Any errors in docker-compose logs web?

    Are you using an IP or hostname besides localhost? If so see note 2 at https://forge-allura.apache.org/docs/getting_started/installation.html#first-run

     
  • jmclean

    jmclean - 2022-06-09

    Running "docker-compose ps" shows all listed containers as up, this includes allura_http1.
    (Sorry, formatting may get broken...)
    allura_http_1 /usr/sbin/apache2 -D Up 0.0.0.0:8080->80/tcp,:::8
    FOREG ... 080->80/tcp
    allura_inmail_1 paster smtp_server Up 0.0.0.0:8825->8825/tcp,::
    docker- ... :8825->8825/tcp
    allura_mongo_1 docker-entrypoint.sh Up 0.0.0.0:27017->27017/tcp,
    mongo ... :::27017->27017/tcp
    allura_outmail_1 python -u -m smtpd -n -c Up 8826/tcp
    a ...
    allura_solr_1 docker-entrypoint.sh Up 0.0.0.0:8983->8983/tcp,::
    solr- ... :8983->8983/tcp
    allura_taskd_1 paster taskd docker- Up
    dev.ini
    allura_web_1 /bin/sh -c gunicorn Up 0.0.0.0:8088->8088/tcp,::
    --past ... :8088->8088/tcp

    Running "docker-compose logs web" gives me:
    web_1 | [2022-06-09 01:45:39 +0000] [6] [INFO] Starting gunicorn 19.10.0
    web_1 | [2022-06-09 01:45:39 +0000] [6] [INFO] Listening at: http://0.0.0.0:8088 (6)
    web_1 | [2022-06-09 01:45:39 +0000] [6] [INFO] Using worker: sync
    web_1 | [2022-06-09 01:45:40 +0000] [9] [INFO] Booting worker with pid: 9
    web_1 | 01:45:48,165 ERROR [tg.configuration.app_config] Failed to initialize mako template engine, removing it...

    I am attempting to access the VM from another system via it's local network address. I did follow the instructions to the note as far as I can tell.
    I tried connecting locally with links on https://localhost:8080 and no luck.

    Thanks again.

     
  • Dave Brondsema

    Dave Brondsema - 2022-06-10

    I noticed you mentioned "https://localhost:8080" with httpS. I don't know if that's what you were actually accessing or not, but there's no https support for local allura. So you'll need to make sure your browser connects to plain http.

     
  • jmclean

    jmclean - 2022-06-11

    Oops. I apologize, that was a miss-type. I tested both http and https just to be sure.

     

Log in to post a comment.