update to 2.2.20 systeminfo mysql with red x (error) Topic is solved

[web8maxy]

after update the cmsms systeminfo shows a red x (error) at Server_Db_Version.
Is mysql 5.7.42 not compatible?

the cms seems to function. i couldnot find any error.

Cms Version: 2.2.20
Installed Modules:
AdminSearch: 1.0.6
CMSContentManager: 1.1.13
Captcha: 1.0.1
CmsJobManager: 1.0.0
DesignManager: 1.1.11
FileManager: 1.6.16
FilePicker: 1.0.8
FormBuilder: 1.2
MicroTiny: 2.2.5
ModuleManager: 2.1.9
Navigator: 1.0.11
News: 2.51.13
Search: 1.53
Config Information:
php_memory_limit:
max_upload_size: 128000000
url_rewriting: none
page_extension:
query_var: page
auto_alias_content: true
locale:
set_names: true
timezone: Europe/Paris
permissive_smarty: false
Php Information:
phpversion: 8.2.10
md5_function: An (Ja)
json_function: An (Ja)
gd_version: 2
tempnam_function: An (Ja)
magic_quotes_runtime: Aus (Nein)
E_ALL: 32759
E_STRICT: 2048
E_DEPRECATED: 8192
test_file_timedifference: Kein Zeitunterschied gefunden
test_db_timedifference: Kein Zeitunterschied gefunden
create_dir_and_file: 1
memory_limit: 512M
max_execution_time: 165
register_globals: Aus (Nein)
output_buffering: 4096
disable_functions: _dyuweyrj4, _dyuweyrj4r, dl
open_basedir:
test_remote_url: Erfolgreich abgeschlossen
file_uploads: An (Ja)
post_max_size: 130M
upload_max_filesize: 128M
session_save_path: /tmp (0700)
session_use_cookies: An (Ja)
xml_function: An (Ja)
xmlreader_class: An (Ja)
check_ini_set: Aus (Nein)
curl: An
Performance Information:
allow_browser_cache: Aus (Nein)
browser_cache_expiry: 60
php_opcache: An (Ja)
smarty_cache: Aus (Nein)
smarty_compilecheck: An (Ja)
auto_clear_cache_age: An (Ja)
Server Information:
Server Software: Apache
Server Api: fpm-fcgi
Server Os: Linux 5.15.124-ovh-vps-grsec-zfs-classid An x86_64
Server Db Type: MySQL (mysqli)
Server Db Version: 5.7.42
Server Db Grants: „Alles gewähren“-Anweisung gefunden, die als geeignet scheint
Permission Information:
tmp: /home/URL/www/tmp (0705)
tmp_cache: /home/URL/www/tmp/cache (0705)
templates_c: /home/URL/www/tmp/templates_c (0705)
modules: /home/URL/www/modules (0705)
uploads: /home/URL/www/uploads (0705)
Maske zum Erstellen von Dateien (umask): /home/URL/www/tmp/cache (0705)
config_file: 0444

[DIGI3]

The system checks for a minimum version of 5.7.44. It may work with 5.7.42 but if you run into issues you should probably have it upgraded. The recommended version is currently 8.3.0.

[creopard]

You can also try checking your webhosting settings. Maybe your webhoster supports switching the underlying database: so you can switch from your old "MySQL" to a (maybe) newer "MariaDB" instance.

[web8maxy]

I have not found any information about the minimum MySQL version in the cmsms documentation.

The webhosting of my provider OVH is currently at version MySQL 5.7.42 and will obviously not get an update very soon. In any case, I was not given a date! The OVH web hosting packages are still offered and sold with MySQL 5.7, although MySQL 5.7.44 received the final update on 2023-10-25!!!

[Jo Morg]

For the moment you can safely disregard that particular red mark. Typically we make the choice to limit as both minimum and recommended the most recent stable versions of the branches we tested. That is the safest assessment not necessarily the lower nor upper limit of the versions that may work with the core. However, if there are any bugs or glitches you'll know why.
Most often than not, versions can be interchangeable between, say, the 5.7.x branch releases. But for sure the latest is the most stable one. And that is usually true for all software projects.