Kirby randomly tries to access msql.so - why?

The CMS Questions
1

I have a very basic Kirby 2 setup. Among other things I provide some product information via an API endpoint, which basically just checks whether a page (for example /category/productname) is existent and then returns the page content.
Since the last server update I randomly run into (inconsistent) server errors (500) about every 5th time accessing this endpoint. With debug_mode enables the error message states
Whoops \ Exception \ ErrorException (E_CORE_WARNING)

Unknown: Unable to load dynamic library ‘msql.so’ (tried: /opt/plesk/php/7.4/lib/php/modules/msql.so (/opt/plesk/php/7.4/lib/php/modules/msql.so: cannot open shared object file: No such file or directory), /opt/plesk/php/7.4/lib/php/modules/msql.so.so (/opt/plesk/php/7.4/lib/php/modules/msql.so.so: cannot open shared object file: No such file or directory))

Since kirby is meant to be file system-based and I did not configure it to use a database such as msql (my config.php is basically empty beside the debugging_mode line), I’m very confused by this error message.
Additionally the error page does not provide any information that could help to further investigate the error (the script name is simply /index.php) and there is not entry in the server’s error logs for the time.

Any idea how to debug this?
My first impression was that this must have something to do with the server update. But since the error message states clearly that it tried to access msql (which is not provided by my hoster) it is hard to argue that the error is on my hoster’s side and not on mine :frowning:

2

No, Kirby does not access that PHP extension.

Check if your php.ini tries to load that extension and disable it. If there’s nothing in your php.ini please get in contact with your provider.

As you can see from the error constant (E_CORE_WARNING), this is an error that occurs during PHP’s initial startup, so nothing to do with Kirby but with your server/PHP configuration.