View Full Version : Solved Database error
aeolian x
12-02-2008, 10:52 AM
I've had this problem since the first install. Cannot preview either HTML or text. Tried to send, and I get this database error. Started with 1.0.1, now running EZNL 1.0.5.
Database error in vBulletin 3.7.4:
Invalid SQL:
UPDATE eznl_data SET lastpage = '1' WHERE timeset = '1228232531';
MySQL Error : MySQL server has gone away
Error Number : 2006
Request Date : Tuesday, December 2nd 2008 @ 09:42:21 AM
Error Date : Tuesday, December 2nd 2008 @ 09:43:56 AM
Script : http://*******.com/forum/admincp/eznl.php?do=send
Referrer : http://*******.com/forum/admincp/eznl.php?do=process
IP Address : 67.54.253.196
Username : *****
Classname : vB_Database
MySQL Version :
So this is just one example and other queries fail with the same error? You have to get through a couple of pages of queries to get there. So the server is not going away in any pattern, just going away?
Are you on windows? What kind of server?
What is you perpage setting for sending?
aeolian x
12-02-2008, 12:21 PM
Linux, setting per page is 100. Can't even get to that point without error though. Right before sending, when previewing the HTML & Text, ithe preview is redirected to my forumhome, which I have set to do whenever a page is non-existant. This is consistant. Everything works fine up to that point. Previewing the lead in Message before the Newsletter preview page does work fine.
I have seen similar when the url accessing the acp is different then the vboptions bburl.
Is there a test account there that I can run the app and see what is causing the redirects?
aeolian x
12-02-2008, 06:56 PM
I'm getting a 403 Forbidden when I click on the previews. The error page also states that there's a 404. Very strange. So I installed this in another forum just to see if there was something wrong on that database, and it does the same thing. I'll send you the test info in a bit.
Thanks for the test info. I was able to identify the preview issue and it's fixed for 1.0.6.
The time out issues I put in some code to keep mysql awake that will add no overhead. But you will have to test that theory. It's not so much a bug, it's more of trying to not hit a limit and timeout.
aeolian x
12-02-2008, 10:18 PM
That worked perfectly. Everything went through without a hitch. Thanks so much!
That worked perfectly. Everything went through without a hitch. Thanks so much!
Thank you for your support and help getting the issues fixed.
Glad to hear we're getting somewhere.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.