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.