Aborted connection message in log in every 5 minutes
Hi Everyone,
we have mailman 3.3.8 venv test installation which in general works fine however our mysql error log is filled up with messages below because they are so frequent.
2023-02-24 0:31:30 199567 [Warning] Aborted connection 199567 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-02-24 0:36:30 201063 [Warning] Aborted connection 201063 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-02-24 0:41:31 202559 [Warning] Aborted connection 202559 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-02-24 0:46:31 204056 [Warning] Aborted connection 204056 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets)
As suggested here https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/3... I tried to correlate with error logs and
/opt/mailman/web/logs/mailmanweb.log shows some hyperkitty.lib.utils Failed to update the fulltext index: (2002, "Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (111)"
/opt/mailman/web/logs/uwsgi-error.log Message: OperationalError(2013, "Lost connection to MySQL server at 'handshake: reading initial communication packet', sy stem error: 104")
but they have not such frequency so unsure if they are related.
Thanks for the suggestions
No timestamps in your logs? That would help you relate. What OS are you using?
On Fri, Feb 24, 2023, 12:28 <zoltan@circle-interactive.co.uk> wrote:
Hi Everyone,
we have mailman 3.3.8 venv test installation which in general works fine however our mysql error log is filled up with messages below because they are so frequent.
2023-02-24 0:31:30 199567 [Warning] Aborted connection 199567 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-02-24 0:36:30 201063 [Warning] Aborted connection 201063 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-02-24 0:41:31 202559 [Warning] Aborted connection 202559 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-02-24 0:46:31 204056 [Warning] Aborted connection 204056 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets)
As suggested here
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/3... I tried to correlate with error logs and
/opt/mailman/web/logs/mailmanweb.log shows some hyperkitty.lib.utils Failed to update the fulltext index: (2002, "Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (111)"
/opt/mailman/web/logs/uwsgi-error.log Message: OperationalError(2013, "Lost connection to MySQL server at 'handshake: reading initial communication packet', sy stem error: 104")
but they have not such frequency so unsure if they are related.
Thanks for the suggestions
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to odhiambo@gmail.com
The OS is Debian GNU/Linux 11
In mailmanweb.log only these two occurrences of the error
ERROR 2023-01-30 13:00:17,375 1078096 hyperkitty.lib.utils Failed to update the fulltext index: (2002, "Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (111)") ERROR 2023-02-22 16:00:02,967 2044909 hyperkitty.lib.utils Failed to update the fulltext index: (2002, "Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (111)")
In uwsgi-error.log they are part of a bigger trace but usually come after a line like which occurs approximately in every 10 minutes
13:17:19 [Q] ERROR reincarnated pusher Process-1:214 after sudden death 13:17:29 [Q] ERROR reincarnated pusher Process-1:215 after sudden death 13:17:40 [Q] ERROR reincarnated pusher Process-1:216 after sudden death 13:17:50 [Q] ERROR reincarnated pusher Process-1:217 after sudden death 13:18:00 [Q] ERROR reincarnated pusher Process-1:218 after sudden death
And you can successfully connect to MySQL manually, from the CLI, with the credentials in settings?
I have MM3 on a few Debían machines and I haven't seen anything like this.
On Fri, Feb 24, 2023, 13:59 <zoltan@circle-interactive.co.uk> wrote:
The OS is Debian GNU/Linux 11
In mailmanweb.log only these two occurrences of the error
ERROR 2023-01-30 13:00:17,375 1078096 hyperkitty.lib.utils Failed to update the fulltext index: (2002, "Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (111)") ERROR 2023-02-22 16:00:02,967 2044909 hyperkitty.lib.utils Failed to update the fulltext index: (2002, "Can't connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (111)")
In uwsgi-error.log they are part of a bigger trace but usually come after a line like which occurs approximately in every 10 minutes
13:17:19 [Q] ERROR reincarnated pusher Process-1:214 after sudden death 13:17:29 [Q] ERROR reincarnated pusher Process-1:215 after sudden death 13:17:40 [Q] ERROR reincarnated pusher Process-1:216 after sudden death 13:17:50 [Q] ERROR reincarnated pusher Process-1:217 after sudden death 13:18:00 [Q] ERROR reincarnated pusher Process-1:218 after sudden death
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to odhiambo@gmail.com
Yes, I can manually connect fine.
UI also works perfectly.
I was hoping you have a clue seeing the periodicity. I will try to debug in mysql first.
On 2/24/23 01:18, zoltan@circle-interactive.co.uk wrote:
Hi Everyone,
we have mailman 3.3.8 venv test installation which in general works fine however our mysql error log is filled up with messages below because they are so frequent.
2023-02-24 0:31:30 199567 [Warning] Aborted connection 199567 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-02-24 0:36:30 201063 [Warning] Aborted connection 201063 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-02-24 0:41:31 202559 [Warning] Aborted connection 202559 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets) 2023-02-24 0:46:31 204056 [Warning] Aborted connection 204056 to db: 'mailman' user: 'mailman' host: 'localhost' (Got an error reading communication packets)
See https://dev.mysql.com/doc/refman/8.0/en/communication-errors.html for information on debugging this.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Same issue at my site. I'm using mailman3 3.3.8 shipped with Debian 12. To debug the problem I stopped apache, cron, postfix and mailman3-web services. But I still get the mariadb aborted connection warnings every 5 minutes. 2024-01-30T19:26:42.272261+01:00 debian12 mariadbd[666]: 2024-01-30 19:26:42 62184 [Warning] Aborted connection 62184 to db: 'mailman3' user: 'mailman3' host: 'localhost' (Got an error reading communication packets) 2024-01-30T19:31:42.434576+01:00 debian12 mariadbd[666]: 2024-01-30 19:31:42 62185 [Warning] Aborted connection 62185 to db: 'mailman3' user: 'mailman3' host: 'localhost' (Got an error reading communication packets) 2024-01-30T19:36:42.653755+01:00 debian12 mariadbd[666]: 2024-01-30 19:36:42 62186 [Warning] Aborted connection 62186 to db: 'mailman3' user: 'mailman3' host: 'localhost' (Got an error reading communication packets) This is what appears in the database debug log for the connection number 62186. 240130 19:36:42 62186 Connect mailman3@localhost on mailman3 using TCP/IP 62186 Query SET AUTOCOMMIT = 0 62186 Query SET SESSION TRANSACTION ISOLATION LEVEL READ UNCOMMITTED 62186 Query COMMIT 62186 Query SET NAMES utf8 62186 Query SELECT VERSION() 62186 Query SELECT DATABASE() 62186 Query SELECT @@tx_isolation 62186 Query SELECT @@sql_mode 62186 Query SELECT @@lower_case_table_names 62186 Query ROLLBACK 62186 Query SELECT COUNT(*) FROM information_schema.tables WHERE table_schema = 'mailman3' AND table_name = 'alembic_version' 62186 Query SELECT alembic_version.version_num 62186 Query COMMIT 62186 Query ROLLBACK 62186 Query SELECT mailinglist.list_id AS mailinglist_list_id, mailinglist.preferred_language AS mailinglist_preferred_language, mailinglist.id AS mailinglist_id, mailinglist.list_name AS mailinglist_list_name, mailinglist.mail_host AS mailinglist_mail_host, mailinglist.allow_list_posts AS mailinglist_allow_list_posts, mailinglist.include_rfc2369_headers AS mailinglist_include_rfc2369_headers, mailinglist.advertised AS mailinglist_advertised, mailinglist.anonymous_list AS mailinglist_anonymous_list, mailinglist.created_at AS mailinglist_created_at, mailinglist.next_request_id AS mailinglist_next_request_id, mailinglist.next_digest_number AS mailinglist_next_digest_number, mailinglist.digest_last_sent_at AS mailinglist_digest_last_sent_at, mailinglist.volume AS mailinglist_volume, mailinglist.last_post_at AS mailinglist_last_post_at, mailinglist.accept_these_nonmembers AS mailinglist_accept_these_nonmembers, mailinglist.admin_immed_notify AS mailinglist_admin_immed_notify, mailinglist.admin_notify_mchanges AS mailinglist_admin_notify_mchanges, mailinglist.administrivia AS mailinglist_administrivia, mailinglist.archive_policy AS mailinglist_archive_policy, mailinglist.autoresponse_grace_period AS mailinglist_autoresponse_grace_period, mailinglist.autorespond_owner AS mailinglist_autorespond_owner, mailinglist.autoresponse_owner_text AS mailinglist_autoresponse_owner_text, mailinglist.autorespond_postings AS mailinglist_autorespond_postings, mailinglist.autoresponse_postings_text AS mailinglist_autoresponse_postings_text, mailinglist.autorespond_requests AS mailinglist_autorespond_requests, mailinglist.autoresponse_request_text AS mailinglist_autoresponse_request_text, mailinglist.filter_action AS mailinglist_filter_action, mailinglist.filter_content AS mailinglist_filter_content, mailinglist.collapse_alternatives AS mailinglist_collapse_alternatives, mailinglist.convert_html_to_plaintext AS mailinglist_convert_html_to_plaintext, mailinglist.bounce_info_stale_after AS mailinglist_bounce_info_stale_after, mailinglist.bounce_matching_headers AS mailinglist_bounce_matching_headers, mailinglist.bounce_notify_owner_on_bounce_increment AS mailinglist_bounce_notify_owner_on_bounce_increment, mailinglist.bounce_notify_owner_on_disable AS mailinglist_bounce_notify_owner_on_disable, mailinglist.bounce_notify_owner_on_removal AS mailinglist_bounce_notify_owner_on_removal, mailinglist.bounce_score_threshold AS mailinglist_bounce_score_threshold, mailinglist.bounce_you_are_disabled_warnings AS mailinglist_bounce_you_are_disabled_warnings, mailinglist.bounce_you_are_disabled_warnings_interval AS mailinglist_bounce_you_are_disabled_warnings_interval, mailinglist.forward_unrecognized_bounces_to AS mailinglist_forward_unrecognized_bounces_to, mailinglist.process_bounces AS mailinglist_process_bounces, mailinglist.dmarc_mitigate_action AS mailinglist_dmarc_mitigate_action, mailinglist.dmarc_mitigate_unconditionally AS mailinglist_dmarc_mitigate_unconditionally, mailinglist.dmarc_moderation_notice AS mailinglist_dmarc_moderation_notice, mailinglist.dmarc_wrapped_message_text AS mailinglist_dmarc_wrapped_message_text, mailinglist.default_member_action AS mailinglist_default_member_action, mailinglist.default_nonmember_action AS mailinglist_default_nonmember_action, mailinglist.description AS mailinglist_description, mailinglist.digests_enabled AS mailinglist_digests_enabled, mailinglist.digest_is_default AS mailinglist_digest_is_default, mailinglist.digest_send_periodic AS mailinglist_digest_send_periodic, mailinglist.digest_size_threshold AS mailinglist_digest_size_threshold, mailinglist.digest_volume_frequency AS mailinglist_digest_volume_frequency, mailinglist.discard_these_nonmembers AS mailinglist_discard_these_nonmembers, mailinglist.emergency AS mailinglist_emergency, mailinglist.encode_ascii_prefixes AS mailinglist_encode_ascii_prefixes, mailinglist.first_strip_reply_to AS mailinglist_first_strip_reply_to, mailinglist.forward_auto_discards AS mailinglist_forward_auto_discards, mailinglist.gateway_to_mail AS mailinglist_gateway_to_mail, mailinglist.gateway_to_news AS mailinglist_gateway_to_news, mailinglist.hold_these_nonmembers AS mailinglist_hold_these_nonmembers, mailinglist.info AS mailinglist_info, mailinglist.linked_newsgroup AS mailinglist_linked_newsgroup, mailinglist.max_days_to_hold AS mailinglist_max_days_to_hold, mailinglist.max_message_size AS mailinglist_max_message_size, mailinglist.max_num_recipients AS mailinglist_max_num_recipients, mailinglist.member_moderation_notice AS mailinglist_member_moderation_notice, mailinglist.moderator_password AS mailinglist_moderator_password, mailinglist.newsgroup_moderation AS mailinglist_newsgroup_moderation, mailinglist.nntp_prefix_subject_too AS mailinglist_nntp_prefix_subject_too, mailinglist.nonmember_rejection_notice AS mailinglist_nonmember_rejection_notice, mailinglist.obscure_addresses AS mailinglist_obscure_addresses, mailinglist.owner_chain AS mailinglist_owner_chain, mailinglist.owner_pipeline AS mailinglist_owner_pipeline, mailinglist.personalize AS mailinglist_personalize, mailinglist.post_id AS mailinglist_post_id, mailinglist.posting_chain AS mailinglist_posting_chain, mailinglist.posting_pipeline AS mailinglist_posting_pipeline, mailinglist.display_name AS mailinglist_display_name, mailinglist.reject_these_nonmembers AS mailinglist_reject_these_nonmembers, mailinglist.reply_goes_to_list AS mailinglist_reply_goes_to_list, mailinglist.reply_to_address AS mailinglist_reply_to_address, mailinglist.require_explicit_destination AS mailinglist_require_explicit_destination, mailinglist.respond_to_post_requests AS mailinglist_respond_to_post_requests, mailinglist.member_roster_visibility AS mailinglist_member_roster_visibility, mailinglist.scrub_nondigest AS mailinglist_scrub_nondigest, mailinglist.send_goodbye_message AS mailinglist_send_goodbye_message, mailinglist.send_welcome_message AS mailinglist_send_welcome_message, mailinglist.subject_prefix AS mailinglist_subject_prefix, mailinglist.subscription_policy AS mailinglist_subscription_policy, mailinglist.topics AS mailinglist_topics, mailinglist.topics_bodylines_limit AS mailinglist_topics_bodylines_limit, mailinglist.topics_enabled AS mailinglist_topics_enabled, mailinglist.unsubscription_policy AS mailinglist_unsubscription_policy, mailinglist.usenet_watermark AS mailinglist_usenet_watermark, mailinglist.archive_rendering_mode AS mailinglist_archive_rendering_mode 62186 Query COMMIT 62186 Query ROLLBACK The regular mailman log doesn't show anything and I'm not sure about how to enable an appropriate debug log for mailman.
On 1/30/24 10:46, andrea.janna.unipd@gmail.com wrote:
Same issue at my site. I'm using mailman3 3.3.8 shipped with Debian 12.
Then your first line of support should be Debian. See <https://wiki.list.org/x/12812344>
To debug the problem I stopped apache, cron, postfix and mailman3-web services. But I still get the mariadb aborted connection warnings every 5 minutes.
The only thing that runs every 5 minutes is mailman gatenews. The
issue may be with that. You could try running it manually via
_MAILMAN_GATENEWS_NNTP=yes;sudo -u list mailman gatenews
...
The regular mailman log doesn't show anything and I'm not sure about how to enable an appropriate debug log for mailman.
Mailman has a number of virtual logs, most of which are written to the file mailman.log. You can enable debug level for those with
[logging.template]
level:debug
See <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.c...> for more info on logging.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Mark,
On Wed, Jan 31, 2024 at 3:12 AM Mark Sapiro <mark@msapiro.net> wrote:
The only thing that runs every 5 minutes is
mailman gatenews. The issue may be with that. You could try running it manually via_MAILMAN_GATENEWS_NNTP=yes;sudo -u list mailman gatenews
I observe occasional error messages in MariaDB log even with NNTP runner disabled via
[runner.nntp]
start: no
They look like this:
2024-01-31 0:23:03 231666 [Warning] Aborted connection 231666 to db:
'mailman_core' user: 'root' host: '192.168.32.7' (Got timeout reading
communication packets)
2024-01-31 6:00:09 232888 [Warning] Aborted connection 232888 to db:
'mailman_core' user: 'root' host: '192.168.32.7' (Got timeout reading
communication packets)
2024-01-31 9:19:34 231643 [Warning] Aborted connection 231643 to db:
'mailman_core' user: 'root' host: '192.168.32.7' (Got timeout reading
communication packets)
2024-01-31 9:19:35 232847 [Warning] Aborted connection 232847 to db:
'mailman_core' user: 'root' host: '192.168.32.7' (Got timeout reading
communication packets)
2024-01-31 9:19:35 233069 [Warning] Aborted connection 233069 to db:
'mailman_web' user: 'root' host: '192.168.32.4' (Got timeout reading
communication packets)
2024-01-31 9:19:35 233068 [Warning] Aborted connection 233068 to db:
'mailman_web' user: 'root' host: '192.168.32.4' (Got timeout reading
communication packets)
2024-01-31 9:19:35 233070 [Warning] Aborted connection 233070 to db:
'mailman_web' user: 'root' host: '192.168.32.4' (Got timeout reading
communication packets)
2024-01-31 9:19:35 233071 [Warning] Aborted connection 233071 to db:
'mailman_web' user: 'root' host: '192.168.32.4' (Got timeout reading
communication packets)
However, no harm caused by them was detected.
BR, Danil Smirnov
Sincerely, Danil Smirnov
On 1/31/24 02:23, Danil Smirnov wrote:
I observe occasional error messages in MariaDB log even with NNTP runner disabled via
[runner.nntp] start: noThey look like this:
2024-01-31 0:23:03 231666 [Warning] Aborted connection 231666 to db: 'mailman_core' user: 'root' host: '192.168.32.7' (Got timeout reading communication packets)
...
However, no harm caused by them was detected.
Can you correlate these with mailmanweb.log entries that might indicate what Django was doing.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
The only thing that runs every 5 minutes is mailman gatenews. The issue may be with that. You could try running it manually via _MAILMAN_GATENEWS_NNTP=yes;sudo -u list mailman gatenews
Yes it's mailman gatenews that triggers mariadbd "[Warning] Aborted connection" log entries. I don't use this feature so as a workaround I set a large gatenews_every interval in mailman.cfg.
[nntp] gatenews_every: 1000000m
Thanks for your support.
Andrea
On 1/31/24 04:00, andrea.janna.unipd@gmail.com wrote:
Yes it's mailman gatenews that triggers mariadbd "[Warning] Aborted connection" log entries. I don't use this feature so as a workaround I set a large gatenews_every interval in mailman.cfg.
[nntp] gatenews_every: 1000000m
Or you can do as Danil does <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...> and put
[runner.nntp]
start: no
in mailman.cfg.
However, it is unclear what in gatenews would do this. Assuming you have no lists for which gateway_to_mail is true, all gatenews will do is
def process_lists(glock):
list_manager = getUtility(IListManager)
for mlist in list_manager.mailing_lists:
glock.refresh()
listname = mlist.fqdn_listname
if not mlist.gateway_to_mail:
continue
The database operations involved in this are things Mailman core is doing all the time, presumably without issues.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
However, it is unclear what in gatenews would do this. Assuming you have no lists for which gateway_to_mail is true, all gatenews will do is def process_lists(glock): list_manager = getUtility(IListManager) for mlist in list_manager.mailing_lists: glock.refresh() listname = mlist.fqdn_listname if not mlist.gateway_to_mail: continue
The database operations involved in this are things Mailman core is doing all the time, presumably without issues.
I have no lists with "Gateway to news" option set to yes in the web interface.
From the database debug log I guess that mailman gatenews abruptly terminates the database connections. For instance this is the database debug log of a connection that doesn't trigger the mariadbd "[Warning] Aborted connection" log entry.
70759 Connect mailman3web@localhost on mailman3web using Socket
70759 Query SET sql_mode='STRICT_TRANS_TABLES'... 240131 18:54:34 70759 Quit
There is a "Quit" at the end. While the log entries of the connections that trigger the aborted connection warning (like the one I posted yesterday) do not have "Quit" at the end.
On 1/31/24 10:12, andrea.janna.unipd@gmail.com wrote:
From the database debug log I guess that mailman gatenews abruptly terminates the database connections. For instance this is the database debug log of a connection that doesn't trigger the mariadbd "[Warning] Aborted connection" log entry.
70759 Connect mailman3web@localhost on mailman3web using Socket 70759 Query SET sql_mode='STRICT_TRANS_TABLES'... 240131 18:54:34 70759 Quit
There is a "Quit" at the end. While the log entries of the connections that trigger the aborted connection warning (like the one I posted yesterday) do not have "Quit" at the end.
You could try the following in mailman shell
$ mailman shell
Welcome to the GNU Mailman shell
Use commit() to commit changes.
Use abort() to discard changes since the last commit.
Exit with ctrl+D does an implicit commit() but exit() does not.
>>> for mlist in getUtility(IListManager).mailing_lists:
... print(mlist.fqdn_listname)
...
(here should be a list of your mailing lists)
>>>
Does this produce the expected list of mailing lists and does it produce the error in the database debug log?
If it does produce the expected list of mailing lists and the error in the database debug log, I'd say this is some issue between SQLAlchemy and MariaDB, but it seems harmless.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
$ mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not.
for mlist in getUtility(IListManager).mailing_lists: ... print(mlist.fqdn_listname) ... (here should be a list of your mailing lists)
Yes that command prints the list of my mailing lists and it triggers the "[Warning] Aborted connection" MariaDB log entry.
I stumbled across the same warning, which has been known for at least two years. It can be triggered by the command above. Since Debian Stable still uses version 1.4 of python3-sqlalchemy:
Do you know if this warning still happens in a version ≥2.0 of python3-sqlalchemy?
Do you know a workaround to generate less noise in the log files without disabling all MariaDB warning messages? We really use the NNTP gateway, turning that off is not an option.
Thanks, Erik
On 12/2/24 11:08 PM, erik@dante.de wrote:
Do you know if this warning still happens in a version ≥2.0 of python3-sqlalchemy?
This may be https://github.com/sqlalchemy/sqlalchemy/issues/10893 which appears to be fixed in 2.0.
Do you know a workaround to generate less noise in the log files without disabling all MariaDB warning messages? We really use the NNTP gateway, turning that off is not an option.
No, but I know nothing about MariaDB.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (6)
-
andrea.janna.unipd＠gmail.com -
Danil Smirnov -
erik＠dante.de -
Mark Sapiro -
Odhiambo Washington -
zoltan＠circle-interactive.co.uk