[SOLVED] mariadb problem

This forum is dedicated to basic help and support :

Ask here your questions about basic installation and usage of Mageia. For example you may post here all your questions about getting Mageia isos and installing it, configuring your printer, using your word processor etc.

Try to ask your questions in the right sub-forum with as much details as you can gather. the more precise the question will be, the more likely you are to get a useful answer

[SOLVED] mariadb problem

Postby bitit » Nov 30th, '17, 14:32

can't connect in mariadb

[enrico@localhost ~]$
Code: Select all
mysql -u root -p
Enter password:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)

AND
Code: Select all
[root@localhost ~]# mysqld status
2017-11-30 13:29:05 140641586747456 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
2017-11-30 13:29:05 140641586747456 [Note] mysqld (mysqld 10.1.28-MariaDB) starting as process 12697 ...
handlersocket: initialized
2017-11-30 13:29:05 140641586747456 [ERROR] mysqld: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
2017-11-30 13:29:36 140641586747456 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/var/lib/mysql/aria_log_control'
2017-11-30 13:29:36 140641586747456 [ERROR] Plugin 'Aria' init function returned error.
2017-11-30 13:29:36 140641586747456 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2017-11-30 13:29:36 140641586747456 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-11-30 13:29:36 140641586747456 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-11-30 13:29:36 140641586747456 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-30 13:29:36 140641586747456 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-11-30 13:29:36 140641586747456 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-11-30 13:29:36 140641586747456 [Note] InnoDB: Compressed tables use zlib 1.2.11
2017-11-30 13:29:36 140641586747456 [Note] InnoDB: Using Linux native AIO
2017-11-30 13:29:36 140641586747456 [Note] InnoDB: Using SSE crc32 instructions
2017-11-30 13:29:36 140641586747456 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-11-30 13:29:36 140641586747456 [Note] InnoDB: Completed initialization of buffer pool
2017-11-30 13:29:36 140641586747456 [Note] InnoDB: Highest supported file format is Barracuda.
2017-11-30 13:29:36 140641586747456 [Note] InnoDB: 128 rollback segment(s) are active.       
2017-11-30 13:29:36 140641586747456 [Note] InnoDB: Waiting for purge to start                 
2017-11-30 13:29:36 140641586747456 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 1600657                                               
2017-11-30 13:29:36 140641048721152 [Note] InnoDB: Dumping buffer pool(s) not yet started     
2017-11-30 13:29:36 140641586747456 [Warning] mysqld: GSSAPI plugin : default principal 'mariadb/localhost@' not found in keytab                                                           
2017-11-30 13:29:36 140641586747456 [ERROR] mysqld: Server GSSAPI error (major 851968, minor 2529639093) : gss_acquire_cred failed -Unspecified GSS failure.  Minor code may provide more information. Keytab FILE:/etc/krb5.keytab is nonexistent or empty.                             
2017-11-30 13:29:36 140641586747456 [ERROR] Plugin 'gssapi' init function returned error.     
171130 13:29:36 server_audit: MariaDB Audit Plugin version 1.4.2 STARTED.                     
171130 13:29:36 server_audit: Query cache is enabled with the TABLE events. Some table reads can be veiled.mysqld: Too many arguments (first extra is 'status').                           
2017-11-30 13:29:36 140641586747456 [ERROR] Aborting

171130 13:29:36 server_audit: STOPPED
handlersocket: terminated


------------------

some tips?
Thank you
Enrico
Last edited by bitit on Dec 3rd, '17, 20:41, edited 1 time in total.
bitit
 
Posts: 162
Joined: Feb 3rd, '16, 14:01

Re: mariadb problem

Postby filip » Dec 1st, '17, 01:14

Hi there.
In Mageia 6 you MUST use mysql_secure_installation. It was only recommended before.
I just did the procedure bellow due to new install because of DE switch. Note that you can run it as user and there's no password set first so you only press Enter (empty password) as written in script itself.

Code: Select all
$ mysql_secure_installation

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
      SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!

In order to log into MariaDB to secure it, we'll need the current
password for the root user.  If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.

Enter current password for root (enter for none):
OK, successfully used password, moving on...

Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.

Set root password? [Y/n]
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
 ... Success!


By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them.  This is intended only for testing, and to make the installation
go a bit smoother.  You should remove them before moving into a
production environment.

Remove anonymous users? [Y/n]
 ... Success!

Normally, root should only be allowed to connect from 'localhost'.  This
ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? [Y/n]
 ... Success!

By default, MariaDB comes with a database named 'test' that anyone can
access.  This is also intended only for testing, and should be removed
before moving into a production environment.

Remove test database and access to it? [Y/n]
 - Dropping test database...
 ... Success!
 - Removing privileges on test database...
 ... Success!

Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.

Reload privilege tables now? [Y/n]
 ... Success!

Cleaning up...

All done!  If you've completed all of the above steps, your MariaDB
installation should now be secure.

Thanks for using MariaDB!
$
filip
 
Posts: 478
Joined: May 4th, '11, 22:10
Location: Kranj, Slovenia

Re: mariadb problem

Postby bitit » Dec 1st, '17, 11:56

ok, thank you, so i can connect by shell and by phpmyadmin , but not by MySqlworkbench reply 111 connection refused
and i have a lot of bed log in mysql restart
Code: Select all
mysqld restart
2017-12-01 10:44:38 139842036406336 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
2017-12-01 10:44:38 139842036406336 [Note] mysqld (mysqld 10.1.28-MariaDB) starting as process 6866 ...
handlersocket: initialized
2017-12-01 10:44:38 139842036406336 [Note] CONNECT: Version 1.06.0004 September 03, 2017
2017-12-01 10:44:38 139842036406336 [ERROR] mysqld: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
2017-12-01 10:45:09 139842036406336 [ERROR] mysqld: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/var/lib/mysql/aria_log_control'
2017-12-01 10:45:09 139842036406336 [ERROR] Plugin 'Aria' init function returned error.
2017-12-01 10:45:09 139842036406336 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2017-12-01 10:45:09 139842036406336 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2017-12-01 10:45:10 139842036406336 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-12-01 10:45:10 139842036406336 [Note] InnoDB: The InnoDB memory heap is disabled
2017-12-01 10:45:10 139842036406336 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-12-01 10:45:10 139842036406336 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2017-12-01 10:45:10 139842036406336 [Note] InnoDB: Compressed tables use zlib 1.2.11
2017-12-01 10:45:10 139842036406336 [Note] InnoDB: Using Linux native AIO
2017-12-01 10:45:10 139842036406336 [Note] InnoDB: Using SSE crc32 instructions
2017-12-01 10:45:10 139842036406336 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-12-01 10:45:10 139842036406336 [Note] InnoDB: Completed initialization of buffer pool
2017-12-01 10:45:10 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:10 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:10 139842036406336 [Note] InnoDB: Retrying to lock the first data file
2017-12-01 10:45:11 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:11 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:12 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:12 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:13 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:13 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:14 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:14 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:15 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:15 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:16 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:16 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:17 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:17 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:18 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:18 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:19 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:19 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:20 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:20 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:21 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:21 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:22 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:22 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:23 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:23 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:24 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:24 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:25 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:25 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:26 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:26 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:27 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:27 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:28 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:28 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:29 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:29 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:30 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:30 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:31 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:31 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:32 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:32 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:33 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:33 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:34 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:34 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:35 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:35 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:36 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:36 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:37 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:37 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:38 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:38 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:39 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:39 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:40 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:40 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:41 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:41 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:42 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:42 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:43 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:43 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:44 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:44 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:45 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:45 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:46 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:46 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:47 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:47 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:48 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:48 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:49 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:49 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:50 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:50 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:51 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:51 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:52 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:52 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:53 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:53 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
^C2017-12-01 10:45:54 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:54 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:55 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:55 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:56 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:56 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:57 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:57 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:58 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:58 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:45:59 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:45:59 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:00 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:00 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:01 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:01 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:02 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:02 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:03 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:03 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:04 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:04 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:05 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:05 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:06 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:06 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:07 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:07 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:08 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:08 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:09 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:09 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:10 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:10 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:11 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:11 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:12 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:12 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:13 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:13 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:14 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:14 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:15 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:15 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:16 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:16 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:17 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:17 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:18 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:18 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:19 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:19 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:20 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:20 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:21 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:21 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:22 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:22 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:23 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:23 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:24 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:24 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:25 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:25 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:26 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:26 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:27 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:27 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:28 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:28 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:29 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:29 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:30 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:30 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:31 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:31 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:32 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:32 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:33 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:33 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:34 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:34 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:35 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:35 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:36 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:36 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:37 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:37 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:38 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:38 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:39 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:39 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:40 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:40 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:41 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:41 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:42 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:42 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:43 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:43 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:44 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:44 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:45 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:45 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:46 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:46 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:47 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:47 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:48 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:48 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:49 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:49 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:50 139842036406336 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
2017-12-01 10:46:50 139842036406336 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
2017-12-01 10:46:50 139842036406336 [Note] InnoDB: Unable to open the first data file
2017-12-01 10:46:50 7f2f82e79840  InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2017-12-01 10:46:50 139842036406336 [ERROR] InnoDB: Can't open './ibdata1'
2017-12-01 10:46:50 139842036406336 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2017-12-01 10:46:50 139842036406336 [ERROR] Plugin 'InnoDB' init function returned error.
2017-12-01 10:46:50 139842036406336 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-12-01 10:46:50 139842036406336 [Warning] mysqld: GSSAPI plugin : default principal 'mariadb/localhost@' not found in keytab
2017-12-01 10:46:50 139842036406336 [ERROR] mysqld: Server GSSAPI error (major 851968, minor 2529639093) : gss_acquire_cred failed -Unspecified GSS failure.  Minor code may provide more information. Keytab FILE:/etc/krb5.keytab is nonexistent or empty.
2017-12-01 10:46:50 139842036406336 [ERROR] Plugin 'gssapi' init function returned error.
171201 10:46:50 server_audit: MariaDB Audit Plugin version 1.4.2 STARTED.
171201 10:46:50 server_audit: Query cache is enabled with the TABLE events. Some table reads can be veiled.mysqld: Too many arguments (first extra is 'restart').
2017-12-01 10:46:50 139842036406336 [ERROR] Aborting

171201 10:46:50 server_audit: STOPPED
handlersocket: terminated

bitit
 
Posts: 162
Joined: Feb 3rd, '16, 14:01

Re: mariadb problem

Postby bitit » Dec 1st, '17, 16:07

and don't find the mysql port
Code: Select all
nmap localhost

Starting Nmap 7.40 ( https://nmap.org ) at 2017-12-01 15:04 CET
Nmap scan report for localhost (127.0.0.1)
Host is up (0.00012s latency).
Other addresses for localhost (not scanned): ::1
Not shown: 993 closed ports
PORT     STATE SERVICE
21/tcp   open  ftp
80/tcp   open  http
111/tcp  open  rpcbind
631/tcp  open  ipp
783/tcp  open  spamassassin
1720/tcp open  h323q931
2049/tcp open  nfs

Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds
bitit
 
Posts: 162
Joined: Feb 3rd, '16, 14:01

Re: mariadb problem

Postby bitit » Dec 1st, '17, 16:15

Code: Select all
service mysqld status
Redirecting to /bin/systemctl status mysqld.service
● mysqld.service - MySQL database server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: enabled)
   Active: active (running) since ven 2017-12-01 14:24:20 CET; 49min ago
  Process: 1595 ExecStartPre=/usr/sbin/mysqld-prepare-db-dir (code=exited, status=0/SUCCESS)
 Main PID: 1852 (mysqld)
   Status: "Taking your SQL requests now..."
   CGroup: /system.slice/mysqld.service
           └─1852 /usr/sbin/mysqld

dic 01 14:24:20 localhost mysqld[1852]: 2017-12-01 14:24:20 139941059033152 [ERROR] mysqld: Server GSSAPI error (major 851968, minor 2529639093) : g
dic 01 14:24:20 localhost mysqld[1852]: 2017-12-01 14:24:20 139941059033152 [ERROR] Plugin 'gssapi' init function returned error.
dic 01 14:24:20 localhost mysqld[1852]: 171201 14:24:20 server_audit: MariaDB Audit Plugin version 1.4.2 STARTED.
dic 01 14:24:20 localhost mysqld[1852]: 171201 14:24:20 server_audit: Query cache is enabled with the TABLE events. Some table reads can be veiled.2
dic 01 14:24:20 localhost mysqld[1852]: 2017-12-01 14:24:20 139941058411264 [Warning] Failed to load slave replication state from table mysql.gtid_s
dic 01 14:24:20 localhost mysqld[1852]: 2017-12-01 14:24:20 139941059033152 [Note] /usr/sbin/mysqld: ready for connections.
dic 01 14:24:20 localhost mysqld[1852]: Version: '10.1.28-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 0  Mageia MariaDB Server
dic 01 14:24:20 localhost systemd[1]: Started MySQL database server.
dic 01 14:29:21 localhost mysqld[1852]: 2017-12-01 14:29:21 139940344100608 [Note] feedback plugin: report to 'https://mariadb.org/feedback_plugin/p
dic 01 14:29:21 localhost mysqld[1852]: 2017-12-01 14:29:21 139940344100608 [Note] feedback plugin: server replied 'ok'
bitit
 
Posts: 162
Joined: Feb 3rd, '16, 14:01

Re: mariadb problem

Postby bitit » Dec 1st, '17, 19:21

ok have commented
Code: Select all
#-skip-networking


in /etc/my.cnf

reload the service and now i see the port 3306

remaining : GSSAPI error

enrico
bitit
 
Posts: 162
Joined: Feb 3rd, '16, 14:01

Re: mariadb problem

Postby wintpe » Dec 3rd, '17, 12:08

gssapi is kerberos, its looking to see if you have a kerberos ticket.
are you running kerberos?
if not something is making it think you are.
regards peter
Redhat 6 Certified Engineer (RHCE)
Sometimes my posts will sound short, or snappy, however its realy not my intention to offend, so accept my apologies in advance.
wintpe
 
Posts: 1204
Joined: May 22nd, '11, 17:08
Location: Rayleigh,, Essex , UK

Re: mariadb problem

Postby doktor5000 » Dec 3rd, '17, 15:19

sshd will also do that by default for incoming connections, that's not something I'd worry about.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 18054
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: mariadb problem

Postby bitit » Dec 3rd, '17, 20:39

kerberos?
no, i haven't installed nothing about .

enrico
bitit
 
Posts: 162
Joined: Feb 3rd, '16, 14:01

Re: mariadb problem

Postby bitit » Dec 3rd, '17, 20:41

doktor5000 wrote:sshd will also do that by default for incoming connections, that's not something I'd worry about.


ok Thank you :)

Enrico
bitit
 
Posts: 162
Joined: Feb 3rd, '16, 14:01


Return to Basic support

Who is online

Users browsing this forum: No registered users and 1 guest

cron