[Loris-dev] LORIS - v21.0.3 (Ubuntu Base 16.04.6) - CRU

[Dave MacFarlane]

In that case. you're missing the equivalent step of the install process
(run `make` for production or `make dev` for a sandbox which invokes
composer.)

There was a bug in the initial 21.0.0 release where that step wasn't
properly documented, so it's easy to have missed but it should be listed as
step 4 in the README as of v21.0.3.

On Thu, Nov 14, 2019 at 1:59 PM Matthew Sparks, Mr <matthew.sparks at mcgill.ca>
wrote:

> Sorry if I was unclear. I’m not upgrading. I have more than one instance
> of Loris running. The v17 version will be made dormant once the latest v21
> clean install works. I would like to port a few modules from the working
> v17 to the latest. Otherwise, I have 10+ point-release iterations to
> updates to make.
>
>
>
> -Matthew
>
>
>
>
>
> *From:* Dave MacFarlane <dave.macfarlane at mcin.ca>
> *Sent:* Thursday, November 14, 2019 1:56 PM
> *To:* Matthew Sparks, Mr <matthew.sparks at mcgill.ca>
> *Cc:* loris-dev at bic.mni.mcgill.ca
> *Subject:* Re: [Loris-dev] LORIS - v21.0.3 (Ubuntu Base 16.04.6) - CRU
>
>
>
> When upgrading, it's required to be on the latest minor release and to go
> one release at a time. If you go to https://github.com/aces/Loris/releases
> there should be an "Upgrade process" section for each release that you
> should follow in order from 17. The error (that it can't find the autoload
> file generated by composer) seems to suggest you missed step 2 of the
> upgrade process to LORIS v21.
>
>
>
> - Dave
>
>
>
> On Thu, Nov 14, 2019 at 1:39 PM Matthew Sparks, Mr <
> matthew.sparks at mcgill.ca> wrote:
>
> Hi Dave,
>
>
>
> Certainly, my apologies for not attaching them initially.
>
>
>
> Best,
>
> Matthew
>
>
>
> *From:* Dave MacFarlane <dave.macfarlane at mcin.ca>
> *Sent:* Thursday, November 14, 2019 1:34 PM
> *To:* Matthew Sparks, Mr <matthew.sparks at mcgill.ca>
> *Cc:* loris-dev at bic.mni.mcgill.ca
> *Subject:* Re: [Loris-dev] LORIS - v21.0.3 (Ubuntu Base 16.04.6) - CRU
>
>
>
> Hi Matthew,
>
>
>
> Do you have access to the web server's error log on Digital Ocean? It's
> difficult to guess why it's generating a 500 error without seeing the error
> log.
>
>
>
> - Dave
>
>
>
> On Thu, Nov 14, 2019 at 1:30 PM Matthew Sparks, Mr <
> matthew.sparks at mcgill.ca> wrote:
>
> Hello Loris Devs,
>
>
>
> I have just installed a new loris instance on the DigitalOcean platform
> and post-install I receive a HTTP 500 Error.
>
>
>
> Please advise and see the screenshot attached;
>
> -          To troubleshoot; From the dev instance you can see that I’ve
> granted excessive permissions beyond what is needed, and the *issue
> persists*.
>
>
>
> Currently;
>
> -          Functional Loris *v17* instance running on DO.
>
> -          Non-functional Loris *v21.0.3 (.1-3)* instance running on DO.
>
>
>
> Nice to have;
>
> -          DigitalOcean application for rapid reployment.
>
> -          Up-to-date Loris install guide (e.g., deprecation of
> python-properties-common etc)
>
>
>
> I can re-initialize the DO base and provide you with root credentials for
> a quick install to loris v21.0.3?
>
> -          Ultimately, we need to be able to use the *DQT*.
>
>
>
> Any suggestions to resolve the issue would be appreciated
>
>
>
> Kindest regards,
>
> Matthew
>
> _______________________________________________
> Loris-dev mailing list
> Loris-dev at bic.mni.mcgill.ca
> https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bic.mni.mcgill.ca/pipermail/loris-dev/attachments/20191114/4c36201e/attachment.html>