[bitnami/matomo] Loop of restarting matomo

[w4rell]

Name and Version

bitnami/matomo:4.15.0-debian-11-r12 (every after version 4)

What architecture are you using?

None

What steps will reproduce the bug?

Originally in tag matomo:4 and mariadb:10.6
Tried to upgrade to latest image changing my docker-compose to latest (only matomo) and docker compose up -d.

What is the expected behavior?

Upgrade the version and work normally.

What do you see instead?

random-matomo-1  | matomo 13:44:31.61 
random-matomo-1  | matomo 13:44:31.62 Welcome to the Bitnami matomo container
random-matomo-1  | matomo 13:44:31.62 Subscribe to project updates by watching https://github.com/bitnami/containers
random-matomo-1  | matomo 13:44:31.62 Submit issues and feature requests at https://github.com/bitnami/containers/issues
random-matomo-1  | matomo 13:44:31.62 
random-matomo-1  | matomo 13:44:31.63 INFO  ==> ** Starting Matomo setup **
random-matomo-1  | realpath: /bitnami/apache/conf: No such file or directory
random-matomo-1  | matomo 13:44:31.69 INFO  ==> Configuring Apache ServerTokens directive
random-matomo-1  | matomo 13:44:31.72 INFO  ==> Configuring PHP options
random-matomo-1  | matomo 13:44:31.72 INFO  ==> Setting PHP expose_php option
random-matomo-1  | matomo 13:44:31.74 INFO  ==> Setting PHP output_buffering option
random-matomo-1  | matomo 13:44:31.76 INFO  ==> Validating settings in MYSQL_CLIENT_* env vars
random-matomo-1  | matomo 13:44:31.80 WARN  ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
random-matomo-1  | matomo 13:44:31.90 INFO  ==> Persisted Matomo installation detected
random-matomo-1  | matomo 13:44:31.91 INFO  ==> Restoring Matomo installation
random-matomo-1  | matomo 13:44:31.93 INFO  ==> Trying to connect to the database server
random-matomo-1  | matomo 13:44:31.98 INFO  ==> Launching schema update
random-matomo-1  | Could not open input file: /opt/bitnami/matomo/console
random-matomo-1 exited with code 1

Additional information

Thanks for your help !

[jotamartos]

From which version to which one are you updating the solution? I just upgraded the container from bitnami/matomo:4.14.2 to bitnami/matomo:4.15.0 and everything worked as expected

matomo-matomo-1  | matomo 10:52:29.64 INFO  ==> Configuring Apache ServerTokens directive
matomo-matomo-1  | matomo 10:52:29.65 INFO  ==> Configuring PHP options
matomo-matomo-1  | matomo 10:52:29.65 INFO  ==> Setting PHP expose_php option
matomo-matomo-1  | matomo 10:52:29.66 INFO  ==> Setting PHP output_buffering option
matomo-matomo-1  | matomo 10:52:29.68 INFO  ==> Validating settings in MYSQL_CLIENT_* env vars
matomo-matomo-1  | matomo 10:52:29.69 WARN  ==> You set the environment variable ALLOW_EMPTY_PASSWORD=yes. For safety reasons, do not use this flag in a production environment.
matomo-matomo-1  | matomo 10:52:29.74 INFO  ==> Persisted Matomo installation detected
matomo-matomo-1  | matomo 10:52:29.74 INFO  ==> Restoring Matomo installation
matomo-matomo-1  | matomo 10:52:30.00 INFO  ==> Trying to connect to the database server
matomo-matomo-1  | matomo 10:52:30.03 INFO  ==> Launching schema update
matomo-matomo-1  |
matomo-matomo-1  |
matomo-matomo-1  | Everything is already up to date.
matomo-matomo-1  |
matomo-matomo-1  |
matomo-matomo-1  | Done.

[w4rell]

Someone of my team made internal upgrades before without telling me.
What I got on the "system check" :

<details>
<summary>Click to view System Check</summary>

### Mandatory checks

#### PHP version >= 7.2.5:
 ✔ 8.1.18

#### PDO extension:
 ✔ 

#### PDO\MYSQL extension:
 ✔ 

#### MYSQLI extension:
 ✔ 

#### Other required extensions:
 ✔ zlib ✔ json ✔ filter ✔ hash ✔ session

