iRedMail — Update MariaDB backend 1.7.2 -> 1.7.3

Re: Update MariaDB backend 1.7.2 -> 1.7.3

null@example.com (OITBGD) — Tue, 05 Aug 2025 17:25:25 +0000

Adding password in two section of file /etc/mysql/debian.cnf and restart mariadb.service fix the issue

Re: Update MariaDB backend 1.7.2 -> 1.7.3

null@example.com (OITBGD) — Sat, 02 Aug 2025 08:27:51 +0000

systemctl -u mariadb

Aug 02 11:12:27 systemd[1]: Starting mariadb.service - MariaDB 10.11.11 database server...
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] Starting MariaDB 10.11.11-MariaDB-0+deb12u1 source revision e69f8cae1a15e15b9e4f5e0f8497e1f17bdc81a4 server_uid VksQtqHVvDsSS>
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] InnoDB: Number of transaction pools: 1
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] InnoDB: Using liburing
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] InnoDB: Initialized memory pressure event listener
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] InnoDB: Completed initialization of buffer pool
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] InnoDB: End of log at LSN=48093846317
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] InnoDB: 128 rollback segments are active.
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] InnoDB: log sequence number 48093846317; transaction id 138108368
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] Plugin 'FEEDBACK' is disabled.
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Warning] 'innodb-large-prefix' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Warning] 'innodb-file-format' was removed. It does nothing now and exists only for compatibility with old my.cnf files.
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] Server socket created on IP: '127.0.0.1'.
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [ERROR] Incorrect definition of table mysql.event: expected column 'definer' at position 3 to have type varchar(, found type char(14>
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [ERROR] mariadbd: Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] /usr/sbin/mariadbd: ready for connections.
Aug 02 11:12:28 mariadbd[798055]: Version: '10.11.11-MariaDB-0+deb12u1' socket: '/run/mysqld/mysqld.sock' port: 3306 Debian 12
Aug 02 11:12:28 mariadbd[798055]: 2025-08-02 11:12:28 0 [Note] InnoDB: Buffer pool(s) load completed at 250802 11:12:28
Aug 02 11:12:28 systemd[1]: Started mariadb.service - MariaDB 10.11.11 database server.
Aug 02 11:12:28 /etc/mysql/debian-start[798072]: Upgrading MySQL tables if necessary.
Aug 02 11:12:28 /etc/mysql/debian-start[798075]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Aug 02 11:12:28 /etc/mysql/debian-start[798075]: Reading datadir from the MariaDB server failed. Got the following error when executing the 'mysql' command line client
Aug 02 11:12:28 /etc/mysql/debian-start[798075]: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)
Aug 02 11:12:28 /etc/mysql/debian-start[798075]: FATAL ERROR: Upgrade failed
Aug 02 11:12:28 /etc/mysql/debian-start[798081]: Checking for insecure root accounts.
Aug 02 11:12:28 debian-start[798084]: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)

Re: Update MariaDB backend 1.7.2 -> 1.7.3

null@example.com (OITBGD) — Sat, 02 Aug 2025 07:57:27 +0000

