Das System beschwert sich ja offensichtlich darüber, dass mysql.service eine directory ist - benötigt wird aber wohl ein file. Gib doch Mal bei Dolphin ausgehend von / die Suche nach mysql.service in Auftrag.
Leap 15.3 - mysql/mariadb lassen sich nicht starten
- bananenkiste
- Erledigt
-
-
Mit einer etwas anderen Fehlermeldung habe ich im Internet das hier gefunden:
-
Gib doch Mal bei Dolphin ausgehend von / die Suche nach mysql.service in Auftrag.
Die Datei gibt es dreimal.
Codefileserver5:~ # find /etc /usr -name mysql.service /etc/systemd/system/multi-user.target.wants/mysql.service /etc/systemd/system/mysql.service /usr/lib/systemd/system/mysql.service fileserver5:~ #Sie sind identisch, bis auf die Zeile 46 CapabilityBoundingSet=CAP_IPC_LOCK CAP_DAC_OVERRIDE CAP_AUDIT_WRITE, die in der Datei /usr/lib/systemd/system/mysql.service fehlt.
Code
Alles anzeigen[Unit] Description=MariaDB database server Documentation=man:mysqld(8) Documentation=https://mariadb.com/kb/en/library/systemd/ Conflicts=mariadb.target After=network.target time-sync.target [Install] WantedBy=multi-user.target Alias=mysql.service [Service] ExecStartPre=/usr/lib/mysql/mysql-systemd-helper install ExecStartPre=/usr/lib/mysql/mysql-systemd-helper upgrade ExecStart=/usr/lib/mysql/mysql-systemd-helper start Type=notify User=mysql Group=mysql KillSignal=SIGTERM # Don't want to see an automated SIGKILL ever SendSIGKILL=no # Restart crashed server only, on-failure would also restart, for example, when # my.cnf contains unknown option Restart=on-abort RestartSec=5s # Configures the time to wait for start-up/stop TimeoutSec=300 # CAP_IPC_LOCK To allow memlock to be used as non-root user # CAP_DAC_OVERRIDE To allow auth_pam_tool (which is SUID root) to read /etc/shadow when it's chmod 0 # does nothing for non-root, not needed if /etc/shadow is u+r # CAP_AUDIT_WRITE auth_pam_tool needs it on Debian for whatever reason CapabilityBoundingSet=CAP_IPC_LOCK CAP_DAC_OVERRIDE CAP_AUDIT_WRITE # Prevent writes to /usr, /boot, and /etc ProtectSystem=full # Prevent accessing /home, /root and /run/user ProtectHome=true # Execute pre and post scripts as root, otherwise it does it as User= PermissionsStartOnly=true UMask=007Mit einer etwas anderen Fehlermeldung habe ich im Internet das hier gefunden:
Er zeigt nur, wie man mariadb startet, wenn alles richtig funktioniert - und das wissen wir ja. Bloß funktioniert hier halt nicht alles richtig.
Code# systemctl start mariadb.service # systemctl enable mariadb.service # mysql_secure_installation -
Poste als root ausgeführt:
Codecat /var/log/mysql/mysqld.log -
Bei mir sieht die mysql.service-Datei, die ja nur ein Link zur mariadb.service-Datei ist, in folgenden Bereich abweichend zu Deiner Datei aus:
[Unit]
Description=MariaDB database server - %I instance
Documentation=man:mysqld(8)
Documentation=https://mariadb.com/kb/en/library/systemd/
PartOf=mariadb.target
After=network.target time-sync.target
-
Bei mir gibt es unter
Code/etc/systemd/system/multi-user.target.wantsdie mysql.service-Datei nicht! Löschen?
Unter
Code/etc/systemd/system/übrigens auch nicht!
-
Poste als root ausgeführt:
cat /var/log/mysql/mysqld.log
Code
Alles anzeigenfileserver5:~ # cat /var/log/mysql/mysqld.log 2022-06-05 15:43:42 0 [Note] InnoDB: Uses event mutexes 2022-06-05 15:43:42 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2022-06-05 15:43:42 0 [Note] InnoDB: Number of pools: 1 2022-06-05 15:43:42 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2022-06-05 15:43:42 0 [Note] InnoDB: Using Linux native AIO 2022-06-05 15:43:42 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728 2022-06-05 15:43:42 0 [Note] InnoDB: Completed initialization of buffer pool 2022-06-05 15:43:42 0 [Note] InnoDB: Upgrading redo log: 100663296 bytes; LSN=1221381827 2022-06-05 15:43:42 0 [Note] InnoDB: Starting to delete and rewrite log file. 2022-06-05 15:43:42 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 100663296 bytes 2022-06-05 15:43:42 0 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 2022-06-05 15:43:42 0 [Note] InnoDB: New log file created, LSN=1221381827 2022-06-05 15:43:42 0 [Note] InnoDB: 128 rollback segments are active. 2022-06-05 15:43:42 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2022-06-05 15:43:42 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2022-06-05 15:43:42 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2022-06-05 15:43:42 0 [Note] InnoDB: 10.5.15 started; log sequence number 1221381827; transaction id 4894373 2022-06-05 15:43:42 0 [Note] InnoDB: Loading buffer pool(s) from /home/daten/Datenbanken/mysql/ib_buffer_pool 2022-06-05 15:43:42 0 [Note] Plugin 'FEEDBACK' is disabled. 2022-06-05 15:43:42 0 [Note] Server socket created on IP: '127.0.0.1'. 2022-06-05 15:43:43 0 [Note] InnoDB: Buffer pool(s) load completed at 220605 15:43:43 2022-06-05 15:43:43 0 [Note] Reading of all Master_info entries succeeded 2022-06-05 15:43:43 0 [Note] Added new Master_info '' to hash table 2022-06-05 15:43:43 0 [Note] /usr/sbin/mysqld: ready for connections. Version: '10.5.15-MariaDB' socket: '/run/mysql/mysql.sock' port: 3306 MariaDB package Status information: Current dir: /home/daten/Datenbanken/mysql/ Running threads: 0 Cached threads: 0 Stack size: 299008 Key caches: default Buffer_size: 134217728 Block_size: 1024 Division_limit: 100 Age_threshold: 300 Partitions: 0 blocks used: 0 not flushed: 0 w_requests: 0 writes: 0 r_requests: 0 reads: 0 handler status: read_key: 0 read_next: 1 read_rnd 0 read_first: 3 write: 0 delete 0 update: 0 Table status: Opened tables: 17 Open tables: 10 Open files: 22 Open streams: 4 Alarm status: Active alarms: 0 Max used alarms: 0 Next alarm time: 0 Memory status: Non-mmapped space allocated from system: 10059776 Number of free chunks: 40 Number of fastbin blocks: 41 Number of mmapped regions: 8 Space in mmapped regions: 41029632 Maximum total allocated space: 0 Space available in freed fastbin blocks: 2944 Total allocated space: 8587984 Total free space: 1471792 Top-most, releasable space: 43520 Estimated memory (with thread stack): 51089408 Global memory allocated by server: 34368024 Memory allocated by threads: 0 Events status: LLA = Last Locked At LUA = Last Unlocked At WOC = Waiting On Condition DL = Data Locked Event scheduler status: State : INITIALIZED Thread id : 0 LLA : n/a:0 LUA : n/a:0 WOC : NO Workers : 0 Executed : 0 Data locked: NO Event queue status: Element count : 0 Data locked : NO Attempting lock : NO LLA : init_queue:141 LUA : init_queue:151 WOC : NO Next activation : never 2022-06-05 16:22:51 0 [Note] /usr/sbin/mysqld (initiated by: unknown): Normal shutdown 2022-06-05 16:22:52 0 [Note] Event Scheduler: Purging the queue. 0 events 2022-06-05 16:22:52 0 [Note] InnoDB: FTS optimize thread exiting. 2022-06-05 16:22:52 0 [Note] InnoDB: Starting shutdown... 2022-06-05 16:22:52 0 [Note] InnoDB: Dumping buffer pool(s) to /home/daten/Datenbanken/mysql/ib_buffer_pool 2022-06-05 16:22:52 0 [Note] InnoDB: Restricted to 2016 pages due to innodb_buf_pool_dump_pct=25 2022-06-05 16:22:52 0 [Note] InnoDB: Buffer pool(s) dump completed at 220605 16:22:52 220605 16:22:52 [ERROR] mysqld got signal 11 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. To report this bug, see https://mariadb.com/kb/en/reporting-bugs We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. Server version: 10.5.15-MariaDB key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=0 max_threads=153 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467872 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x0 thread_stack 0x49000 2022-06-05 16:22:52 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2022-06-05 16:22:52 0 [Note] InnoDB: Shutdown completed; log sequence number 1221382168; transaction id 4894374 2022-06-05 16:22:52 0 [Note] /usr/sbin/mysqld: Shutdown complete /usr/sbin/mysqld(my_print_stacktrace+0x3d)[0x55eddc9d923d] /usr/sbin/mysqld(handle_fatal_signal+0x565)[0x55eddc453145] ??:0(__restore_rt)[0x7fd7075018c0] ??:0(hostname_cache_refresh())[0x55eddc463ce3] ??:0(reload_acl_and_cache(THD*, unsigned long long, TABLE_LIST*, int*))[0x55eddc364c45] ??:0(signal_hand)[0x55eddc192361] ??:0(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x55eddc678bb3] ??:0(start_thread)[0x7fd7074f56ea] ??:0(__GI___clone)[0x7fd706692a8f] The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains information that should help you find out what is causing the crash. Writing a core file... Working directory at /home/daten/Datenbanken/mysql Resource Limits: Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 8388608 unlimited bytes Max core file size unlimited unlimited bytes Max resident set unlimited unlimited bytes Max processes 31449 31449 processes Max open files 32184 32184 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 31449 31449 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h fileserver5:~ #Ich kann beim besten Willen nicht verstehen, wie dieses Logfile zur Fehlermeldung passt. Loaded: error (Reason: Unit mysql.service failed to load properly: Is a directory.)
-
Alles anzeigen
Bei mir sieht die mysql.service-Datei, die ja nur ein Link zur mariadb.service-Datei ist, in folgenden Bereich abweichend zu Deiner Datei aus:
[Unit]
Description=MariaDB database server - %I instance
Documentation=man:mysqld(8)
Documentation=https://mariadb.com/kb/en/library/systemd/
PartOf=mariadb.target
After=network.target time-sync.target
Du hast Tumbleweed, bei Leap 15.3 sieht es anscheinend anders aus.
Bei mir gibt es unter
Code/etc/systemd/system/multi-user.target.wantsdie mysql.service-Datei nicht! Löschen?
Unter
Code/etc/systemd/system/übrigens auch nicht!
ZitatAlles anzeigen# It's not recommended to modify this unit file because your changes
# would be overwritten during the package update.
#
# However, there are 2 methods how to customize this unit file:
#
# 1) Copy this unit file from /usr/lib/systemd/system to
# /etc/systemd/system and modify the chosen settings.
#
# 2) Create a directory named mariadb.service.d/ within /etc/systemd/system
# and place a drop-in file name.conf there that only changes the specific
# settings one is interested in.
#
# see systemd.unit(5) for details
#
# Example - increasing of the TimeoutSec= limit
# mkdir /etc/systemd/system/mariadb.service.d
# cat > /etc/systemd/system/mariadb.service.d/timeout.conf << EOF
# [Service]
# TimeoutSec=600
# EOF
aus /usr/lib/systemd/system/mysql.service
-
Hast du mal alle mysql und maria Pakete neu installiert?
-
Bananenkiste hatte doch unter Post #3 angezeigt, welche Pakete installiert sind!
