Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[wordpress] wordpress does not start after update #20609

Closed
2 tasks done
qraynaud opened this issue Apr 11, 2024 · 5 comments
Closed
2 tasks done

[wordpress] wordpress does not start after update #20609

qraynaud opened this issue Apr 11, 2024 · 5 comments
Labels
bug Something isn't working
Milestone
backlog

Comments

@qraynaud
Copy link

qraynaud commented Apr 11, 2024 •
edited by PrivatePuffin
Loading

chart Name

wordpress

Operating System

TrueNAS SCALE 23.10.1

Deployment Method

TrueNAS SCALE charts

Chart Version

7.15.9

Kubernetes Events

2024-04-11 18:51:04
Back-off restarting failed container melaniegohin-wordpress in pod melaniegohin-wordpress-6db88bdc94-bfchp_ix-melaniegohin(04263d6c-1a5e-413f-a0bd-e8df07c31e5f)
2024-04-11 18:41:12
Startup probe failed: dial tcp 172.16.2.65:10591: connect: connection refused
2024-04-11 18:41:02
Created container melaniegohin-wordpress
2024-04-11 18:41:02
Started container melaniegohin-wordpress

chartlication Logs

wordpress container :
========
2024-04-11 18:52:08.585388+02:00�[38;5;6mwordpress �[38;5;5m18:52:08.58 �[0m�[38;5;2mINFO �[0m ==> 
2024-04-11 18:52:08.586236+02:00�[38;5;6mwordpress �[38;5;5m18:52:08.58 �[0m�[38;5;2mINFO �[0m ==> �[1mWelcome to the Bitnami wordpress container�[0m
2024-04-11 18:52:08.586895+02:00�[38;5;6mwordpress �[38;5;5m18:52:08.58 �[0m�[38;5;2mINFO �[0m ==> Subscribe to project updates by watching �[1mhttps://github.com/bitnami/containers�[0m
2024-04-11 18:52:08.587667+02:00�[38;5;6mwordpress �[38;5;5m18:52:08.58 �[0m�[38;5;2mINFO �[0m ==> Submit issues and feature requests at �[1mhttps://github.com/bitnami/containers/issues�[0m
2024-04-11 18:52:08.588445+02:00�[38;5;6mwordpress �[38;5;5m18:52:08.58 �[0m�[38;5;2mINFO �[0m ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit �[1mhttps://bitnami.com/enterprise�[0m
2024-04-11 18:52:08.589088+02:00�[38;5;6mwordpress �[38;5;5m18:52:08.58 �[0m�[38;5;2mINFO �[0m ==> 
2024-04-11 18:52:08.590751+02:00�[38;5;6mwordpress �[38;5;5m18:52:08.59 �[0m�[38;5;2mINFO �[0m ==> ** Starting WordPress setup **
2024-04-11 18:52:08.604574+02:00�[38;5;6mwordpress �[38;5;5m18:52:08.60 �[0m�[38;5;2mINFO �[0m ==> Generating sample certificates
2024-04-11 18:52:09.515742+02:00Certificate request self-signature ok
2024-04-11 18:52:09.515770+02:00subject=CN = example.com
2024-04-11 18:52:10.703103+02:00realpath: /bitnami/apache/conf: No such file or directory
2024-04-11 18:52:10.704365+02:00�[38;5;6mwordpress �[38;5;5m18:52:10.70 �[0m�[38;5;2mINFO �[0m ==> Configuring the HTTP port
2024-04-11 18:52:12.229144+02:00�[38;5;6mwordpress �[38;5;5m18:52:12.22 �[0m�[38;5;2mINFO �[0m ==> Configuring Apache ServerTokens directive
2024-04-11 18:52:12.239948+02:00�[38;5;6mwordpress �[38;5;5m18:52:12.23 �[0m�[38;5;2mINFO �[0m ==> Configuring PHP options
2024-04-11 18:52:12.243555+02:00�[38;5;6mwordpress �[38;5;5m18:52:12.24 �[0m�[38;5;2mINFO �[0m ==> Setting PHP opcache.enable option
2024-04-11 18:52:13.047346+02:00�[38;5;6mwordpress �[38;5;5m18:52:13.04 �[0m�[38;5;2mINFO �[0m ==> Setting PHP expose_php option
2024-04-11 18:52:13.052679+02:00�[38;5;6mwordpress �[38;5;5m18:52:13.05 �[0m�[38;5;2mINFO �[0m ==> Setting PHP memory_limit option
2024-04-11 18:52:13.057786+02:00�[38;5;6mwordpress �[38;5;5m18:52:13.05 �[0m�[38;5;2mINFO �[0m ==> Setting PHP output_buffering option
2024-04-11 18:52:13.068446+02:00�[38;5;6mwordpress �[38;5;5m18:52:13.06 �[0m�[38;5;2mINFO �[0m ==> Validating settings in MYSQL_CLIENT_* env vars
2024-04-11 18:52:15.684663+02:00�[38;5;6mwordpress �[38;5;5m18:52:15.68 �[0m�[38;5;2mINFO �[0m ==> Restoring persisted WordPress installation
2024-04-11 18:52:16.634723+02:00�[38;5;6mwordpress �[38;5;5m18:52:16.63 �[0m�[38;5;2mINFO �[0m ==> Trying to connect to the database server
==> Failed to connect to the database server

mariadb container :
========
2024-04-11 18:45:58.062700+02:00�[38;5;6mmariadb �[38;5;5m16:45:58.06 �[0m�[38;5;2mINFO �[0m ==> 
2024-04-11 18:45:58.063650+02:00�[38;5;6mmariadb �[38;5;5m16:45:58.06 �[0m�[38;5;2mINFO �[0m ==> �[1mWelcome to the Bitnami mariadb container�[0m
2024-04-11 18:45:58.064509+02:00�[38;5;6mmariadb �[38;5;5m16:45:58.06 �[0m�[38;5;2mINFO �[0m ==> Subscribe to project updates by watching �[1mhttps://github.com/bitnami/containers�[0m
2024-04-11 18:45:58.065246+02:00�[38;5;6mmariadb �[38;5;5m16:45:58.06 �[0m�[38;5;2mINFO �[0m ==> Submit issues and feature requests at �[1mhttps://github.com/bitnami/containers/issues�[0m
2024-04-11 18:45:58.066098+02:00�[38;5;6mmariadb �[38;5;5m16:45:58.06 �[0m�[38;5;2mINFO �[0m ==> Upgrade to Tanzu Application Catalog for production environments to access custom-configured and pre-packaged software components. Gain enhanced features, including Software Bill of Materials (SBOM), CVE scan result reports, and VEX documents. To learn more, visit �[1mhttps://bitnami.com/enterprise�[0m
2024-04-11 18:45:58.066963+02:00�[38;5;6mmariadb �[38;5;5m16:45:58.06 �[0m�[38;5;2mINFO �[0m ==> 
2024-04-11 18:45:58.068878+02:00�[38;5;6mmariadb �[38;5;5m16:45:58.06 �[0m�[38;5;2mINFO �[0m ==> ** Starting MariaDB setup **
2024-04-11 18:45:58.077419+02:00�[38;5;6mmariadb �[38;5;5m16:45:58.07 �[0m�[38;5;2mINFO �[0m ==> Validating settings in MYSQL_*/MARIADB_* env vars
2024-04-11 18:45:58.079740+02:00�[38;5;6mmariadb �[38;5;5m16:45:58.07 �[0m�[38;5;2mINFO �[0m ==> Initializing mariadb database
2024-04-11 18:45:58.084681+02:00�[38;5;6mmariadb �[38;5;5m16:45:58.08 �[0m�[38;5;2mINFO �[0m ==> Updating 'my.cnf' with custom configuration
2024-04-11 18:45:58.087287+02:00�[38;5;6mmariadb �[38;5;5m16:45:58.08 �[0m�[38;5;2mINFO �[0m ==> Setting user option
2024-04-11 18:45:59.217162+02:00�[38;5;6mmariadb �[38;5;5m16:45:59.21 �[0m�[38;5;2mINFO �[0m ==> Setting slow_query_log option
2024-04-11 18:45:59.227987+02:00�[38;5;6mmariadb �[38;5;5m16:45:59.22 �[0m�[38;5;2mINFO �[0m ==> Setting long_query_time option
2024-04-11 18:45:59.239273+02:00�[38;5;6mmariadb �[38;5;5m16:45:59.23 �[0m�[38;5;2mINFO �[0m ==> Using persisted data
2024-04-11 18:45:59.244533+02:00/opt/bitnami/mariadb/bin/mysql: Deprecated program name. It will be removed in a future release, use '/opt/bitnami/mariadb/bin/mariadb' instead
2024-04-11 18:45:59.248192+02:00/opt/bitnami/mariadb/bin/mysql: Deprecated program name. It will be removed in a future release, use '/opt/bitnami/mariadb/bin/mariadb' instead
2024-04-11 18:45:59.251325+02:00/opt/bitnami/mariadb/bin/mysql: Deprecated program name. It will be removed in a future release, use '/opt/bitnami/mariadb/bin/mariadb' instead
2024-04-11 18:45:59.252977+02:00�[38;5;6mmariadb �[38;5;5m16:45:59.25 �[0m�[38;5;2mINFO �[0m ==> Running mysql_upgrade
2024-04-11 18:45:59.255723+02:00�[38;5;6mmariadb �[38;5;5m16:45:59.25 �[0m�[38;5;2mINFO �[0m ==> Starting mariadb in background
2024-04-11 18:45:59.279374+02:002024-04-11 16:45:59 0 [Note] Starting MariaDB 11.3.2-MariaDB source revision 068a6819eb63bcb01fdfa037c9bf3bf63c33ee42 as process 66
2024-04-11 18:45:59.299850+02:002024-04-11 16:45:59 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2024-04-11 18:45:59.300769+02:002024-04-11 16:45:59 0 [Note] InnoDB: Number of transaction pools: 1
2024-04-11 18:45:59.300779+02:002024-04-11 16:45:59 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-04-11 18:45:59.300792+02:002024-04-11 16:45:59 0 [Note] mysqld: O_TMPFILE is not supported on /opt/bitnami/mariadb/tmp (disabling future attempts)
2024-04-11 18:45:59.385764+02:002024-04-11 16:45:59 0 [Note] InnoDB: Using Linux native AIO
2024-04-11 18:45:59.386078+02:002024-04-11 16:45:59 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-04-11 18:45:59.397822+02:002024-04-11 16:45:59 0 [Note] InnoDB: Completed initialization of buffer pool
2024-04-11 18:45:59.398436+02:002024-04-11 16:45:59 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2024-04-11 18:45:59.406608+02:002024-04-11 16:45:59 0 [Note] InnoDB: End of log at LSN=35374034
2024-04-11 18:45:59.407808+02:002024-04-11 16:45:59 0 [Note] InnoDB: Opened 3 undo tablespaces
2024-04-11 18:45:59.407827+02:002024-04-11 16:45:59 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active.
2024-04-11 18:45:59.408029+02:002024-04-11 16:45:59 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2024-04-11 18:45:59.408047+02:002024-04-11 16:45:59 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2024-04-11 18:45:59.408272+02:002024-04-11 16:45:59 0 [Note] InnoDB: log sequence number 35374034; transaction id 24781
2024-04-11 18:45:59.408297+02:002024-04-11 16:45:59 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-04-11 18:45:59.408308+02:002024-04-11 16:45:59 0 [Note] Plugin 'wsrep-provider' is disabled.
2024-04-11 18:45:59.408339+02:002024-04-11 16:45:59 0 [Note] InnoDB: Loading buffer pool(s) from /bitnami/mariadb/data/ib_buffer_pool
2024-04-11 18:45:59.411216+02:002024-04-11 16:45:59 0 [Note] InnoDB: Buffer pool(s) load completed at 240411 16:45:59
2024-04-11 18:45:59.433207+02:002024-04-11 16:45:59 0 [Note] Server socket created on IP: '127.0.0.1'.
2024-04-11 18:45:59.433934+02:002024-04-11 16:45:59 0 [Warning] 'proxies_priv' entry '@% root@melaniegohin-mariadb-77f857c9b6-xqsqp' ignored in --skip-name-resolve mode.
2024-04-11 18:45:59.466267+02:002024-04-11 16:45:59 0 [Note] mysqld: Event Scheduler: Loaded 0 events
2024-04-11 18:45:59.488426+02:002024-04-11 16:45:59 3 [Warning] 'proxies_priv' entry '@% root@melaniegohin-mariadb-77f857c9b6-xqsqp' ignored in --skip-name-resolve mode.
2024-04-11 18:45:59.488458+02:002024-04-11 16:45:59 0 [Note] /opt/bitnami/mariadb/sbin/mysqld: ready for connections.
2024-04-11 18:45:59.488476+02:00Version: '11.3.2-MariaDB'  socket: '/opt/bitnami/mariadb/tmp/mysql.sock'  port: 3306  Source distribution
2024-04-11 18:46:01.273875+02:00find: '/docker-entrypoint-startdb.d/': No such file or directory
2024-04-11 18:46:01.275506+02:00�[38;5;6mmariadb �[38;5;5m16:46:01.27 �[0m�[38;5;2mINFO �[0m ==> Stopping mariadb
2024-04-11 18:46:01.276162+02:002024-04-11 16:46:01 0 [Note] /opt/bitnami/mariadb/sbin/mysqld (initiated by: unknown): Normal shutdown
2024-04-11 18:46:01.276318+02:002024-04-11 16:46:01 0 [Note] InnoDB: FTS optimize thread exiting.
2024-04-11 18:46:01.332951+02:002024-04-11 16:46:01 0 [Note] InnoDB: Starting shutdown...
2024-04-11 18:46:01.332974+02:002024-04-11 16:46:01 0 [Note] InnoDB: Dumping buffer pool(s) to /bitnami/mariadb/data/ib_buffer_pool
2024-04-11 18:46:01.333193+02:002024-04-11 16:46:01 0 [Note] InnoDB: Buffer pool(s) dump completed at 240411 16:46:01
2024-04-11 18:46:01.585192+02:002024-04-11 16:46:01 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2024-04-11 18:46:01.585214+02:002024-04-11 16:46:01 0 [Note] InnoDB: Shutdown completed; log sequence number 35374034; transaction id 24782
2024-04-11 18:46:01.630930+02:002024-04-11 16:46:01 0 [Note] /opt/bitnami/mariadb/sbin/mysqld: Shutdown complete
2024-04-11 18:46:01.630968+02:002024-04-11T18:46:01.630968960+02:00
2024-04-11 18:46:02.284283+02:00�[38;5;6mmariadb �[38;5;5m16:46:02.28 �[0m�[38;5;2mINFO �[0m ==> ** MariaDB setup finished! **
2024-04-11 18:46:02.284313+02:002024-04-11T18:46:02.284313062+02:00
2024-04-11 18:46:02.305770+02:00�[38;5;6mmariadb �[38;5;5m16:46:02.30 �[0m�[38;5;2mINFO �[0m ==> ** Starting MariaDB **
2024-04-11 18:46:02.311360+02:00/opt/bitnami/mariadb/sbin/mysqld: Deprecated program name. It will be removed in a future release, use '/opt/bitnami/mariadb/sbin/mariadbd' instead
2024-04-11 18:46:02.328238+02:002024-04-11 16:46:02 0 [Note] Starting MariaDB 11.3.2-MariaDB source revision 068a6819eb63bcb01fdfa037c9bf3bf63c33ee42 as process 1
2024-04-11 18:46:02.349135+02:002024-04-11 16:46:02 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2024-04-11 18:46:02.350379+02:002024-04-11 16:46:02 0 [Note] InnoDB: Number of transaction pools: 1
2024-04-11 18:46:02.350407+02:002024-04-11 16:46:02 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-04-11 18:46:02.350424+02:002024-04-11 16:46:02 0 [Note] mysqld: O_TMPFILE is not supported on /opt/bitnami/mariadb/tmp (disabling future attempts)
2024-04-11 18:46:02.429877+02:002024-04-11 16:46:02 0 [Note] InnoDB: Using Linux native AIO
2024-04-11 18:46:02.430212+02:002024-04-11 16:46:02 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-04-11 18:46:02.440928+02:002024-04-11 16:46:02 0 [Note] InnoDB: Completed initialization of buffer pool
2024-04-11 18:46:02.441607+02:002024-04-11 16:46:02 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2024-04-11 18:46:02.446685+02:002024-04-11 16:46:02 0 [Note] InnoDB: End of log at LSN=35374034
2024-04-11 18:46:02.449025+02:002024-04-11 16:46:02 0 [Note] InnoDB: Opened 3 undo tablespaces
2024-04-11 18:46:02.449051+02:002024-04-11 16:46:02 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active.
2024-04-11 18:46:02.449266+02:002024-04-11 16:46:02 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2024-04-11 18:46:02.449283+02:002024-04-11 16:46:02 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2024-04-11 18:46:02.450319+02:002024-04-11 16:46:02 0 [Note] InnoDB: log sequence number 35374034; transaction id 24781
2024-04-11 18:46:02.450402+02:002024-04-11 16:46:02 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-04-11 18:46:02.450447+02:002024-04-11 16:46:02 0 [Note] Plugin 'wsrep-provider' is disabled.
2024-04-11 18:46:02.450463+02:002024-04-11 16:46:02 0 [Note] InnoDB: Loading buffer pool(s) from /bitnami/mariadb/data/ib_buffer_pool
2024-04-11 18:46:02.455239+02:002024-04-11 16:46:02 0 [Note] InnoDB: Buffer pool(s) load completed at 240411 16:46:02
2024-04-11 18:46:02.475572+02:002024-04-11 16:46:02 0 [Note] Server socket created on IP: '0.0.0.0'.
2024-04-11 18:46:02.476308+02:002024-04-11 16:46:02 0 [Warning] 'proxies_priv' entry '@% root@melaniegohin-mariadb-77f857c9b6-xqsqp' ignored in --skip-name-resolve mode.
2024-04-11 18:46:02.476916+02:002024-04-11 16:46:02 0 [Note] mysqld: Event Scheduler: Loaded 0 events
2024-04-11 18:46:02.500374+02:002024-04-11 16:46:02 3 [Warning] 'proxies_priv' entry '@% root@melaniegohin-mariadb-77f857c9b6-xqsqp' ignored in --skip-name-resolve mode.
2024-04-11 18:46:02.500407+02:002024-04-11 16:46:02 0 [Note] /opt/bitnami/mariadb/sbin/mysqld: ready for connections.
2024-04-11 18:46:02.500415+02:00Version: '11.3.2-MariaDB'  socket: '/opt/bitnami/mariadb/tmp/mysql.sock'  port: 3306  Source distribution
2024-04-11 18:46:11.688944+02:002024-04-11 16:46:11 8 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:46:16.696044+02:002024-04-11 16:46:16 9 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:47:16.028552+02:002024-04-11 16:47:16 34 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:47:21.034995+02:002024-04-11 16:47:21 39 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:47:26.042394+02:002024-04-11 16:47:26 41 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:47:31.048596+02:002024-04-11 16:47:31 46 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:47:36.055939+02:002024-04-11 16:47:36 48 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:47:41.063256+02:002024-04-11 16:47:41 53 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:47:46.071175+02:002024-04-11 16:47:46 54 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:47:51.079037+02:002024-04-11 16:47:51 59 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:47:56.087409+02:002024-04-11 16:47:56 60 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:48:01.094711+02:002024-04-11 16:48:01 65 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:48:06.102313+02:002024-04-11 16:48:06 66 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:48:11.110261+02:002024-04-11 16:48:11 71 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:48:27.147620+02:002024-04-11 16:48:27 76 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:48:32.154953+02:002024-04-11 16:48:32 82 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:48:37.161517+02:002024-04-11 16:48:37 83 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:48:42.167903+02:002024-04-11 16:48:42 88 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:48:47.176125+02:002024-04-11 16:48:47 89 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:48:52.183065+02:002024-04-11 16:48:52 94 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:48:57.191234+02:002024-04-11 16:48:57 95 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:49:02.199113+02:002024-04-11 16:49:02 100 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:49:07.205833+02:002024-04-11 16:49:07 101 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:49:12.215144+02:002024-04-11 16:49:12 106 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:49:17.223130+02:002024-04-11 16:49:17 107 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:49:22.229990+02:002024-04-11 16:49:22 112 [Warning] Access denied for user 'wordpress'@'172.16.2.65' (using password: YES)
2024-04-11 18:51:58.392826+02:002024-04-11 16:51:58 173 [Warning] Access denied for user 'wordpress'@'localhost' (using password: YES)
2024-04-11 18:52:16.211999+02:002024-04-11 16:52:16 182 [Warning] Access denied for user 'wordpress'@'localhost' (using password: YES)

Describe the bug

To Reproduce

Update from old version.

Expected Behavior

It should start.

Screenshots

N/A

Additional Context

I connected to the wordpress container using a shell and found out its config is correct. No problem there.
Then I connected to the mariadb container and found the following content in the /init/passinit.sql file:

ALTER USER root@'%' IDENTIFIED VIA mysql_native_password USING PASSWORD("PLACEHOLDERROOTPASSWORD");
ALTER USER wordpress@'%' IDENTIFIED VIA mysql_native_password USING PASSWORD("PLACEHOLDERPASSWORD");
FLUSH PRIVILEGES;

So I tried using PLACEHOLDERPASSWORD to connect to mariadb with root and it worked. I used this access to alter the wordpress password to the one found in the wp_config.ini of the wordpress container. If I do not restart my pods, it’s working properly.

Devnote

Wordpress does not contain code to correctly process database password changes

I've read and agree with the following

  • I've checked all open and closed issues and my issue is not there.
  • I've prefixed my issue title with [Chart-Name]
@qraynaud qraynaud added the bug Something isn't working label Apr 11, 2024
@PrivatePuffin
Copy link
Member

Not a common issue, wordpress is not correctly setup to deal with database password changes.

I'll adapt the issue to reflect this

@PrivatePuffin PrivatePuffin added this to the backlog milestone Apr 11, 2024
@PrivatePuffin
Copy link
Member

PrivatePuffin commented Apr 11, 2024 •
edited
Loading

Likely not getting maintainer attention for the next few weeks. -> backlog
Adaptation of wp_config.ini should be permanent though.

@newton-per-sqm
Copy link

I'm suffering the same issue. A rollback is not helping out, the issue remains. Because of that, my current WordPress instance (used more or less productively in a private environment) is down, that's bad.

Could you explain me in more detail how to fix this manually, maybe by altering the wp_config.ini from the PVC?

@PrivatePuffin
Copy link
Member

PrivatePuffin commented Apr 11, 2024 •
edited
Loading

I'm suffering the same issue. A rollback is not helping out, the issue remains. Because of that, my current WordPress instance (used more or less productively in a private environment) is down, that's bad.

please don't make +1 comments on issues.
Rollback will not work.

Could you explain me in more detail how to fix this manually, maybe by altering the wp_config.ini from the PVC?

He literally wrote that above.
If you want to discuss mitigation steps or discuss in detail, please use the discord.
The bugtracker is only a dev-tool for us.

As the issue and solution is clear, we don't need more information at this point.
So i'm locking this.

@truecharts truecharts locked and limited conversation to collaborators Apr 11, 2024
@alfi0812
Copy link
Collaborator

alfi0812 commented Oct 4, 2024

Closing as SCALE isnt a supported platform any longer. Feel free to open a new Issue if the issue persists on one of the currently supported platforms.

@alfi0812 alfi0812 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
backlog
Development

No branches or pull requests
4 participants
@qraynaud @PrivatePuffin @alfi0812 @newton-per-sqm