Healthcheck is false - mysqld did not start correctly about snap-documentserver

[igwyd]

@chrbayer hello, i can't reproduce your mysql error. I think it's your server, permissions or a previous installations. Fist of all try clear install onlyoffice:

1. remove with purge sudo snap remove --purge onlyoffice-ds
2. install sudo snap install onlyoffice-ds

If that doesn't help, decribe more detail your setup: server version, snap version and all what you think may important.

[chrbayer]

@igwyd Thanks for your help!

Purging everything didn't help, after all settings where in place again (certs, ports and jwt stuff), I have the same problem, the mysqld has not been started and the healthcheck is correctly false...

My server is running Arch Linux with kernel 5.16.11-arch1-2, I have an mariadb server running at port 3306, port OO mysqld is set to 3307. Snap version is 2.24.4... I don't know what else could be relevant...

[totten]

2022-03-04T07:58:54.953794Z 0 [ERROR] unknown variable 'provider_bzip2=force_plus_permanent'

Came across this page while debugging a completely different app with a similar error message from another arch user. (I don't use arch or onlyoffice.)

Arch includes a config file provider_bzip2 on its own builds of MySQL/MariaDB (https://archlinux.org/packages/extra/x86_64/mariadb/files/). If you are trying to run a secondary copy of MySQL in a half-isolated environment (eg a "snap" package?), then be aware that mysql binaries often have a strong preference for reading the system-wide /etc/my.cnf.

We haven't seen this conflict on Debian/Ubuntu -- probably because Debian puts the config in a different place (/etc/mysql/my.cnf). On Debian hosts, /etc/my.cnf is always blank.

You might want to audit the calls to mysql, mysqld, mysql_install_db, or similar and see if they need an extra guard (eg --no-defaults or --defaults-file).

[chrbayer]

@totten Thank you for this hint!

@igwyd I temporally renamed the system mysql configuration files, I don't get this error any more. So this seems to be the root cause of my reported problem. It is possible to adjust the mysql configuration to eliminate the usage of the system default files completely?

[igwyd]

@chrbayer i reproduce it on Arch Linux and create issue 56453 in our private issue tracker. Thank you for report.

[igwyd]

It's fixed at: 119db53
And will be released in the next release.

[chrbayer]

That are great news, thanks :-)

[ShockwaveNN]

I'll close this issue, since fix should be released