1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403
|
2015-06-24 15:13:08 11168 [Note] Plugin 'FEDERATED' is disabled.
2015-06-24 15:13:08 2bc4 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-06-24 15:13:08 11168 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-24 15:13:08 11168 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-24 15:13:08 11168 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-24 15:13:08 11168 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-24 15:13:08 11168 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-24 15:13:08 11168 [Note] InnoDB: Completed initialization of buffer pool
2015-06-24 15:13:08 11168 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-24 15:13:08 11168 [Note] InnoDB: 128 rollback segment(s) are active.
2015-06-24 15:13:08 11168 [Note] InnoDB: Waiting for purge to start
2015-06-24 15:13:09 11168 [Note] InnoDB: 5.6.11 started; log sequence number 1758932
2015-06-24 15:13:09 11168 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
2015-06-24 15:13:09 11168 [Note] - '127.0.0.1' resolves to '127.0.0.1';
2015-06-24 15:13:09 11168 [Note] Server socket created on IP: '127.0.0.1'.
2015-06-24 15:13:10 11168 [Warning] InnoDB: Cannot open table mysql/slave_master_info 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.
2015-06-24 15:13:10 11168 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2015-06-24 15:13:10 11168 [Warning] InnoDB: Cannot open table mysql/slave_worker_info 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.
2015-06-24 15:13:10 11168 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info 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.
2015-06-24 15:13:10 11168 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2015-06-24 15:13:11 11168 [Note] Event Scheduler: Loaded 0 events
2015-06-24 15:13:11 11168 [Note] E:\EASYPH~1.1VC\EASYPH~2.1VC\binaries\mysql\bin\mysqld.exe: ready for connections.
Version: '5.6.11-log' socket: '' port: 3306 MySQL Community Server (GPL)
2015-06-24 15:13:35 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:13:35 2a1c InnoDB: Error: Fetch of persistent statistics requested for table "touslesport"."parcours" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2015-06-24 15:13:35 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:13:35 2a1c InnoDB: Error: Fetch of persistent statistics requested for table "touslesport"."parcours_bis" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2015-06-24 15:13:35 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:13:35 2a1c InnoDB: Error: Fetch of persistent statistics requested for table "touslesport"."sorties" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2015-06-24 15:13:35 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:13:35 2a1c InnoDB: Error: Fetch of persistent statistics requested for table "touslesport"."sorties_bis" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2015-06-24 15:54:45 11168 [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.
2015-06-24 15:54:45 11168 [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.
2015-06-24 15:54:45 11168 [Warning] InnoDB: Cannot open table mysql/slave_master_info 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.
2015-06-24 15:54:45 11168 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info 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.
2015-06-24 15:54:45 11168 [Warning] InnoDB: Cannot open table mysql/slave_worker_info 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.
2015-06-24 15:54:45 11168 [Warning] InnoDB: Cannot open table sport/parcours 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.
2015-06-24 15:54:45 11168 [Warning] InnoDB: Cannot open table sport/parcours@002dbis 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.
2015-06-24 15:54:45 11168 [Warning] InnoDB: Cannot open table sport/sorties 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.
2015-06-24 15:54:45 11168 [Warning] InnoDB: Cannot open table sport/sorties@002dbis 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.
2015-06-24 15:54:45 11168 [Warning] InnoDB: Cannot open table sport_essai1/parcours 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.
2015-06-24 15:54:45 11168 [Warning] InnoDB: Cannot open table sport_essai1/sorties 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.
2015-06-24 15:54:45 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:54:45 2a1c InnoDB: Error: Fetch of persistent statistics requested for table "touslesport"."parcours" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2015-06-24 15:54:45 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:54:45 2a1c InnoDB: Error: Fetch of persistent statistics requested for table "touslesport"."parcours_bis" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2015-06-24 15:54:45 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:54:45 2a1c InnoDB: Error: Fetch of persistent statistics requested for table "touslesport"."sorties" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2015-06-24 15:54:45 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:54:45 2a1c InnoDB: Error: Fetch of persistent statistics requested for table "touslesport"."sorties_bis" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2015-06-24 15:54:46 11168 [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.
2015-06-24 15:54:46 11168 [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.
2015-06-24 15:54:47 11168 [Warning] InnoDB: Cannot open table mysql/slave_master_info 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.
2015-06-24 15:54:47 11168 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info 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.
2015-06-24 15:54:47 11168 [Warning] InnoDB: Cannot open table mysql/slave_worker_info 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.
2015-06-24 15:54:48 11168 [Warning] InnoDB: Cannot open table sport/parcours 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.
2015-06-24 15:54:48 11168 [Warning] InnoDB: Cannot open table sport/parcours@002dbis 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.
2015-06-24 15:54:48 11168 [Warning] InnoDB: Cannot open table sport/sorties 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.
2015-06-24 15:54:48 11168 [Warning] InnoDB: Cannot open table sport/sorties@002dbis 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.
2015-06-24 15:54:48 11168 [Warning] InnoDB: Cannot open table sport_essai1/parcours 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.
2015-06-24 15:54:48 11168 [Warning] InnoDB: Cannot open table sport_essai1/sorties 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.
2015-06-24 15:54:48 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:54:48 2a1c InnoDB: Error: Fetch of persistent statistics requested for table "touslesport"."parcours" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2015-06-24 15:54:48 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:54:48 2a1c InnoDB: Error: Fetch of persistent statistics requested for table "touslesport"."parcours_bis" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2015-06-24 15:54:48 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:54:48 2a1c InnoDB: Error: Fetch of persistent statistics requested for table "touslesport"."sorties" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2015-06-24 15:54:48 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:54:48 2a1c InnoDB: Error: Fetch of persistent statistics requested for table "touslesport"."sorties_bis" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2015-06-24 15:55:19 25d4 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:55:19 25d4 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:55:19 25d4 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:55:19 25d4 InnoDB: Recalculation of persistent statistics requested for table "touslesport"."sorties_bis" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2015-06-24 15:55:19 25d4 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 15:55:19 25d4 InnoDB: Error: Fetch of persistent statistics requested for table "touslesport"."sorties_bis" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2015-06-24 16:21:33 1928 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 16:21:33 1928 InnoDB: Recalculation of persistent statistics requested for table "touslesport"."sorties_bis" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2015-06-24 16:25:32 1928 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 16:25:33 1928 InnoDB: Recalculation of persistent statistics requested for table "touslesport"."sorties_bis" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2015-06-24 16:28:24 1928 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 16:28:24 1928 InnoDB: Recalculation of persistent statistics requested for table "touslesport"."sorties_bis" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2015-06-24 16:30:27 1928 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 16:30:27 1928 InnoDB: Recalculation of persistent statistics requested for table "touslesport"."sorties_bis" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2015-06-24 16:54:04 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 16:54:04 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 16:54:04 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 16:54:04 2a1c InnoDB: Recalculation of persistent statistics requested for table "touslesport"."sorties_bis" but the required persistent statistics storage is not present or is corrupted. Using transient stats instead.
2015-06-24 16:54:05 2a1c InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2015-06-24 16:54:05 2a1c InnoDB: Error: Fetch of persistent statistics requested for table "touslesport"."sorties_bis" but the required system tables mysql.innodb_table_stats and mysql.innodb_index_stats are not present or have unexpected structure. Using transient stats instead.
2015-06-25 09:45:57 2128 [Note] Plugin 'FEDERATED' is disabled.
2015-06-25 09:45:57 21b8 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-06-25 09:45:57 2128 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-25 09:45:57 2128 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-25 09:45:57 2128 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-25 09:45:57 2128 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-25 09:45:57 2128 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-25 09:45:57 2128 [Note] InnoDB: Completed initialization of buffer pool
2015-06-25 09:45:58 2128 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-25 09:45:58 2128 [Note] InnoDB: The log sequence numbers 1758932 and 1758932 in ibdata files do not match the log sequence number 1782626 in the ib_logfiles!
2015-06-25 09:45:58 2128 [Note] InnoDB: Database was not shutdown normally!
2015-06-25 09:45:58 2128 [Note] InnoDB: Starting crash recovery.
2015-06-25 09:45:58 2128 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-25 09:45:58 2128 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace touslesport/parcours which uses space ID: 3 at filepath: .\touslesport\parcours.ibd
InnoDB: Error: could not open single-table tablespace file .\touslesport\parcours.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-06-25 09:46:15 11880 [Note] Plugin 'FEDERATED' is disabled.
2015-06-25 09:46:15 2d10 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-06-25 09:46:15 11880 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-25 09:46:15 11880 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-25 09:46:15 11880 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-25 09:46:15 11880 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-25 09:46:15 11880 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-25 09:46:15 11880 [Note] InnoDB: Completed initialization of buffer pool
2015-06-25 09:46:15 11880 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-25 09:46:15 11880 [Note] InnoDB: The log sequence numbers 1758932 and 1758932 in ibdata files do not match the log sequence number 1782626 in the ib_logfiles!
2015-06-25 09:46:15 11880 [Note] InnoDB: Database was not shutdown normally!
2015-06-25 09:46:15 11880 [Note] InnoDB: Starting crash recovery.
2015-06-25 09:46:15 11880 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-25 09:46:15 11880 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace touslesport/parcours which uses space ID: 3 at filepath: .\touslesport\parcours.ibd
InnoDB: Error: could not open single-table tablespace file .\touslesport\parcours.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-06-25 09:46:30 7972 [Note] Plugin 'FEDERATED' is disabled.
2015-06-25 09:46:30 2ef0 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-06-25 09:46:30 7972 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-25 09:46:30 7972 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-25 09:46:30 7972 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-25 09:46:30 7972 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-25 09:46:30 7972 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-25 09:46:30 7972 [Note] InnoDB: Completed initialization of buffer pool
2015-06-25 09:46:30 7972 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-25 09:46:30 7972 [Note] InnoDB: The log sequence numbers 1758932 and 1758932 in ibdata files do not match the log sequence number 1782626 in the ib_logfiles!
2015-06-25 09:46:30 7972 [Note] InnoDB: Database was not shutdown normally!
2015-06-25 09:46:30 7972 [Note] InnoDB: Starting crash recovery.
2015-06-25 09:46:30 7972 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-25 09:46:30 7972 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace touslesport/parcours which uses space ID: 3 at filepath: .\touslesport\parcours.ibd
InnoDB: Error: could not open single-table tablespace file .\touslesport\parcours.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-06-25 09:46:46 6720 [Note] Plugin 'FEDERATED' is disabled.
2015-06-25 09:46:46 1780 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-06-25 09:46:46 6720 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-25 09:46:46 6720 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-25 09:46:46 6720 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-25 09:46:46 6720 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-25 09:46:46 6720 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-25 09:46:46 6720 [Note] InnoDB: Completed initialization of buffer pool
2015-06-25 09:46:46 6720 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-25 09:46:46 6720 [Note] InnoDB: The log sequence numbers 1758932 and 1758932 in ibdata files do not match the log sequence number 1782626 in the ib_logfiles!
2015-06-25 09:46:46 6720 [Note] InnoDB: Database was not shutdown normally!
2015-06-25 09:46:46 6720 [Note] InnoDB: Starting crash recovery.
2015-06-25 09:46:46 6720 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-25 09:46:46 6720 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace touslesport/parcours which uses space ID: 3 at filepath: .\touslesport\parcours.ibd
InnoDB: Error: could not open single-table tablespace file .\touslesport\parcours.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-06-25 09:47:21 8172 [Note] Plugin 'FEDERATED' is disabled.
2015-06-25 09:47:21 1314 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-06-25 09:47:21 8172 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-25 09:47:21 8172 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-25 09:47:21 8172 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-25 09:47:21 8172 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-25 09:47:21 8172 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-25 09:47:21 8172 [Note] InnoDB: Completed initialization of buffer pool
2015-06-25 09:47:21 8172 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-25 09:47:21 8172 [Note] InnoDB: The log sequence numbers 1758932 and 1758932 in ibdata files do not match the log sequence number 1782626 in the ib_logfiles!
2015-06-25 09:47:21 8172 [Note] InnoDB: Database was not shutdown normally!
2015-06-25 09:47:21 8172 [Note] InnoDB: Starting crash recovery.
2015-06-25 09:47:21 8172 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-25 09:47:21 8172 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace touslesport/parcours which uses space ID: 3 at filepath: .\touslesport\parcours.ibd
InnoDB: Error: could not open single-table tablespace file .\touslesport\parcours.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-06-25 09:48:10 11396 [Note] Plugin 'FEDERATED' is disabled.
2015-06-25 09:48:10 2a18 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-06-25 09:48:10 11396 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-25 09:48:10 11396 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-25 09:48:10 11396 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-25 09:48:10 11396 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-25 09:48:10 11396 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-25 09:48:10 11396 [Note] InnoDB: Completed initialization of buffer pool
2015-06-25 09:48:10 11396 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-25 09:48:10 11396 [Note] InnoDB: The log sequence numbers 1758932 and 1758932 in ibdata files do not match the log sequence number 1782626 in the ib_logfiles!
2015-06-25 09:48:10 11396 [Note] InnoDB: Database was not shutdown normally!
2015-06-25 09:48:10 11396 [Note] InnoDB: Starting crash recovery.
2015-06-25 09:48:10 11396 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-25 09:48:10 11396 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace touslesport/parcours which uses space ID: 3 at filepath: .\touslesport\parcours.ibd
InnoDB: Error: could not open single-table tablespace file .\touslesport\parcours.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-06-25 09:56:31 12172 [Note] Plugin 'FEDERATED' is disabled.
2015-06-25 09:56:31 f04 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-06-25 09:56:31 12172 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-25 09:56:31 12172 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-25 09:56:31 12172 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-25 09:56:31 12172 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-25 09:56:31 12172 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-25 09:56:31 12172 [Note] InnoDB: Completed initialization of buffer pool
2015-06-25 09:56:31 12172 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-25 09:56:31 12172 [Note] InnoDB: The log sequence numbers 1758932 and 1758932 in ibdata files do not match the log sequence number 1782626 in the ib_logfiles!
2015-06-25 09:56:31 12172 [Note] InnoDB: Database was not shutdown normally!
2015-06-25 09:56:31 12172 [Note] InnoDB: Starting crash recovery.
2015-06-25 09:56:31 12172 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-25 09:56:31 12172 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace touslesport/parcours which uses space ID: 3 at filepath: .\touslesport\parcours.ibd
InnoDB: Error: could not open single-table tablespace file .\touslesport\parcours.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-06-25 10:00:34 7380 [Note] Plugin 'FEDERATED' is disabled.
2015-06-25 10:00:34 2704 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-06-25 10:00:34 7380 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-25 10:00:34 7380 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-25 10:00:34 7380 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-25 10:00:34 7380 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-25 10:00:34 7380 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-25 10:00:34 7380 [Note] InnoDB: Completed initialization of buffer pool
2015-06-25 10:00:34 7380 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-25 10:00:34 7380 [Note] InnoDB: The log sequence numbers 1758932 and 1758932 in ibdata files do not match the log sequence number 1782626 in the ib_logfiles!
2015-06-25 10:00:34 7380 [Note] InnoDB: Database was not shutdown normally!
2015-06-25 10:00:34 7380 [Note] InnoDB: Starting crash recovery.
2015-06-25 10:00:34 7380 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-25 10:00:34 7380 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace touslesport/parcours which uses space ID: 3 at filepath: .\touslesport\parcours.ibd
InnoDB: Error: could not open single-table tablespace file .\touslesport\parcours.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-06-25 10:00:56 6448 [Note] Plugin 'FEDERATED' is disabled.
2015-06-25 10:00:56 4fc InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-06-25 10:00:56 6448 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-25 10:00:56 6448 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-25 10:00:56 6448 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-25 10:00:56 6448 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-25 10:00:56 6448 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-25 10:00:56 6448 [Note] InnoDB: Completed initialization of buffer pool
2015-06-25 10:00:56 6448 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-25 10:00:56 6448 [Note] InnoDB: The log sequence numbers 1758932 and 1758932 in ibdata files do not match the log sequence number 1782626 in the ib_logfiles!
2015-06-25 10:00:56 6448 [Note] InnoDB: Database was not shutdown normally!
2015-06-25 10:00:56 6448 [Note] InnoDB: Starting crash recovery.
2015-06-25 10:00:56 6448 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-25 10:00:56 6448 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace touslesport/parcours which uses space ID: 3 at filepath: .\touslesport\parcours.ibd
InnoDB: Error: could not open single-table tablespace file .\touslesport\parcours.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-06-25 10:32:15 12932 [Note] Plugin 'FEDERATED' is disabled.
2015-06-25 10:32:16 37bc InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-06-25 10:32:16 12932 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-25 10:32:16 12932 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-25 10:32:16 12932 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-25 10:32:16 12932 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-25 10:32:16 12932 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-25 10:32:16 12932 [Note] InnoDB: Completed initialization of buffer pool
2015-06-25 10:32:16 12932 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-25 10:32:16 12932 [Note] InnoDB: The log sequence numbers 1758932 and 1758932 in ibdata files do not match the log sequence number 1782626 in the ib_logfiles!
2015-06-25 10:32:16 12932 [Note] InnoDB: Database was not shutdown normally!
2015-06-25 10:32:16 12932 [Note] InnoDB: Starting crash recovery.
2015-06-25 10:32:16 12932 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-25 10:32:16 12932 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace touslesport/parcours which uses space ID: 3 at filepath: .\touslesport\parcours.ibd
InnoDB: Error: could not open single-table tablespace file .\touslesport\parcours.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-06-25 10:45:20 15792 [Note] Plugin 'FEDERATED' is disabled.
2015-06-25 10:45:20 34c8 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-06-25 10:45:20 15792 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-25 10:45:20 15792 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-25 10:45:20 15792 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-25 10:45:20 15792 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-25 10:45:20 15792 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-25 10:45:20 15792 [Note] InnoDB: Completed initialization of buffer pool
2015-06-25 10:45:20 15792 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-25 10:45:20 15792 [Note] InnoDB: The log sequence numbers 1758932 and 1758932 in ibdata files do not match the log sequence number 1782626 in the ib_logfiles!
2015-06-25 10:45:20 15792 [Note] InnoDB: Database was not shutdown normally!
2015-06-25 10:45:20 15792 [Note] InnoDB: Starting crash recovery.
2015-06-25 10:45:20 15792 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-25 10:45:20 15792 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace touslesport/parcours which uses space ID: 3 at filepath: .\touslesport\parcours.ibd
InnoDB: Error: could not open single-table tablespace file .\touslesport\parcours.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-06-25 11:08:16 16880 [Note] Plugin 'FEDERATED' is disabled.
2015-06-25 11:08:16 42bc InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-06-25 11:08:16 16880 [Note] InnoDB: The InnoDB memory heap is disabled
2015-06-25 11:08:16 16880 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-06-25 11:08:16 16880 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-06-25 11:08:16 16880 [Note] InnoDB: Not using CPU crc32 instructions
2015-06-25 11:08:16 16880 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-06-25 11:08:16 16880 [Note] InnoDB: Completed initialization of buffer pool
2015-06-25 11:08:16 16880 [Note] InnoDB: Highest supported file format is Barracuda.
2015-06-25 11:08:16 16880 [Note] InnoDB: The log sequence numbers 1758932 and 1758932 in ibdata files do not match the log sequence number 1782626 in the ib_logfiles!
2015-06-25 11:08:16 16880 [Note] InnoDB: Database was not shutdown normally!
2015-06-25 11:08:16 16880 [Note] InnoDB: Starting crash recovery.
2015-06-25 11:08:16 16880 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-06-25 11:08:16 16880 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/slave_relay_log_info uses space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open tablespace touslesport/parcours which uses space ID: 3 at filepath: .\touslesport\parcours.ibd
InnoDB: Error: could not open single-table tablespace file .\touslesport\parcours.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here. |
Partager