API tools faq
paste
Advertisement
Guest User

After restart Server - Not login phpmyadmin

a guest
Aug 2nd, 2021
52
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 16.34 KB | None | 0 0
raw download clone embed print report
  1. 210803 07:02:57 mysqld_safe A mysqld process already exists
  2. 210803 07:02:59 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
  3. 210803 7:02:59 [Note] /usr/sbin/mysqld (mysqld 10.0.38-MariaDB) starting as process 13381 ...
  4. 210803 7:02:59 [Note] InnoDB: Using mutexes to ref count buffer pool pages
  5. 210803 7:02:59 [Note] InnoDB: The InnoDB memory heap is disabled
  6. 210803 7:02:59 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  7. 210803 7:02:59 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
  8. 210803 7:02:59 [Note] InnoDB: Compressed tables use zlib 1.2.7
  9. 210803 7:02:59 [Note] InnoDB: Using Linux native AIO
  10. 210803 7:02:59 [Note] InnoDB: Using CPU crc32 instructions
  11. 210803 7:02:59 [Note] InnoDB: Initializing buffer pool, size = 192.0M
  12. 210803 7:02:59 [Note] InnoDB: Completed initialization of buffer pool
  13. 210803 7:02:59 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
  14. 210803 7:02:59 [Note] InnoDB: Setting file ./ibdata1 size to 10 MB
  15. 210803 7:02:59 [Note] InnoDB: Database physically writes the file full: wait...
  16. 210803 7:02:59 [Note] InnoDB: Setting log file ./ib_logfile101 size to 128 MB
  17. 210803 7:03:00 [Note] InnoDB: Setting log file ./ib_logfile1 size to 128 MB
  18. 210803 7:03:00 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
  19. 210803 7:03:00 [Warning] InnoDB: New log files created, LSN=45781
  20. 210803 7:03:00 [Note] InnoDB: Doublewrite buffer not found: creating new
  21. 210803 7:03:00 [Note] InnoDB: Doublewrite buffer created
  22. 210803 7:03:00 [Note] InnoDB: 128 rollback segment(s) are active.
  23. 210803 7:03:00 [Warning] InnoDB: Creating foreign key constraint system tables.
  24. 210803 7:03:00 [Note] InnoDB: Foreign key constraint system tables created
  25. 210803 7:03:00 [Note] InnoDB: Creating tablespace and datafile system tables.
  26. 210803 7:03:00 [Note] InnoDB: Tablespace and datafile system tables created.
  27. 210803 7:03:00 [Note] InnoDB: Waiting for purge to start
  28. 210803 7:03:00 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence number 0
  29. 210803 7:03:00 [Note] Plugin 'FEEDBACK' is disabled.
  30. 2021-08-03 07:03:00 7fe604ffd700 InnoDB: Loading buffer pool(s) from .//ib_buffer_pool
  31. 2021-08-03 07:03:00 7fe604ffd700 InnoDB: Cannot open './/ib_buffer_pool' for reading: No such file or directory
  32. 210803 7:03:00 [Note] Server socket created on IP: '::'.
  33. 210803 7:03:00 [Warning] InnoDB: Cannot open table mysql/gtid_slave_pos from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  34. 210803 7:03:00 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1932: Table 'mysql.gtid_slave_pos' doesn't exist in engine
  35. 210803 7:03:00 [Note] /usr/sbin/mysqld: ready for connections.
  36. Version: '10.0.38-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
  37. 210803 7:03:00 [Warning] InnoDB: Cannot open table mysql/gtid_slave_pos from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  38. 210803 7:03:00 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  39. 210803 7:03:00 [Warning] InnoDB: Cannot open table mysql/innodb_table_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  40. 210803 7:03:00 [Warning] InnoDB: Cannot open table mysql/gtid_slave_pos from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  41. 210803 7:03:00 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  42. 210803 7:03:00 [Warning] InnoDB: Cannot open table mysql/innodb_table_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  43. 210803 7:03:00 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  44. 210803 7:03:00 [Warning] InnoDB: Cannot open table mysql/innodb_table_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  45. 210803 7:03:00 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  46. 210803 7:03:00 [Warning] InnoDB: Cannot open table mysql/innodb_table_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  47. 210803 7:03:00 [Warning] InnoDB: Cannot open table mysql/innodb_index_stats from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  48. 210803 7:03:14 [Note] /usr/sbin/mysqld: Normal shutdown
  49. 210803 7:03:14 [Note] Event Scheduler: Purging the queue. 0 events
  50. 210803 7:03:14 [Note] InnoDB: FTS optimize thread exiting.
  51. 210803 7:03:14 [Note] InnoDB: Starting shutdown...
  52. 2021-08-03 07:03:14 7fe604ffd700 InnoDB: Dumping buffer pool(s) to .//ib_buffer_pool
  53. 2021-08-03 07:03:14 7fe604ffd700 InnoDB: Buffer pool(s) dump completed at 210803 7:03:14
  54. 210803 7:03:14 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
  55. 210803 7:03:16 [Note] InnoDB: Shutdown completed; log sequence number 1600614
  56. 210803 7:03:16 [Note] /usr/sbin/mysqld: Shutdown complete
  57.  
  58. 210803 07:03:16 mysqld_safe mysqld from pid file /var/lib/mysql/centos7x64.pid ended
  59. 210803 07:03:27 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
  60. 210803 7:03:27 [Note] /usr/sbin/mysqld (mysqld 10.0.38-MariaDB) starting as process 1886 ...
  61. 210803 7:03:27 [Note] InnoDB: Using mutexes to ref count buffer pool pages
  62. 210803 7:03:27 [Note] InnoDB: The InnoDB memory heap is disabled
  63. 210803 7:03:27 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  64. 210803 7:03:27 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
  65. 210803 7:03:27 [Note] InnoDB: Compressed tables use zlib 1.2.7
  66. 210803 7:03:27 [Note] InnoDB: Using Linux native AIO
  67. 210803 7:03:27 [Note] InnoDB: Using CPU crc32 instructions
  68. 210803 7:03:27 [Note] InnoDB: Initializing buffer pool, size = 192.0M
  69. 210803 7:03:27 [Note] InnoDB: Completed initialization of buffer pool
  70. 210803 7:03:27 [Note] InnoDB: Highest supported file format is Barracuda.
  71. 210803 7:03:27 [Note] InnoDB: 128 rollback segment(s) are active.
  72. 210803 7:03:27 [Note] InnoDB: Waiting for purge to start
  73. 210803 7:03:28 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence number 1600614
  74. 210803 7:03:28 [Note] Plugin 'FEEDBACK' is disabled.
  75. 2021-08-03 07:03:28 7f75007fd700 InnoDB: Loading buffer pool(s) from .//ib_buffer_pool
  76. 2021-08-03 07:03:28 7f75007fd700 InnoDB: Buffer pool(s) load completed at 210803 7:03:28
  77. 210803 7:03:28 [Note] Server socket created on IP: '::'.
  78. 210803 7:03:28 [Warning] InnoDB: Cannot open table mysql/gtid_slave_pos from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
  79. 210803 7:03:28 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1932: Table 'mysql.gtid_slave_pos' doesn't exist in engine
  80. 210803 7:03:28 [Note] /usr/sbin/mysqld: ready for connections.
  81. Version: '10.0.38-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
  82. 2021-08-03 07:26:53 7f75263f2700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
  83. 210803 07:32:42 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
  84. 210803 7:32:42 [Note] /usr/sbin/mysqld (mysqld 10.0.38-MariaDB) starting as process 1547 ...
  85. 210803 7:32:43 [Note] InnoDB: Using mutexes to ref count buffer pool pages
  86. 210803 7:32:43 [Note] InnoDB: The InnoDB memory heap is disabled
  87. 210803 7:32:43 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  88. 210803 7:32:43 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
  89. 210803 7:32:43 [Note] InnoDB: Compressed tables use zlib 1.2.7
  90. 210803 7:32:43 [Note] InnoDB: Using Linux native AIO
  91. 210803 7:32:43 [Note] InnoDB: Using CPU crc32 instructions
  92. 210803 7:32:43 [Note] InnoDB: Initializing buffer pool, size = 192.0M
  93. 210803 7:32:43 [Note] InnoDB: Completed initialization of buffer pool
  94. 210803 7:32:43 [Note] InnoDB: Highest supported file format is Barracuda.
  95. 210803 7:32:43 [Note] InnoDB: The log sequence numbers 1600614 and 1600614 in ibdata files do not match the log sequence number 309779133 in the ib_logfiles!
  96. 210803 7:32:43 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 4 at filepath: ./mysql/innodb_index_stats.ibd. Cannot open tablespace vdstoredb/nb2_actionscheduler_claims which uses space ID: 4 at filepath: ./vdstoredb/nb2_actionscheduler_claims.ibd
  97. 2021-08-03 07:32:43 7f867931b8c0 InnoDB: Operating system error number 2 in a file operation.
  98. InnoDB: The error means the system cannot find the path specified.
  99. InnoDB: If you are installing InnoDB, remember that you must create
  100. InnoDB: directories yourself, InnoDB does not create them.
  101. InnoDB: Error: could not open single-table tablespace file ./vdstoredb/nb2_actionscheduler_claims.ibd
  102. InnoDB: We do not continue the crash recovery, because the table may become
  103. InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
  104. InnoDB: To fix the problem and start mysqld:
  105. InnoDB: 1) If there is a permission problem in the file and mysqld cannot
  106. InnoDB: open the file, you should modify the permissions.
  107. InnoDB: 2) If the table is not needed, or you can restore it from a backup,
  108. InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
  109. InnoDB: crash recovery and ignore that table.
  110. InnoDB: 3) If the file system or the disk is broken, and you cannot remove
  111. InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
  112. InnoDB: and force InnoDB to continue crash recovery here.
  113. 210803 07:32:43 mysqld_safe mysqld from pid file /var/lib/mysql/centos7x64.pid ended
  114. 210803 07:38:40 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
  115. 210803 7:38:40 [Note] /usr/sbin/mysqld (mysqld 10.0.38-MariaDB) starting as process 2504 ...
  116. 210803 7:38:41 [Note] InnoDB: Using mutexes to ref count buffer pool pages
  117. 210803 7:38:41 [Note] InnoDB: The InnoDB memory heap is disabled
  118. 210803 7:38:41 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  119. 210803 7:38:41 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
  120. 210803 7:38:41 [Note] InnoDB: Compressed tables use zlib 1.2.7
  121. 210803 7:38:41 [Note] InnoDB: Using Linux native AIO
  122. 210803 7:38:41 [Note] InnoDB: Using CPU crc32 instructions
  123. 210803 7:38:41 [Note] InnoDB: Initializing buffer pool, size = 192.0M
  124. 210803 7:38:41 [Note] InnoDB: Completed initialization of buffer pool
  125. 210803 7:38:41 [Note] InnoDB: Highest supported file format is Barracuda.
  126. 210803 7:38:41 [Note] InnoDB: The log sequence numbers 1600614 and 1600614 in ibdata files do not match the log sequence number 309779133 in the ib_logfiles!
  127. 210803 7:38:41 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 4 at filepath: ./mysql/innodb_index_stats.ibd. Cannot open tablespace vdstoredb/nb2_actionscheduler_claims which uses space ID: 4 at filepath: ./vdstoredb/nb2_actionscheduler_claims.ibd
  128. 2021-08-03 07:38:41 7f853d8c98c0 InnoDB: Operating system error number 2 in a file operation.
  129. InnoDB: The error means the system cannot find the path specified.
  130. InnoDB: If you are installing InnoDB, remember that you must create
  131. InnoDB: directories yourself, InnoDB does not create them.
  132. InnoDB: Error: could not open single-table tablespace file ./vdstoredb/nb2_actionscheduler_claims.ibd
  133. InnoDB: We do not continue the crash recovery, because the table may become
  134. InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
  135. InnoDB: To fix the problem and start mysqld:
  136. InnoDB: 1) If there is a permission problem in the file and mysqld cannot
  137. InnoDB: open the file, you should modify the permissions.
  138. InnoDB: 2) If the table is not needed, or you can restore it from a backup,
  139. InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
  140. InnoDB: crash recovery and ignore that table.
  141. InnoDB: 3) If the file system or the disk is broken, and you cannot remove
  142. InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
  143. InnoDB: and force InnoDB to continue crash recovery here.
  144. 210803 07:38:41 mysqld_safe mysqld from pid file /var/lib/mysql/centos7x64.pid ended
  145. 210803 07:40:17 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
  146. 210803 7:40:17 [Note] /usr/sbin/mysqld (mysqld 10.0.38-MariaDB) starting as process 3122 ...
  147. 210803 7:40:17 [Note] InnoDB: Using mutexes to ref count buffer pool pages
  148. 210803 7:40:17 [Note] InnoDB: The InnoDB memory heap is disabled
  149. 210803 7:40:17 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  150. 210803 7:40:17 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
  151. 210803 7:40:17 [Note] InnoDB: Compressed tables use zlib 1.2.7
  152. 210803 7:40:17 [Note] InnoDB: Using Linux native AIO
  153. 210803 7:40:17 [Note] InnoDB: Using CPU crc32 instructions
  154. 210803 7:40:17 [Note] InnoDB: Initializing buffer pool, size = 192.0M
  155. 210803 7:40:17 [Note] InnoDB: Completed initialization of buffer pool
  156. 210803 7:40:17 [Note] InnoDB: Highest supported file format is Barracuda.
  157. 210803 7:40:17 [Note] InnoDB: The log sequence numbers 1600614 and 1600614 in ibdata files do not match the log sequence number 309779133 in the ib_logfiles!
  158. 210803 7:40:17 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 4 at filepath: ./mysql/innodb_index_stats.ibd. Cannot open tablespace vdstoredb/nb2_actionscheduler_claims which uses space ID: 4 at filepath: ./vdstoredb/nb2_actionscheduler_claims.ibd
  159. 2021-08-03 07:40:17 7ff56a9fd8c0 InnoDB: Operating system error number 2 in a file operation.
  160. InnoDB: The error means the system cannot find the path specified.
  161. InnoDB: If you are installing InnoDB, remember that you must create
  162. InnoDB: directories yourself, InnoDB does not create them.
  163. InnoDB: Error: could not open single-table tablespace file ./vdstoredb/nb2_actionscheduler_claims.ibd
  164. InnoDB: We do not continue the crash recovery, because the table may become
  165. InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
  166. InnoDB: To fix the problem and start mysqld:
  167. InnoDB: 1) If there is a permission problem in the file and mysqld cannot
  168. InnoDB: open the file, you should modify the permissions.
  169. InnoDB: 2) If the table is not needed, or you can restore it from a backup,
  170. InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
  171. InnoDB: crash recovery and ignore that table.
  172. InnoDB: 3) If the file system or the disk is broken, and you cannot remove
  173. InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
  174. InnoDB: and force InnoDB to continue crash recovery here.
  175. 210803 07:40:17 mysqld_safe mysqld from pid file /var/lib/mysql/centos7x64.pid ended
  176.  
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!