mail:~# mysqlrepair -A
amavisd.maddr
note : The storage engine for the table doesn't support repair
amavisd.mailaddr
note : The storage engine for the table doesn't support repair
amavisd.msgrcpt
note : The storage engine for the table doesn't support repair
amavisd.msgs
note : The storage engine for the table doesn't support repair
amavisd.outbound_wblist
note : The storage engine for the table doesn't support repair
amavisd.policy
note : The storage engine for the table doesn't support repair
amavisd.quarantine
note : The storage engine for the table doesn't support repair
amavisd.users
note : The storage engine for the table doesn't support repair
amavisd.wblist
note : The storage engine for the table doesn't support repair
fail2ban.banned
note : The storage engine for the table doesn't support repair
iredadmin.deleted_mailboxes
note : The storage engine for the table doesn't support repair
iredadmin.domain_ownership
note : The storage engine for the table doesn't support repair
iredadmin.log
note : The storage engine for the table doesn't support repair
iredadmin.newsletter_subunsub_confirms
note : The storage engine for the table doesn't support repair
iredadmin.sessions
note : The storage engine for the table doesn't support repair
iredadmin.settings
note : The storage engine for the table doesn't support repair
iredadmin.tracking
note : The storage engine for the table doesn't support repair
iredadmin.updatelog
note : The storage engine for the table doesn't support repair
iredapd.greylisting
note : The storage engine for the table doesn't support repair
iredapd.greylisting_tracking
note : The storage engine for the table doesn't support repair
iredapd.greylisting_whitelist_domain_spf
note : The storage engine for the table doesn't support repair
iredapd.greylisting_whitelist_domains
note : The storage engine for the table doesn't support repair
iredapd.greylisting_whitelists
note : The storage engine for the table doesn't support repair
iredapd.senderscore_cache
note : The storage engine for the table doesn't support repair
iredapd.smtp_sessions
note : The storage engine for the table doesn't support repair
iredapd.srs_exclude_domains
note : The storage engine for the table doesn't support repair
iredapd.throttle
note : The storage engine for the table doesn't support repair
iredapd.throttle_tracking
note : The storage engine for the table doesn't support repair
iredapd.wblist_rdns
note : The storage engine for the table doesn't support repair
mysql.column_stats OK
mysql.columns_priv OK
mysql.db OK
mysql.event OK
mysql.func OK
mysql.gtid_slave_pos
note : The storage engine for the table doesn't support repair
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.host OK
mysql.index_stats OK
mysql.innodb_index_stats
note : The storage engine for the table doesn't support repair
mysql.innodb_table_stats
note : The storage engine for the table doesn't support repair
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.roles_mapping OK
mysql.servers OK
mysql.table_stats OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.transaction_registry
note : The storage engine for the table doesn't support repair
mysql.user OK
roundcubemail.cache
note : The storage engine for the table doesn't support repair
roundcubemail.cache_index
note : The storage engine for the table doesn't support repair
roundcubemail.cache_messages
note : The storage engine for the table doesn't support repair
roundcubemail.cache_shared
note : The storage engine for the table doesn't support repair
roundcubemail.cache_thread
note : The storage engine for the table doesn't support repair
roundcubemail.collected_addresses
note : The storage engine for the table doesn't support repair
roundcubemail.contactgroupmembers
note : The storage engine for the table doesn't support repair
roundcubemail.contactgroups
note : The storage engine for the table doesn't support repair
roundcubemail.contacts
note : The storage engine for the table doesn't support repair
roundcubemail.dictionary
note : The storage engine for the table doesn't support repair
roundcubemail.filestore
note : The storage engine for the table doesn't support repair
roundcubemail.identities
note : The storage engine for the table doesn't support repair
roundcubemail.responses
note : The storage engine for the table doesn't support repair
roundcubemail.searches
note : The storage engine for the table doesn't support repair
roundcubemail.session
note : The storage engine for the table doesn't support repair
roundcubemail.system
note : The storage engine for the table doesn't support repair
roundcubemail.users
note : The storage engine for the table doesn't support repair
vmail.admin
note : The storage engine for the table doesn't support repair
vmail.alias
note : The storage engine for the table doesn't support repair
vmail.alias_domain
note : The storage engine for the table doesn't support repair
vmail.anyone_shares
note : The storage engine for the table doesn't support repair
vmail.deleted_mailboxes
note : The storage engine for the table doesn't support repair
vmail.domain
note : The storage engine for the table doesn't support repair
vmail.domain_admins
note : The storage engine for the table doesn't support repair
vmail.forwardings
note : The storage engine for the table doesn't support repair
vmail.last_login
note : The storage engine for the table doesn't support repair
vmail.mailbox
note : The storage engine for the table doesn't support repair
vmail.maillist_owners
note : The storage engine for the table doesn't support repair
vmail.maillists
note : The storage engine for the table doesn't support repair
vmail.moderators
note : The storage engine for the table doesn't support repair
vmail.recipient_bcc_domain
note : The storage engine for the table doesn't support repair
vmail.recipient_bcc_user
note : The storage engine for the table doesn't support repair
vmail.sender_bcc_domain
note : The storage engine for the table doesn't support repair
vmail.sender_bcc_user
note : The storage engine for the table doesn't support repair
vmail.sender_relayhost
note : The storage engine for the table doesn't support repair
vmail.share_folder
note : The storage engine for the table doesn't support repair
vmail.used_quota
note : The storage engine for the table doesn't support repair

mail:~# mysql vmail < /tmp/vmail.mysql
--------------
drop procedure if exists irm173_schema_change
--------------

ERROR 1728 (HY000) at line 19: Cannot load from mysql.proc. The table is probably corrupted

No fix, same issue.

Re: Update MariaDB backend 1.7.2 -> 1.7.3

null@example.com (ZhangHuangbin) — Sat, 02 Aug 2025 01:08:17 +0000

Does command "mysqlrepair -A" fix the issue?

Update MariaDB backend 1.7.2 -> 1.7.3

null@example.com (OITBGD) — Fri, 01 Aug 2025 16:40:16 +0000

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.7.2
- Deployed with iRedMail Easy or the downloadable installer? installer
- Linux/BSD distribution name and version: Debian 12
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? NO
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Hello. We have this issue after try to add new columns in vmail database.

mail:~# mysql vmail < /tmp/vmail.mysql
--------------
drop procedure if exists irm173_schema_change
--------------

ERROR 1728 (HY000) at line 19: Cannot load from mysql.proc. The table is probably corrupted