MySQL Log Files in CentOS












2















I am having a heck of a time getting this web server to log MySQL errors for me. I just started having issues with MySQL crashing every night and having to restart the service. I am running MySQL on CentOS release 7.6.1810
MySQL version is 15.1 (distrib 10.1.37-MariaDB).



I am trying to pinpoint the cause but I am unable to get the log files to generate.



If I go to:



/etc/my.cnf


then edit it in nano it does not have the [mysql] line in the file.
This is where you would add in the general_log stuff.



However, in /etc/my.cnf.d/ I do have a mysql-clients.cnf and a server.cnf which do show the [mysql] line in the file to add in the logs.



If I add the line in manually to my.cnf when I stop the service I cannot restart it.



I get an error:



Job for mariadb.service failed because the control process exited with error code.


The same thing happens if I add the code for the log files in the server.cnf.



If I add the code in on the mysql-clients.cnf I can stop and start the server with no issues, but nothing is being written to any of the files.



I also created the files and gave them 777 permissions and chown to mysql:mysql.



Does anyone have any idea on what I can do to get this logging?



The following lines are what I have been trying to add:



[mysqld_safe]
log_error=/var/log/mysql/mysql_error.log

[mysqld]
log_error=/var/log/mysql/mysql_error.log

general_log_file = /var/log/mysql/mysql.log
general_log = 1

log_slow_queries = /var/log/mysql/mysql-slow.log
long_query_time = 2
log-queries-not-using-indexes


Thank you for any and all help!










share|improve this question

























  • First, please edit your question to specify what version of CentOS you are using. Ditto with MySQL. That said, you should just add those lines to the /etc/my.cnf and restart the MySQL service via sudo service mysqld stop and then sudo service mysqld start. There is utterly no way any of those config options would ever be needed for the MySQL client; you simply want logging for the MySQL server. Ditto with the chmod of 777 and even the chown stuff. You might be best to just force a reinstall of MySQL and then deal with it that way.

    – JakeGould
    Jan 23 at 0:06






  • 1





    Jake, Thank you for the reply. I feel dumb not using the Sudo command to start mysqld. I added the code to the my.cnf file and it was able to start using sudo service mysqld start without saying Failed. I am running into a new issue though - When I try to enable the logs: SET GLOBAL general_log = 'ON'; SET GLOBAL slow_query_log = 'ON'; using mysql -u root -p I am getting an error: mysql: unknown variable 'log_error=/var/log/mysql/mysql_error.log any ideas?

    – Chuck Coggins III
    Jan 23 at 3:04













  • Happy to hear something worked! As far as the log_error setting goes, I would suggest commenting out all that extra stuff you added, starting MySQL and then running this command SHOW VARIABLES;. That will show you all of the mysqld variable options including names and settings. Should help. And I would recommend removing any/all additions you made to client related config like mysql-clients.cnf and such. I think now that you know that sudo works, the reality is you need to undo the tons of “Hail Mary…” things you tweaked and get back to a stable baseline.

    – JakeGould
    Jan 23 at 3:13






  • 1





    lol! Thank you again. I have been banging my head on this for the last 3 days. I need to talk with someone in the morning about the mysql password. The information I have seems to be incorrect so I am unable to proceed any further tonight. I did end up going ahead and removing everything I added to the other config files.

    – Chuck Coggins III
    Jan 23 at 3:22






  • 1





    Got everything up and running like it is supposed to! Thank you again for the help!

    – Chuck Coggins III
    Jan 23 at 23:04
















2















I am having a heck of a time getting this web server to log MySQL errors for me. I just started having issues with MySQL crashing every night and having to restart the service. I am running MySQL on CentOS release 7.6.1810
MySQL version is 15.1 (distrib 10.1.37-MariaDB).



I am trying to pinpoint the cause but I am unable to get the log files to generate.



If I go to:



/etc/my.cnf


then edit it in nano it does not have the [mysql] line in the file.
This is where you would add in the general_log stuff.



However, in /etc/my.cnf.d/ I do have a mysql-clients.cnf and a server.cnf which do show the [mysql] line in the file to add in the logs.



If I add the line in manually to my.cnf when I stop the service I cannot restart it.



I get an error:



Job for mariadb.service failed because the control process exited with error code.


The same thing happens if I add the code for the log files in the server.cnf.



If I add the code in on the mysql-clients.cnf I can stop and start the server with no issues, but nothing is being written to any of the files.



I also created the files and gave them 777 permissions and chown to mysql:mysql.



Does anyone have any idea on what I can do to get this logging?



The following lines are what I have been trying to add:



[mysqld_safe]
log_error=/var/log/mysql/mysql_error.log

[mysqld]
log_error=/var/log/mysql/mysql_error.log

general_log_file = /var/log/mysql/mysql.log
general_log = 1

log_slow_queries = /var/log/mysql/mysql-slow.log
long_query_time = 2
log-queries-not-using-indexes


Thank you for any and all help!










share|improve this question

























  • First, please edit your question to specify what version of CentOS you are using. Ditto with MySQL. That said, you should just add those lines to the /etc/my.cnf and restart the MySQL service via sudo service mysqld stop and then sudo service mysqld start. There is utterly no way any of those config options would ever be needed for the MySQL client; you simply want logging for the MySQL server. Ditto with the chmod of 777 and even the chown stuff. You might be best to just force a reinstall of MySQL and then deal with it that way.

    – JakeGould
    Jan 23 at 0:06






  • 1





    Jake, Thank you for the reply. I feel dumb not using the Sudo command to start mysqld. I added the code to the my.cnf file and it was able to start using sudo service mysqld start without saying Failed. I am running into a new issue though - When I try to enable the logs: SET GLOBAL general_log = 'ON'; SET GLOBAL slow_query_log = 'ON'; using mysql -u root -p I am getting an error: mysql: unknown variable 'log_error=/var/log/mysql/mysql_error.log any ideas?

    – Chuck Coggins III
    Jan 23 at 3:04













  • Happy to hear something worked! As far as the log_error setting goes, I would suggest commenting out all that extra stuff you added, starting MySQL and then running this command SHOW VARIABLES;. That will show you all of the mysqld variable options including names and settings. Should help. And I would recommend removing any/all additions you made to client related config like mysql-clients.cnf and such. I think now that you know that sudo works, the reality is you need to undo the tons of “Hail Mary…” things you tweaked and get back to a stable baseline.

    – JakeGould
    Jan 23 at 3:13






  • 1





    lol! Thank you again. I have been banging my head on this for the last 3 days. I need to talk with someone in the morning about the mysql password. The information I have seems to be incorrect so I am unable to proceed any further tonight. I did end up going ahead and removing everything I added to the other config files.

    – Chuck Coggins III
    Jan 23 at 3:22






  • 1





    Got everything up and running like it is supposed to! Thank you again for the help!

    – Chuck Coggins III
    Jan 23 at 23:04














2












2








2








I am having a heck of a time getting this web server to log MySQL errors for me. I just started having issues with MySQL crashing every night and having to restart the service. I am running MySQL on CentOS release 7.6.1810
MySQL version is 15.1 (distrib 10.1.37-MariaDB).



I am trying to pinpoint the cause but I am unable to get the log files to generate.



If I go to:



/etc/my.cnf


then edit it in nano it does not have the [mysql] line in the file.
This is where you would add in the general_log stuff.



However, in /etc/my.cnf.d/ I do have a mysql-clients.cnf and a server.cnf which do show the [mysql] line in the file to add in the logs.



If I add the line in manually to my.cnf when I stop the service I cannot restart it.



I get an error:



Job for mariadb.service failed because the control process exited with error code.


The same thing happens if I add the code for the log files in the server.cnf.



