MaridDB warning

Bugs in eFa 4
Post Reply
samrein
Posts: 28
Joined: 04 May 2018 08:41

MaridDB warning

Post by samrein » 19 Jul 2021 07:27

Hello,

since two days i have the fallow message in mariadb log:

Code: Select all

2021-07-19  8:44:30 140352889427712 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  8:44:39 140352888813312 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  8:47:47 140352889120512 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  8:48:03 140352889427712 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  8:48:32 140352889120512 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  8:51:15 140352889427712 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  8:51:15 140352889120512 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  8:51:15 140352892098304 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  8:51:37 140352889120512 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  8:53:37 140352889427712 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  8:53:37 140352892098304 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  8:57:07 140352889120512 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  8:58:22 140352889427712 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  8:58:23 140352892098304 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  8:59:39 140352888813312 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  8:59:39 140352889427712 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  9:00:22 140352889120512 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  9:01:56 140352889427712 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  9:02:43 140352889120512 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  9:07:40 140352889427712 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  9:08:23 140352889120512 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  9:08:36 140352892098304 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  9:09:03 140352889427712 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  9:10:18 140352888813312 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  9:11:23 140352892098304 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  9:11:23 140352889120512 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  9:14:46 140352892098304 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  9:14:56 140352889120512 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  9:15:55 140352888813312 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  9:16:05 140352889427712 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
2021-07-19  9:17:10 140352888813312 [Warning] Access denied for user 'efa'@'localhost' (using password: NO)
I dont have do any changes. I see the message:

Code: Select all

2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Uses event mutexes
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Compressed tables use zlib 1.2.7
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Using Linux native AIO
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Number of pools: 1
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Using SSE2 crc32 instructions
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Completed initialization of buffer pool
2021-07-18  9:19:03 139742151595776 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Highest supported file format is Barracuda.
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Upgrading redo log: 2*50331648 bytes; LSN=20376536801
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Starting to delete and rewrite log files.
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Setting log file ./ib_logfile101 size to 50331648 bytes
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Setting log file ./ib_logfile1 size to 50331648 bytes
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: New log files created, LSN=20376536801
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: 128 out of 128 rollback segments are active.
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Creating sys_virtual system tables.
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Creating shared tablespace for temporary tables
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: Waiting for purge to start
2021-07-18  9:19:03 139742709614784 [Note] InnoDB: 5.7.28 started; log sequence number 20376536801
2021-07-18  9:19:03 139741911570176 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2021-07-18  9:19:03 139741911570176 [Note] InnoDB: Cannot open '/var/lib/mysql/ib_buffer_pool' for reading: No such file or directory
2021-07-18  9:19:03 139742709614784 [Note] Plugin 'FEEDBACK' is disabled.
2021-07-18  9:19:03 139742709614784 [Note] Server socket created on IP: '::'.
2021-07-18  9:19:03 139742476560128 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:03 139742476560128 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:03 139742709614784 [Note] Reading of all Master_info entries succeeded
2021-07-18  9:19:03 139742709614784 [Note] Added new Master_info '' to hash table
2021-07-18  9:19:03 139742709614784 [Note] /usr/libexec/mysqld: ready for connections.
Version: '10.2.30-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
2021-07-18  9:19:05 139742475945728 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:05 139742475945728 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:05 139742475945728 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:05 139742475945728 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:05 139742475638528 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:05 139742475638528 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:06 139742476252928 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:06 139742476252928 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:07 139742475331328 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:07 139742475331328 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:07 139742475331328 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:07 139742475331328 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:07 139742475331328 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:07 139742475331328 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:08 139742475331328 [Warning] InnoDB: Table mysql/innodb_table_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
2021-07-18  9:19:08 139742475331328 [Warning] InnoDB: Table mysql/innodb_index_stats has length mismatch in the column name table_name.  Please run mysql_upgrade
Can i run mysql_upgrade without problems?

i'm not that deep in the centos system.

Greetings Stefan

Mr. Happy
Posts: 50
Joined: 03 Jan 2014 17:07

Re: MaridDB warning

Post by Mr. Happy » 29 Jul 2021 21:34

do you have an efa-account on your mysql?
Some time ago I had the same error and I (re?)created the account. Do not know if I needed to, but it took care of the message...

samrein
Posts: 28
Joined: 04 May 2018 08:41

Re: MaridDB warning

Post by samrein » 30 Jul 2021 06:05

Hey Herr Happy,

Shawan answers me on slack channel.

Code: Select all

Just to allay any concerns this account is for a little used feature, so it isn't going to hurt anything that it is having an access problem. It is used in /usr/share/MailScanner/perl/custom/CustomAction.pm and a cron script.
The user is exist, and i am setting the password in /etc/eFa/eFa-Config, without any changes.

Regards
Stefan

Mr. Happy
Posts: 50
Joined: 03 Jan 2014 17:07

Re: MaridDB warning

Post by Mr. Happy » 30 Jul 2021 10:45

Hi Stefan,

Thanks for your feedback.
I think whether it is used often or not it should work and more importantly not create any warnings/errors...
That's the reason I added it to the configuration as well...

Post Reply