Score:0

Writing to the temporary directory randomly stops working

bz flag

In one of the websites on production, when Drupal writes on the temporary directory, it randomly stops working with the following error, even though the permissions are set correctly, and there is enough space.

Temporary file data could not be written

The temporary directory is set to the DRUPAL_ROOT/sites/default/files/tmp directory.

Removing the content of the temporary directory solves the problem, but it came back again. I can't debug the reason.

How can I fix this issue?

usmanjutt84 avatar
in flag
Have you upgraded version of Drupal core?
id flag
Is there an operational reason on that site for putting the temporary directory where it is publicly accessible over the web? Instructions for that configuration are "This directory must be absolute, outside of the Drupal installation directory and not accessible over the web."
bz flag
@usmanjutt84 Drupal is the latest version
bz flag
@cilefen There was a reason before, but currently, no, I actually set the temporary folder to the default '/tmp' now, but it happened today again. I'm still not sure why.
Score:1
bz flag

I solved the issue, turns out that there was a user quota with a maximum amount of blocks that can be written.

Use this command to check if there is a quota.

sudo quota -vs USER
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.