We had an install that we upgraded from 2.2 to 2.4.8 I believe. I’ve then tried a fair few times now to upgrade to 3.0.2.
This latest attempt appeared to go ok, the command line upgrade said it was successful but since then we are getting a http 500 internal server error when trying to access the install. The error logs are not particularly helpful:
any help would be gratefully received as we need to repeat this on another 2 installs after this has been completed (we are trying to bring a number of installs into one but before we can export/import the journals they need to be upgraded inline)
I’ve found the error log I think but I’m not sure what out of it would be pertinent. There are some warnings and such from earlier in the day but around the time I tried to access following the upgrade I just have this repeatedly:
[13-Apr-2018 11:23:43 UTC] ojs2: Couldn’t lock the file.
We are only upgrading to 3.0.2 in order to be able to export the journal for import into a newer OJS installation.
We are only upgrading to 3.0.2 in order to be able to export the journal for import into a newer OJS installation.
Can you describe what you’re working on further? Is it not feasible to just upgrade the installation to a newer version rather than exporting/importing?
Regards,
Alec Smecher
Public Knowledge Project Team
We’ve sorted the issue. It was a permissions problem.
We have multiple installations being combined into one. Upgrading this one to the latest wouldn’t solve the problem of having multiple installations in the first place.