SOGo | BTS

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004684SOGosogo-toolpublic2019-02-19 22:502019-03-13 04:53
Reporterzhb 
Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
StatusnewResolutionopen 
PlatformOSOS Version
Product Version4.0.4 
Target VersionFixed in Version 
Summary0004684: sogo-tool on FreeBSD 12.0 always triggers MySQL error "Got an error reading communication packets"
Description- OS: FreeBSD 12.0
- SOGo: 4.0.4 (installed from FreeBSD ports tree, 4.0.5 is not yet available)
- MySQL: 5.7.25

We run 3 "sogo-tool" commands with cron daemon, and it causes mysql error EVERY time the command runs:

/usr/local/GNUstep/Local/Tools/Admin/sogo-tool expire-sessions 30
/usr/local/GNUstep/Local/Tools/Admin/sogo-ealarms-notify
/usr/local/GNUstep/Local/Tools/Admin/sogo-tool update-autoreply -p /usr/local/etc/sogo/sieve.cred

Running them manually causes same mysql error:

2019-02-19T11:59:33.502480Z 2883 [Note] Aborted connection 2883 to db: 'sogo' user: 'sogo' host: 'localhost' (Got an error reading communication packets)

Seems sogo-tool / sogo-ealarms-notify don't close MySQL connection correctly. This error causes MySQL global status variable "Aborted_clients" increased, when it reaches max errors, SOGo can not connect to MySQL.

+------------------+-------+
| Variable_name | Value |
+------------------+-------+
| Aborted_clients | 1456 |
| Aborted_connects | 0 |
+------------------+-------+
MySQL timeout settings:

+-----------------------------+----------+
| Variable_name | Value |
+-----------------------------+----------+
| connect_timeout | 10 |
| delayed_insert_timeout | 300 |
| have_statement_timeout | YES |
| innodb_flush_log_at_timeout | 1 |
| innodb_lock_wait_timeout | 50 |
| innodb_rollback_on_timeout | OFF |
| interactive_timeout | 28800 |
| lock_wait_timeout | 31536000 |
| net_read_timeout | 30 |
| net_write_timeout | 60 |
| rpl_stop_slave_timeout | 31536000 |
| slave_net_timeout | 60 |
| wait_timeout | 28800 |
+-----------------------------+----------+
Steps To ReproduceInstall SOGo from ports tree on FreeBSD 12.x.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0013398)
zhb (reporter)
2019-02-19 22:52

Update: when it reaches max (mysql) errors, mysql is unreachable by SOGo and other applications like Postfix/Dovecot.
User avatar (0013399)
Christian Mack (developer)
2019-02-20 04:11

Which SOPE Version do you use?
(0013403)
zhb (reporter)
2019-02-20 04:44

It's sope4-4.0.4. Installed from FreeBSD ports tree too.
(0013434)
zhb (reporter)
2019-03-11 00:58

Dear developers,

Any update? This issue drives all FreeBSD users crazy. :(
(0013443)
nycvelo (reporter)
2019-03-12 21:27

Also seeing the same issue since upgrading to FreeBSD 12.0-RELEASE and MySQL 5.7.25 client and server installed from ports. Haven't yet detected any pattern to the frequency of MySQL becoming unreachable. A very kludgy workaround is a little script that monitors the MySQL error log and restarts the database whenever the "Bad handshake" message count increments -- but that really is a hack. The system has plenty of CPU, memory, disk, etc., and there's no apparent reason why MySQL should lock up. It ran OK on previous versions of FreeBSD.
(0013444)
Peter2121 (reporter)
2019-03-13 04:53

I confirm the same problem on FreeBSD 11.2.

- Issue History
Date Modified Username Field Change
2019-02-19 22:50 zhb New Issue
2019-02-19 22:52 zhb Note Added: 0013398
2019-02-20 04:11 Christian Mack Note Added: 0013399
2019-02-20 04:44 zhb Note Added: 0013403
2019-03-11 00:58 zhb Note Added: 0013434
2019-03-12 21:27 nycvelo Note Added: 0013443
2019-03-13 04:53 Peter2121 Note Added: 0013444


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker