Логи ошибок phpmyadmin

I am using phpMyAdmin version 4.2.11. At the time of writing, my Status tab looks like this (a few options expanded; note «Current settings», bottom right):

Image of Status Panel

Note, there are no directly visible «features» that allow for the enabling of things such as slow_query_log. So, I went digging on the internet because UI-oriented answers will only be relevant to a particular release and, therefore, will quickly become out of date. So, what do you do if you don’t see a relevant answer, above?

As this article explains, you can run a global query to enable or disable the slow_query_log et al. The queries for enabling and disabling these logs are not difficult, so don’t be afraid of them, e.g.

SET GLOBAL slow_query_log = 'ON';

From here, phpMyAdmin is pretty helpful and a bit of Googling will get you up to speed in no time. For instance, after I ran the above query, I can go back to the «Instructions/Setup» option under the Status tab’s Monitor window and see this (note the further instructions):

Slow query enabled

I am using phpMyAdmin version 4.2.11. At the time of writing, my Status tab looks like this (a few options expanded; note «Current settings», bottom right):

Image of Status Panel

Note, there are no directly visible «features» that allow for the enabling of things such as slow_query_log. So, I went digging on the internet because UI-oriented answers will only be relevant to a particular release and, therefore, will quickly become out of date. So, what do you do if you don’t see a relevant answer, above?

As this article explains, you can run a global query to enable or disable the slow_query_log et al. The queries for enabling and disabling these logs are not difficult, so don’t be afraid of them, e.g.

SET GLOBAL slow_query_log = 'ON';

From here, phpMyAdmin is pretty helpful and a bit of Googling will get you up to speed in no time. For instance, after I ran the above query, I can go back to the «Instructions/Setup» option under the Status tab’s Monitor window and see this (note the further instructions):

Slow query enabled

  • #1

Where i can check whats going on in log file where phpMyAdmin errors exist?

I was uploading an directadmin backup of an sql file into PhpMyAdmin from import page and got internal server error in middle of upload 61%. Upload took ~10 seconds before interruption. The file was 19mb and i checked every php.ini file variable which all looked ok.

max_execution_time 600 600
max_input_time 600 600
memory_limit 1000M 1000M
post_max_size 1000M 1000M

Importing worked only with other smaller file where i partly exported only some tables from the same database. The sql filesize was 7mb.

It also worked with command-line.
mysql -u myuser -p mydatabase < myfile.sql

Thanks

Last edited:

  • #2

check max_allowed_packet at mysql config

  • #3

You can check if there is a error log at this path: /var/www/html/phpMyAdmin-5.0.1-all-languages/log/

Also maybe check: /var/log/httpd/error_log

Also remember to check this value in php.ini: upload_max_filesize (you did not mention it in your post)

  • #4

This folder contains only .htaccess file
/var/www/html/phpMyAdmin-5.0.1-all-languages/log/

Also maybe check: /var/log/httpd/error_log

Found my error here:
ModSecurity: Request body (Content-Length) is larger than the configured limit (13107200).

UPDATE: It weird if i save changes in the comodo plugin and restart apache, after that i do CTRL+F5 on the plugin config page, then the old parameters are all back like the new ones never saved. But it said it saved and restarted the server. I have removed the plugin and reinstalled it many times now, still the same issue but i was able to change SecRequestBodyNoFilesLimit value from conf file located at /etc/httpd/conf/extra/httpd-modsecurity.conf

Also remember to check this value in php.ini: upload_max_filesize (you did not mention it in your post)

Yes, forgot to mention, it was set to:
upload_max_filesize = 1024M

Thank You

Last edited:

Я использую phpMyAdmin версии 4.2.11. На момент написания моей вкладки моя вкладка Status выглядит следующим образом (несколько вариантов расширены, обратите внимание на «Текущие настройки», внизу справа):

Изображение 106872

Обратите внимание, что нет прямых видимых «функций», которые позволяют включить такие вещи, как slow_query_log. Итак, я пошел в Интернете, потому что ориентированные на пользовательский интерфейс ответы будут иметь отношение только к определенному выпуску и, следовательно, быстро устареют. Итак, что вы будете делать, если не см. Соответствующий ответ выше?

Как объясняется в статье вы можете запустить глобальный запрос, чтобы включить или отключить slow_query_log et al. Запросы на включение и отключение этих журналов не сложны, поэтому не бойтесь их, например.

SET GLOBAL slow_query_log = 'ON';

Отсюда phpMyAdmin очень полезен, и немного Googling поможет вам быстро и быстро. Например, после выполнения вышеуказанного запроса я могу вернуться к опции «Инструкции/Настройка» в окне «Состояние» Monitor и увидеть это (обратите внимание на дальнейшие инструкции):

Изображение 106873

Better Stack Team

Updated on November 23, 2022

In the older version of the phpMyAdmin control panel, there is Binary log in
which all logs are stored. This can be opened by clicking Status → Binary log

In newer versions, the Status page looks like this

Here you can monitor all activity on your MySQL server.

Explore more

Licensed under CC-BY-NC-SA

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

We are hiring.

Software is our way of making the world a tiny bit better. We build tools for the makers of tomorrow.

Explore all positions →

Понравилась статья? Поделить с друзьями:

Интересное по теме:

  • Лифт коне ошибка 0026
  • Лишь та ошибка что не исправляется объяснение
  • Лифт вниз не поднимает исправить ошибку
  • Лифт коне ошибка 0021
  • Лифт sigma коды ошибок

  • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии