Логотип   Простое и понятное управление
  Уникальные возможности по настройке
  Open Server скачали уже 1 021 987 раз!

Форум

Добро пожаловать, Гость!

Сервер не запускается? Пиши СЮДА!

Обсуждение проблем в работе программного комплекса
aleks1234
Сообщения: 2
C нами: 9 мес 5 дней

Непрочитанное сообщение aleks1234 » 04 мар 2016, 11:46

Не удалось установить Open Server... ОС Windows 10 x64, антивирус от Микрософта. Пробовал установить от имени админа - бесполезно. Возможно что то с установочным файлом, хеш md5 98719D4CC299D621893A1C19BABB8D20
Вложения
Безымянный.png
скрин

aleks1234
Сообщения: 2
C нами: 9 мес 5 дней

Непрочитанное сообщение aleks1234 » 04 мар 2016, 13:13

решилась проблемка... скачал установочный файл с торрента

trump90
Сообщения: 1
C нами: 9 мес 4 дня

Непрочитанное сообщение trump90 » 05 мар 2016, 10:45

Добрый день!

Подскажите, пожалуйста, в чем может быть проблема?
При обращении к mysql (установка joomla) "вылетает" mysqld.exe, сам сервер не падает
Протестировано на трех разных системах - две win7 64x и win10 64x, запускается одна и та же копия Open Server 5.2.3, с внешнего hdd

Основной лог:
2016-03-05 12:41:10  --------------------------------------------
2016-03-05 12:41:10  Начало процедуры запуска сервера
2016-03-05 12:41:10  Обновление Hosts файла
2016-03-05 12:41:10  Обновление конфигурации MySQL-5.5
2016-03-05 12:41:10  Обновление конфигурации Sendmail
2016-03-05 12:41:10  Обновление конфигурации PHP-5.3
2016-03-05 12:41:10  Обновление конфигурации PHPMyAdmin
2016-03-05 12:41:10  Обновление конфигурации Apache-2.2
2016-03-05 12:41:11  Запуск MySQL-5.5
2016-03-05 12:41:11  Запуск Apache-2.2
2016-03-05 12:41:11  Проверка состояния сервера
2016-03-05 12:41:15  Cервер успешно запущен за 5,226 секунд!

