maria-discuss team mailing list archive

[Tanstaafl <tanstaafl@xxxxxxxxxxxxxxx>]

On 7/2/2014 8:30 AM, Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote:
> you refuse to understand that this message comes from the*client*
> and not from MySQL/MariaDB - so guess why nobody here gave an
> answer

Yes, the error I posted comes from the client, but apparently the server 
is seeing errors from the client too...

I just realized that when I responded to this thread again on 6/30, I 
neglected to include some new additional/important info regarding this 
issue that happened a couple of weeks after this initial report (about a 
week ago) that leads me to believe that I should be able to troubleshoot 
this, at least to an extent, on the mysql server level...

Per my initial email, these errors were happening randomly for a couple 
of weeks, and only 1 to 3 or 4 times per day...

But a couple of weeks later, my mysql server actually blocked the SOGo 
server completely:

2014-06-29 19:49:01.986 sogo-tool[7566] ERROR: could not open MySQL4 
connection to database 'sogo': Host 'sogo.example.com' is blocked 
because of many connection errors; unblock with 'mysqladmin flush-hosts'

This clearly shows that the mysql server was seeing too many errors from 
the client. I had to log into the mysql server and issue the flush-hosts 
command to restore communication between the two.

But, I cannot find any evidence of any connection errors in 
/var/log/mysql/mysqld.err or any other logs on my mysql server.

So... where should I find these errors that were occurring that caused 
mariadb to block all connections to my SOGo host until I issued the 
flush-hosts command?

The only things in /var/log/mysql/mysqld.err on both sides of the 
date/time that I updated SOGo are:

