As it says on the tin: I ubgraded from v3 to v4 and cells won’t start. in the log I’m seeing this:
2024-09-01T07:41:41.259-0600 WARN pydio.grpc.data.index.cellsdata [SQL] Server does not answer yet, will retry in 10 seconds... {"error": "Error 1045: Access denied for user 'root'@'localhost' (using password: YES)"}
2024-09-01T07:41:41.261-0600 WARN pydio.grpc.data.index.versions [SQL] Server does not answer yet, will retry in 10 seconds... {"error": "Error 1045: Access denied for user 'root'@'localhost' (using password: YES)"}
2024-09-01T07:41:41.278-0600 INFO pydio.grpc.data.sync.personal ready
2024-09-01T07:41:41.281-0600 WARN pydio.grpc.data.index.personal [SQL] Server does not answer yet, will retry in 10 seconds... {"error": "Error 1045: Access denied for user 'root'@'localhost' (using password: YES)"}
2024-09-01T07:41:41.284-0600 INFO pydio.grpc.data.sync.thumbnails ready
2024-09-01T07:41:41.285-0600 WARN pydio.grpc.data.index.thumbnails [SQL] Server does not answer yet, will retry in 10 seconds... {"error": "Error 1045: Access denied for user 'root'@'localhost' (using password: YES)"}
Pydio Cells Home Edition
Version: 4.1.0
Built: 31 Jan 23 07:03 +0000
Git commit: d7276aacaea3f7c35ece7c893f4098b89bdc5d90
OS/Arch: linux/amd64
Go version: go1.19.4
OS: Debian GNU/Linux 10 (buster) x86_64
mysql Ver 15.1 Distrib 10.3.39-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
you have configured the service to run with a specific user (usually the pydio ) user, and you tried to start the server manually from the command line using the wrong user e.G.: root@host:~$ cells start
…
Or something similar.
This kind of errors should not be bound to the upgrade per say.
If this is not the issue, we need more info to be able to help.
That said, another warning:
you should really take the latest patch from the major when you update (as we write this the v4.4.4 ), we regularly fix things and update third party libraries to avoid bugs and security issues. So if you already took the step to upgrade to v4, take the latest one.
I’m running cells manually from CLI to try to isolate the problem… That said, I’m logged in with the pydio user (the user configured to run cells). Also, I did have to force change the password for the db because the documented password did not work. I also ran cells configure (again from the pydio account) to set the password… same errors.
So I have to assume that’s the source of my woes. So if cells configure (ran as the pydio user) doesn’t update the password… where do I need to update the sql password for cells?
Alright, I sorted the sql login issue (located the password change in bash history)
Still not starting, now THIS is in the log:
|2024-09-03T06:19:48.006-0600|INFO|pydio.grpc.oauth|Detected HydraJwkMigration - We are migrating from a v3 version - You may be disconnected after that!
|2024-09-03T06:19:48.010-0600|ERROR|pydio.grpc.oauth|Stopping all migrations as some tables may have collations differing from the database defaults. This may break migrations and foreign keys.|
|2024-09-03T06:19:58.006-0600|INFO|pydio.grpc.oauth|Detected HydraJwkMigration - We are migrating from a v3 version - You may be disconnected after that!|
|2024-09-03T06:19:58.009-0600|ERROR|pydio.grpc.oauth|Stopping all migrations as some tables may have collations differing from the database defaults. This may break migrations and foreign keys.|
|2024-09-03T06:20:08.005-0600|INFO|pydio.grpc.oauth|Detected HydraJwkMigration - We are migrating from a v3 version - You may be disconnected after that!|
|2024-09-03T06:20:08.009-0600|ERROR|pydio.grpc.oauth|Stopping all migrations as some tables may have collations differing from the database defaults. This may break migrations and foreign keys.|
|2024-09-03T06:20:16.909-0600|INFO|pydio.grpc.tasks|Run Job flush-mailer-queue on timer event Iso8601Schedule:R/2012-06-04T19:25:16.828696-07:00/PT5M|
|2024-09-03T06:20:18.006-0600|INFO|pydio.grpc.oauth|Detected HydraJwkMigration - We are migrating from a v3 version - You may be disconnected after that!|
|2024-09-03T06:20:18.009-0600|ERROR|pydio.grpc.oauth|Stopping all migrations as some tables may have collations differing from the database defaults. This may break migrations and foreign keys.|
|2024-09-03T06:20:28.005-0600|INFO|pydio.grpc.oauth|Detected HydraJwkMigration - We are migrating from a v3 version - You may be disconnected after that!|
|2024-09-03T06:20:28.009-0600|ERROR|pydio.grpc.oauth|Stopping all migrations as some tables may have collations differing from the database defaults. This may break migrations and foreign keys.|
|2024-09-03T06:20:38.005-0600|INFO|pydio.grpc.oauth|Detected HydraJwkMigration - We are migrating from a v3 version - You may be disconnected after that!|
|2024-09-03T06:20:38.009-0600|ERROR|pydio.grpc.oauth|Stopping all migrations as some tables may have collations differing from the database defaults. This may break migrations and foreign keys.|
|2024-09-03T06:20:48.006-0600|INFO|pydio.grpc.oauth|Detected HydraJwkMigration - We are migrating from a v3 version - You may be disconnected after that!|
|2024-09-03T06:20:48.009-0600|ERROR|pydio.grpc.oauth|Stopping all migrations as some tables may have collations differing from the database defaults. This may break migrations and foreign keys.|
|2024-09-03T06:20:58.006-0600|INFO|pydio.grpc.oauth|Detected HydraJwkMigration - We are migrating from a v3 version - You may be disconnected after that!|
|2024-09-03T06:20:58.010-0600|ERROR|pydio.grpc.oauth|Stopping all migrations as some tables may have collations differing from the database defaults. This may break migrations and foreign keys.|
pretty much just that.
I already followed the instructions here to no avail.
After about 5 or 10 minutes of just the error above cells just closes.
This looks like a common issue when upgrading from v3 to v4 - most probably resulting from a export/import of a DB dump when maintaining your cell Server.
You have some more explanations and a strategy to fix this in the v4 release note: