mysql gone error and header warning - not sure what is happening?

bunnyjen

Joined: 2004-01-27
Posts: 22
Posted: Fri, 2007-01-26 20:47


Gallery version = 2.1.2 core 1.1.0.2
PHP version = 4.4.4 cgi
Webserver = Apache/1.3.37 (Unix) mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a PHP-CGI/0.1b
Database = mysql 4.0.27-standard, lock.system=flock
Toolkits = ArchiveUpload, Exif, Thumbnail, Gd, NetPBM
Acceleration = none, none
Operating system = Linux advancednetworkhosting.com 2.4.21-47.ELsmp #1 SMP Tue Aug 1 08:47:53 EDT 2006 i686
Default theme = Trevandjen
Locale = en_US
Browser = Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1

My G2 has run flawlessly for ... well, since I installed it (http://www.trevandjen.ca/gallery). I love it. However, a little while ago my server company had a massive hardware failure and my domain was down for a while. It's been up for a bit but I haven't had cause to go use my Gallery (other than a cursory look to see whether it was actually working when it was restored) until today.

However, I am getting some really strange errors. I can't replicate them consistently, either, so although I wrote the hosting company I'm not really sure whether they can help me as I am not sure what the issue really is and I don't know whether they have replicated them at all or not. They happen to me both in FF and IE.

There are two errors that I am getting. The first is a "mysql gone" error which appears in the upper left-hand corner of my browser. This seems to appear when things are not rendering right or when thumbnails aren't there and I refresh the page.

The second error, but seemingly related, is this one:

From what I can see, all of the permissions are correct. I am running another version of G2 on the domain (located at michael.trevandjen.ca) and it doesn't seem to have these errors so I don't think that they have reconfigured anything that would be interfering with Gallery. Could it be corrupted data in the restored version of my SQL DB for my gallery? I was going to try to go through the Gallery install to see if that would fix it but the install keeps hanging up right after authentication. :|

I have attached two screenshots showing the errors.

I do have a backup of my SQL DB from August 2006. Unfortunately, I forgot to back it up more recently and I have added one album since (not sure if there is a way to extract only the data from one album from a DB and add it so I wouldn't have to redo it again?) but if I have to redo the album that's what I have to do. It's not that big a deal. I just didn't want to do too much damage until I saw if someone else had run across these issues and/or knew what was causing them.

Thanks in advance for any help you can give.

Jennifer

AttachmentSize
screenshot1.jpg53.93 KB
screenshot2.jpg117.9 KB
Login or register to post comments
bunnyjen

Joined: 2004-01-27
Posts: 22
Posted: Fri, 2007-01-26 21:47

Hmm. I finally got the installation module to run past the authentication step and things seem to be working OK for now. Here's hoping it's fixed itself!

Login or register to post comments
valiant

Joined: 2003-01-04
Posts: 32356
Posted: Sat, 2007-01-27 00:03

the second error, "Warning: Cannot modify header information - headers already sent by (output started at" is just a consequence of the "mysql gone" issue.
you'd get the second error pretty often as a symptom of another issue, as in this case.

so let's focus on "mysql gone".

it's definitely a mysql related issue. either the mysql server has a problem or some corruption in the database actually kills the connection or the server during an interaction.

have you already run mysqlchk / myisamchk or other tools to check your database?

--------------
Enter the Gallery 2 Theme Contest today!

Login or register to post comments
bunnyjen

Joined: 2004-01-27
Posts: 22
Posted: Sat, 2007-01-27 06:17

I ran a check on the SQL DB through the mysql page and everything came back OK. I wrote the service provider assuming it was some sort of data corruption from when they repaired everything and they are, as I expected, trying to argue it is a script error (likely because of the second error, which is obviously caused by the first error but try arguing that with them... never works no matter how helpful they are I guess) which I know is unlikely but whatever. I haven't run into the problem since I reran the installation module so I don't know if whatever hiccup existed in the SQL file was overwritten somehow or what but I'm not going to argue with it. Thanks for the response, though. I was getting nervous for a minute! :)

Login or register to post comments