1 Topic by iredmailtnt (edited by iredmailtnt 2021-01-22 07:22:05)

  • iredmailtnt
  • Member
  • Offline
  • Registered: 2016-02-10
  • Posts: 52

Topic: mysql warnings on MariaDB 10.x

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

I just built a new 1.3.2 MARIADB edition server with iRedAdmin-Pro 4.7. In order to be running a supported version of MariaDB I upgraded to 10.5. After the install completed everything seems to be working as advertised, except that I see the following in the logs:
2021-01-19 13:01:02 253 [Warning] Aborted connection 253 to db: 'iredapd' user: 'iredapd' host: 'localhost' (Got an error reading communication packets)
2021-01-19 13:01:02 255 [Warning] Aborted connection 255 to db: 'iredadmin' user: 'iredadmin' host: 'localhost' (Got an error reading communication packets)
2021-01-19 13:01:02 256 [Warning] Aborted connection 256 to db: 'vmail' user: 'vmailadmin' host: 'localhost' (Got an error reading communication packets)
2021-01-19 13:02:17 262 [Warning] Aborted connection 262 to db: 'iredapd' user: 'iredapd' host: 'localhost' (Got an error reading communication packets)

I experimented with this by downgrading Maria to 10.3 then 10.2 and then finally the 5.5.68 version that comes with Centos-7. 10.2 and 10.3 still produce the errors but 5.5 does not.

In addition this problem exists with both iRedAdmin open source and iRedAdmin-Pro.

I understand that the standard install installs 5.5.68 but Centos-8 installs 10.3.27 so I am wondering if this is a known issue and harmless or is this something to be concerned about? I have not tried Centos-8 but it seems reasonable to me that if 10.3.x works on IRedMail on Centos-8 It should also work on 10.3 running on Centos-7.

Am I missing something?

I originally posted about this issue in the iRedAdmin-pro forum but since I have confirmed the exists issue with iRedAdmin open source and pro I deleted that message and created this one.

Regards,

Tom

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: mysql warnings on MariaDB 10.x

This is a known issue and it happens one some servers, i still didn't figure out why it happened. sad

3 Reply by iredmailtnt

  • iredmailtnt
  • Member
  • Offline
  • Registered: 2016-02-10
  • Posts: 52

Re: mysql warnings on MariaDB 10.x

ZhangHuangbin wrote:

This is a known issue and it happens one some servers, i still didn't figure out why it happened. sad

If it helps, this is a Centos-7 VM on VMware esxi 6.5 latest. I cannot imagine that the hypervisor type would make a difference but...

I have tried this about 6 or 7 times trying to narrow it down to a particular MariaDB version. Anytime I use Maria 10.x it occurs. Anything that accesses the db triggers it. Even simply bringing up the login screen.

Is it your feeling that it is harmless?

Regards,

Tom

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,088

Re: mysql warnings on MariaDB 10.x

iredmailtnt wrote:

Is it your feeling that it is harmless?

MariaDB has a max error setting, if it reaches the max number, mariadb will stop working. So this is harmful. But i just cannot figure out why it happened ...

5 Reply by iredmailtnt

  • iredmailtnt
  • Member
  • Offline
  • Registered: 2016-02-10
  • Posts: 52

Re: mysql warnings on MariaDB 10.x

ZhangHuangbin wrote:
iredmailtnt wrote:

Is it your feeling that it is harmless?

MariaDB has a max error setting, if it reaches the max number, mariadb will stop working. So this is harmful. But i just cannot figure out why it happened ...

Does that apply to warnings? I only see warnings not errors.

FWIW, I have another installation that runs 2 iredmail instances with a separate db server. The db server is maria 10.4 the iredmail instances use the 5.5 client. I do not get the warnings on them.