[bitnami/suitecrm] Suitecrm upgrade error

[nidhin077]

Name and Version

bitnami/suitecrm:8.5.1

What architecture are you using?

None

What steps will reproduce the bug?

Try to upgrade the suitcrm from 7.11 to 8.5.1

What is the expected behavior?

With the right configuration, Suitcrm will start.

What do you see instead?

Stuck at the point

suitecrm 06:32:03.83 INFO  ==> ** Starting Apache **
[Thu Apr 25 06:32:03.953560 2024] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.58 (Unix) OpenSSL/3.0.11 configured -- resuming normal operations
[Thu Apr 25 06:32:03.953617 2024] [core:notice] [pid 1] AH00094: Command line: '/opt/bitnami/apache/bin/httpd -f /opt/bitnami/apache/conf/httpd.conf -D FOREGROUND'

Additional information

Hi,

In an attempt to update my suitecrm version from 7.11.8 to 8.5.1, I have removed the volume and downloaded the most recent image; nevertheless, the container becomes stuck at this point when it starts.

Certificate request self-signature ok
subject=CN = example.com
realpath: /bitnami/apache/conf: No such file or directory
suitecrm 06:31:26.65 INFO  ==> Configuring Apache ServerTokens directive
suitecrm 06:31:26.70 INFO  ==> Configuring PHP options
suitecrm 06:31:26.71 INFO  ==> Setting PHP expose_php option
suitecrm 06:31:26.72 INFO  ==> Setting PHP output_buffering option
suitecrm 06:31:26.76 INFO  ==> Validating settings in MYSQL_CLIENT_* env vars
suitecrm 06:31:26.88 INFO  ==> Ensuring SuiteCRM directories exist
suitecrm 06:31:26.90 INFO  ==> Trying to connect to the database server
suitecrm 06:31:26.93 INFO  ==> Running setup wizard
suitecrm 06:31:47.62 INFO  ==> Persisting SuiteCRM installation
suitecrm 06:32:03.79 INFO  ==> ** SuiteCRM setup finished! **

suitecrm 06:32:03.81 INFO  ==> ** Starting cron **
suitecrm 06:32:03.83 INFO  ==> ** Starting Apache **
[Thu Apr 25 06:32:03.953560 2024] [mpm_prefork:notice] [pid 1] AH00163: Apache/2.4.58 (Unix) OpenSSL/3.0.11 configured -- resuming normal operations
[Thu Apr 25 06:32:03.953617 2024] [core:notice] [pid 1] AH00094: Command line: '/opt/bitnami/apache/bin/httpd -f /opt/bitnami/apache/conf/httpd.conf -D FOREGROUND'

Please check this issue and let me know the fix for the same.

[javsalgar]

Hi!

In principle it seems that the Apache daemon has started without issues, do you find any problem accessing the UI?

[nidhin077]

@javsalgar Yes, the UI getting 503 error message

[javsalgar]

Note that you are trying to upgrade between major versions, did you check the upstream documentation to see how the upgrade process works?

[nidhin077]

@javsalgar Normally, when we upgrade service in a container, we first make a backup volume that includes the database, then we modify the docker-compos file to reflect the new version, and last we rebuild the container. Here, we take the same actions, but we encounter the previously noted issue.
Should you find any errors in the steps, kindly share the steps that need to be updated.

Current using image 
 "image": "bitnami/mariadb:10.3"
  "image": "bitnami/suitecrm:7.11.8"

Version we are trying to upgrade
    "image": "bitnami/mariadb:11.3"
    "image": "bitnami/suitecrm:8.5.1"

Also please have a look at this below error message

/opt/bitnami/mysql/bin/mysql: Deprecated program name. It will be removed in a future release, use '/opt/bitnami/mysql/bin/mariadb' instead
ERROR 2002 (HY000): Can't connect to server on 'mariadb.next-crm' (115)
suitecrm 11:22:35.82 DEBUG ==> Executing SQL command:

[nidhin077]

@javsalgar We are waiting for any updates since we are currently stuck and would appreciate any information on this matter.

[rafariossaa]

Hi,
From the message, it seems that the database did not start, or maybe there is a problem with the credentials.
Could you share the mysql container logs ?
Did you try to start only the database and connect to it using the user and password ?

[nidhin077]

@rafariossaa I have attached the MySQL log below, please have a look.

mariadb 12:40:41.60 INFO ==> Running mysql_upgrade
mariadb 12:40:41.61 INFO ==> Starting mariadb in background
2024-05-07 12:40:41 0 [Note] Starting MariaDB 11.3.2-MariaDB source revision 068a6819eb63bcb01fdfa037c9bf3bf63c33ee42 as process 67
2024-05-07 12:40:41 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2024-05-07 12:40:41 0 [Note] InnoDB: Number of transaction pools: 1
2024-05-07 12:40:41 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2024-05-07 12:40:41 0 [Note] mysqld: O_TMPFILE is not supported on /opt/bitnami/mariadb/tmp (disabling future attempts)
2024-05-07 12:40:41 0 [Note] InnoDB: Using Linux native AIO
2024-05-07 12:40:41 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2024-05-07 12:40:41 0 [Note] InnoDB: Completed initialization of buffer pool
2024-05-07 12:40:41 0 [Note] InnoDB: File system buffers for log disabled (block size=4096 bytes)
2024-05-07 12:40:41 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.3.39. You must start up and shut down MariaDB 10.4 or earlier.
2024-05-07 12:40:41 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2024-05-07 12:40:41 0 [Note] InnoDB: Starting shutdown...
2024-05-07 12:40:41 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2024-05-07 12:40:41 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-05-07 12:40:41 0 [Note] Plugin 'wsrep-provider' is disabled.
2024-05-07 12:40:41 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2024-05-07 12:40:41 0 [ERROR] Aborting

[rafariossaa]

Hi,
Could you change the version of mysql ? You are using 11.3.2, but it seems it would need 10.4 or earlier to upgrade.

2024-05-07 12:40:41 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.3.39. You must start up and shut down MariaDB 10.4 or earlier.

[nidhin077]

@rafariossaa Yes, I did attempt to upgrade MySQL as well. Must I continue using the same version?

[rafariossaa]

I would give it a try, if it starts, dump the database and then import it in the new version.