[Solved] 4.0.17 to 4.0.18 / Request has not been logged into access log

Discussion in 'Bug Reports' started by track1, Dec 12, 2010.

  1. track1

    track1 New Member

    4.0.17 to 4.0.18 / Request has not been logged into access log, response body sent

    After upgrading server from 4.0.17 to 4.0.18, tons of messages like this at error log:

    2010-12-12 02:19:59.624 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 17499!
    2010-12-12 02:19:59.617 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 12883!
    2010-12-12 02:19:59.582 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 17499!
    2010-12-12 02:19:59.576 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 9695!
    2010-12-12 02:19:59.561 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 17499!
    2010-12-12 02:19:59.517 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 17499!
    2010-12-12 02:19:59.492 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 0!
    2010-12-12 02:19:59.483 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 50!
    2010-12-12 02:19:59.151 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 17499!
    2010-12-12 02:19:58.879 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 17499!
    2010-12-12 02:19:58.784 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 12800!
    2010-12-12 02:19:58.760 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 17499!
    2010-12-12 02:19:58.693 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 13106!
    2010-12-12 02:19:58.645 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 0!
    2010-12-12 02:19:58.635 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 50!
    2010-12-12 02:19:58.600 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 0!
    2010-12-12 02:19:58.363 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 0!
    2010-12-12 02:19:58.354 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 50!
    2010-12-12 02:19:58.287 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 0!
    2010-12-12 02:19:58.269 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 0!
    2010-12-12 02:19:58.260 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 50!
    2010-12-12 02:19:58.134 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 5011!
    2010-12-12 02:19:58.046 [WARN]x.x.x.x Request has not been logged into access log, response body sent: 17499!


    Server switched back to 4.0.17
    Last edited by a moderator: Dec 14, 2010
  2. mistwang

    mistwang LiteSpeed Staff

    It is harmless, fixed in the updated 4.0.18 build.
  3. track1

    track1 New Member

    ok! updated to new 4.0.18 build. Everything working ok now.
  4. mistwang

    mistwang LiteSpeed Staff

    Please update again, the previous build may stop logging into access log files.
  5. track1

    track1 New Member

    I have tested new build and problem is back, tons of "Request has not been logged into access log, response body sent: xxxx" errors at log.

    Server is using cpanel/whm and apache config replacement. (Only litespeed)
  6. mistwang

    mistwang LiteSpeed Staff

    Sorry, the previous fix is not right, updated again, please give it a try.
  7. track1

    track1 New Member

    new build installed, all seems to work ok.

Share This Page