> 140201  9:59:40 InnoDB: The InnoDB memory heap is disabled
> 140201  9:59:40 InnoDB: Mutexes and rw_locks use GCC atomic builtins
> 140201  9:59:40 InnoDB: Compressed tables use zlib 1.2.7
> 140201  9:59:40 InnoDB: Using Linux native AIO
> 140201  9:59:40 InnoDB: Initializing buffer pool, size = 16.0M
> 140201  9:59:40 InnoDB: Completed initialization of buffer pool
> 140201  9:59:40 InnoDB: highest supported file format is Barracuda.
> 140201  9:59:40  InnoDB: Waiting for the background threads to start
> 140201  9:59:41 Percona XtraDB (http://www.percona.com) 5.5.30-MariaDB-30.1 started; log sequence number 3480883
> 140201  9:59:41 [Warning] /usr/sbin/mysqld: unknown option '--loose-federated'
> 140201  9:59:41 [Note] Event Scheduler: Loaded 0 events
> 140201  9:59:41 [Note] /usr/sbin/mysqld: ready for connections.
> Version: '5.5.30-MariaDB-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Source distribution
> 140614 14:24:40 [Note] /usr/sbin/mysqld: Normal shutdown
>
> 140614 14:24:40 [Note] Event Scheduler: Purging the queue. 0 events
> 140614 14:24:40  InnoDB: Starting shutdown...
> 140614 14:24:41  InnoDB: Shutdown completed; log sequence number 219455836
> 140614 14:24:41 [Note] /usr/sbin/mysqld: Shutdown complete
>
> 140614 14:24:42 [Warning] No argument was provided to --log-bin and neither --log-basename or --log-bin-index where used;  This may cause repliction to break when this server acts as a master and has its h
> ostname changed! Please use '--log-basename=myhost' or '--log-bin=mysqld-bin' to avoid this problem.
> 140614 14:24:42 InnoDB: The InnoDB memory heap is disabled
> 140614 14:24:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins
> 140614 14:24:42 InnoDB: Compressed tables use zlib 1.2.8
> 140614 14:24:42 InnoDB: Using Linux native AIO
> 140614 14:24:42 InnoDB: Initializing buffer pool, size = 16.0M
> 140614 14:24:42 InnoDB: Completed initialization of buffer pool
> 140614 14:24:42 InnoDB: highest supported file format is Barracuda.
> 140614 14:24:42  InnoDB: Waiting for the background threads to start
> 140614 14:24:43 Percona XtraDB (http://www.percona.com) 5.5.37-MariaDB-34.0 started; log sequence number 219455836
> 140614 14:24:43 [Warning] /usr/sbin/mysqld: unknown option '--loose-federated'
> 140614 14:24:43 [Note] Server socket created on IP: '0.0.0.0'.
> 140614 14:24:43 [Note] Event Scheduler: Loaded 0 events
> 140614 14:24:43 [Note] /usr/sbin/mysqld: ready for connections.
> Version: '5.5.37-MariaDB-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Source distribution
> 140615 10:36:21 [Note] /usr/sbin/mysqld: Normal shutdown
>
> 140615 10:36:21 [Note] Event Scheduler: Purging the queue. 0 events
> 140615 10:36:21  InnoDB: Starting shutdown...
> 140615 10:36:22  InnoDB: Shutdown completed; log sequence number 219486293
> 140615 10:36:22 [Note] /usr/sbin/mysqld: Shutdown complete
>
> 140615 10:36:22 [Warning] No argument was provided to --log-bin and neither --log-basename or --log-bin-index where used;  This may cause repliction to break when this server acts as a master and has its h
> ostname changed! Please use '--log-basename=myhost' or '--log-bin=mysqld-bin' to avoid this problem.
> 140615 10:36:22 InnoDB: The InnoDB memory heap is disabled
> 140615 10:36:22 InnoDB: Mutexes and rw_locks use GCC atomic builtins
> 140615 10:36:22 InnoDB: Compressed tables use zlib 1.2.8
> 140615 10:36:22 InnoDB: Using Linux native AIO
> 140615 10:36:22 InnoDB: Initializing buffer pool, size = 16.0M
> 140615 10:36:22 InnoDB: Completed initialization of buffer pool
> 140615 10:36:22 InnoDB: highest supported file format is Barracuda.
> 140615 10:36:22  InnoDB: Waiting for the background threads to start
> 140615 10:36:23 Percona XtraDB (http://www.percona.com) 5.5.37-MariaDB-34.0 started; log sequence number 219486293
> 140615 10:36:23 [Warning] /usr/sbin/mysqld: unknown option '--loose-federated'
> 140615 10:36:23 [Note] Server socket created on IP: '0.0.0.0'.
> 140615 10:36:23 [Note] Event Scheduler: Loaded 0 events
> 140615 10:36:23 [Note] /usr/sbin/mysqld: ready for connections.
> Version: '5.5.37-MariaDB-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Source distribution
> 140701  5:56:47 [Note] /usr/sbin/mysqld: Normal shutdown
>
> 140701  5:56:47 [Note] Event Scheduler: Purging the queue. 0 events
> 140701  5:56:47  InnoDB: Starting shutdown...
> 140701  5:56:48  InnoDB: Shutdown completed; log sequence number 240645473
> 140701  5:56:48 [Note] /usr/sbin/mysqld: Shutdown complete
>
> 140701  5:56:48 [Warning] No argument was provided to --log-bin and neither --log-basename or --log-bin-index where used;  This may cause repliction to break when this server acts as a master and has its hostname changed! Please use '--log-basename=myhost' or '--log-bin=mysqld-bin' to avoid this problem.
> 140701  5:56:48 InnoDB: The InnoDB memory heap is disabled
> 140701  5:56:48 InnoDB: Mutexes and rw_locks use GCC atomic builtins
> 140701  5:56:48 InnoDB: Compressed tables use zlib 1.2.8
> 140701  5:56:48 InnoDB: Using Linux native AIO
> 140701  5:56:48 InnoDB: Initializing buffer pool, size = 16.0M
> 140701  5:56:48 InnoDB: Completed initialization of buffer pool
> 140701  5:56:48 InnoDB: highest supported file format is Barracuda.
> 140701  5:56:48  InnoDB: Waiting for the background threads to start
> 140701  5:56:49 Percona XtraDB (http://www.percona.com) 5.5.37-MariaDB-34.0 started; log sequence number 240645473
> 140701  5:56:49 [Warning] /usr/sbin/mysqld: unknown option '--loose-federated'
> 140701  5:56:49 [Note] Server socket created on IP: '0.0.0.0'.
> 140701  5:56:49 [Note] Event Scheduler: Loaded 0 events
> 140701  5:56:49 [Note] /usr/sbin/mysqld: ready for connections.
> Version: '5.5.37-MariaDB-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Source distribution

Anyone have any ideas on how to proceed troubleshooting this? It is most 
likely just a matter of time until the block happens again, and I'd 
prefer to try to find the problem and fix it, and I'll have better luck 
fixing this on the client side if I can give more details of errors the 
server is seeing from them.

Thanks