Seeing a lot of these errors for a view with a date field that is an exposed filter:

Unable to write temp file: cache/normal/www.ngopulse.org/group/home-page/events_order=field_event_start_date_value&sort=asc&page=14&date_filter[min][year]=&date_filter[min][hour]=0&date_filter[min][minute]=0&date_filter[min][second]=0&date_filter[min][month]=&date_filter[min][day]=&date_filter[max][year]=&date_filter[max][hour]=0&date_filter[max][minute]=0&date_filter[max][second]=0&date_filter[max][month]=12&date_filter[max][day]=27.html2244
Group ID: 0
User ID: 0
Current script owner: root

Any ideas what the problem could be? There are other files that have been written to that directory and the permissions are 775 although the owner of the folder is www-data and not root (I assume the root mentioned as the "Current script owner" is because cron is running as root, and I just enabled the boost crawler.

Comments

bibo’s picture

bibo commented

I have the same problem on a large site, and the error is usually but not always when there are date filters exposed. I believe it's because the url is simply too long to be stored as a file name. On many systems the limit is 255 characters.

events_order=field_event_start_date_value&sort=asc&page=14&date_filter[min][year]=&date_filter[min][hour]=0&date_filter[min][minute]=0&date_filter[min][second]=0&date_filter[min][month]=&date_filter[min][day]=&date_filter[max][year]=&date_filter[max][hour]=0&date_filter[max][minute]=0&date_filter[max][second]=0&date_filter[max][month]=12&date_filter[max][day]=27.html2244

is 374 characters.

This results in annoying errors, but shouldn't affect the site much. One way to avoid the error would be if boost exposed a maximum filename lenght, and would just not try to write the cache files for too long urls.

mrP’s picture

mrP commented
Title: Unable to write temp file error for view with exposed date filter » Unable to write temp file error for view with exposed date filter / pagination

same issue here with views and pagination. on the ~10th page of results the URL (and resulting cache filename) is too long for boost to save to the filesystem.