Closed issue by zedmango on void-packages repository

https://github.com/void-linux/void-packages/issues/29297

Description:
When I updated, and it switched everything to OpenSSL, I got some errors. For some reason it made me switch from MySQL to MariaDB :(

Now it won't complete the install - it says it's already done

Please help me update...

Here's what it said:


    mariadb-client-10.1.48_2: configuring ...
    mariadb-client-10.1.48_2: installed successfully.
    mariadb-10.1.48_2: configuring ...
    Updated mysql system user.
    WARNING: The host 'enigmatic' could not be looked up with /usr/bin/resolveip.
    This probably means that your libc libraries are not 100 % compatible
    with this binary MariaDB version. The MariaDB daemon, mysqld, should work
    normally with the exception that host name resolving will not work.
    This means that you should use IP addresses instead of hostnames
    when specifying MariaDB privileges !
    Installing MariaDB/MySQL system tables in '/var/lib/mysql' ...
    2021-03-07 16:25:16 3079522048 [Note] /usr/bin/mysqld (mysqld 10.1.48-MariaDB) starting as process 14759 ...
    2021-03-07 16:25:16 3079522048 [ERROR] mysqld: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
    2021-03-07 16:25:47 3079522048 [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'
    2021-03-07 16:25:47 3079522048 [ERROR] Plugin 'Aria' init function returned error.
    2021-03-07 16:25:47 3079522048 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
    2021-03-07 16:25:47 3079522048 [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.

    2021-03-07 16:25:47 3079522048 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    2021-03-07 16:25:47 3079522048 [Note] InnoDB: The InnoDB memory heap is disabled
    2021-03-07 16:25:47 3079522048 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    2021-03-07 16:25:47 3079522048 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
    2021-03-07 16:25:47 3079522048 [Note] InnoDB: Compressed tables use zlib 1.2.11
    2021-03-07 16:25:47 3079522048 [Note] InnoDB: Using generic crc32 instructions
    2021-03-07 16:25:47 3079522048 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    2021-03-07 16:25:47 3079522048 [Note] InnoDB: Completed initialization of buffer pool
    2021-03-07 16:25:47 3079522048 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
    2021-03-07 16:25:47 3079522048 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
    2021-03-07 16:25:47 3079522048 [Note] InnoDB: Retrying to lock the first data file
    2021-03-07 16:25:48 3079522048 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
    2021-03-07 16:25:48 3079522048 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
    2021-03-07 16:25:49 3079522048 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
    2021-03-07 16:25:49 3079522048 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
    2021-03-07 16:25:50 3079522048 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11

Then the last two lines repeated many times, and then:


    2021-03-07 16:27:28 3079522048 [ERROR] InnoDB: Unable to lock ./ibdata1, error: 11
    2021-03-07 16:27:28 3079522048 [Note] InnoDB: Check that you do not already have another mysqld process using the same InnoDB data or log files.
    2021-03-07 16:27:28 3079522048 [Note] InnoDB: Unable to open the first data file
    2021-03-07 16:27:28 b78dc700  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
    2021-03-07 16:27:28 3079522048 [ERROR] InnoDB: Can't open './ibdata1'
    2021-03-07 16:27:28 3079522048 [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!
    2021-03-07 16:27:28 3079522048 [ERROR] Plugin 'InnoDB' init function returned error.
    2021-03-07 16:27:28 3079522048 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
    2021-03-07 16:27:28 3079522048 [ERROR] Unknown/unsupported storage engine: InnoDB
    2021-03-07 16:27:28 3079522048 [ERROR] Aborting
    
    ^C
    $ ^C

And even though I cut it off in the middle, it won't update any of the packages that come after mariadb alphabetically - it just says they're already done!

    $ sudo xbps-install -Su
    [*] Updating repository `https://alpha.de.repo.voidlinux.org/current/i686-repodata' ...
    $
    $ sudo xbps-install mdcat
    Package `mdcat' already installed.
    $ sudo xbps-install openssh
    Package `openssh' already installed.
    $ sudo xbps-install rsync
    Package `rsync' already installed.
    $