Errors after failed update to 5.5.2.1
Permalink
I tried to update a site to 5.5.2.1 from 5.4.2.2 through the dashboard as I have done for other sites. The update failed, and despite restoring the previously back-up database, I am getting these kinds of errors all over the site now.
mysql error: [1: Can't create/write to file '/tmp/#sql_1f9b_0.MYD' (Errcode: 122)] in EXECUTE("SHOW COLUMNS FROM `btNavigation`")
This is hosted on a VPS site that hosts a number of other updated C5 sites using the same version of MySql without any issues. There shouldn't be any issues with the disk space for this site. Any help would be appreciated. Thanks.
mysql error: [1: Can't create/write to file '/tmp/#sql_1f9b_0.MYD' (Errcode: 122)] in EXECUTE("SHOW COLUMNS FROM `btNavigation`")
This is hosted on a VPS site that hosts a number of other updated C5 sites using the same version of MySql without any issues. There shouldn't be any issues with the disk space for this site. Any help would be appreciated. Thanks.
Thanks. Site is working again, albeit still as a a 5.4.2.2 site, obviously.
For anyone else who might encounter these sporadic MySql errors, I checked with the webhost. According to them, while there was plenty of disk space and no spike in MySql requests, I had reached their default limit for inodes for that VPS account. They upped the limit (no problem, no extra charge). But if someone has a similar issue (particularly on a shared hosting account, I would think), a large number of files combined with a jump in temp files could be the culprit. Or not. As I have done in the past, I am going through each C5 site to delete older page versions and cleaning out unused/outdated images in the File Manager. Just for fun.
For anyone else who might encounter these sporadic MySql errors, I checked with the webhost. According to them, while there was plenty of disk space and no spike in MySql requests, I had reached their default limit for inodes for that VPS account. They upped the limit (no problem, no extra charge). But if someone has a similar issue (particularly on a shared hosting account, I would think), a large number of files combined with a jump in temp files could be the culprit. Or not. As I have done in the past, I am going through each C5 site to delete older page versions and cleaning out unused/outdated images in the File Manager. Just for fun.
Glad it helped,
There have been problems with auto update recently so I would advice against using it, instead do this,
download the latest package from this website (currently 5.5.2.1),
unzip the package and ftp it into the root/updates/ folder,
then run this file from your browser,
http://www.yoursite.com/index.php/tools/required/upgrade...
make sure you backup your database before updating just in case..
If you need to re-run the update file use this code
http://www.yoursite.com/index.php/tools/required/upgrade?force=1...
There have been problems with auto update recently so I would advice against using it, instead do this,
download the latest package from this website (currently 5.5.2.1),
unzip the package and ftp it into the root/updates/ folder,
then run this file from your browser,
http://www.yoursite.com/index.php/tools/required/upgrade...
make sure you backup your database before updating just in case..
If you need to re-run the update file use this code
http://www.yoursite.com/index.php/tools/required/upgrade?force=1...
Thanks. I actually tried that, but even with the 5.5.2.1 files in the root/updates/ folder folder.http://www..../index.php/tools/required/upgrade... just confirmed that the site was updated (to 5.4.2.2). I will try again tonight while my client sleeps peacefully.
Lifesaver! - thought I'd be looking at HOURS of re-uploading and whatnot. Thank you so much for this! :-D
You now need to edit your root/config/site.php file and remove this line