My website used CodeIgnter framework and host with iPage. Before, my PHP version is 5.2, then i update it to 5.3. After i updated to PHP 5.3 always get error as below:
- Got error 28 from storage engine
- Incorrect key file for table '/mysql-tmp/#sql_16c4_0.MYI'. try to repair it
- Got error -1 from storage engine
It's not a new question in StackOverflow, but I want to make sure that:
Does these error cause from my update from PHP 5.2 to 5.3?
Does it cause from my misconfiguration in php.ini?
From hosting? or any others?
Sounds like a disk space issue:
MySQL: #126 - Incorrect key file for table
Contact your hosting provider.
Also, this is a mysql issue, not a PHP issue; doesn't matter what version of php you are running.
Got error 28 from storage engine
Disk space problem..
Need space to save the data in the database
if it is loaclhost check your drive memory status if memory is full in that disk free some space.
if it is hosting contact your hosting provider
Related
I have migrated my magento website from one server to another, I have changed base url for secure and non secure to new domain, also changed database credentials in env file. but still i am getting error of PDO exception regard databse connection on exception log.
Note: I have enabled error log in index.php file.
Can you post the error details?
(keep sensible data out of it)
As far as I usually encounter, errors like these are related to file permissions. Especially after migrating. Kindly check your files & folders permissions.
Of course the above is assuming the new server meets the system requirements (PHP version, PHP extensions and Mysql versions).
Here are the Magento System Requirements for v2.1.x: https://devdocs.magento.com/guides/v2.1/install-gde/system-requirements-tech.html
Here is some info about permissions:
https://devdocs.magento.com/guides/v2.1/install-gde/prereq/file-system-perms.html
And if you happen to use SELinux check this: https://devdocs.magento.com/guides/v2.1/install-gde/prereq/security.html
I'm using Codeigniter for my website. I have tried setup memcached to cache object from database and when its running i saw the warning like this:
ERROR - 2016-01-12 00:28:40 --> Severity: Warning --> Memcached::get(): could not read long value, too big /var/www/CodeigniterProject/system/libraries/Cache/drivers/Cache_memcached.php 149
How can i fix this?
I've seen this happen when values have been saved using the Memcache extension and then are retrieved with the Memcached extension - there's an incompatibility between the serialisation used in the two. Flushing the memcache server should solve the issue.
We had the same problem. To resolve it we have changed the package from php5-memcached to php5-memcache. It solved our problem.
You can try changing the Memcached serializer by:
$m->setOption(Memcached::OPT_SERIALIZER, Memcached::SERIALIZER_PHP);
(where $m is the Memcached instance).
I have a CodeIgniter setup that has been running fine for the past 2 months and recently I keep getting:
CodeIgniter error- unable to connect to database using the provided settings
I've recently added a new domain that has a landing page for the database login (zPanel), but I don't see how that could have caused a problem--maybe the page keeps getting directory attacked or something, but I'm not sure.
Is there a way to check if this is the problem through logs? I'm at dead ends with this problem, as when I restart the server (DigitalOcean) it works fine again.
Really not sure. If anyone else has had a similar problem, I'd love to hear your solution.
Thanks.
I think your mysql is going down so Codeigniter can't connect to your database settings.
Please login to SSH and check processes by "TOP" comment. See what is using resources ram or cpu.
And check your mysql conf settings, be sure that everything written if its empty it will cause alot of problems.
Some example :
http://www.maxwhale.com/how-to-optimize-mysql-for-1gb-memory-vps/
I'm setting up a new website and the site uses asp.net membership. This was working fine but today when I try and log in or do anything such as add a new user/role in the asp.net configuration wizard I get:
Warning: Fatal error 9001 occurred at Jul 30 2012 7:52PM. Note the error and time, and contact your system administrator.
Searching online, it seems to suggest that the logs are full, but I'm advised by the website host that there is ample free space, so I dont really know what to try next.
Has anyone come accross this before and if so, how did you manage to resolve it?
Thanks
I have had this problem recently too and after mountains of research it appears to be common when a database is set to AUTO CLOSE. I set all the databases to AUTO CLOSE = FALSE. This started with one database then went over to two and the next it was on all of them. I simply restarted the SQL Server Instance Service instead of restoring databases. Another way to fix the symptom is to take the problematic database offline and bring it back online again.
As it turns out this was a database issue. I couldn't even create a new table or drop a table and ultimately had to get the database restored, which solved everything.
I am upgrading an existing magento website for 1.4 to 1.6.1.0.
I had dumped the existing database,
Copied all the required custom extension in the blank magento version 1.6.1.0
and after running the installation got the following error:
Error in file:
"/app/code/core/Mage/Customer/sql/customer_setup/mysql4-upgrade-1.5.9.9-1.6.0.0.php"
- SQLSTATE[HY000]: General error: 1025 Error on rename of './sales_flat_order' to './#sql2-3af-a7' (errno: 152)
How can I fix this issue?
Upgrading magento is very painful process. I suggest you to import-export data from old to new shop.
I just went through the same heartburn. I found that letting the page try to load until the script got an error or timed out and then trying again eventually worked. The upgrade script will attempt to start where it last stopped.
Before you do that, make a backup of you site and database. If it continually errors in the same spot, restore and try again.
These tips may help improve the odds of a quicker success:
Put the site in maintenance mode (by adding the maintenance.flag file
to the root directory) before starting.
Increase server and php timeouts by a very large amount (3-5minutes).
Cleanup temp and log database tables that you don't care about
(carefully, everybody has different needs here)
I tried several different methods and that is the only thing that worked. It took probably 10 reloads (waiting for a 3min timeout each time). In the end, everything upgraded correctly. No matter what method you choose, if you want to keep your store data, you will have to run the bulky db upgrade scripts that take forever.
I had similar issues when updating from 1.4.2 to latest.
I built a custom maintenance script included in my index.php that only allowes to access my ip. But the update process via shell replaced my index.php so it was accessible for everyone.
That was the cause that the final sql scripts where run by several clients and caused errors like "can't move table" etc. because those steps where already done.
--> Summing it up: Be sure that the site gets called only once, until the upgrade was successful!
The very best way to migrate magento in my opinion, is to import your entire db to an environment that you have your new magento. Then magento will run all scripts and updates and keep your data.
Maybe you find some problems on the upgrade scripts, but it's easier to fix them than fix the problems regarding model/eav's problems on the fly.
I have succeed by doing this on migrate from 1.4.1 to 1.8.1.