API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Jan 4th, 2020
208
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 17.12 KB | None | 0 0
raw download clone embed print report
  1. Jan 4 14:30:24 vmi223751 mysqld[6831]: 2020-01-04 14:30:24 0 [Note] /usr/sbin/mysqld: ready for connections.
  2. Jan 4 14:30:24 vmi223751 mysqld[6831]: Version: '10.4.11-MariaDB-1:10.4.11+maria~bionic-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
  3. Jan 4 14:30:24 vmi223751 systemd[1]: Started MariaDB 10.4.11 database server.
  4. Jan 4 14:30:24 vmi223751 /etc/mysql/debian-start[6863]: Upgrading MySQL tables if necessary.
  5. Jan 4 14:30:24 vmi223751 /etc/mysql/debian-start[6866]: Looking for 'mysql' as: /usr/bin/mysql
  6. Jan 4 14:30:24 vmi223751 /etc/mysql/debian-start[6866]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
  7. Jan 4 14:30:24 vmi223751 /etc/mysql/debian-start[6866]: This installation of MariaDB is already upgraded to 10.4.11-MariaDB, use --force if you still need to run mysql_upgrade
  8. Jan 4 14:30:24 vmi223751 /etc/mysql/debian-start[6874]: Checking for insecure root accounts.
  9. Jan 4 14:30:24 vmi223751 /etc/mysql/debian-start[6878]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables
  10. Jan 4 14:30:25 vmi223751 mysqld[6831]: 2020-01-04 14:30:25 0 [Note] InnoDB: Buffer pool(s) load completed at 200104 14:30:25
  11. Jan 4 14:35:18 vmi223751 mysqld[6831]: 2020-01-04 14:35:18 0x7f811413d700 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.4.11/storage/innobase/btr/btr0btr.cc line 204
  12. Jan 4 14:35:18 vmi223751 mysqld[6831]: InnoDB: Failing assertion: mach_read_from_4(seg_header + FSEG_HDR_SPACE) == space
  13. Jan 4 14:35:18 vmi223751 mysqld[6831]: InnoDB: We intentionally generate a memory trap.
  14. Jan 4 14:35:18 vmi223751 mysqld[6831]: InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
  15. Jan 4 14:35:18 vmi223751 mysqld[6831]: InnoDB: If you get repeated assertion failures or crashes, even
  16. Jan 4 14:35:18 vmi223751 mysqld[6831]: InnoDB: immediately after the mysqld startup, there may be
  17. Jan 4 14:35:18 vmi223751 mysqld[6831]: InnoDB: corruption in the InnoDB tablespace. Please refer to
  18. Jan 4 14:35:18 vmi223751 mysqld[6831]: InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
  19. Jan 4 14:35:18 vmi223751 mysqld[6831]: InnoDB: about forcing recovery.
  20. Jan 4 14:35:18 vmi223751 mysqld[6831]: 200104 14:35:18 [ERROR] mysqld got signal 6 ;
  21. Jan 4 14:35:18 vmi223751 mysqld[6831]: This could be because you hit a bug. It is also possible that this binary
  22. Jan 4 14:35:18 vmi223751 mysqld[6831]: or one of the libraries it was linked against is corrupt, improperly built,
  23. Jan 4 14:35:18 vmi223751 mysqld[6831]: or misconfigured. This error can also be caused by malfunctioning hardware.
  24. Jan 4 14:35:18 vmi223751 mysqld[6831]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
  25. Jan 4 14:35:18 vmi223751 mysqld[6831]: We will try our best to scrape up some info that will hopefully help
  26. Jan 4 14:35:18 vmi223751 mysqld[6831]: diagnose the problem, but since we have already crashed,
  27. Jan 4 14:35:18 vmi223751 mysqld[6831]: something is definitely wrong and this may fail.
  28. Jan 4 14:35:18 vmi223751 mysqld[6831]: Server version: 10.4.11-MariaDB-1:10.4.11+maria~bionic-log
  29. Jan 4 14:35:18 vmi223751 mysqld[6831]: key_buffer_size=134217728
  30. Jan 4 14:35:18 vmi223751 mysqld[6831]: read_buffer_size=2097152
  31. Jan 4 14:35:18 vmi223751 mysqld[6831]: max_used_connections=1
  32. Jan 4 14:35:18 vmi223751 mysqld[6831]: max_threads=102
  33. Jan 4 14:35:18 vmi223751 mysqld[6831]: thread_count=4
  34. Jan 4 14:35:18 vmi223751 mysqld[6831]: It is possible that mysqld could use up to
  35. Jan 4 14:35:18 vmi223751 mysqld[6831]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 760249 K bytes of memory
  36. Jan 4 14:35:18 vmi223751 mysqld[6831]: Hope that's ok; if not, decrease some variables in the equation.
  37. Jan 4 14:35:18 vmi223751 mysqld[6831]: Thread pointer: 0x7f7eec000c08
  38. Jan 4 14:35:18 vmi223751 mysqld[6831]: Attempting backtrace. You can use the following information to find out
  39. Jan 4 14:35:18 vmi223751 mysqld[6831]: where mysqld died. If you see no messages after this, something went
  40. Jan 4 14:35:18 vmi223751 mysqld[6831]: terribly wrong...
  41. Jan 4 14:35:18 vmi223751 mysqld[6831]: stack_bottom = 0x7f811413cdd8 thread_stack 0x49000
  42. Jan 4 14:35:18 vmi223751 mysqld[6831]: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x5620fc6eb1de]
  43. Jan 4 14:35:18 vmi223751 mysqld[6831]: /usr/sbin/mysqld(handle_fatal_signal+0x515)[0x5620fc1602f5]
  44. Jan 4 14:35:18 vmi223751 mysqld[6831]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f811de35890]
  45. Jan 4 14:35:19 vmi223751 mysqld[6831]: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f811c768e97]
  46. Jan 4 14:35:19 vmi223751 mysqld[6831]: /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f811c76a801]
  47. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(+0x56b69a)[0x5620fbe6769a]
  48. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(+0xb5a600)[0x5620fc456600]
  49. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(+0xb5be00)[0x5620fc457e00]
  50. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(+0xb5bf01)[0x5620fc457f01]
  51. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(+0x56bf8e)[0x5620fbe67f8e]
  52. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(+0xbdc7a9)[0x5620fc4d87a9]
  53. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(+0xbdcfe1)[0x5620fc4d8fe1]
  54. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(+0xbcddb3)[0x5620fc4c9db3]
  55. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(+0xa16262)[0x5620fc312262]
  56. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(_ZN7handler7ha_openEP5TABLEPKcijP11st_mem_rootP4ListI6StringE+0x4a)[0x5620fc164dda]
  57. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(_Z21open_table_from_shareP3THDP11TABLE_SHAREPK25st_mysql_const_lex_stringjjjP5TABLEbP4ListI6StringE+0x8fc)[0x5620fc00956c]
  58. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP18Open_table_context+0xc60)[0x5620fbeeb5d0]
  59. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(_Z11open_tablesP3THDRK14DDL_options_stPP10TABLE_LISTPjjP19Prelocking_strategy+0xc13)[0x5620fbeee753]
  60. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(_Z20open_and_lock_tablesP3THDRK14DDL_options_stP10TABLE_LISTbjP19Prelocking_strategy+0x33)[0x5620fbeef383]
  61. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(+0x7432e8)[0x5620fc03f2e8]
  62. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(+0x74412b)[0x5620fc04012b]
  63. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(_ZN19Sql_cmd_check_table7executeEP3THD+0x82)[0x5620fc041e42]
  64. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1f2b)[0x5620fbf4d87b]
  65. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x22a)[0x5620fbf5447a]
  66. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x13a1)[0x5620fbf56a01]
  67. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(_Z10do_commandP3THD+0x148)[0x5620fbf582d8]
  68. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x25e)[0x5620fc0342ae]
  69. Jan 4 14:35:19 vmi223751 mysqld[6831]: /usr/sbin/mysqld(handle_one_connection+0x3d)[0x5620fc03436d]
  70. Jan 4 14:35:19 vmi223751 mysqld[6831]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x76db)[0x7f811de2a6db]
  71. Jan 4 14:35:19 vmi223751 mysqld[6831]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f811c84b88f]
  72. Jan 4 14:35:19 vmi223751 mysqld[6831]: Trying to get some variables.
  73. Jan 4 14:35:19 vmi223751 mysqld[6831]: Some pointers may be invalid and cause the dump to abort.
  74. Jan 4 14:35:19 vmi223751 mysqld[6831]: Query (0x7f7eec013340): CHECK TABLE `CANhistoriacenseriale`
  75. Jan 4 14:35:19 vmi223751 mysqld[6831]: Connection ID (thread ID): 32
  76. Jan 4 14:35:19 vmi223751 mysqld[6831]: Status: NOT_KILLED
  77. Jan 4 14:35:19 vmi223751 mysqld[6831]: Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on
  78. Jan 4 14:35:19 vmi223751 mysqld[6831]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
  79. Jan 4 14:35:19 vmi223751 mysqld[6831]: information that should help you find out what is causing the crash.
  80. Jan 4 14:35:19 vmi223751 mysqld[6831]: Writing a core file...
  81. Jan 4 14:35:19 vmi223751 mysqld[6831]: Working directory at /var/lib/mysql
  82. Jan 4 14:35:19 vmi223751 mysqld[6831]: Resource Limits:
  83. Jan 4 14:35:19 vmi223751 mysqld[6831]: Limit Soft Limit Hard Limit Units
  84. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max cpu time unlimited unlimited seconds
  85. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max file size unlimited unlimited bytes
  86. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max data size unlimited unlimited bytes
  87. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max stack size 8388608 unlimited bytes
  88. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max core file size 0 unlimited bytes
  89. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max resident set unlimited unlimited bytes
  90. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max processes 31730 31730 processes
  91. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max open files 16364 16364 files
  92. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max locked memory 16777216 16777216 bytes
  93. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max address space unlimited unlimited bytes
  94. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max file locks unlimited unlimited locks
  95. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max pending signals 31730 31730 signals
  96. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max msgqueue size 819200 819200 bytes
  97. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max nice priority 0 0
  98. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max realtime priority 0 0
  99. Jan 4 14:35:19 vmi223751 mysqld[6831]: Max realtime timeout unlimited unlimited us
  100. Jan 4 14:35:19 vmi223751 mysqld[6831]: Core pattern: core
  101. Jan 4 14:35:19 vmi223751 systemd[1]: mariadb.service: Main process exited, code=killed, status=6/ABRT
  102. Jan 4 14:35:19 vmi223751 systemd[1]: mariadb.service: Failed with result 'signal'.
  103. Jan 4 14:35:24 vmi223751 systemd[1]: mariadb.service: Service hold-off time over, scheduling restart.
  104. Jan 4 14:35:24 vmi223751 systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 1.
  105. Jan 4 14:35:24 vmi223751 systemd[1]: Stopped MariaDB 10.4.11 database server.
  106. Jan 4 14:35:24 vmi223751 systemd[1]: Starting MariaDB 10.4.11 database server...
  107. Jan 4 14:35:24 vmi223751 mysqld[7161]: 2020-01-04 14:35:24 0 [Note] /usr/sbin/mysqld (mysqld 10.4.11-MariaDB-1:10.4.11+maria~bionic-log) starting as process 7161 ...
  108. Jan 4 14:35:24 vmi223751 mysqld[7161]: 2020-01-04 14:35:24 0 [Warning] option 'innodb-purge-threads': unsigned value 0 adjusted to 1
  109. Jan 4 14:35:24 vmi223751 mysqld[7161]: 2020-01-04 14:35:24 0 [Note] InnoDB: Using Linux native AIO
  110. Jan 4 14:35:24 vmi223751 mysqld[7161]: 2020-01-04 14:35:24 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  111. Jan 4 14:35:24 vmi223751 mysqld[7161]: 2020-01-04 14:35:24 0 [Note] InnoDB: Uses event mutexes
  112. Jan 4 14:35:24 vmi223751 mysqld[7161]: 2020-01-04 14:35:24 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
  113. Jan 4 14:35:24 vmi223751 mysqld[7161]: 2020-01-04 14:35:24 0 [Note] InnoDB: Number of pools: 1
  114. Jan 4 14:35:24 vmi223751 mysqld[7161]: 2020-01-04 14:35:24 0 [Note] InnoDB: Using SSE2 crc32 instructions
  115. Jan 4 14:35:24 vmi223751 mysqld[7161]: 2020-01-04 14:35:24 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
  116. Jan 4 14:35:24 vmi223751 mysqld[7161]: 2020-01-04 14:35:24 0 [Note] InnoDB: Initializing buffer pool, total size = 6G, instances = 8, chunk size = 128M
  117. Jan 4 14:35:25 vmi223751 mysqld[7161]: 2020-01-04 14:35:25 0 [Note] InnoDB: Completed initialization of buffer pool
  118. Jan 4 14:35:25 vmi223751 mysqld[7161]: 2020-01-04 14:35:25 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
  119. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1130023
  120. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
  121. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
  122. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] InnoDB: Creating shared tablespace for temporary tables
  123. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
  124. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
  125. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] InnoDB: 10.4.11 started; log sequence number 1130032; transaction id 1501
  126. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] InnoDB: !!! innodb_force_recovery is set to 3 !!!
  127. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
  128. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] Plugin 'FEEDBACK' is disabled.
  129. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] Recovering after a crash using /var/log/mysql/mariadb-bin
  130. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] Starting crash recovery...
  131. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] Crash recovery finished.
  132. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] Server socket created on IP: '127.0.0.1'.
  133. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] Reading of all Master_info entries succeeded
  134. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] Added new Master_info '' to hash table
  135. Jan 4 14:35:26 vmi223751 mysqld[7161]: 2020-01-04 14:35:26 0 [Note] /usr/sbin/mysqld: ready for connections.
  136. Jan 4 14:35:26 vmi223751 mysqld[7161]: Version: '10.4.11-MariaDB-1:10.4.11+maria~bionic-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
  137. Jan 4 14:35:26 vmi223751 systemd[1]: Started MariaDB 10.4.11 database server.
  138. Jan 4 14:35:26 vmi223751 /etc/mysql/debian-start[7194]: Upgrading MySQL tables if necessary.
  139. Jan 4 14:35:26 vmi223751 /etc/mysql/debian-start[7197]: Looking for 'mysql' as: /usr/bin/mysql
  140. Jan 4 14:35:26 vmi223751 /etc/mysql/debian-start[7197]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
  141. Jan 4 14:35:26 vmi223751 /etc/mysql/debian-start[7197]: This installation of MariaDB is already upgraded to 10.4.11-MariaDB, use --force if you still need to run mysql_upgrade
  142. Jan 4 14:35:26 vmi223751 /etc/mysql/debian-start[7205]: Checking for insecure root accounts.
  143. Jan 4 14:35:26 vmi223751 /etc/mysql/debian-start[7209]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables
  144. Jan 4 14:35:28 vmi223751 mysqld[7161]: 2020-01-04 14:35:28 0 [Note] InnoDB: Buffer pool(s) load completed at 200104 14:35:28
  145. Jan 4 14:36:26 vmi223751 systemd[1]: Stopping MariaDB 10.4.11 database server...
  146. Jan 4 14:36:26 vmi223751 mysqld[7161]: 2020-01-04 14:36:26 0 [Note] /usr/sbin/mysqld (initiated by: unknown): Normal shutdown
  147. Jan 4 14:36:26 vmi223751 mysqld[7161]: 2020-01-04 14:36:26 0 [Note] Event Scheduler: Purging the queue. 0 events
  148. Jan 4 14:36:26 vmi223751 mysqld[7161]: 2020-01-04 14:36:26 0 [Note] InnoDB: Starting shutdown...
  149. Jan 4 14:36:26 vmi223751 mysqld[7161]: 2020-01-04 14:36:26 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
  150. Jan 4 14:36:26 vmi223751 mysqld[7161]: 2020-01-04 14:36:26 0 [Note] InnoDB: Buffer pool(s) dump completed at 200104 14:36:26
  151. Jan 4 14:36:29 vmi223751 mysqld[7161]: 2020-01-04 14:36:29 0 [Note] InnoDB: Shutdown completed; log sequence number 1130041; transaction id 1502
  152. Jan 4 14:36:29 vmi223751 mysqld[7161]: 2020-01-04 14:36:29 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
  153. Jan 4 14:36:29 vmi223751 mysqld[7161]: 2020-01-04 14:36:29 0 [Note] /usr/sbin/mysqld: Shutdown complete
  154. Jan 4 14:36:29 vmi223751 systemd[1]: Stopped MariaDB 10.4.11 database server.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!