[ansible@focal] role epgd: mariadb startet nicht

danielweidner · 13. Juni 2020

Hi!

Nun das nächste Problem:

Wärend der Instakation der Rolle epgd startet MaraDB nicht:

Code

dw@vdr:~/yavdr-ansible$ sudo -H ansible-playbook yavdr07.yml -b -i 'localhost_inventory' --connection=local --tags="epgd"
[sudo] password for dw: 

PLAY [set up yaVDR] **************************************************************************************************

TASK [Gathering Facts] ***********************************************************************************************
ok: [localhost]

TASK [collect-facts : get information about usb and pci hardware and loaded kernel modules] **************************
ok: [localhost]

TASK [collect-facts : get detailed PCI device information] ***********************************************************
ok: [localhost]

TASK [epgd : MariaDB and Plugin | install] ***************************************************************************
changed: [localhost]

TASK [epgd : copy file | epgd mariadb config] ************************************************************************
ok: [localhost]

TASK [epgd : create /root/.ssh if it doesn't exist yes] **************************************************************
ok: [localhost]

TASK [epgd : copy file | mysqlpasswd] ********************************************************************************
changed: [localhost]

TASK [epgd : Restart mariadb] ****************************************************************************************
fatal: [localhost]: FAILED! => {
    "changed": false
}

MSG:

Unable to start service mariadb.service: Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.


PLAY RECAP ***********************************************************************************************************
localhost                  : ok=7    changed=2    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0   

dw@vdr:~/yavdr-ansible$ ^C
dw@vdr:~/yavdr-ansible$ systemctl status mariadb.service
● mariadb.service - MariaDB 10.3.22 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sat 2020-06-13 11:35:39 CEST; 13s ago
       Docs: man:mysqld(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 2384 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUC>
    Process: 2385 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SU>
    Process: 2386 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recover>
    Process: 2395 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, st>
   Main PID: 2395 (code=exited, status=1/FAILURE)

Jun 13 11:35:39 vdr systemd[1]: Starting MariaDB 10.3.22 database server...
Jun 13 11:35:39 vdr mysqld[2395]: [98B blob data]
Jun 13 11:35:39 vdr mysqld[2395]: Fatal error in defaults handling. Program aborted
Jun 13 11:35:39 vdr systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 11:35:39 vdr systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jun 13 11:35:39 vdr systemd[1]: Failed to start MariaDB 10.3.22 database server.
lines 1-17/17 (END)...skipping...
● mariadb.service - MariaDB 10.3.22 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sat 2020-06-13 11:35:39 CEST; 13s ago
       Docs: man:mysqld(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 2384 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUC>
    Process: 2385 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SU>
    Process: 2386 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recover>
    Process: 2395 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, st>
   Main PID: 2395 (code=exited, status=1/FAILURE)

Jun 13 11:35:39 vdr systemd[1]: Starting MariaDB 10.3.22 database server...
Jun 13 11:35:39 vdr mysqld[2395]: [98B blob data]
Jun 13 11:35:39 vdr mysqld[2395]: Fatal error in defaults handling. Program aborted
Jun 13 11:35:39 vdr systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 11:35:39 vdr systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jun 13 11:35:39 vdr systemd[1]: Failed to start MariaDB 10.3.22 database server.
dw@vdr:~/yavdr-ansible$ journalctl -xe
Jun 13 11:35:38 vdr python3[2366]: ansible-stat Invoked with path=/root/.ssh/mysqlpasswd follow=False get_checksum=Tr>
Jun 13 11:35:38 vdr python3[2371]: ansible-copy Invoked with src=/root/.ansible/tmp/ansible-tmp-1592040938.537531-214>
Jun 13 11:35:39 vdr python3[2378]: ansible-systemd Invoked with name=mariadb.service state=restarted enabled=True mas>
Jun 13 11:35:39 vdr systemd[1]: Starting MariaDB 10.3.22 database server...
-- Subject: A start job for unit mariadb.service has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit mariadb.service has begun execution.
-- 
-- The job identifier is 1399.
Jun 13 11:35:39 vdr sh[2392]: [108B blob data]
Jun 13 11:35:39 vdr sh[2392]: Fatal error in defaults handling. Program aborted
Jun 13 11:35:39 vdr mysqld[2395]: [98B blob data]
Jun 13 11:35:39 vdr mysqld[2395]: Fatal error in defaults handling. Program aborted
Jun 13 11:35:39 vdr systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- An ExecStart= process belonging to unit mariadb.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
Jun 13 11:35:39 vdr systemd[1]: mariadb.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- The unit mariadb.service has entered the 'failed' state with result 'exit-code'.
Jun 13 11:35:39 vdr systemd[1]: Failed to start MariaDB 10.3.22 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- A start job for unit mariadb.service has finished with a failure.
-- 
-- The job identifier is 1399 and the job result is failed.

Alles anzeigen

An was liegt das?

Daniel

seahawk1986 · 13. Juni 2020

Zitat von danielweidner

An was liegt das?

Leider ist die Ausgabe wohl aus less in einem zu kleinen Fenster kopiert und da fehlt etwas am rechten Rand.

Hier in einer frisch aufgesetzten VM für focal ist die Rolle für epgd brav durchgelaufen und mariadb lässt sich ohne Probleme neu starten.

Zitat von danielweidner

Jun 13 11:35:39 vdr mysqld[2395]: Fatal error in defaults handling. Program aborted

Das sieht fast so aus, als ob da etwas mit den Konfigurationsdateien nicht passt. Hast du an den Rechten von Dateien und Ordnern in /etc, /var oder /usr etwas verändert?

Vielleicht sieht man in der Ungekürzten Ausgabe noch etwas mehr:

Code

systemctl status mariadb.service -l --no-pager
journalctl -u mariadb -l -b --no-pager

danielweidner · 13. Juni 2020

An den Rechten habe ich (bewusst) nichts geändert

Code

dw@vdr:~$ systemctl status mariadb.service -l --no-pager
● mariadb.service - MariaDB 10.3.22 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sat 2020-06-13 11:35:39 CEST; 1h 14min ago
       Docs: man:mysqld(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 2384 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 2385 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 2386 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
    Process: 2395 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
   Main PID: 2395 (code=exited, status=1/FAILURE)

Jun 13 11:35:39 vdr systemd[1]: Starting MariaDB 10.3.22 database server...
Jun 13 11:35:39 vdr mysqld[2395]: [98B blob data]
Jun 13 11:35:39 vdr mysqld[2395]: Fatal error in defaults handling. Program aborted
Jun 13 11:35:39 vdr systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 11:35:39 vdr systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jun 13 11:35:39 vdr systemd[1]: Failed to start MariaDB 10.3.22 database server.
dw@vdr:~$ systemctl status mariadb.service -l --no-pager
● mariadb.service - MariaDB 10.3.22 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sat 2020-06-13 11:35:39 CEST; 1h 15min ago
       Docs: man:mysqld(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 2384 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 2385 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 2386 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
    Process: 2395 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
   Main PID: 2395 (code=exited, status=1/FAILURE)

Jun 13 11:35:39 vdr systemd[1]: Starting MariaDB 10.3.22 database server...
Jun 13 11:35:39 vdr mysqld[2395]: [98B blob data]
Jun 13 11:35:39 vdr mysqld[2395]: Fatal error in defaults handling. Program aborted
Jun 13 11:35:39 vdr systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 11:35:39 vdr systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jun 13 11:35:39 vdr systemd[1]: Failed to start MariaDB 10.3.22 database server.

Alles anzeigen

Code

dw@vdr:~$ systemctl status mariadb.service -l --no-pager
● mariadb.service - MariaDB 10.3.22 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sat 2020-06-13 11:35:39 CEST; 1h 15min ago
       Docs: man:mysqld(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 2384 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 2385 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 2386 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
    Process: 2395 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
   Main PID: 2395 (code=exited, status=1/FAILURE)

Jun 13 11:35:39 vdr systemd[1]: Starting MariaDB 10.3.22 database server...
Jun 13 11:35:39 vdr mysqld[2395]: [98B blob data]
Jun 13 11:35:39 vdr mysqld[2395]: Fatal error in defaults handling. Program aborted
Jun 13 11:35:39 vdr systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 11:35:39 vdr systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jun 13 11:35:39 vdr systemd[1]: Failed to start MariaDB 10.3.22 database server.
dw@vdr:~$ journalctl -u mariadb -l -b --no-pager
-- Logs begin at Thu 2020-06-11 10:48:48 CEST, end at Sat 2020-06-13 12:51:11 CEST. --
Jun 13 11:35:35 vdr systemd[1]: Starting MariaDB 10.3.22 database server...
Jun 13 11:35:35 vdr mysqld[2086]: [98B blob data]
Jun 13 11:35:35 vdr mysqld[2086]: Fatal error in defaults handling. Program aborted
Jun 13 11:35:35 vdr systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 11:35:35 vdr systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jun 13 11:35:35 vdr systemd[1]: Failed to start MariaDB 10.3.22 database server.
Jun 13 11:35:39 vdr systemd[1]: Starting MariaDB 10.3.22 database server...
Jun 13 11:35:39 vdr mysqld[2395]: [98B blob data]
Jun 13 11:35:39 vdr mysqld[2395]: Fatal error in defaults handling. Program aborted
Jun 13 11:35:39 vdr systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 11:35:39 vdr systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jun 13 11:35:39 vdr systemd[1]: Failed to start MariaDB 10.3.22 database server.
dw@vdr:~$

Alles anzeigen

seahawk1986 · 13. Juni 2020

Was gibt es denn bei dir für Dateien in /etc/mysql?

Code

tree -puh /etc/mysql

danielweidner · 13. Juni 2020

Code

dw@vdr:~$     tree -puh /etc/mysql
/etc/mysql
├── [-rw------- root      261]  debian.cnf
├── [-rwxr-xr-x root     1.6K]  debian-start
├── [-rw-r--r-- root      869]  mariadb.cnf
├── [drwxr-xr-x root     4.0K]  mariadb.conf.d
│   ├── [-rw-r--r-- root      733]  50-client.cnf
│   ├── [-rw-r--r-- root      336]  50-mysql-clients.cnf
│   ├── [-rw-r--r-- root     1.0K]  50-mysqld_safe.cnf
│   ├── [-rw-r--r-- root     3.8K]  50-server.cnf
│   └── [-rw-r--r-- root      175]  99-epgd.cnf
└── [lrwxrwxrwx root       24]  my.cnf -> /etc/alternatives/my.cnf

1 directory, 9 files

Alles anzeigen

seahawk1986 · 13. Juni 2020

Da fehlt gegenüber meiner VM das Verzeichnis /etc/mysql/conf.d, das über die /etc/alternatives/my.cnf inkludiert wird:

Code: /etc/alternatives/my.cnf

# The MariaDB configuration file
#
# The MariaDB/MySQL tools read configuration files in the following order:
# 1. "/etc/mysql/mariadb.cnf" (this file) to set global defaults,
# 2. "/etc/mysql/conf.d/*.cnf" to set global options.
# 3. "/etc/mysql/mariadb.conf.d/*.cnf" to set MariaDB-only options.
# 4. "~/.my.cnf" to set user-specific options.
#
# If the same option is defined multiple times, the last one will apply.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.

#
# This group is read both both by the client and the server
# use it for options that affect everything
#
[client-server]

# Import all .cnf files from configuration directory
!includedir /etc/mysql/conf.d/
!includedir /etc/mysql/mariadb.conf.d/

Alles anzeigen

Also würde ich mal versuchen diese beiden Dateien zu ergänzen:

Code: /etc/mysql/conf.d/mysql.cnf

[mysql]

Code: /etc/mysql/conf.d/mysqldump.cnf

[mysqldump]
quick
quote-names
max_allowed_packet      = 16M

danielweidner · 13. Juni 2020

Hab ich alles ergänzt.

Wenn ich das Playbook laufen lasse, kommt im syslog folgendes:

Code

Jun 13 15:04:54 vdr python3[9589]: ansible-setup Invoked with gather_subset=['all'] gather_timeout=10 filter=* fact_path=/etc/ansible/facts.d
Jun 13 15:04:55 vdr python3[9649]: ansible-hardware_facts Invoked with usb=True pci=True serial=True modules=True gpus=True acpi_power_modes=True
Jun 13 15:04:55 vdr python3[9657]: ansible-pci_facts Invoked
Jun 13 15:04:55 vdr python3[9663]: ansible-apt Invoked with name=['mariadb-server', 'mariadb-plugin-epglv', 'python3-pymysql'] state=present package=['mariadb-server', 'mariadb-plugin-epglv', 'python3-pymysql'] cache_valid_time=0 purge=False force=False dpkg_options=force-confdef,force-confold autoremove=False autoclean=False only_upgrade=False force_apt_get=False allow_unauthenticated=False update_cache=None deb=None default_release=None install_recommends=None upgrade=None policy_rc_d=None
Jun 13 15:04:56 vdr python3[9680]: ansible-stat Invoked with path=/etc/mysql/mariadb.conf.d/99-epgd.cnf follow=False get_checksum=True checksum_algorithm=sha1 get_md5=False get_mime=True get_attributes=True
Jun 13 15:04:56 vdr python3[9685]: ansible-file Invoked with owner=root group=root mode=None follow=False dest=/etc/mysql/mariadb.conf.d/99-epgd.cnf _original_basename=etc_mysql_mariadb.conf.d_99-epgd.cnf.j2 recurse=False state=file path=/etc/mysql/mariadb.conf.d/99-epgd.cnf force=False modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None content=NOT_LOGGING_PARAMETER backup=None remote_src=None regexp=None delimiter=None directory_mode=None unsafe_writes=None
Jun 13 15:04:57 vdr python3[9692]: ansible-file Invoked with path=/root/.ssh state=directory owner=root group=root mode=448 recurse=False force=False follow=True modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S _original_basename=None _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None content=NOT_LOGGING_PARAMETER backup=None remote_src=None regexp=None delimiter=None directory_mode=None unsafe_writes=None
Jun 13 15:04:57 vdr python3[9703]: ansible-stat Invoked with path=/root/.ssh/mysqlpasswd follow=False get_checksum=True checksum_algorithm=sha1 get_md5=False get_mime=True get_attributes=True
Jun 13 15:04:57 vdr python3[9708]: ansible-file Invoked with owner=root group=root mode=384 follow=False dest=/root/.ssh/mysqlpasswd _original_basename=root_.ssh_mysqlpasswd.j2 recurse=False state=file path=/root/.ssh/mysqlpasswd force=False modification_time_format=%Y%m%d%H%M.%S access_time_format=%Y%m%d%H%M.%S _diff_peek=None src=None modification_time=None access_time=None seuser=None serole=None selevel=None setype=None attributes=None content=NOT_LOGGING_PARAMETER backup=None remote_src=None regexp=None delimiter=None directory_mode=None unsafe_writes=None
Jun 13 15:04:57 vdr python3[9715]: ansible-systemd Invoked with name=mariadb.service state=restarted enabled=True masked=False daemon_reload=False daemon_reexec=False no_block=False force=None user=None scope=None
Jun 13 15:04:57 vdr systemd[1]: Starting MariaDB 10.3.22 database server...
Jun 13 15:04:57 vdr mysqld[9787]: 2020-06-13 15:04:57 0 [Note] /usr/sbin/mysqld (mysqld 10.3.22-MariaDB-1ubuntu1) starting as process 9787 ...
Jun 13 15:04:58 vdr systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 15:04:58 vdr systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jun 13 15:04:58 vdr systemd[1]: Failed to start MariaDB 10.3.22 database server.
Jun 13 15:05:01 vdr vdr: video:  8:31:18.349  +35 7196 240/\ms 182+6+4 v-buf

Alles anzeigen

Code

dw@vdr:~/yavdr-ansible$ systemctl status mariadb.service
● mariadb.service - MariaDB 10.3.22 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sat 2020-06-13 15:04:58 CEST; 1min 25s ago
       Docs: man:mysqld(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 9721 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 9723 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 9736 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1>
    Process: 9787 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
   Main PID: 9787 (code=exited, status=1/FAILURE)
     Status: "Starting final batch to recover 13 pages from redo log"

Jun 13 15:04:57 vdr systemd[1]: Starting MariaDB 10.3.22 database server...
Jun 13 15:04:57 vdr mysqld[9787]: 2020-06-13 15:04:57 0 [Note] /usr/sbin/mysqld (mysqld 10.3.22-MariaDB-1ubuntu1) starting as process 9787 ...
Jun 13 15:04:58 vdr systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 15:04:58 vdr systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jun 13 15:04:58 vdr systemd[1]: Failed to start MariaDB 10.3.22 database server.
lines 1-17/17 (END)...skipping...
● mariadb.service - MariaDB 10.3.22 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sat 2020-06-13 15:04:58 CEST; 1min 25s ago
       Docs: man:mysqld(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 9721 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 9723 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 9736 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1>
    Process: 9787 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
   Main PID: 9787 (code=exited, status=1/FAILURE)
     Status: "Starting final batch to recover 13 pages from redo log"

Jun 13 15:04:57 vdr systemd[1]: Starting MariaDB 10.3.22 database server...
Jun 13 15:04:57 vdr mysqld[9787]: 2020-06-13 15:04:57 0 [Note] /usr/sbin/mysqld (mysqld 10.3.22-MariaDB-1ubuntu1) starting as process 9787 ...
Jun 13 15:04:58 vdr systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 15:04:58 vdr systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jun 13 15:04:58 vdr systemd[1]: Failed to start MariaDB 10.3.22 database server.

Alles anzeigen

seahawk1986 · 13. Juni 2020

Mir ist noch nicht ganz klar, warum das Verzeichnis überhaupt gefehlt hat - hast du da Daten von einer älteren Installation übernommen bzw. wurden da nach der Installation des Ubuntu Servers zusätzliche Anpassungen am Playbook vorbei vorgenommen?

danielweidner · 13. Juni 2020

Ich habe nur mit dem yausbir gekämpft.

danielweidner · 13. Juni 2020

Hilft es, wenn ich das (wie unter EPGD Installation auf Ubuntu 18.04 - kurze Anleitung) manuell installiere?

Was müsste ich alles vorher deinstallieren?

seahawk1986 · 13. Juni 2020

Eigentlich greift das Playbook nicht groß in die Konfiguration von Mariadb ein - es wird eigentlich nur die Datei

/etc/mysql/mariadb.conf.d/99-epgd.cnf angelegt, die dafür sorgt, dass MariaDB auf allen Interfaces erreichbar ist.

Zitat von danielweidner

Status: "Starting final batch to recover 13 pages from redo log"

Das klingt so, als ob die Datenbank beschädigt ist. Probier mal, ob die automatische Reparatur da etwas findet:

sudo mysqlcheck --auto-repair -A

Mir ist gerade aufgefallen, dass da noch mehr nicht passt - meine VM hat auch noch eine /etc/mysql/my.cnf.fallback:

Code: /etc/mysql/my.cnf.fallback

#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

!includedir /etc/mysql/conf.d/

Alles anzeigen

Ich werde das Gefühl nicht los, dass ja recht wild auf dem System herumgefuhrwerkt wurde... - eventuell sieht man in der ~/.bash_history (ggf. auch mal in die von root schauen), was da genau passiert ist.

Zitat von danielweidner

Hilft es, wenn ich das (wie unter EPGD Installation auf Ubuntu 18.04 - kurze Anleitung) manuell installiere?

Was müsste ich alles vorher deinstallieren?

Du kannst versuchen mariadb komplett abzuräumen und alle dazugehörigen Nutzdaten zu entfernen und dann die Rolle aus dem Playbook erneut laufen lassen bzw. die Pakete von Hand zu installieren. Wenn nicht klar wird, was da kaputt gespielt wurde (wie schon geschrieben kann ich mir den Zustand des Systems nicht dadurch erklären, dass da nur das Playbook gelaufen ist), wäre eine Neuinstallation noch eine Möglichkeit.

danielweidner · 14. Juni 2020

Guten Morgen!

Ich habe mariadb-server mit purge gelöscht und (fast) alles, was ich in Zusammenhabg mit mariadb oder mysql gefunden habe gelöscht. Dann habe ich mariadb-server manuell installiert. Dabei hat er /etc/mysql nicht anlegen können. Manuell das Verzechnis angelegt, mariadb-server nochmal gelöscht und wieder installiert und schon gings.

Jetzt habe ich das Playbook nochmal laufen lassen und bekomme eine Warnung:

Code

[WARNING]: Module did not set no_log for update_password

Muss ich da noch was machen?

[ansible@focal] role epgd: mariadb startet nicht

Jetzt mitmachen!

Teilen