Please make sure that “/” is writable by the web-server. [Magento 2.4 Sitemap]

[digitalstartup]

Elasticsearch files
Firstly, let’s address the elasticsearch files. Those are only temporary files that you would have downloaded in order to install Elasticsearch. This is why I recommended downloading the files to your “My Documents” directory (e.g. /home/god/). As they’re only used to installing elasticsearch, you don’t need them anymore. So, just delete them.

Sitemap
As you’ve clearly identified, magento2 user has appropriate permissions to write to the /var/www/html/ Directory However, you should ask yourself:

"But who is trying to write to the /var/www/html/ Directory?"

If memory serves, crontab is responsible for actually creating the sitemap files. Therefore, in your case you should check that you have setup crontab under the correct user. Because if you accidently setup crontab up as god user (for example), then it’s god user trying to write the file, not magento2 user.

Check out this excerpt I wrote in 2019.

@YouTube

How to fix Cron Tasks
Another common mistake I see are cron tasks being created under the wrong user. So, during the installation process of Magento 2.3 you run a command that sets up cron tasks. To give you an example, if I were to set these cron tasks under the “craig” user rather than the “magento” user then every time a cron tasks was executed then it would either result in:

• An error where “craig” user didn’t have the permissions to change any files
• Or the creation of files as with the “craig” user as the owner, thus creating more issues further on

So, I’ve created a scenario where that is exactly what has happened.

First, I want to check what cron tasks are setup under each user. This is something that’s best done as a superuser. So, once again I’ll switch to the superuser… Now that I’m logged back in I’ll run:

sudo crontab -l -u magento

This will check any cron tasks setup under the “magento” user. As you can see from the results there are no tasks setup under the “magento” user, when there should be.

Next I’ll run the same command without “-u magento” at the end:

crontab -l

This displays the cron tasks for the user I’m logged in as. And as you can see, there are Magento tasks setup that shouldn’t be there.

Now we know the issue for sure. All we have to do is delete the cron tasks from the superuser and install them under magento.

To delete the tasks that I setup under the “craig” user I simply type:

crontab -e

If you’ve never entered this command in before, you’ll be asked what text editor you want to use. Just press “2” to use the nano text editor.

With the file now open, removing the tasks are as simple as holding down the Delete Key… Once finished press Ctrl+X to exit and “Y” and Enter to save.

The final thing to do now is switch back to my magento user by typing

exit

And running the cron installation command to reinstall the cron tasks as the correct user, which is done with:

bin/magento cron:install

Remember, we can verify this is installed under the “magento” user now by running:

crontab -l

Which shows all of the tasks setup under the user that I’m currently logged in as - Which is the “magento” user. And there’s the output we’d expect to see

Regards,