mycota Posted November 26, 2014 Posted November 26, 2014 All of the files installed properly and I had the environment running. While I was working with settings this error came up for both the front end and admin login. Not sure if it is a bug or something I did. Can anyone provide some insight on how to diagnose and repair? Beta 2.
Farcaster II Posted November 26, 2014 Posted November 26, 2014 Take a look at the log files inside the uploads/logs directory
Stuart 4 Posted November 26, 2014 Posted November 26, 2014 yes I got that to when I try to run the instiller I getting this Installer Lockedhope you made a back up
mycota Posted November 28, 2014 Author Posted November 28, 2014 There was a temporary file that was not readable. Reset the container on the server and problem solved.
Stuart 4 Posted November 28, 2014 Posted November 28, 2014 what is the file was not readable so I can change my
Captain Ginns Posted December 1, 2014 Posted December 1, 2014 I'm having the same problem. A couple of details would be nice. Also how to reset "container" ...how is that done. Thanks.
mycota Posted December 1, 2014 Author Posted December 1, 2014 Look in uploads/logs to find the error. In my case it was a temporary file that could not be written to. The error looked like:Wed, 26 Nov 2014 23:57:48 +0000 (Severity: 0)XX.XXX.XX.XXX - http://XXXX.com/robots.txtCan't create/write to file '/tmp/#sql_2a8_0.MYD' (Errcode: 17)X's are the IP and domain. To fix this I reset the server. Or I am told you can delete the problem file.
TexFanatico Posted September 6, 2015 Posted September 6, 2015 Mhhh, personally I've made the convertion: Error The database tables are UTF-8, collations are correct and there is nothing to convert. You can proceed with the upgrade Unfortunalty I got the same problem: I've checked the logs and I find a lot of table that doesn't exist. They are all the ".x_utf_core_..." table. An easy way to resolve this problem? Now I see only "delete" the DB, take back a backup (but it would be really long) and retry all. Thank you Edit: finally, the problem was on conf_global (take back the old one and the problem was solved)
Recommended Posts
Archived
This topic is now archived and is closed to further replies.