API tools faq
paste
Advertisement
Barry_IA

BE3 - MariaDB - May 17

Barry_IA
May 17th, 2019
174
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 10.17 KB | None | 0 0
raw download clone embed print report
  1. On 5/16/19 5:56 PM, Barry Martin wrote:
  2. >
  3. > ???As?I?mentioned?from?some?Google-wandering?found?where?appears?to?be
  4. > ???configured?to?localhost?127.0.0.1?and?I?m?guessing?it?should?be
  5. > ???looking?at?Backend-3?192.168.0.3
  6.  
  7. Ignore where MariaDB is listening *for now*. As Stephen already mentioned,
  8. localhost will work just fine.
  9.  
  10. You may notice that systemctl output is truncated to the width of the
  11. current screen.
  12.  
  13. Try this (and copy/paste the output in a pastebin please.) The last one didn't
  14. have any log lines, just an email from this thread.
  15.  
  16. systemctl show mariadb.service -p ExecStart -p ExecStartPre -p ExecStartPost|cat
  17.  
  18. --
  19. Bill
  20.  
  21. Results of the command line and some 'extra credit' attached.
  22.  
  23. ...Not seeing the attachment so just appending until I figure out:
  24.  
  25.  
  26.  
  27. barry@Backend-3:~$ systemctl show mariadb.service -p ExecStart -p ExecStartPre -p ExecStartPost|cat
  28. ExecStartPre={ path=/usr/bin/install ; argv[]=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld ; ignore_errors=no ; start_time=[Fri 2019-05-17 07:55:02 CDT] ; stop_time=[Fri 2019-05-17 07:55:02 CDT] ; pid=909 ; code=exited ; status=0 }
  29. ExecStartPre={ path=/bin/sh ; argv[]=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION ; ignore_errors=no ; start_time=[Fri 2019-05-17 07:55:02 CDT] ; stop_time=[Fri 2019-05-17 07:55:02 CDT] ; pid=919 ; code=exited ; status=0 }
  30. ExecStartPre={ path=/bin/sh ; argv[]=/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 ; ignore_errors=no ; start_time=[Fri 2019-05-17 07:55:02 CDT] ; stop_time=[Fri 2019-05-17 07:55:02 CDT] ; pid=929 ; code=exited ; status=0 }
  31. ExecStart={ path=/usr/sbin/mysqld ; argv[]=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION ; ignore_errors=no ; start_time=[Fri 2019-05-17 07:55:02 CDT] ; stop_time=[Fri 2019-05-17 07:56:35 CDT] ; pid=1024 ; code=exited ; status=0 }
  32. ExecStartPost={ path=/etc/mysql/debian-start ; argv[]=/etc/mysql/debian-start ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
  33. ExecStartPost={ path=/bin/sh ; argv[]=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
  34. barry@Backend-3:~$
  35.  
  36.  
  37.  
  38.  
  39.  
  40. And for an 'extra credit' attempt:
  41.  
  42.  
  43. barry@Backend-3:~$
  44. barry@Backend-3:~$ sudo cat /var/log/mysql/error.log
  45. [sudo] password for barry:
  46. barry@Backend-3:~$
  47. barry@Backend-3:~$
  48. barry@Backend-3:~$ ls /var/log/mysql/error.log
  49. /var/log/mysql/error.log
  50. barry@Backend-3:~$ nano /var/log/mysql/error.log ==> is empty
  51. barry@Backend-3:~$
  52. barry@Backend-3:~$
  53. barry@Backend-3:~$
  54. barry@Backend-3:~$ sudo systemctl start mariadb
  55. Job for mariadb.service failed because a timeout was exceeded.
  56. See "systemctl status mariadb.service" and "journalctl -xe" for details.
  57. barry@Backend-3:~$
  58.  
  59.  
  60. barry@Backend-3:~$ sudo cat /var/log/mysql/error.log
  61. 2019-05-17 8:02:09 140319656078464 [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.
  62.  
  63. 2019-05-17 8:02:09 140319656078464 [Note] InnoDB: Using mutexes to ref count buffer pool pages
  64. 2019-05-17 8:02:09 140319656078464 [Note] InnoDB: The InnoDB memory heap is disabled
  65. 2019-05-17 8:02:09 140319656078464 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  66. 2019-05-17 8:02:09 140319656078464 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
  67. 2019-05-17 8:02:09 140319656078464 [Note] InnoDB: Compressed tables use zlib 1.2.11
  68. 2019-05-17 8:02:09 140319656078464 [Note] InnoDB: Using Linux native AIO
  69. 2019-05-17 8:02:09 140319656078464 [Note] InnoDB: Using SSE crc32 instructions
  70. 2019-05-17 8:02:09 140319656078464 [Note] InnoDB: Initializing buffer pool, size = 128.0M
  71. 2019-05-17 8:02:09 140319656078464 [Note] InnoDB: Completed initialization of buffer pool
  72. 2019-05-17 8:02:09 140319656078464 [Note] InnoDB: Highest supported file format is Barracuda.
  73. 2019-05-17 8:02:09 140319656078464 [Note] InnoDB: 128 rollback segment(s) are active.
  74. 2019-05-17 8:02:09 140319656078464 [Note] InnoDB: Waiting for purge to start
  75. 2019-05-17 8:02:09 140319656078464 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence number 1616837
  76. 2019-05-17 8:02:09 140318993282816 [Note] InnoDB: Dumping buffer pool(s) not yet started
  77. 2019-05-17 8:02:09 140319656078464 [Note] Plugin 'FEEDBACK' is disabled.
  78. 2019-05-17 8:02:09 140319656078464 [Note] Server socket created on IP: '127.0.0.1'.
  79. 2019-05-17 8:02:09 140319656078464 [Note] /usr/sbin/mysqld: ready for connections.
  80. Version: '10.1.38-MariaDB-0ubuntu0.18.04.2' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Ubuntu 18.04
  81. 2019-05-17 8:03:38 140319655278336 [Note] /usr/sbin/mysqld: Normal shutdown
  82. 2019-05-17 8:03:38 140319655278336 [Note] Event Scheduler: Purging the queue. 0 events
  83. 2019-05-17 8:03:38 140319051978496 [Note] InnoDB: FTS optimize thread exiting.
  84. 2019-05-17 8:03:38 140319655278336 [Note] InnoDB: Starting shutdown...
  85. 2019-05-17 8:03:39 140319655278336 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
  86. 2019-05-17 8:03:41 140319655278336 [Note] InnoDB: Shutdown completed; log sequence number 1616847
  87. 2019-05-17 8:03:41 140319655278336 [Note] /usr/sbin/mysqld: Shutdown complete
  88.  
  89. barry@Backend-3:~$
  90.  
  91.  
  92.  
  93.  
  94. barry@Backend-3:~$ systemctl status mariadb.service
  95. ● mariadb.service - MariaDB 10.1.38 database server
  96. Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
  97. Active: failed (Result: timeout) since Fri 2019-05-17 08:03:41 CDT; 4min 41s ago
  98. Docs: man:mysqld(8)
  99. https://mariadb.com/kb/en/library/systemd/
  100. Process: 2194 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  101. Process: 2116 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 (cod
  102.  
  103. (Ah! Truncating!)
  104. e=exited, status=0/SUCCESS)
  105.  
  106.  
  107.  
  108. Process: 2113 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  109. Process: 2112 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
  110. Main PID: 2194 (code=exited, status=0/SUCCESS)
  111.  
  112. May 17 08:02:08 Backend-3 systemd[1]: Starting MariaDB 10.1.38 database server...
  113. May 17 08:02:09 Backend-3 mysqld[2194]: 2019-05-17 8:02:09 140319656078464 [Note] /usr/sbin/mysqld (mysqld 10.1.38-MariaDB-0ubuntu0.18.04.2) starting as process 2194 ...
  114. May 17 08:03:38 Backend-3 systemd[1]: mariadb.service: Start operation timed out. Terminating.
  115. May 17 08:03:41 Backend-3 systemd[1]: mariadb.service: Failed with result 'timeout'.
  116. May 17 08:03:41 Backend-3 systemd[1]: Failed to start MariaDB 10.1.38 database server.
  117. lines 1-16/16 (END)
  118.  
  119.  
  120.  
  121.  
  122. Preface: I have the Ethenet cable unplugged to avoid screwing up the working Backend (BE-2) like I managed to before with BE-1.
  123.  
  124. barry@Backend-3:~$ journalctl -xe
  125. -- Subject: Unit systemd-tmpfiles-clean.service has begun start-up
  126. -- Defined-By: systemd
  127. -- Support: http://www.ubuntu.com/support
  128. --
  129. -- Unit systemd-tmpfiles-clean.service has begun starting up.
  130. May 17 08:09:45 Backend-3 systemd[1]: Started Cleanup of Temporary Directories.
  131. -- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
  132. -- Defined-By: systemd
  133. -- Support: http://www.ubuntu.com/support
  134. --
  135. -- Unit systemd-tmpfiles-clean.service has finished starting up.
  136. --
  137. -- The start-up result is RESULT.
  138. May 17 08:10:16 Backend-3 ntpd[945]: error resolving pool 2.ubuntu.pool.ntp.org:
  139. May 17 08:10:16 Backend-3 ntpd[945]: error resolving pool 1.ubuntu.pool.ntp.org:
  140. May 17 08:10:23 Backend-3 ntpd[945]: error resolving pool 0.ubuntu.pool.ntp.org:
  141. May 17 08:10:26 Backend-3 ntpd[945]: error resolving pool ntp.ubuntu.com: Name o
  142. May 17 08:10:29 Backend-3 ntpd[945]: error resolving pool 3.ubuntu.pool.ntp.org:
  143. May 17 08:11:22 Backend-3 ntpd[945]: error resolving pool 2.ubuntu.pool.ntp.org:
  144. May 17 08:11:22 Backend-3 ntpd[945]: error resolving pool 1.ubuntu.pool.ntp.org:
  145. May 17 08:11:28 Backend-3 ntpd[945]: error resolving pool 0.ubuntu.pool.ntp.org:
  146. May 17 08:11:30 Backend-3 ntpd[945]: error resolving pool ntp.ubuntu.com: Name o
  147. May 17 08:11:35 Backend-3 ntpd[945]: error resolving pool 3.ubuntu.pool.ntp.org:
  148. lines 1627-1649/1649 (END)
  149. -- Subject: Unit systemd-tmpfiles-clean.service has begun start-up
  150. -- Defined-By: systemd
  151. -- Support: http://www.ubuntu.com/support
  152. --
  153. -- Unit systemd-tmpfiles-clean.service has begun starting up.
  154. May 17 08:09:45 Backend-3 systemd[1]: Started Cleanup of Temporary Directories.
  155. -- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
  156. -- Defined-By: systemd
  157. -- Support: http://www.ubuntu.com/support
  158. --
  159. -- Unit systemd-tmpfiles-clean.service has finished starting up.
  160. --
  161. -- The start-up result is RESULT.
  162. May 17 08:10:16 Backend-3 ntpd[945]: error resolving pool 2.ubuntu.pool.ntp.org: Name or service not known (-2)
  163. May 17 08:10:16 Backend-3 ntpd[945]: error resolving pool 1.ubuntu.pool.ntp.org: Name or service not known (-2)
  164. May 17 08:10:23 Backend-3 ntpd[945]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not known (-2)
  165. May 17 08:10:26 Backend-3 ntpd[945]: error resolving pool ntp.ubuntu.com: Name or service not known (-2)
  166. May 17 08:10:29 Backend-3 ntpd[945]: error resolving pool 3.ubuntu.pool.ntp.org: Name or service not known (-2)
  167. May 17 08:11:22 Backend-3 ntpd[945]: error resolving pool 2.ubuntu.pool.ntp.org: Name or service not known (-2)
  168. May 17 08:11:22 Backend-3 ntpd[945]: error resolving pool 1.ubuntu.pool.ntp.org: Name or service not known (-2)
  169. May 17 08:11:28 Backend-3 ntpd[945]: error resolving pool 0.ubuntu.pool.ntp.org: Name or service not known (-2)
  170. May 17 08:11:30 Backend-3 ntpd[945]: error resolving pool ntp.ubuntu.com: Name or service not known (-2)
  171. May 17 08:11:35 Backend-3 ntpd[945]: error resolving pool 3.ubuntu.pool.ntp.org: Name or service not known (-2)
  172. ~
  173. ~
  174. ~
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!