Unable to change dbhost using occ config:system:set if existing dbhost isn't functioning
#40904
Closed
5 of 8 tasks
Labels
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
27-feedback
bug
feature: occ
Comments
gabriel-v
added
0. Needs triage
gabriel-v
added a commit
to gabriel-v/docker
that referenced
this issue
Oct 13, 2023
closes nextcloud/server#40904 Signed-off-by: Gabriel Vîjială <gabriel.vijiala@gmail.com>
|
Most of this is about the Docker image, not server, but I'll keep open because this part is in scope:
However I don't think there's going to be much hope of making that work... |
joshtrichards
changed the title
dbhost using occ config:system:set
joshtrichards
changed the title
dbhost using occ config:system:setdbhost using occ config:system:set if existing dbhost isn't functioning
8 tasks
|
Duplicate of #44924 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
In the "Auto configuration via environment variables" section of the Docker Readme, one can use
MYSQL_HOSTto set the database connection info, andNEXTCLUOD_UPDATE=1to automate installation.The problem is when we want to change that MySQL_HOST into something else. We change the environment variable, restart the container, and we get this error:
SQLSTATE[HY000] [2006] MySQL server has gone away.We investigate and find that, while the autoconfig.php reads environment variables, the config.php is hard-coded at installation time with the actual IP/PORTS:
OK, let's try to use the CLI command to edit that hard-coded file, like this:
We then get this error again:
SQLSTATE[HY000] [2006] MySQL server has gone awaySo the
config:system:setcan't fix thedbhostvariable without trying to connect to the old, faulty dbhost!That means the only option is either to manually edit the config file, to overwrite it with
sed, or to overwrite it entirely (which sounds complex because it has to keep all the generated secrets already present in it).Steps to reproduce
Trivial Docker-compose example that renames "db" into "db2": https://gist.github.com/gabriel-v/c6e5a1e18686f39649546c1161fadd64
Expected behavior
Nextcloud starts successfully with the new DB connection info
Installation method
Community Docker image
Nextcloud Server version
confirmed on 26, 27, latest docker images
Operating system
Debian/Ubuntu
PHP engine version
None
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
{ "system": { "htaccess.RewriteBase": "\/", "memcache.local": "\\OC\\Memcache\\APCu", "apps_paths": [ { "path": "\/var\/www\/html\/apps", "url": "\/apps", "writable": false }, { "path": "\/var\/www\/html\/custom_apps", "url": "\/custom_apps", "writable": true } ], "overwriteprotocol": "http", "objectstore": { "class": "\\OC\\Files\\ObjectStore\\S3", "arguments": { "bucket": "nextcloud27", "region": "optional", "hostname": "10.66.60.1", "port": "9970", "objectPrefix": "urn:oid:", "autocreate": true, "use_ssl": false, "use_path_style": true, "legacy_auth": false, "key": "***REMOVED SENSITIVE VALUE***", "secret": "***REMOVED SENSITIVE VALUE***" } }, "passwordsalt": "***REMOVED SENSITIVE VALUE***", "secret": "***REMOVED SENSITIVE VALUE***", "trusted_domains": [ "localhost", "10.66.60.1", "ZZZZZZZZZZZZZZZZZZZ.ZZZZZZZZZ.ZZZ" ], "datadirectory": "***REMOVED SENSITIVE VALUE***", "dbtype": "mysql", "version": "27.0.1.2", "overwrite.cli.url": "http:\/\/localhost", "dbname": "***REMOVED SENSITIVE VALUE***", "dbhost": "***REMOVED SENSITIVE VALUE***", "dbport": "", "dbtableprefix": "oc_", "mysql.utf8mb4": true, "dbuser": "***REMOVED SENSITIVE VALUE***", "dbpassword": "***REMOVED SENSITIVE VALUE***", "installed": true, "instanceid": "***REMOVED SENSITIVE VALUE***", "social_login_auto_redirect": "true", "loglevel": 2, "maintenance": false } }List of activated Apps
Nextcloud Signing status
server doesn't startNextcloud Logs
Additional info
Found on the interwebs:
Questions
php occ config:system:set dbhost --value 1.2.3.4be made not to connect to the previous (inaccessible) dbhost?Is there some kind of override config file we can put in the config dir, to override only the dbhost value with the actual envrionment variable set on the container?Work-Around
https://github.com/nextcloud/helm/tree/main/charts/nextcloud#multiple-configphp-file
Create file
config/dbhostoverride.config.phpwith content:And add keys to this file for each value expected to change (dbport, passwords, etc.)
Suggestions
This causes a great deal of confusion: one expects the environment variable to be the source of truth for configuring the image. Inspecting the
autoconfig.phpfile also does not help, because it's not obvious the$AUTOCONFIGvar is used only at install time, while the$CONFIGvar is used at run time.The text was updated successfully, but these errors were encountered: