Repeated CSS optimization warnings in LiteSpeed Cache

  • Resolved mdavis77

    (@mdavis77)


    7 months, 2 weeks ago

    Hello,

    I am seeing repeated warnings in my error log related to LiteSpeed Cache, which are filling my logs and may affect site performance:

    Warning: md5_file(/wp-content/litespeed/css/404.css.tmp): failed to open stream: No such file or directory in optimizer.cls.php on line 148
    Warning: rename(/wp-content/litespeed/css/404.css.tmp,/wp-content/litespeed/css/.css): No such file or directory in optimizer.cls.php on line 153

    WordPress: 6.8.3
    LiteSpeed Cache: 7.5.0.1
    PHP: 7.4.33
    I am using a custom theme on my site, in case this affects the CSS optimization behavior.

    Could you advise on a solution or fix?

    Thank you.

    • This topic was modified 7 months, 2 weeks ago by mdavis77.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support litetim

    (@litetim)

    7 months, 2 weeks ago

    @mdavis77 Let’s start debugging
    I will need a report ID generated from LSC => Toolbox => Report => Click on “Send to Litespeed” and paste me the generated ID(8 string chars).

    Are there errors in CSS generation?
    Does it happen on any pages? or just 404 pages?

    Thread Starter mdavis77

    (@mdavis77)

    7 months, 1 week ago

    FIRGRHBD
    I don’t know where this is happening.

    And I also have an error
    Cron reschedule event error for hook: litespeed_task_ucss, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {“schedule”:”litespeed_filter”,”args”:[],”interval”:60}

    Plugin Support litetim

    (@litetim)

    7 months, 1 week ago

    @mdavis77 please update to 7.6.2. This is a hotfix version that resolve other bugs.

    Plugin Support litetim

    (@litetim)

    7 months, 1 week ago

    @mdavis77 please create a new report but add the PHP info to the report(make sure checkbox is checked:  Attach PHP info to report)

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

The topic ‘Repeated CSS optimization warnings in LiteSpeed Cache’ is closed to new replies.