Cannot access Users page. error:"An unexpected error occurred"

shamim4s

i have also a issue when i installed clean openpanel, i cannot access Users page.
its gives error "An unexpected error occurred"
Even i cant create Plans. its says "No plan or Mysql Services is Running"

here is my server_info
http://support.openpanel.co/server_info/oKEXcDM4T9IsMv2wJTYf1l3NjccCucvjyP0mBk1APhjMs1onL5pxc1hl6S6a.txt

here is my error screenshots
screenshot 01

nosql

stefan

Hello,

Mysql Is not starting

[ERROR] [MY-012960] [InnoDB] Cannot create redo log files because data files are corrupt or the database was not shut down cleanly after creating the data files.
2024-09-24T07:41:08.552287Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2024-09-24T07:41:08.552591Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2024-09-24T07:41:08.552611Z 0 [ERROR] [MY-010119] [Server] Aborting

Remove the volume and start again:

docker stop openpanel_mysql && docker rm openpanel_mysql

docker volume rm openpanel_mysql

Them retry install with --repair flag

shamim4s

stefan
i have tried repair after delete openpanel_mysql, but its showing docker deamon is not running after few minutes.
So, i reinstall Ubuntu 22.04 again and install fresh openpanel by this command "bash <(curl -sSL https://openpanel.org)"

Still same problem. Users page showing error, Plan page showing mysql is not running.
all are same error as like those screenshots.
what to do now??

stefan

shamim4s we use the Oracle's mysql image: mysql/mysql-server - make sure that your cpu type is supported and confirm that you can run that docker image regardless of openpanel.

if you run docker with that mysql image and it keeps failing, then run these commands to remove data, and start with the official myslq image instead:

docker stop openpanel_mysql && docker rm openpanel_mysql
docker volume rm openpanel_mysql
sed -i 's/mysql\/mysql-server/mysql/g' /root/docker-compose.yml
cd /root && docker compose up -d openpanel_mysql

MixDelo

Same error is shown when mysql is down, can we improve that?

stefan

MixDelo please reopen the issue on github