VVV: WordPress database error Disk full
After using my clean VM (with db_share_type: false) for almost a day, I got this weird error in my WP error log:
[18-Jun-2019 12:59:25 UTC] WordPress database error Disk full (/tmp/#sql_12a6_0.MAI); waiting for someone to free some space... (errno: 28 "No space left on device") for query SHOW FULL COLUMNS FROM `wp_postmeta` made by do_action('wp_ajax_heartbeat'), WP_Hook->do_action, WP_Hook->apply_filters, wp_ajax_heartbeat, apply_filters('heartbeat_received'), WP_Hook->apply_filters, wp_refresh_post_lock, wp_set_post_lock, update_post_meta, update_metadata
Also when running df -h in my machine using SSH, I saw that /dev/sda1 was using 100% of its space.
My computer didn’t run out of free space of course, but the drive assigned to the VM (10gb) did. I’m wondering how this had happened. I’m using VVV for over two years and this has never happened before. Moreover, I did nothing different today when using the VM
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 27 (11 by maintainers)
These are not Tideways, but Xdebug traces. So its not related to Tideways at all. The tideways-header.php is always loaded because it is the auto_prepend_file. the enable_tideways check inside the file prevents tideways from being started. What happens here is that you generate Xdebug trace files.
OK, I figured out that the disk is getting full due to files inside the
/tmpfolder.These files are traces generated by
Tidewayseven though I’m not adding?enable-tidewaysto my URL.I also noticed that when debugging with PHPStorm, the execution stops on
tideways-header.phpbecause a path mapping hasn’t been set for this file. I get past to this issue by choosing to not stop when path mappings are not set.