🧨 fwrite(): write of 2268 bytes failed with errno=28 no space left on device

Hello,

It looks like your server has run out of disk space. What I could suggest is to upgrade your server and add some extra storage, you can do that directly via your DigitalOcean control panel by following the steps here:

https://docs.digitalocean.com/products/droplets/how-to/resize/

This does not require any coding or technical skills.

Alternatively, if you want to get to the bottom of the problem and find out what is filling up the disk space, you can follow the steps from this answer here:

https://www.digitalocean.com/community/questions/28-no-space-left-on-device-error

Let me know how it goes!

Best,

Bobby

The error message you provided, “fwrite(): write of 2268 bytes failed with errno=28 no space left on device”, suggests that your server has run out of disk space. When the disk is full, applications can’t write to the filesystem, which can cause various issues, including the one you’re experiencing.

Here are the steps to diagnose and address the issue:

Check Disk Usage: SSH into your server and use the df command to verify the disk usage:

df -h

This will show the amount of space used and available on each partition. If any partition, especially the root (/), is at 100% usage, then that’s the source of the issue.

Identify Large Files and Directories: To find which directories are consuming most of the space, you can use the du command. Here’s a way to list the size of top-level directories under /:

sudo du -h --max-depth=1 /

You can then drill down into directories that seem to be unusually large.

Clear Unnecessary Files:

• Log Files: Log files can often consume a large amount of space. Check the /var/log directory and consider removing or compressing old logs.
• Temporary Files: Clear out the /tmp directory.
• Cache: If you use a system like apt for package management, you can clear out cached package files with:

sudo apt autoclean
sudo apt autoremove

1. • Old Kernels: If you’re using a system that accumulates kernel updates, these can take up space. Be careful with removing these, but old unused kernels can be safely removed in most cases.
   • Databases: If you’re running a database server, it may have generated large binary logs or temporary tables. Check its configuration and consider cleanup or adjustments to prevent unbounded growth.
   • Backups: If you’re taking backups and storing them on the same disk, they can also occupy a lot of space. Consider moving them offsite or to a different storage medium.

2. Expand Disk Space: If you find that even after cleanup, the space is insufficient, you might need to consider resizing your server’s disk or attaching additional storage, depending on your hosting provider’s offerings.

3. Automate Monitoring: To prevent this from happening in the future, consider setting up monitoring and alerts for disk usage. There are many tools available that can notify you when disk space is getting low, giving you a chance to address the issue before it impacts your users.

Finally, once you’ve cleared up enough space, you might need to restart some services (or even the whole server) to resolve any issues caused by the lack of disk space.