mysql not responding (with vaultwarden installed)
-
@nebulon thx
but this does not help.more infos:
2023-03-28T10:00:08.374631Z 8 [ERROR] [MY-012153] [InnoDB] Trying to access page number 1667445293 in space 1781, space name aea049681ed9c3bb/users, which is outside the tablespace bounds. Byte offset 0, len 16384, i/o type read. If you get this error at mysqld startup, please check that your my.cnf matches the ibdata files that you have in the MySQL server. 2023-03-28T10:00:08.374717Z 8 [ERROR] [MY-012154] [InnoDB] Server exits. 2023-03-28T10:00:08.374736Z 8 [ERROR] [MY-013183] [InnoDB] Assertion failure: fil0fil.cc:7531 thread 140018124093184@Grienauer actually this should be the same issue, have you tried my suggested solution? As @opensourced explained, one can also of course remove the table store and restore all apps.
-
@nebulon yes, i have vaultwarden installed...
-
This same thing just happened to my box as well. I have vaultwarden installed. My bookstack instance crashed as well.
*Edit
I restored from a backup and I was able to get everything working - vault warden is on v1.11.0 now and i disabled updates for it after reading this thread
-
I have revoked vaultwarden package update by now, as it is strongly related to this issue. Still not sure how a mysql client can cause such issues for the database server!
-
Crap, I literally just pushed the Update button on my bitwarden. Is it a given that something will go wrong? Should I just restore now to the previous bitwarden before things start breaking?
-
@scooke I think ou should restore to the version from yesterday, to prevent problems and deactivate auto update for now. just in case and follow this thread.
-
It's not a given that mysql crashes. The latest vaultwarden works on my cloudron as well. It seems to happen only on some servers but we got atleast 5-10 support tickets so far with the same mysql crash.
I think we have to narrow it down further. Maybe kernel/ubuntu version related as well.
-
Since 7.4 is out and also a new vaultwarden, I have released a package for manual updates on 7.4 today. Maybe there is someone who was affected by the mysql issue, who is brave enough to test this.
If you do manually update and your Cloudron breaks again, let us know, so we fix it up again and can revoke that vaultwarden version.
The reason to pull you in for help here is, that we had no Cloudron where we were able to reproduce this for debugging.
-
Since 7.4 is out and also a new vaultwarden, I have released a package for manual updates on 7.4 today. Maybe there is someone who was affected by the mysql issue, who is brave enough to test this.
If you do manually update and your Cloudron breaks again, let us know, so we fix it up again and can revoke that vaultwarden version.
The reason to pull you in for help here is, that we had no Cloudron where we were able to reproduce this for debugging.
-
@Neluser The mysql service for Board was getting an error.
Otherwise, all applications worked. I tried downloading some of the logs. But I did not see that somewhere it would be written about the problem. -
@Neluser so you have manually updated vaultwarden and the mysql service now keeps crashing/restarting?
If this is the case and you want us to fix this, please enable remote SSH support and send a mail to support@cloudron.io with your Cloudron IP.
-
G girish referenced this topic on
