Reading Server Logs

  • thvs2

    (@thvs2)


    9 years, 10 months ago

    Hello, I have been using WordPress for client sites, I have been in scenarios where a customer support person from my hosting company (site5) can assist me by reading my server logs to me, is there any resources to help me learn about how to read these server logs – specifically in how they relate towards WordPress? Any help would be more than welcomed!

    background info:

    This came up because I have to reset all of a wordpress installs plugins to find an erroneous plugin that prevents persons from logging into the wp-admin.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Tanveer Sure

    (@tsure)

    9 years, 10 months ago

    Hi,

    Are you a programmer yourself ? Do you understand PHP code? WordPress framework uses PHP as the underlying programming language. So when you want to debug something in WordPress one can generally set “WP_DEBUG” to “true” will cause all PHP errors, notices and warnings to be displayed. This is likely to modify the default behavior of PHP which only displays fatal errors and/or shows a white screen of death when errors are reached.

    Showing all PHP notices and warnings often results in error messages for things that don’t seem broken, but do not follow proper data validation conventions inside PHP. These warnings are easy to fix once the relevant code has been identified, and the resulting code is almost always more bug-resistant and easier to maintain. You may want to read more on this by viewing the following link:

    https://codex.ww.wp.xz.cn/Debugging_in_WordPress

    ~Tanveer

    zerobullhosting

    (@zerobullhosting)

    9 years, 10 months ago

    Hi thvs2,

    You may or may not have access to all of the relevant logs, depending on your hosting providers configuration. If you do, you’ll generally see a /logs/ folder that contains an error.log and an access.log, which are the main two you’ll be looking at when diagnosing issues in WordPress.

    access.log will contain a listing of requests made to the site. This can help you determine what page an error is occurring on if a client is reporting an issue in vague terms. It’s also useful for determining use patterns, detecting attacks, and ensuring that a connection is being made to the proper server.

    error.log will contain any errors that the application decides to write to it. By default this isn’t very much, and the best case is usually identifying the source of an issue, but if you enable debug mode (as tsure suggests) the log will contain a lot more information and should point you towards a solution with a little bit of reading and searching. Keep in mind that enabling debug mode will slow the performance of your site – and it’ll grow the error.log file very quickly. You should only keep debug mode on while you are actively testing, or the server you’re on could run out of space in short order.

    Let me know if you have any more questions!

    Thread Starter thvs2

    (@thvs2)

    9 years, 10 months ago

    Hey tsure and zerobullhosting,

    I cannot thank you both enough!! Your two responses provided me a great place to start learning about server logs.

    Thank you both for taking time for helping me figure this out.

    Cheers

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Reading Server Logs’ is closed to new replies.