If I add the code in on the mysql-clients.cnf I can stop and start the server with no issues, but nothing is being written to any of the files.



I also created the files and gave them 777 permissions and chown to mysql:mysql.



Does anyone have any idea on what I can do to get this logging?



The following lines are what I have been trying to add:



[mysqld_safe]
log_error=/var/log/mysql/mysql_error.log

[mysqld]
log_error=/var/log/mysql/mysql_error.log

general_log_file = /var/log/mysql/mysql.log
general_log = 1

log_slow_queries = /var/log/mysql/mysql-slow.log
long_query_time = 2
log-queries-not-using-indexes


Thank you for any and all help!










share|improve this question
















I am having a heck of a time getting this web server to log MySQL errors for me. I just started having issues with MySQL crashing every night and having to restart the service. I am running MySQL on CentOS release 7.6.1810
MySQL version is 15.1 (distrib 10.1.37-MariaDB).



I am trying to pinpoint the cause but I am unable to get the log files to generate.



If I go to:



/etc/my.cnf


then edit it in nano it does not have the [mysql] line in the file.
This is where you would add in the general_log stuff.



However, in /etc/my.cnf.d/ I do have a mysql-clients.cnf and a server.cnf which do show the [mysql] line in the file to add in the logs.



If I add the line in manually to my.cnf when I stop the service I cannot restart it.



I get an error:



Job for mariadb.service failed because the control process exited with error code.


The same thing happens if I add the code for the log files in the server.cnf.



If I add the code in on the mysql-clients.cnf I can stop and start the server with no issues, but nothing is being written to any of the files.



I also created the files and gave them 777 permissions and chown to mysql:mysql.



Does anyone have any idea on what I can do to get this logging?



The following lines are what I have been trying to add:



[mysqld_safe]
log_error=/var/log/mysql/mysql_error.log

[mysqld]
log_error=/var/log/mysql/mysql_error.log

general_log_file = /var/log/mysql/mysql.log
general_log = 1

log_slow_queries = /var/log/mysql/mysql-slow.log
long_query_time = 2
log-queries-not-using-indexes


Thank you for any and all help!







linux centos mysql






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 23 at 3:09









JakeGould

32.1k1098141




32.1k1098141










asked Jan 22 at 23:51









Chuck Coggins IIIChuck Coggins III

112




112













  • First, please edit your question to specify what version of CentOS you are using. Ditto with MySQL. That said, you should just add those lines to the /etc/my.cnf and restart the MySQL service via sudo service mysqld stop and then sudo service mysqld start. There is utterly no way any of those config options would ever be needed for the MySQL client; you simply want logging for the MySQL server. Ditto with the chmod of 777 and even the chown stuff. You might be best to just force a reinstall of MySQL and then deal with it that way.

    – JakeGould
    Jan 23 at 0:06






  • 1





    Jake, Thank you for the reply. I feel dumb not using the Sudo command to start mysqld. I added the code to the my.cnf file and it was able to start using sudo service mysqld start without saying Failed. I am running into a new issue though - When I try to enable the logs: SET GLOBAL general_log = 'ON'; SET GLOBAL slow_query_log = 'ON'; using mysql -u root -p I am getting an error: mysql: unknown variable 'log_error=/var/log/mysql/mysql_error.log any ideas?

    – Chuck Coggins III
    Jan 23 at 3:04













  • Happy to hear something worked! As far as the log_error setting goes, I would suggest commenting out all that extra stuff you added, starting MySQL and then running this command SHOW VARIABLES;. That will show you all of the mysqld variable options including names and settings. Should help. And I would recommend removing any/all additions you made to client related config like mysql-clients.cnf and such. I think now that you know that sudo works, the reality is you need to undo the tons of “Hail Mary…” things you tweaked and get back to a stable baseline.

    – JakeGould
    Jan 23 at 3:13






  • 1





    lol! Thank you again. I have been banging my head on this for the last 3 days. I need to talk with someone in the morning about the mysql password. The information I have seems to be incorrect so I am unable to proceed any further tonight. I did end up going ahead and removing everything I added to the other config files.

    – Chuck Coggins III
    Jan 23 at 3:22






  • 1





    Got everything up and running like it is supposed to! Thank you again for the help!

    – Chuck Coggins III
    Jan 23 at 23:04



















  • First, please edit your question to specify what version of CentOS you are using. Ditto with MySQL. That said, you should just add those lines to the /etc/my.cnf and restart the MySQL service via sudo service mysqld stop and then sudo service mysqld start. There is utterly no way any of those config options would ever be needed for the MySQL client; you simply want logging for the MySQL server. Ditto with the chmod of 777 and even the chown stuff. You might be best to just force a reinstall of MySQL and then deal with it that way.

    – JakeGould
    Jan 23 at 0:06






  • 1





    Jake, Thank you for the reply. I feel dumb not using the Sudo command to start mysqld. I added the code to the my.cnf file and it was able to start using sudo service mysqld start without saying Failed. I am running into a new issue though - When I try to enable the logs: SET GLOBAL general_log = 'ON'; SET GLOBAL slow_query_log = 'ON'; using mysql -u root -p I am getting an error: mysql: unknown variable 'log_error=/var/log/mysql/mysql_error.log any ideas?

    – Chuck Coggins III
    Jan 23 at 3:04













  • Happy to hear something worked! As far as the log_error setting goes, I would suggest commenting out all that extra stuff you added, starting MySQL and then running this command SHOW VARIABLES;. That will show you all of the mysqld variable options including names and settings. Should help. And I would recommend removing any/all additions you made to client related config like mysql-clients.cnf and such. I think now that you know that sudo works, the reality is you need to undo the tons of “Hail Mary…” things you tweaked and get back to a stable baseline.

    – JakeGould
    Jan 23 at 3:13






  • 1





    lol! Thank you again. I have been banging my head on this for the last 3 days. I need to talk with someone in the morning about the mysql password. The information I have seems to be incorrect so I am unable to proceed any further tonight. I did end up going ahead and removing everything I added to the other config files.

    – Chuck Coggins III
    Jan 23 at 3:22






  • 1





    Got everything up and running like it is supposed to! Thank you again for the help!

    – Chuck Coggins III
    Jan 23 at 23:04

















First, please edit your question to specify what version of CentOS you are using. Ditto with MySQL. That said, you should just add those lines to the /etc/my.cnf and restart the MySQL service via sudo service mysqld stop and then sudo service mysqld start. There is utterly no way any of those config options would ever be needed for the MySQL client; you simply want logging for the MySQL server. Ditto with the chmod of 777 and even the chown stuff. You might be best to just force a reinstall of MySQL and then deal with it that way.

– JakeGould
Jan 23 at 0:06





First, please edit your question to specify what version of CentOS you are using. Ditto with MySQL. That said, you should just add those lines to the /etc/my.cnf and restart the MySQL service via sudo service mysqld stop and then sudo service mysqld start. There is utterly no way any of those config options would ever be needed for the MySQL client; you simply want logging for the MySQL server. Ditto with the chmod of 777 and even the chown stuff. You might be best to just force a reinstall of MySQL and then deal with it that way.

– JakeGould
Jan 23 at 0:06




1




1





Jake, Thank you for the reply. I feel dumb not using the Sudo command to start mysqld. I added the code to the my.cnf file and it was able to start using sudo service mysqld start without saying Failed. I am running into a new issue though - When I try to enable the logs: SET GLOBAL general_log = 'ON'; SET GLOBAL slow_query_log = 'ON'; using mysql -u root -p I am getting an error: mysql: unknown variable 'log_error=/var/log/mysql/mysql_error.log any ideas?

– Chuck Coggins III
Jan 23 at 3:04