Apache отладка:
[05-Mar-2016 10:41:47 Europe/Moscow] PHP Warning:  mysqli_query() [<a href='function.mysqli-query'>function.mysqli-query</a>]: MySQL server has gone away in E:\OpenServer\domains\cybertronik\libraries\joomla\database\database\mysqli.php on line 382
[05-Mar-2016 10:41:47 Europe/Moscow] PHP Warning:  mysqli_query() [<a href='function.mysqli-query'>function.mysqli-query</a>]: Error reading result set's header in E:\OpenServer\domains\cybertronik\libraries\joomla\database\database\mysqli.php on line 382
[05-Mar-2016 10:41:47 Europe/Moscow] PHP Fatal error:  Uncaught exception 'JDatabaseException' with message 'MySQL server has gone away SQL=UPDATE `i8l1o_extensions` SET `name`='com_cpanel',`type`='component',`element`='com_cpanel',`folder`='',`client_id`='1',`enabled`='1',`access`='1',`protected`='1',`manifest_cache`='{\"legacy\":false,\"name\":\"com_cpanel\",\"type\":\"component\",\"creationDate\":\"April 2006\",\"author\":\"Joomla! Project\",\"copyright\":\"(C) 2005 - 2014 Open Source Matters. All rights reserved.\",\"authorEmail\":\"admin@joomla.org\",\"authorUrl\":\"www.joomla.org\",\"version\":\"2.5.0\",\"description\":\"COM_CPANEL_XML_DESCRIPTION\",\"group\":\"\"}',`params`='',`custom_data`='',`system_data`='',`checked_out`='0',`checked_out_time`='0000-00-00 00:00:00',`ordering`='0',`state`='0' WHERE `extension_id`='9'' in E:\OpenServer\domains\cybertronik\libraries\joomla\database\database\mysqli.php:403
Stack trace:
#0 E:\OpenServer\domains\cybertronik\libraries\joomla\database\database.php(1676): JDatabaseMySQLi->execute()
#1 E:\OpenServer\domains\cybertronik\libraries\joomla\database\table.php(611): JDatabase->updateObject('#__extensions', Object(JTableExtension), 'extension_id', false)
#2 E:\OpenServer\domains\cybertronik\libraries\joomla\installer\adapters\component.php(2031): JTable->store()
#3 E:\OpenServer\domains\cybertronik\libraries\joomla\installer\installer.php(767): JInstallerComponent->refreshManifestCache()
#4 E:\OpenServer\domains\cybertronik\installation\models\database.php(253): JInstaller->refreshManifestCache('9')
#5 E:\OpenServer\domains\cybertronik\installation\controllers\setup.json.php(139): JInstallationModelDatabase->initialise(Array)
#6 E:\OpenServer\domains\cybertronik\libraries\joomla\application\component\controller.php(761): JInstallationControllerSetup->database()
#7 E:\OpenServer\domains\cybertronik\installation\includes\application.php(81): JController->execute('database')
#8 E:\OpenServer\domains\cybertronik\installation\index.php(75): JInstallation->render()
#9 {main}
  thrown in E:\OpenServer\domains\cybertronik\libraries\joomla\database\database\mysqli.php on line 403

MySQL отладка:
160305 12:41:11 [Note] e:\openserver\modules\database\MySQL-5.5\bin\mysqld.exe (mysqld 5.5.45) starting as process 5720 ...
160305 12:41:11 [Note] Plugin 'FEDERATED' is disabled.
160305 12:41:11 InnoDB: The InnoDB memory heap is disabled
160305 12:41:11 InnoDB: Mutexes and rw_locks use Windows interlocked functions
160305 12:41:11 InnoDB: Compressed tables use zlib 1.2.3
160305 12:41:11 InnoDB: Initializing buffer pool, size = 20.0M
160305 12:41:11 InnoDB: Completed initialization of buffer pool
160305 12:41:11 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 26755337
160305 12:41:11  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 27381232
160305 12:41:11  InnoDB: Error: page 4 log sequence number 344546524
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:11  InnoDB: Error: page 816 log sequence number 118023086
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:12  InnoDB: Error: page 210 log sequence number 479461412
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:12  InnoDB: Error: page 8518 log sequence number 479379413
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:13  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 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 160305 12:41:13  InnoDB: Error: page 5455 log sequence number 461247204
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 160305 12:41:13  InnoDB: Error: page 5995 log sequence number 369693593
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
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 160305 12:41:13  InnoDB: Error: page 1273 log sequence number 345301352
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.

InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 214672, file name .\mysql-bin.000300
160305 12:41:14  InnoDB: Error: page 1230 log sequence number 461247204
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 1259 log sequence number 462362491
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 1907 log sequence number 463766164
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 5926 log sequence number 467403074
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 5927 log sequence number 423973676
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 5308 log sequence number 342624898
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 5309 log sequence number 441452687
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 4167 log sequence number 441519093
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 5313 log sequence number 441452687
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 7828 log sequence number 441452687
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 3398 log sequence number 435304944
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 1908 log sequence number 213393509
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 910 log sequence number 118023086
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 1414 log sequence number 344558863
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 1933 log sequence number 130438559
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 619 log sequence number 130438559
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 625 log sequence number 130990993
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 2264 log sequence number 132244495
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 1177 log sequence number 135410096
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 2388 log sequence number 138118781
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 2611 log sequence number 201375712
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 2802 log sequence number 207502458
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 2753 log sequence number 213606312
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 3322 log sequence number 273280612
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 3571 log sequence number 369306125
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 3533 log sequence number 299768195
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 4531 log sequence number 300110463
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 4481 log sequence number 308154811
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 4482 log sequence number 331735993
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 4488 log sequence number 393640747
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 5741 log sequence number 393784736
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 4938 log sequence number 354064992
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 6044 log sequence number 354783442
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 6067 log sequence number 459567071
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 6915 log sequence number 459589859
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 7201 log sequence number 458824036
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 7536 log sequence number 461540022
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 7484 log sequence number 464539302
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 516 log sequence number 118023282
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 701 log sequence number 118023080
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 303 log sequence number 213493551
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Error: page 304 log sequence number 213493633
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:14  InnoDB: Waiting for the background threads to start
160305 12:41:15 InnoDB: 5.5.45 started; log sequence number 27381232
160305 12:41:15 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
160305 12:41:15 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
160305 12:41:15 [Note] Server socket created on IP: '127.0.0.1'.
160305 12:41:15  InnoDB: Error: page 3376 log sequence number 464721934
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:15 [Note] Event Scheduler: Loaded 0 events
160305 12:41:15 [Note] e:\openserver\modules\database\MySQL-5.5\bin\mysqld.exe: ready for connections.
Version: '5.5.45'  socket: ''  port: 3306  MySQL Community Server (GPL)
160305 12:41:15  InnoDB: Error: page 6020 log sequence number 461541629
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:15  InnoDB: Error: page 3369 log sequence number 453948115
InnoDB: is in the future! Current system log sequence number 27381232.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_assets` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_associations` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_banner_clients` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_banner_tracks` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_banners` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_categories` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_contact_details` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_content` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_content_frontpage` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_content_rating` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_core_log_searches` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_extensions` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_filters` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_terms0` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_terms1` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_terms2` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_terms3` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_terms4` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_terms5` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_terms6` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_terms7` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_terms8` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_terms9` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_termsa` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_termsb` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_termsc` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_termsd` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_termse` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_links_termsf` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_taxonomy` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_taxonomy_map` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_terms` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_terms_common` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_finder_types` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_languages` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_menu` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_menu_types` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_messages` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_messages_cfg` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_modules` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_modules_menu` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_newsfeeds` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_overrider` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_redirect_links` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_schemas` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_session` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_template_styles` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_update_categories` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_update_sites` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_update_sites_extensions` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_updates` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_user_notes` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_user_profiles` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_user_usergroup_map` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_usergroups` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_users` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_viewlevels` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:27  InnoDB: Error: table `cyber`.`i8l1o_weblinks` does not exist in the InnoDB internal
InnoDB: data dictionary though MySQL is trying to drop it.
InnoDB: Have you copied the .frm file of the table to the
InnoDB: MySQL database directory from another database?
InnoDB: You can look for further help from
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
160305 12:41:28  InnoDB: Assertion failure in thread 6072 in file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
07:41:28 UTC - mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=268435456
read_buffer_size=268435456
max_used_connections=1
max_threads=30
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3408093 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x23271ed8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
47ed80    mysqld.exe!my_thread_name()
5d955e    mysqld.exe!my_mb_ctype_mb()
527b8d    mysqld.exe!my_osmaperr()
527e6a    mysqld.exe!my_osmaperr()
5284e3    mysqld.exe!my_osmaperr()
4bf6e3    mysqld.exe!my_osmaperr()
51fa13    mysqld.exe!my_osmaperr()
4cd005    mysqld.exe!my_osmaperr()
31fc67    mysqld.exe!?find_field_in_tables@@YAPAVField@@PAVTHD@@PAVItem_ident@@PAUTABLE_LIST@@2PAPAVItem@@W4find_item_error_report_type@@_N5@Z()
3bc8e7    mysqld.exe!?field_type_merge@Field@@SA?AW4enum_field_types@@W42@0@Z()
48c293    mysqld.exe!my_msync()
48c564    mysqld.exe!my_hash_delete()
48c71f    mysqld.exe!my_hash_delete()
360d23    mysqld.exe!?exclude_from_free_memory_list@Query_cache@@IAEXPAUQuery_cache_block@@@Z()
360d66    mysqld.exe!?insert_into_free_memory_list@Query_cache@@IAEXPAUQuery_cache_block@@@Z()
361a93    mysqld.exe!?free_memory_block@Query_cache@@IAEXPAUQuery_cache_block@@@Z()
361e6a    mysqld.exe!?free_query_internal@Query_cache@@AAEXPAUQuery_cache_block@@@Z()
361ea0    mysqld.exe!?free_query@Query_cache@@IAEXPAUQuery_cache_block@@@Z()
35f77f    mysqld.exe!?hostname_cache_free@@YAXXZ()
48cb09    mysqld.exe!my_hash_search()
36018a    mysqld.exe!?unlock@Query_cache@@QAEXXZ()
362c1a    mysqld.exe!?invalidate_table@Query_cache@@IAEXPAVTHD@@PAEI@Z()
362f4e    mysqld.exe!?invalidate_table@Query_cache@@IAEXPAVTHD@@PAUTABLE@@@Z()
363715    mysqld.exe!?invalidate_table@Query_cache@@IAEXPAVTHD@@PAUTABLE_LIST@@@Z()
363724    mysqld.exe!?invalidate_table@Query_cache@@IAEXPAVTHD@@PAUTABLE_LIST@@@Z()
77a33111    ntdll.dll!RtlQueryPerformanceCounter()
589989    mysqld.exe!my_vsnprintf_ex()
3ac9b5    mysqld.exe!?set_ok_status@Diagnostics_area@@QAEXPAVTHD@@_K1PBD@Z()
2e3036    mysqld.exe!?my_ok@@YAXPAVTHD@@_K1PBD@Z()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (232c9c90): UPDATE `i8l1o_extensions` SET `name`='com_cpanel',`type`='component',`element`='com_cpanel',`folder`='',`client_id`='1',`enabled`='1',`access`='1',`protected`='1',`manifest_cache`='{\"legacy\":false,\"name\":\"com_cpanel\",\"type\":\"component\",\"creationDate\":\"April 2006\",\"author\":\"Joomla! Project\",\"copyright\":\"(C) 2005 - 2014 Open Source Matters. All rights reserved.\",\"authorEmail\":\"admin@joomla.org\",\"authorUrl\":\"www.joomla.org\",\"version\":\"2.5.0\",\"description\":\"COM_CPANEL_XML_DESCRIPTION\",\"group\":\"\"}',`params`='',`custom_data`='',`system_data`='',`checked_out`='0',`checked_out_time`='0000-00-00 00:00:00',`ordering`='0',`state`='0' WHERE `extension_id`='9'Connection ID (thread ID): 1
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

В конфиге mysql увеличивал размеры памяти, не помогло.

dizzyk
Сообщения: 7
C нами: 9 мес 2 дня

Непрочитанное сообщение dizzyk » 07 мар 2016, 19:00

Здравствуйте. Поиск ничего не дал.

Default.ini
[main]
start=30
allow=1
autowait=0
emformat=txt
maxmemcache=64
cgiprocess=6
pginitencode=UTF8
pginitlocale=Russian_Russia.1251
ip=127.0.0.1
http_log=1
mysql_log=0
postgresql_log=0
mongodb_log=0
dns_log=0
memcache_log=0
redis_log=0
debugmail=0
mysqlcharset=utf8_general_ci
phpdriver="PHP-5.5"
httpdriver="Apache-2.4"
mysql_driver="MySQL-5.5"
pg_driver=none
mongo_driver=none
memcachedriver=none
redisdriver=none
dnsdriver=none
httpcharset=notset
logreadsize=256
showversion=0
astart=0
crdisk=1
crpath=1
crdomain=0
showfvr=0
showprogs=1
hdomains=0
balloon=1
favorite=0
showswitch=1
debugmode=1
stext=1
sbrowser=1
email=0
vdisk=Z
selfhosts=0
webdir="domains"
browser="%realprogdir%\progs\_Internet\GoogleChromePortable\GoogleChromePortable.exe"
textred="%realprogdir%\progs\_Office\Notepad2\Notepad2.exe"
filebrowser=""
sfilebrowser=0
maxrequests=0
folders=""

[ports]
mysqlport=3306
postgresqlport=5432
mongodbport=27017
httpport=80
httpsport=443
httpbackport=8080
ftpport=21
sftpport=990
phpport=9000
redisport=6379
memcacheport=11211

[ftp]
ftp=0
ftpcommandtimeout=600
ftpconnecttimeout=60

[sendmail]
smtp_server=""
smtp_port=""
auth_username=""
auth_password=""
smtp_ssl=0
pop3_server=""
pop3_username=""
pop3_password=""
force_sender=""



Логи:
основной
2016-03-07 18:45:45  --------------------------------------------
2016-03-07 18:45:45  Начало процедуры запуска сервера
2016-03-07 18:45:46  Обновление Hosts файла
2016-03-07 18:45:46  Обновление конфигурации MySQL-5.5
2016-03-07 18:45:46  Обновление конфигурации Sendmail
2016-03-07 18:45:46  Обновление конфигурации PHP-5.5
2016-03-07 18:45:46  Обновление конфигурации PHPMyAdmin
2016-03-07 18:45:46  Обновление конфигурации Apache-2.4
2016-03-07 18:45:46  Запуск MySQL-5.5
2016-03-07 18:45:46  Запуск Apache-2.4
2016-03-07 18:45:46  Проверка состояния сервера
2016-03-07 18:46:23  Не удалось запустить Apache-2.4
2016-03-07 18:46:23  Сбой запуска!
2016-03-07 18:46:23  --------------------------------------------
2016-03-07 18:46:23  Начало процедуры остановки сервера
2016-03-07 18:46:23  Остановка системных модулей
2016-03-07 18:46:24  Отключение виртуального диска
2016-03-07 18:46:24  Сервер успешно остановлен за 0,859 секунд!


MySQL
160307 18:45:46 [Note] Plugin 'FEDERATED' is disabled.
160307 18:45:46 InnoDB: The InnoDB memory heap is disabled
160307 18:45:46 InnoDB: Mutexes and rw_locks use Windows interlocked functions
160307 18:45:46 InnoDB: Compressed tables use zlib 1.2.3
160307 18:45:46 InnoDB: Initializing buffer pool, size = 20.0M
160307 18:45:46 InnoDB: Completed initialization of buffer pool
160307 18:45:46 InnoDB: highest supported file format is Barracuda.
160307 18:45:47  InnoDB: Waiting for the background threads to start
160307 18:45:48 InnoDB: 5.5.45 started; log sequence number 1595675
160307 18:45:48 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
160307 18:45:48 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
160307 18:45:48 [Note] Server socket created on IP: '127.0.0.1'.
160307 18:45:48 [Note] Event Scheduler: Loaded 0 events
160307 18:45:49 [Note] f:\openserver\modules\database\MySQL-5.5\bin\mysqld.exe: ready for connections.
Version: '5.5.45'  socket: ''  port: 3306  MySQL Community Server (GPL)
160307 18:46:23 [Note] f:\openserver\modules\database\MySQL-5.5\bin\mysqld.exe: Normal shutdown

160307 18:46:23 [Note] Event Scheduler: Purging the queue. 0 events
160307 18:46:23  InnoDB: Starting shutdown...
160307 18:46:24  InnoDB: Shutdown completed; log sequence number 1595675
160307 18:46:24 [Note] f:\openserver\modules\database\MySQL-5.5\bin\mysqld.exe: Shutdown complete


в остальных пусто

Windows 7, не под администратором. Запускал под админом - то же самое
Антивирус Avira. Выключать пробовал.

cmd.jpg

Кракозябры переводятся как "Произошел сбой в программе инициализации библиотеки динамической компоновки"
Первый запуск тоже делал.

Аватара пользователя
barkon
Сообщения: 44
C нами: 9 мес 28 дней

Непрочитанное сообщение barkon » 08 мар 2016, 02:22

Что вы хотите ставить? Ни чего не понятно. Если скрипт на localhost? то он пойдёт. Если домен то надо на сервер поставить IP провайдера.

dizzyk
Сообщения: 7
C нами: 9 мес 2 дня

Непрочитанное сообщение dizzyk » 08 мар 2016, 14:16

barkon писал(а):Что вы хотите ставить? Ни чего не понятно. Если скрипт на localhost? то он пойдёт. Если домен то надо на сервер поставить IP провайдера.

Вы о чем вообще? :o

Аватара пользователя
barkon
Сообщения: 44
C нами: 9 мес 28 дней

Непрочитанное сообщение barkon » 08 мар 2016, 14:32

dizzyk писал(а):
barkon писал(а):Что вы хотите ставить? Ни чего не понятно. Если скрипт на localhost? то он пойдёт. Если домен то надо на сервер поставить IP провайдера.

Вы о чем вообще? :o

На простой localhost?

dizzyk
Сообщения: 7
C нами: 9 мес 2 дня

Непрочитанное сообщение dizzyk » 08 мар 2016, 15:01

Да.
Переустановил пакет Visual C++ для Visual Studio 2012 - php запустился

dizzyk
Сообщения: 7
C нами: 9 мес 2 дня

Непрочитанное сообщение dizzyk » 08 мар 2016, 16:48

Только теперь проблема с mysql
160308 16:43:22 [Note] Plugin 'FEDERATED' is disabled.
160308 16:43:22  InnoDB: Initializing buffer pool, size = 20.0M
160308 16:43:22  InnoDB: Completed initialization of buffer pool
160308 16:43:23  InnoDB: Started; log sequence number 0 45068
160308 16:43:23 [Note] Event Scheduler: Loaded 0 events
160308 16:43:23 [Note] f:\openserver\modules\database\MySQL-5.1\bin\mysqld.exe: ready for connections.
Version: '5.1.73-community'  socket: ''  port: 3306  MySQL Community Server (GPL)
160308 16:43:57 [Note] f:\openserver\modules\database\MySQL-5.1\bin\mysqld.exe: Normal shutdown

160308 16:43:57 [Note] Event Scheduler: Purging the queue. 0 events
160308 16:43:57  InnoDB: Starting shutdown...
160308 16:43:58  InnoDB: Shutdown completed; log sequence number 0 45068
160308 16:43:58 [Note] f:\openserver\modules\database\MySQL-5.1\bin\mysqld.exe: Shutdown complete


2016-03-08 16:43:22  --------------------------------------------
2016-03-08 16:43:22  Начало процедуры запуска сервера
2016-03-08 16:43:22  Обновление Hosts файла
2016-03-08 16:43:22  Обновление конфигурации MySQL-5.1
2016-03-08 16:43:22  Обновление конфигурации Sendmail
2016-03-08 16:43:22  Обновление конфигурации PHP-5.5
2016-03-08 16:43:22  Обновление конфигурации PHPMyAdmin
2016-03-08 16:43:22  Обновление конфигурации Apache-2.4
2016-03-08 16:43:22  Запуск MySQL-5.1
2016-03-08 16:43:22  Запуск Apache-2.4
2016-03-08 16:43:22  Проверка состояния сервера
2016-03-08 16:43:57  Не удалось запустить Apache-2.4
2016-03-08 16:43:57  Сбой запуска!
2016-03-08 16:43:57  --------------------------------------------
2016-03-08 16:43:57  Начало процедуры остановки сервера
2016-03-08 16:43:57  Остановка системных модулей
2016-03-08 16:43:58  Отключение виртуального диска
2016-03-08 16:43:58  Сервер успешно остановлен за 1,406 секунд!

Аватара пользователя
barkon
Сообщения: 44
C нами: 9 мес 28 дней

Непрочитанное сообщение barkon » 08 мар 2016, 23:59

Apache-2.4+Nginx-1.9
PHP 5.6
MySQL 5.6
Должно будет всё работать как надо. Тока сохранит не забудь.


Вернуться в «Ошибки Open Server»

Кто сейчас на конференции

Сейчас этот форум просматривают: нет зарегистрированных пользователей и 0 гостей