#### Required functions:
 ✔ debug_backtrace ✔ eval ✔ hash ✔ gzcompress ✔ gzuncompress ✔ pack

#### Required PHP configuration (php.ini):
 ✔ session.auto_start = 0 ✔ max_execution_time = 0 OR = -1 OR >= 30

#### Directories with write access:
 ✔ $DOC_ROOT/tmp ✔ $DOC_ROOT/tmp/assets ✔ $DOC_ROOT/tmp/cache ✔ $DOC_ROOT/tmp/climulti ✔ $DOC_ROOT/tmp/latest ✔ $DOC_ROOT/tmp/logs ✔ $DOC_ROOT/tmp/sessions ✔ $DOC_ROOT/tmp/tcpdf ✔ $DOC_ROOT/tmp/templates_c

#### Directories with write access for Tag Manager:
 ✔ /bitnami/matomo/js


### Optional checks

#### Required Private Directories:
 ✔ All private directories are inaccessible from the internet.

#### Recommended Private Directories:
 ✔ All private directories are inaccessible from the internet.

#### File integrity:
 ⚠ Warning: File integrity check failed and reported some errors. You should fix this issue and then refresh this page until it shows no error.<br/><br/>Files were found in your Matomo, but we didn't expect them.<br/>--> Please delete these files to prevent errors. 

#### 64-bit PHP Binary:
 ✔ 

#### Tracker status:
 ✔ 

#### Memory limit:
 ✔ 256M

#### Time zone:
 ✔ 

#### Open URL:
 ✔ curl

#### PageSpeed is turned off:
 ✔ 

#### GD > 2.x + FreeType (graphics):
 ✔ 

#### Other extensions:
 ✔ json ✔ libxml ✔ dom ✔ SimpleXML ✔ openssl

#### Other functions:
 ✔ shell_exec ✔ set_time_limit ✔ mail ✔ parse_ini_file ✔ glob ✔ gzopen ✔ md5_file

#### Filesystem:
 ✔ 

#### Set up Cron (faster report-loading):
 ⚠ Warning: For optimal performance and a speedy Matomo, it is highly recommended to set up a crontab to automatically archive your reports, and to disable browser triggering in the Matomo settings. Learn more.

#### Set up Cron - Managing processes via CLI:
 ✔ Ok

#### Database abilities:
 ✔ UTF8mb4 charset ✔ LOAD DATA INFILE ✔ CREATE TEMPORARY TABLES ✔ Changing transaction isolation level

#### Max Packet Size:
 ✔ 

#### Forced SSL Connection:
 ⚠ Warning: We recommend using Matomo over secure SSL connections only. To prevent insecure access over http, add <code>force_ssl = 1</code> to the <code>General</code> section in your Matomo config/config.ini.php file.

#### Geolocation:
 ✔ geoip2php (continent_code, continent_name, country_code, country_name, region_code, region_name, city_name, postal_code, lat, long)

#### Update over HTTPS:
 ✔ 

#### Writable JavaScript Tracker ("/matomo.js"):
 ✔ 


### Informational results

#### Matomo Version:
 4.15.0

#### Matomo Update History:
 4.13.0,4.12.3,

#### Matomo Install Version:
 4.12.3

#### Latest Available Version:
 4.15.0

#### Is Git Deployment:
 0

#### PHP_OS:
 Linux

#### PHP SAPI:
 apache2handler

#### Timezone Version:
 2023.3

#### PHP Timezone:
 UTC

#### PHP Time:
 1690287978

#### PHP Datetime:
 2023-07-25 12:26:18

#### PHP INI max_execution_time:
 30

#### PHP INI post_max_size:
 40M

#### PHP INI max_input_vars:
 1000

#### PHP INI zlib.output_compression:
 

#### Curl Version:
 7.74.0, OpenSSL/1.1.1n

#### Suhosin Installed:
 0

#### DB Prefix:
 matomo_

#### DB Charset:
 utf8mb4

#### DB Adapter:
 MYSQLI

#### MySQL Version:
 10.6.12-MariaDB

#### Num Tables:
 59

#### Browser Segment Archiving Enabled:
 1

#### Development Mode Enabled:
 0

#### Internet Enabled:
 1

#### Multi Server Environment:
 0

#### Auto Update Enabled:
 1

