Details
Description
Hi, I am unable to find detailed documentation on mariadb regarding this, but from mysql[1] page it explains that aborted connections in logs should be happening only during certain cases which doesn't apply to our environment.
For each connection, closed gracefully we get entry like this with logging setting
[Warning] Aborted connection 2934 to db: 'unconnected' user: 'ABC' host: '127.0.0.1' (This connection closed normally)
Settings:
log_warnings 5
OS Ubuntu 20.04 latest updates
1:10.5.8+maria~focal
The question is if I am missing something here or this is expected from normal connection(different from mysql).
If this is normal logging then I would question whether this is useful and systematic. If intention is to allow some auditing then connectivity start and finish should be recorded alongside source port number as otherwise it is hard to identify among many connections from the same source IP.
Many thanks
[1] https://dev.mysql.com/doc/refman/5.7/en/communication-errors.html
Attachments
Issue Links
- relates to
-
MDEV-33557 Connections closed normally were not logged when log_warning>=4
-
- Confirmed
-
Activity
Field | Original Value | New Value |
---|---|---|
Description |
Hi, I am unable to find detailed documentation on mariadb regarding this, but from mysql[1] page it explains that aborted connections in logs should be happening only during certain cases which doesn't apply to our environment.
For each connection, closed gracefully we get entry like this with logging setting log_warnings 5 OS Ubuntu 20.04 latest updates 1:10.5.8+maria~focal [Warning] Aborted connection 2934 to db: 'unconnected' user: 'ABC' host: '127.0.0.1' (This connection closed normally) The question is if I am missing something here or this is expected from normal connection(different from mysql). If this is normal logging then I would question whether this is useful and systematic. If intention is to allow some auditing then connectivity start and finish should be recorded alongside source port number as otherwise it is hard to identify among many connections from the same source IP. Many thanks [1] https://dev.mysql.com/doc/refman/5.7/en/communication-errors.html |
Hi, I am unable to find detailed documentation on mariadb regarding this, but from mysql[1] page it explains that aborted connections in logs should be happening only during certain cases which doesn't apply to our environment.
For each connection, closed gracefully we get entry like this with logging setting [Warning] Aborted connection 2934 to db: 'unconnected' user: 'ABC' host: '127.0.0.1' (This connection closed normally) Settings: log_warnings 5 OS Ubuntu 20.04 latest updates 1:10.5.8+maria~focal The question is if I am missing something here or this is expected from normal connection(different from mysql). If this is normal logging then I would question whether this is useful and systematic. If intention is to allow some auditing then connectivity start and finish should be recorded alongside source port number as otherwise it is hard to identify among many connections from the same source IP. Many thanks [1] https://dev.mysql.com/doc/refman/5.7/en/communication-errors.html |
Component/s | Server [ 13907 ] | |
Fix Version/s | 10.2 [ 14601 ] | |
Fix Version/s | 10.3 [ 22126 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Fix Version/s | 10.5 [ 23123 ] | |
Affects Version/s | 5.5 [ 15800 ] | |
Affects Version/s | 10.1 [ 16100 ] | |
Affects Version/s | 10.2 [ 14601 ] | |
Affects Version/s | 10.3 [ 22126 ] | |
Affects Version/s | 10.4 [ 22408 ] | |
Affects Version/s | 10.5 [ 23123 ] | |
Assignee | Oleksandr Byelkin [ sanja ] |
Status | Open [ 1 ] | Confirmed [ 10101 ] |
Workflow | MariaDB v3 [ 116232 ] | MariaDB v4 [ 144321 ] |
Fix Version/s | 10.2 [ 14601 ] |
Fix Version/s | 10.3 [ 22126 ] | |
Fix Version/s | 10.5 [ 23123 ] |
Assignee | Oleksandr Byelkin [ sanja ] | Daniel Black [ danblack ] |
Assignee | Daniel Black [ danblack ] | Oleksandr Byelkin [ sanja ] |
Status | Confirmed [ 10101 ] | In Review [ 10002 ] |
Assignee | Oleksandr Byelkin [ sanja ] | Daniel Black [ danblack ] |
Status | In Review [ 10002 ] | Stalled [ 10000 ] |
Fix Version/s | 10.4.29 [ 28510 ] | |
Fix Version/s | 10.5.20 [ 28512 ] | |
Fix Version/s | 10.6.13 [ 28514 ] | |
Fix Version/s | 10.7.9 [ 28516 ] | |
Fix Version/s | 10.8.8 [ 28518 ] | |
Fix Version/s | 10.9.6 [ 28520 ] | |
Fix Version/s | 10.10.4 [ 28522 ] | |
Fix Version/s | 10.11.2 [ 28523 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Resolution | Fixed [ 1 ] | |
Status | Stalled [ 10000 ] | Closed [ 6 ] |
Fix Version/s | 10.7.9 [ 28516 ] |
Fix Version/s | 10.11.3 [ 28524 ] | |
Fix Version/s | 10.11.2 [ 28523 ] |
Link | This issue relates to MDEV-33557 [ MDEV-33557 ] |
Indeed, the warning is printed in all MariaDB versions from at least 5.5, with log_warnings >= 4.
I don't have a reasonable explanation for it, maybe sanja does.