Jake, Thank you for the reply. I feel dumb not using the Sudo command to start mysqld. I added the code to the my.cnf file and it was able to start using sudo service mysqld start without saying Failed. I am running into a new issue though - When I try to enable the logs: SET GLOBAL general_log = 'ON'; SET GLOBAL slow_query_log = 'ON'; using mysql -u root -p I am getting an error: mysql: unknown variable 'log_error=/var/log/mysql/mysql_error.log any ideas?

– Chuck Coggins III
Jan 23 at 3:04















Happy to hear something worked! As far as the log_error setting goes, I would suggest commenting out all that extra stuff you added, starting MySQL and then running this command SHOW VARIABLES;. That will show you all of the mysqld variable options including names and settings. Should help. And I would recommend removing any/all additions you made to client related config like mysql-clients.cnf and such. I think now that you know that sudo works, the reality is you need to undo the tons of “Hail Mary…” things you tweaked and get back to a stable baseline.

– JakeGould
Jan 23 at 3:13





Happy to hear something worked! As far as the log_error setting goes, I would suggest commenting out all that extra stuff you added, starting MySQL and then running this command SHOW VARIABLES;. That will show you all of the mysqld variable options including names and settings. Should help. And I would recommend removing any/all additions you made to client related config like mysql-clients.cnf and such. I think now that you know that sudo works, the reality is you need to undo the tons of “Hail Mary…” things you tweaked and get back to a stable baseline.

– JakeGould
Jan 23 at 3:13




1




1





lol! Thank you again. I have been banging my head on this for the last 3 days. I need to talk with someone in the morning about the mysql password. The information I have seems to be incorrect so I am unable to proceed any further tonight. I did end up going ahead and removing everything I added to the other config files.

– Chuck Coggins III
Jan 23 at 3:22





lol! Thank you again. I have been banging my head on this for the last 3 days. I need to talk with someone in the morning about the mysql password. The information I have seems to be incorrect so I am unable to proceed any further tonight. I did end up going ahead and removing everything I added to the other config files.

– Chuck Coggins III
Jan 23 at 3:22




1




1





Got everything up and running like it is supposed to! Thank you again for the help!

– Chuck Coggins III
Jan 23 at 23:04





Got everything up and running like it is supposed to! Thank you again for the help!

– Chuck Coggins III
Jan 23 at 23:04










1 Answer
1






active

oldest

votes


















0














So, what you describe sounds like (good faith) desperation. The reality is you only ever need to edit one config file to do what you have set out to do and that is (typically) the /etc/my.cnf file.



With that established, I would recommend you rewind and undo all of the adjustments you made to others files, and start from “tabula rasa.”



Once you are at a stable state, I recommend logging into MySQL and running this command to check the values of current MySQL server settings:



SHOW VARIABLES;


That will show you all variable names and settings. Make sure the values you are adjusting are indeed named the way the MySQL install expects them to be named.



Once you confirm those values, set them as you have outlined. Just note that you will only ever be changing the mysqld settings since those are the MySQL server settings; mysqld equates to “MySQL Daemon” which is a classic name for a Linux/Unix server.



