Errors after migration to another server 500 internal error, unexpected error and Slim Application Error

Greetings support team,
We have recently migrated to a new server which is Cent O.S. The previous server was also Cent OS. Since the migration we are experiencing the following error:

  1. An unexpected error message arise when someone wants to open the PDF files of already published articles.
  2. HTTPS 500 error arises when an editor or reviewer wants to open / download the submitted files from the dashboard.
  3. Slim Application error arises when someone wants to make a submission and upload a file.

Unfortunately there are no error logs generating so i am unable to do the root cause analysis.

We are using OJS Ver.

PHP: 7.4.1
MySQL: 10.4.31-MariaDB

Hi @KMC,

Did you get these error messages from your PHP error log? If so, it might be helpful to post the contents of your error log - that can help others who might assist you in troubleshooting this issue.

PKP Team

These errors are shown on the frontend, The OJS is not generating error logs, i dont know why? as usually they are in the installation directory of the OJS i.e home/public.html.
However i noticed these errors of the php
[Fri Dec 01 05:39:16.558820 2023] [:error] [pid 24003:tid 139807570454272] [client] PHP Warning: PHP Startup: Unable to load dynamic library ‘’ (tried: /usr/local/lib/php/extensions/no-debug-non-zts-20190902/ (/usr/local/lib/php/extensions/no-debug-non-zts-20190902/ cannot open shared object file: No such file or directory), /usr/local/lib/php/extensions/no-debug-non-zts-20190902/ (/usr/local/lib/php/extensions/no-debug-non-zts-20190902/ cannot open shared object file: No such file or directory)) in Unknown on line 0

Hi @KMC,

Thanks for clarifying and providing the error log messages. I can’t say for certain what is going on here, but I will see if one of our team members can comment when they are available.

Best regards,

PKP Team

Hi @KMC,

I’d suggest looking on e.g. StackOverflow for ways to resolve that error message; it’s related to your PHP setup, not OJS. Once you get it resolved, continue looking in your PHP error log for other details.

Alec Smecher
Public Knowledge Project Team

1 Like

Thank you @asmecher . The issue was due to a php.module plugin and the hosting company fixed that. Now the OJS is working properly.

1 Like