Skip to content

Failed to open stream: File name too long #2440

Description

@logdirect

We are using WP-Rocket Plugin on a customer website.
Since the last update, it seems that the naming conventions for the cache files have been changed. We are having lots and lots of these errors:


Stack trace
E_WARNING: copy(/var/www/html/wp-content/cache/wp-rocket/www.astrology-psychic-reading.com-myemailaddress@example.net-5cdbc7c23e4a8161374624/fi/the_great_vision_from_the_quantum_pendulum_2003_en/lv/#k=eyJhbGciOiJIUzI1NiJ9.eyJpZCI6OTUzNDEsImtleSI6Ijg1ZGM0ZTE2NTc1NThjYzZlMGU3NTM1ZmIzNmVmYjU3In0.7I1EGjzMv_f1N7xHAlWbkcJOpO49LVfI6UkuZg8dpUw&mname=UzCJhMgB30++xmUH9P3XnYavt+Yea7rSt%2fqNzyJxV+A%3d&va3=epbYIGPLDid%2fpDHgM39Nng%3d%3d&va4=1mDowu%2fZfpaMRgcZyqg+kA%3d%3d/index-https-webp.html_gzip_temp): failed to open stream: File name too long
in copy called at /var/www/html/wp-admin/includes/class-wp-filesystem-direct.php (281)
in WP_Filesystem_Direct::copy called at /var/www/html/wp-admin/includes/class-wp-filesystem-direct.php (309)
in WP_Filesystem_Direct::move called at /var/www/html/wp-content/plugins/wp-rocket/inc/classes/Buffer/class-cache.php (363)
in WP_Rocket\Buffer\Cache::write_cache_file called at /var/www/html/wp-content/plugins/wp-rocket/inc/classes/Buffer/class-cache.php (308)
in WP_Rocket\Buffer\Cache::maybe_process_buffer called at ? (?)
in ob_end_flush called at /var/www/html/wp-includes/functions.php (4552)
in wp_ob_end_flush_all called at /var/www/html/wp-includes/class-wp-hook.php (288)
in WP_Hook::apply_filters called at /var/www/html/wp-includes/class-wp-hook.php (312)
in WP_Hook::do_action called at /var/www/html/wp-includes/plugin.php (478)
in do_action called at /var/www/html/wp-includes/load.php (947)
in shutdown_action_hook called at ? (?)

We are seeing more than 8000 occurences over 24 hours. The stack traces are of course slightly different, but the error message is the same. The cache file which is generated is too long.

Metadata

Metadata

Assignees

No one assigned

    Labels

    communityIssues created by someone outside of our teammodule: cacheneeds: detailspriority: mediumIssues which are important, but no one will go out of business.severity: majorFeature is not working as expected and no work around availabletype: bugIndicates an unexpected problem or unintended behavior

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions