blc-log.txt too big 1,139 MB

  • Resolved persist9

    (@persist9)


    7 years, 7 months ago

    the broken link checker log file is way too big, 1,139 MB.
    My backup program alerted me to this.
    Our site is 1,800 posts + 80 pages – not enormous

    How can I remedy this?
    Can I simply edit this file, deleting all content or leaving a bit?
    Would I have to regularly edit the log file?

Viewing 1 replies (of 1 total)
  • Thread Starter persist9

    (@persist9)

    I deleted the content of this log file.
    I did not delete it.
    BLC has retained its memory and still seems to be working
    Perhaps I will have to do this every 6 months.

    Below is the last ten lines from the big file.
    the same link get repeated many times in this log
    There may be some a debug mode active. A guess.
    Our file system was 91% full as we had 8 copies of the site backup each containing a copy of this enormous file
    The log included dates from when we installed BLC to current

    [2017-04-19 07:26:07 +00:00] INFO: blcCurlHttp Checking link ‘https://dirtybusinessthefilm.com/’
    [2017-04-19 07:26:07 +00:00] DEBUG: blcCurlHttp Clean URL: ‘https://dirtybusinessthefilm.com/’
    [2017-04-19 07:26:07 +00:00] DEBUG: HTTP request took 0.257 seconds
    [2017-04-19 07:26:07 +00:00] INFO: HTTP response: 500, duration: 0.26 seconds, status text: “N/A”
    [2017-04-19 07:26:07 +00:00] DEBUG: blcLink:save Updating a link. SQL query:
    ‘UPDATE wp_blc_links SET url = \’https://dirtybusinessthefilm.com/\’, first_failure = \’2017-04-19 06:55:43\’, last_check = \’2017-04-19 07:26:06\’, last_success = \’2017-04-16 06:47:41\’, last_check_attempt = \’2017-04-19 07:26:06\’, check_count = 2, final_url = \’https://dirtybusinessthefilm.com/\’, redirect_count = 0, log = \’=== HTTP code : 500 ===\\n\\nResponse headers\\n================\\nHTTP/1.1 500 Internal Server Error\\r\\nDate: Wed, 19 Apr 2017 07:26:07 GMT\\r\\nContent-Type: text/html; charset=utf-8\\r\\nTransfer-Encoding: chunked\\r\\nConnection: close\\r\\nSet-Cookie: __cfduid=da11c03f0a01a49d0c68c11740055f36a1492586767; expires=Thu, 19-Apr-18 07:26:07 GMT; path=/; domain=.dirtybusinessthefilm.com; HttpOnly\\r\\nX-Powered-By: PHP/5.3.29\\r\\nExpires: Wed, 11 Jan 1984 05:00:00 GMT\\r\\nCache-Control: no-cache, must-revalidate, max-age=0\\r\\nPragma: no-cache\\r\\nServer: cloudflare-nginx\\r\\nCF-RAY: 351e223f92374d34-PER\\r\\n\\r\\nRequest headers\\n================\\nGET / HTTP/1.1\\r\\nUser-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)\\r\\nHost: dirtybusinessthefilm.com\\r\\nAccept: */*\\r\\nReferer: https://bze.org.au\\r\\nConnection: close\\r\\nRange: bytes=0-2048\\r\\n\\r\\nResponse HTML\\n================\\n<!DOCTYPE html>\\n<html xmlns="https://www.w3.org/1999/xhtml"&gt;\\n<head>\\n<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>\\n<title>Database Error</title>\\n</head>\\n<body>\\n<h1>Error establishing a database connection</h1>\\n</body>\\n</html>\\n\\nLink is broken.\’, http_code = 500, request_duration = 0.256568, timeout = 0, result_hash = \’500|broken|0|https://dirtybusinessthefilm.com/\’, broken = 1, warning = 0, false_positive = 0, may_recheck = 1, being_checked = 0, status_text = \’\’, status_code = \’\’, dismissed = 0 WHERE link_id=1763′
    [2017-04-19 07:26:07 +00:00] DEBUG: blcLink:save Link updated.
    [2017-04-19 07:26:07 +00:00] INFO: work(): All done.
    [2017-04-19 07:30:16 +00:00] INFO: … 0 links deleted in 0.023 seconds
    [2017-04-19 07:30:16 +00:00] INFO: … 0 links deleted in 0.021 seconds

Viewing 1 replies (of 1 total)
  • The topic ‘blc-log.txt too big 1,139 MB’ is closed to new replies.