Upgrading from 2.4x to 3.0.2 http 500 error

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:

    • [13/Apr/2018:12:20:44 +0100] “GET /index.php/index/install HTTP/1.1” 200 -
    • [13/Apr/2018:12:23:42 +0100] “GET / HTTP/1.1” 500 32
    • [13/Apr/2018:12:23:51 +0100] “GET /index.php/ HTTP/1.1” 500 32
    • [13/Apr/2018:12:30:22 +0100] “GET /index.php/index/login HTTP/1.1” 500 32

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)

thanks

Hi @loola,

I think you’re looking at your web server access log, not your error log; check around to see if there’s a separate error log with more details.

Note that 3.0.2 is now getting old; I’d suggest upgrading to something newer.

Regards,
Alec Smecher
Public Knowledge Project Team

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.

Regards,

Lucy

Lucy Peck

Applications Analyst

cid:image002.jpg@01D22E04.CF78E800

Digital Technology Services

Sheffield Hallam University

Howard Street

Sheffield, S1 1WB

0114 225 5555

0114 225 3652

Hi @loola,

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.