Frustrating Error 500 without much details

[sochartetu]

"GET /en/part/30/info HTTP/2.0" 500 3467 "https://192.168.10.10:12443/en/category/33/parts" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:131.0) Gecko/20100101 Firefox/131.0"

Get Error 500 when I try to get info about parts.
Not a lot of details in docker logs.

I've tried to clear the cache, check the perms of such folder. Nothing constructive.

The only thing I see is this error when I try to interact with composer but DB is working fine.

17:29:36 CRITICAL [console] Error thrown while running command "doctrine:schema:validate". Message: "An exception occurred in the driver: could not find driver" ["exception" => Doctrine\DBAL\Exception\DriverException^ { …},"command" => "doctrine:schema:validate","message" => "An exception occurred in the driver: could not find driver"] ["token" => null,"command" => ["name" => "doctrine:schema:validate","arguments" => ["command" => "doctrine:schema:validate"]]]

[sochartetu]

So, after investing 5h to debug that, I've found out the culprit
is mb_strimwidth.
Despite mbstring being installed and enable in php 8.2 fpm, I get an error when going to Dev mode.
When commented, no more error.
WTH ?

[jbtronics]

What is the exact error message for this function to fail?

Do you have some weirdly encoded text in your database? I see not much reasons why this specific function should fail. Especially as these function has no (documented) failure behavior, which could cause an exception.

[sochartetu]

Fatal error: Call to undefined function mb_strimwidth() in ...

mbstring module is enable in PHP FPM and PHP CLI

No special char.

[CyberTeckyLLC]

I'm not sure if this is related, but I've included another 500 internal server error while running docker-compose.yml. The following 'docker-error.md' contains the docker-compose logs -f info.

docker-error.md

[jbtronics]

I'm not sure if this is related, but I've included another 500 internal server error while running docker-compose.yml. The following 'docker-error.md' contains the docker-compose logs -f info.

docker-error.md

This error log just tells you that Part-DB cannot reach the database server and cannnot resolve its name (probably due to some misconfiguration somewhere). Thats unrelated to this issue here