#### Custom User Path:
 0

#### Custom Include Path:
 0

#### Release Channel:
 latest_stable

#### Plugins Activated:
 API, Actions, Annotations, BulkTracking, Contents, CoreAdminHome, CoreConsole, CoreHome, CorePluginsAdmin, CoreUpdater, CoreVisualizations, CoreVue, CustomDimensions, CustomJsTracker, Dashboard, DevicePlugins, DevicesDetection, Diagnostics, Ecommerce, Events, GeoIp2, Goals, Heartbeat, ImageGraph, Insights, Installation, Intl, IntranetMeasurable, InvalidateReports 4.1.1, LanguagesManager, Live, LoginLdap 4.7.3, Marketplace, MobileMessaging, Monolog, Morpheus, MultiSites, Overlay, PagePerformance, PrivacyManager, ProfessionalServices, Provider 4.0.5, Proxy, Referrers, Resolution, RssWidget, SEO, ScheduledReports, SegmentEditor, SitesManager, TagManager, Tour, Transitions, TwoFactorAuth, UserCountry, UserCountryMap, UserId, UserLanguage, UsersManager, VisitFrequency, VisitTime, VisitorInterest, VisitsSummary, WebsiteMeasurable, Widgetize

#### Plugins Deactivated:
 DBStats, Feedback, IP2Location 4.1.2, Login, MobileAppMeasurable

#### Plugins Invalid:
 

#### Server Info:
 Apache

#### Had visits in last 1 day:
 1

#### Had visits in last 3 days:
 1

#### Had visits in last 5 days:
 1

#### Archive Time Last Started:
 -

#### Archive Time Last Finished:
 -

#### User Agent:
 Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0

#### Browser Language:
 en-us,en

#### Total Invalidation Count:
 1081

#### In Progress Invalidation Count:
 0

#### Scheduled Invalidation Count:
 1081

#### Earliest invalidation ts_started:
 

#### Latest invalidation ts_started:
 

#### Earliest invalidation ts_invalidated:
 2022-12-05 15:09:11

#### Latest invalidation ts_invalidated:
 2023-07-25 06:46:04

#### Number of segment invalidations:
 0

#### Number of plugin invalidations:
 0

#### List of plugins being invalidated:
 

#### Anonymize Referrer:
 

#### Do Not Track enabled:
 1

</details>

The container image is :

Tag : 4
Image Id : 41f53162829d

Thanks for your help !

[Micht69]

Hi,

Same problem here running Matomo on kubernetes using the bitnami chart.

I was on 4.14.1 and running fine, after applying the version 1.1.8 of the chart which result in Matomo 4.15.0, I have the same error and my podis in CrashLoop state.

matomo 16:04:51.03 INFO ==> Launching schema update
Could not open input file: /opt/bitnami/matomo/console

Launching the pod in debug mode (using sleep), I found that /opt/bitnami/matomo/console is not executable ; could this be the issue ?
--> Scratch that comment, this is a php file ...

Edit: The chart is using image docker.io/bitnami/matomo:4.15.0-debian-11-r2

[Micht69]

I rolled back to 4.14.2-debian-11-r0 and the pod is starting fine.

[jotamartos]

Hi @Micht69,

I reproduced the issue and will investigate what's wrong with the upgrade process. Will update this ticket once I have more information.

[jotamartos]

I just found that we changed the data to persist/recover in the solution some weeks ago but didn't release a new major of the chart. Those changes were meant to solve an issue with the chart. Investigating what's the best approach to upgrade the solution now.

[jotamartos]

Hi all,

We released yesterday a new version of the Matomo container and Chart to fix this issue.

#42956
bitnami/charts#18064

The solution persists the entire installation directory and it takes care of updating the Matomo files as mentioned in the official documentation.

Please confirm everything works as expected

[w4rell]

Hi all,

We released yesterday a new version of the Matomo container and Chart to fix this issue.

#42956 bitnami/charts#18064

The solution persists the entire installation directory and it takes care of updating the Matomo files as mentioned in the official documentation.

Please confirm everything works as expected

Just tried, everything is working fine now !

[Micht69]

Hi,

Same here, updated to chart 1.1.11 without issue.

Thanks

[jotamartos]

Great! 😄 I'm really happy to hear that!

Enjoy!

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.