Couldn't lock the file - after updating in prep for upgrade

when viewing our test journal sites we are seeing Couldn’t lock the file error position varies depending on which section of the journal you are on.

Most recent thing that we changed was to update any Tables currently using Engine of MyISAM to instead use InnoDB. e.g. submission_files - this was done because we were attempting to test run upgrade and errors were generated during upgrade which we believe were related to the mix of MyISAM and InnoDB in use. We refreshed Test and updated the tables and have not yet attempted the upgrade again.

We are currently on 3.1.1.4 aiming to move to 3.3.0.10. Php version has been updated accordingly.

I’d like to know if this is a problem before attempting upgrade again.

Hi @loola

There is a previous thread that the user managed to fix this issue you have reported. Please see:

Best,
Israel

I’m sorry but reading that thread it doesn’t appear to be the same issue?

Hi @loola

Could you please post the error_log of your server where it shows the fatal error of application?

Best,
Israel

it isn’t a fatal error - it appears to have been resolved by changing the database engine and upgrading to 3.3.0-10

1 Like