Error (ERROR_STORAGE_FAILURE)
terp4life2001
Joined: 2005-02-03
Posts: 4 |
Posted: Tue, 2005-11-01 03:27 |
Hey there, I've had Gallery! up and running for about a year now with no problems. I believe that I upgrated the Gallery Remote to the most recent version and attempted to connect to my gallery. Ever since my gallery is down. The main problem is this, Error (ERROR_STORAGE_FAILURE) * in modules/core/classes/GalleryStorage/DatabaseStorage.class at line 720 (gallerystatus::error) To me that looks like I'm having a problem with my database. I turned on debugging ('logged') in my config.php file, but it doesn't seem to print anything out. I also tried to use phpMyAdmin to check out my database. I can't see anything wrong, allthough I don't know what to look for. Lastly, I tried to log into the alpha installer to see if I could do a system check up. It won't let me get past the first page. IE, I can't even get into the authentication page. I'm fairly capable, I just need some debugging suggestions? How can I tell if my database is stable? How can I test the connection between Gallery and the DB? Thanks in advance, //Rob The following information is required to get an answer: |
|
Posts: 32509
read the debug instructions in config.php, logged debugging doesn't print the debug output to the browser, it prints the debug output to a log file.
buffered debug output prints the debug output to the browser, but doesn't print super detailed log messages.
immediate debug output prints all debug output to the browser, but screws up the look of the site completely.
so i'd continue to use logged debug output.
alpha installer? a G2 alpha version installer? why?
you know that you can only upgrade from alpha 4 and later to the current g2 version, right?
g2 alpha versions are more than a year old now...
and what did you do to break the system? upgrade Gallery Remote?? GR the java applet or GR the G2 module? to use GR with G2 you need both of course. just asking what you changed since you had a working G2.
with buffered debug, you should see the exact db error on the page.