Once your /etc/my.cnf is set, restart MySQL. But be sure to run it as sudo with something like sudo service mysqld restart; might be different for MariaDB. After the restart completes, the new settings should be set… Which you can then confirm my logging into MySQL and running that SHOW VARIABLES; command again.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1397220%2fmysql-log-files-in-centos%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    So, what you describe sounds like (good faith) desperation. The reality is you only ever need to edit one config file to do what you have set out to do and that is (typically) the /etc/my.cnf file.



    With that established, I would recommend you rewind and undo all of the adjustments you made to others files, and start from “tabula rasa.”



    Once you are at a stable state, I recommend logging into MySQL and running this command to check the values of current MySQL server settings:



    SHOW VARIABLES;


    That will show you all variable names and settings. Make sure the values you are adjusting are indeed named the way the MySQL install expects them to be named.



    Once you confirm those values, set them as you have outlined. Just note that you will only ever be changing the mysqld settings since those are the MySQL server settings; mysqld equates to “MySQL Daemon” which is a classic name for a Linux/Unix server.



    Once your /etc/my.cnf is set, restart MySQL. But be sure to run it as sudo with something like sudo service mysqld restart; might be different for MariaDB. After the restart completes, the new settings should be set… Which you can then confirm my logging into MySQL and running that SHOW VARIABLES; command again.






    share|improve this answer




























      0














      So, what you describe sounds like (good faith) desperation. The reality is you only ever need to edit one config file to do what you have set out to do and that is (typically) the /etc/my.cnf file.



      With that established, I would recommend you rewind and undo all of the adjustments you made to others files, and start from “tabula rasa.”



      Once you are at a stable state, I recommend logging into MySQL and running this command to check the values of current MySQL server settings:



      SHOW VARIABLES;


      That will show you all variable names and settings. Make sure the values you are adjusting are indeed named the way the MySQL install expects them to be named.



      Once you confirm those values, set them as you have outlined. Just note that you will only ever be changing the mysqld settings since those are the MySQL server settings; mysqld equates to “MySQL Daemon” which is a classic name for a Linux/Unix server.



      Once your /etc/my.cnf is set, restart MySQL. But be sure to run it as sudo with something like sudo service mysqld restart; might be different for MariaDB. After the restart completes, the new settings should be set… Which you can then confirm my logging into MySQL and running that SHOW VARIABLES; command again.






      share|improve this answer


























        0












        0








        0







        So, what you describe sounds like (good faith) desperation. The reality is you only ever need to edit one config file to do what you have set out to do and that is (typically) the /etc/my.cnf file.



        With that established, I would recommend you rewind and undo all of the adjustments you made to others files, and start from “tabula rasa.”



        Once you are at a stable state, I recommend logging into MySQL and running this command to check the values of current MySQL server settings:



        SHOW VARIABLES;


        That will show you all variable names and settings. Make sure the values you are adjusting are indeed named the way the MySQL install expects them to be named.



        Once you confirm those values, set them as you have outlined. Just note that you will only ever be changing the mysqld settings since those are the MySQL server settings; mysqld equates to “MySQL Daemon” which is a classic name for a Linux/Unix server.



        Once your /etc/my.cnf is set, restart MySQL. But be sure to run it as sudo with something like sudo service mysqld restart; might be different for MariaDB. After the restart completes, the new settings should be set… Which you can then confirm my logging into MySQL and running that SHOW VARIABLES; command again.






        share|improve this answer













        So, what you describe sounds like (good faith) desperation. The reality is you only ever need to edit one config file to do what you have set out to do and that is (typically) the /etc/my.cnf file.



        With that established, I would recommend you rewind and undo all of the adjustments you made to others files, and start from “tabula rasa.”



        Once you are at a stable state, I recommend logging into MySQL and running this command to check the values of current MySQL server settings:



        SHOW VARIABLES;


        That will show you all variable names and settings. Make sure the values you are adjusting are indeed named the way the MySQL install expects them to be named.



        Once you confirm those values, set them as you have outlined. Just note that you will only ever be changing the mysqld settings since those are the MySQL server settings; mysqld equates to “MySQL Daemon” which is a classic name for a Linux/Unix server.



        Once your /etc/my.cnf is set, restart MySQL. But be sure to run it as sudo with something like sudo service mysqld restart; might be different for MariaDB. After the restart completes, the new settings should be set… Which you can then confirm my logging into MySQL and running that SHOW VARIABLES; command again.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 24 at 2:35









        JakeGouldJakeGould

        32.1k1098141




        32.1k1098141






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1397220%2fmysql-log-files-in-centos%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

            Alcedinidae

            Origin of the phrase “under your belt”?