When doing the database upgrade from 2.4.7.1 to 2.4.8.1 from the web, we receive the following error message. Tried a couple of times and same error occurs. Yes, I turned installed=off to get to the page. Turned installed=on after failure and system seems to run fine. Suggestions? Is this also a max execution time? This is on a VPS so max execution time should not be an issue as in a shared host. Thank you.
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator to inform of the time the error occurred and of anything you might have done that may have caused the error.
More information about this error may be available in the server error log
No I did not. Will check. Interestingly, OJS still reporting that the upgrade needs to be done. I did do the test install first and it ran to completion.
If the version number still reports as your old version, it suggests that the upgrade didn’t complete. One of the final steps is to update the version number in the DB. Your error log, I suspect, will contain some useful information.
Regards,
Alec Smecher
Public Knowledge Project Team
The location of your PHP error log will depend on your hosting provider’s configuration, but usually it’s a file called error_log somewhere within your account.
Regards,
Alec Smecher
Public Knowledge Project Team
It may, but not necessarily. If PHP is configured to log errors through the web server, it’ll be up to the web server (e.g. Apache) to find the appropriate place to log the messages; that’s beyond PHP’s configuration.
Regards,
Alec Smecher
Public Knowledge Project Team
Those SIGKILL messages suggest a possible Apache timeout to me. I’d suggest checking your Apache configuration to see whether there’s a hard limit (e.g. 30 seconds).
Another option would be to run the upgrade again, then check the log immediately to see if a new message has been added. It’s hard to know from your log how long those messages have been there (beyond the few that do have timestamps).
Regards,
Alec Smecher
Public Knowledge Project Team
Alec, this was hard coded as Timeout 60. But you would think that it should be enough? I have changed to 120. Will check to see if it runs. Is there an issue with a longer timeout? This would be a per session timeout correct? Thank you.
Depending on how much data you’re running through the upgrade, and the specifics of your server, it may indeed take longer than 60 seconds. If you suspect a timeout, try timing the upgrade with a watch to see if the process stops at a round number.
Regards,
Alec Smecher
Public Knowledge Project Team
Tried timeouts set at 480 seconds and it still fails around 60 seconds. I reread this not on the install page. Am I looking in the wrong place? Not HTTPF.CONF but PHP.INI??
please ensure that the max_execution_time directive in your php.ini configuration file is set to a high limit. If this or any other time limit (e.g. Apache’s “Timeout” directive) is reached and the upgrade process is interrupted, manual intervention will be required.