Title: Database error ? using 4.4.1
Last modified: September 7, 2026

---

# Database error ? using 4.4.1

 *  Resolved [mbsharp](https://wordpress.org/support/users/mbsharp/)
 * (@mbsharp)
 * [3 weeks, 3 days ago](https://wordpress.org/support/topic/database-error-using-4-4-1/)
 * Having got rid of one set of SQL errors, 4.4.1 may have introduced something 
   else. Multiple copies of these two error types now appearing for more than one
   site.
 * [06-Sep-2026 18:08:05 UTC] WordPress database error Disk got full writing ‘information_schema.(
   temporary)’ (Errcode: 28 “No space left on device”) for query SHOW FULL COLUMNS
   FROM `wp_options` made by Imagely\NGG\Util\Router->cache_lookups, Imagely\NGG\
   Util\Transient::update, Imagely\NGG\Util\Transient->set, set_transient, update_option
 * [06-Sep-2026 18:08:13 UTC] WordPress database error Disk got full writing ‘.(
   temporary)’ (Errcode: 28 “No space left on device”) for query SELECT DISTINCT
   wp_ngg_pictures.* , GROUP_CONCAT(CONCAT_WS(‘@@’, meta_key, meta_value)) AS ‘extras’
   FROM `wp_ngg_pictures` LEFT OUTER JOIN `wp_postmeta` ON `wp_postmeta`.`post_id`
   = `extras_post_id` WHERE (`exclude` = 0) AND (`galleryid` IN (150)) GROUP BY 
   wp_ngg_pictures.pid ORDER BY `sortorder` ASC LIMIT 500 made by require(‘wp-blog-
   header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/themes/
   weaver-xtreme/404.php’), weaverx_page_tail, weaverx_sidebar_after, get_sidebar,
   locate_template, load_template, require_once(‘/themes/weaver-xtreme/sidebar-right.
   php’), weaverx_put_widgetarea, dynamic_sidebar, WP_Widget->display_callback, 
   WP_Widget_Block->widget, apply_filters(‘widget_block_content’), WP_Hook->apply_filters,
   do_shortcode, preg_replace_callback, do_shortcode_tag, Imagely\NGG\Display\Shortcodes-
   >__call, Imagely\NGG\Display\Shortcodes->render_shortcode, Imagely\NGG\Display\
   DisplayManager->display_images, Imagely\NGG\DisplayedGallery\Renderer->display_images,
   Imagely\NGG\DisplayedGallery\Renderer->render, Imagely\NGG\DisplayTypes\Slideshow-
   >index_action, Imagely\NGG\DataTypes\DisplayedGallery->get_included_entities,
   Imagely\NGG\DataTypes\DisplayedGallery->get_entities, Imagely\NGG\DataTypes\DisplayedGallery-
   >_get_image_entities, Imagely\NGG\DataMapper\TableDriver->run_query

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Support [Mihai](https://wordpress.org/support/users/mceban/)
 * (@mceban)
 * [3 weeks, 1 day ago](https://wordpress.org/support/topic/database-error-using-4-4-1/#post-19015400)
 * Hi [@mbsharp](https://wordpress.org/support/users/mbsharp/) ,
 * Thank you for sending the log lines and for flagging that this started after 
   the 4.4.1 update. That is exactly the right instinct after an update, and the
   detail you included made this quick to check.
 * I have good news and a bit of unwelcome news. The unwelcome part is that these
   are not NextGEN errors. The good news is that the real cause is something your
   host can fix quickly.
 * **What these errors mean**
 * Both lines contain the same MySQL code: “Errcode: 28 – No space left on device”.
   That message comes from the database server, not from a plugin. MySQL writes 
   temporary working files to disk while it runs certain queries. When that disk
   fills up, any query that needs a temporary file fails.
 * That is what you are seeing. It is not a bad query and it is not a broken table.
   The database server ran out of room to work in.
 * **Why NextGEN’s name is on both lines**
 * WordPress prints the call stack of whatever query happened to fail, so the plugin
   that was running at that moment gets named. Two things make NextGEN a frequent
   name on that list, and neither is a fault.
 * First, NextGEN saves a small routing value at the end of each page load. That
   often makes it the first thing on the page to write to the “wp_options” table,
   so it is the first to hit the wall. The failing query in that line (“SHOW FULL
   COLUMNS FROM wp_options”) is WordPress core, not ours.
 * Second, the gallery query in your other line groups and sorts its results. MySQL
   always uses a temporary file for that kind of query, so it fails immediately 
   whenever the disk is full.
 * Once the disk has room again, both messages stop. You will likely see the same
   errors from other plugins in the meantime.
 * **What changed in 4.4.1**
 * I checked the 4.4.1 code against 4.3.0 directly. The two files named in your 
   log are byte for byte identical between the two releases, so nothing in this 
   area changed.
 * There is one small connection worth mentioning, though. The 4.4.1 fix you noticed(“
   broken album and gallery links no longer fill the error log with database errors”)
   stopped those requests from failing early. They now run the full gallery query
   instead. On a server that is already out of disk space, that means a request 
   which used to fail cheaply now asks MySQL for a temporary file and fails there
   instead. The symptom moved. The disk problem was already present.
 * **What to ask your host**
 * Please ask them to check three things:
    1. Free disk space on the database server, and on the volume that holds the MySQL
       data directory.
    2. Free space in the MySQL temporary directory, which is often on a small partition
       of its own.
    3. Whether a quota on your account has been reached, if these sites are on shared
       or managed hosting.
 * Since you are seeing this on more than one site, a shared volume or a shared 
   quota is the most likely explanation. That is worth mentioning to them, because
   it points away from any single site being at fault.
 * **Two things worth a look on your side**
 * Your log shows a gallery rendering inside a sidebar widget on your theme’s 404
   page. That means every hit to a missing URL on that site builds a full gallery.
   If the site is getting crawled or scanned, that adds up fast, both in database
   writes and in cached gallery data. Removing the gallery widget from the 404 sidebar
   would cut that load a lot.
 * It is also worth checking the size of your WordPress debug log itself. On a site
   logging at this volume, the log file can be what fills the disk.
 * Nothing is needed from you in NextGEN right now, and there is no reason to roll
   back to an earlier version. The fix here is disk space on the server.
 * If your host confirms the disk was full and clears it, and you still see these
   errors afterward, please send me a fresh log along with the site’s cached data
   size and I will take another look. I am also happy to review your host’s reply
   if it is unclear.
 * Best,
   Mihai
 *  Thread Starter [mbsharp](https://wordpress.org/support/users/mbsharp/)
 * (@mbsharp)
 * [3 weeks, 1 day ago](https://wordpress.org/support/topic/database-error-using-4-4-1/#post-19015436)
 * Thank you for your really detailed analysis.
 * I have three sites on separate shared hosting but run with matching theme and
   styles of content. One is personal; second is a regional organisation; third 
   is a national organisation. The errors shown above happened on the regional and
   national sites and about an hour apart on each one. None of the sites uses WP_DEBUG
   so that would not be filling the database. But the server logs do show that the
   national site particularly is being constantly bombarded with bot searches with
   invalid content, so 404 alerts are frequent alongside 301.
 * The errors do appear to be page building, and 404 is mentioned. There is no real
   prospect for me to edit the theme’s 404 page, which does include my sidebar and
   that does include one (regional site) and two (national site) gallery shortcodes.
 * As every page therefore includes a gallery, and you explain that this is a server
   side capacity issue, that accounts for the messages appearing to be caused by
   ngg when they are not.
 * I am pleased to say that the error clusters have not repeated since.
 * Thank you again. Resolved.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fdatabase-error-using-4-4-1%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/nextgen-gallery/assets/icon-256x256.png?rev=2083961)
 * [Photo Gallery, Sliders, Proofing and Themes - NextGEN Gallery](https://wordpress.org/plugins/nextgen-gallery/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/nextgen-gallery/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/nextgen-gallery/)
 * [Active Topics](https://wordpress.org/support/plugin/nextgen-gallery/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/nextgen-gallery/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/nextgen-gallery/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [mbsharp](https://wordpress.org/support/users/mbsharp/)
 * Last activity: [3 weeks, 1 day ago](https://wordpress.org/support/topic/database-error-using-4-4-1/#post-19015436)
 * Status: resolved