[MDEV-10241] Error in Flush Logs Created: 2016-06-15  Updated: 2016-06-16

Status: Open
Project: MariaDB Server
Component/s: Admin statements
Affects Version/s: 5.5, 10.0, 10.1, 10.2
Fix Version/s: 10.2

Type: Bug Priority: Minor
Reporter: Diego Hellas Assignee: Sergei Golubchik
Resolution: Unresolved Votes: 0
Labels: None
Environment:

CentOS 7
10.1.14-MariaDB MariaDB Server

Attachments: Text File show_variables.txt    

 Description   

I'm trying to rotate the logs, but this error is preventing me. This error occurs both in version 10.1.13 and in 10.1.14.

MariaDB [(none)]> flush logs;
 
ERROR 1105 (HY000): Unknown error


MariaDB [(none)]> status;
 
--------------
 
mysql  Ver 15.1 Distrib 10.1.14-MariaDB, for Linux (x86_64) using readline 5.1
 
 
 
Connection id:          4
 
Current database:
 
Current user:           root@localhost
 
SSL:                    Not in use
 
Current pager:          stdout
 
Using outfile:          ''
 
Using delimiter:        ;
 
Server:                 MariaDB
 
Server version:         10.1.14-MariaDB MariaDB Server
 
Protocol version:       10
 
Connection:             Localhost via UNIX socket
 
Server characterset:    latin1
 
Db     characterset:    latin1
 
Client characterset:    utf8
 
Conn.  characterset:    utf8
 
UNIX socket:            /var/lib/mysql/mysql.sock
 
Uptime:                 1 hour 29 min 36 sec
 
 
 
Threads: 1  Questions: 9  Slow queries: 0  Opens: 17  Flush tables: 1  Open tables: 11  Queries per second avg: 0.001
 
--------------



 Comments   
Comment by Diego Hellas [ 2016-06-15 ]

I found the poblem.

In my /etc/my.cnf.d/server.cnf
I having this line:
log_error=/var/log/rmaria01-error.log
But this file(/var/log/rmaria01-error.log) not exists.

I change /etc/my.cnf.d/server.cnf
log_error=rmaria01-error.log
And Wroks

Comment by Diego Hellas [ 2016-06-15 ]

I think this bug can be closed.

Comment by Elena Stepanova [ 2016-06-16 ]

Yes, it is a configuration problem, but I wonder if it's possible to return a more sensible error message in this case; so I'll keep it open for consideration.

Comment by Diego Hellas [ 2016-06-16 ]

Agree, better error memsagem will be able to have helped me find the problem more easily.
It also has the fact because he had no error returned to start the MariaDB Server service, since it failed to create the error file defined in the configuration.

Generated at Thu Feb 08 07:40:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.