Jump to content

Featured Replies

Posted
comment_161395

Здравствуйте, форум работал нормально без ошибок очень долгое время. Со вчерашнего вечера на форум не зайти ошибка: 

2020-03-31_16-38-57.png.e8b2dbfbe89f2a671d1a2032a4522686.png

В логах mysql: 

Спойлер

2020-03-31 10:55:56 140522062808832 [ERROR] InnoDB: Could not find a valid tablespace file for 'forum_moonpw/ibf_core_cache'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2020-03-31 11:45:01 7fcdd7a30700 InnoDB: Error: Write to file ./forum_moonpw/ibf_core_log.ibd failed at offset 16777216.
InnoDB: 1048576 bytes should have been written, only 200704 were written.
InnoDB: Operating system error number 28.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not 2020-03-31 13:01:48 139958264475008 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2020-03-31 13:01:48 139958264475008 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2020-03-31 13:01:48 139958264475008 [Note] InnoDB: The InnoDB memory heap is disabled
2020-03-31 13:01:48 139958264475008 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-03-31 13:01:48 139958264475008 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-03-31 13:01:48 139958264475008 [Note] InnoDB: Compressed tables use zlib 1.2.8
2020-03-31 13:01:48 139958264475008 [Note] InnoDB: Using Linux native AIO
2020-03-31 13:01:48 139958264475008 [Note] InnoDB: Using SSE crc32 instructions
2020-03-31 13:01:48 139958264475008 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2020-03-31 13:01:48 139958264475008 [Note] InnoDB: Completed initialization of buffer pool
2020-03-31 13:01:48 139958264475008 [Note] InnoDB: Highest supported file format is Barracuda.
2020-03-31 13:01:49 7f4a92a32d80  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2020-03-31 13:01:49 139958264475008 [ERROR] InnoDB: Could not find a valid tablespace file for 'forum_moonpw/ibf_core_cache'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2020-03-31 13:01:49 139958264475008 [ERROR] InnoDB: Tablespace open failed for '"forum_moonpw"."ibf_core_cache"', ignored.
2020-03-31 13:01:49 7f4a92a32d80  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2020-03-31 13:01:49 139958264475008 [ERROR] InnoDB: Could not find a valid tablespace file for 'forum_moonpw/ibf_core_store'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2020-03-31 13:01:49 139958264475008 [ERROR] InnoDB: Tablespace open failed for '"forum_moonpw"."ibf_core_store"', ignored.
2020-03-31 13:01:49 139958264475008 [Note] InnoDB: 128 rollback segment(s) are active.
2020-03-31 13:01:49 139958264475008 [Note] InnoDB: Waiting for purge to start
2020-03-31 13:01:49 139958264475008 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.44-86.0 started; log sequence number 95671481671
2020-03-31 13:01:49 139957607855872 [Note] InnoDB: Dumping buffer pool(s) not yet started
2020-03-31 13:01:49 139958264475008 [Note] Plugin 'FEEDBACK' is disabled.
2020-03-31 13:01:49 139958264475008 [Note] Server socket created on IP: '127.0.0.1'.
2020-03-31 13:01:49 139958264475008 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.1.41-MariaDB-0+deb9u1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Debian 9.9
2020-03-31 13:01:50 139958263834368 [ERROR] InnoDB: Failed to find tablespace for table '"forum_moonpw"."ibf_core_cache"' in the cache. Attempting to load the tablespace with space id 13509.
2020-03-31 13:01:50 7f4a92996700  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
2020-03-31 13:01:50 139958263834368 [ERROR] InnoDB: Could not find a valid tablespace file for 'forum_moonpw/ibf_core_cache'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
 

 

При входе в админку

2020-03-31_16-48-57.png.5395a53c85159c17c04caa66e29b4b95.png

comment_161396
Цитата

Наиболее частой причиной ошибки 500 (Internal Server Error, внутренняя ошибка сервера) является неверный синтаксис файла . htaccess или наличие в нем неподдерживаемых директив. Чаще всего достаточно закомментировать директиву Options (для этого нужно поставить в начале строки решетку — #), и проблема исчезнет.

 

comment_161398
2 часа назад, ward55 сказал:

дело в том, что файла .htaccess в корне форуме нету.

Т.е. это не то что у вас в подписи? Тогда зайдите в phpMyAdmin и оптимизируйте в БД таблицу ibf_core_cache,иногда помогает.

  • 2 месяца спустя...
comment_162621

lsnull если ты обратил внимание, ошибка то у всех с одним номером, а описание ошибки разное. Вряд ли у всех одно решение 😁

comment_162622
1 минуту назад, Maiden8 сказал:

lsnull если ты обратил внимание, ошибка то у всех с одним номером, а описание ошибки разное. Вряд ли у всех одно решение 😁

Без понятия... я и логи глянуть не могу в Админке, так как попасть не могу туда.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.


Guest
Ответить в этой теме...

Последние посетители 0

  • No registered users viewing this page.