Update errors - every single time since v.3.8

[sth-chris]

I've been using HB since v2.6. Ran fine up until they started the auto-update feature. I've probably been luckier than most and never had major problems with HB.

Ever since then, when I perform the auto-update, it runs the update and then throws this error:

Uh oh! Something went wrong ...
Exception: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away IN /home/*******/public_html/clients/hbf/core/class.hbconfig.php(174), stack trace:
#0 /home/*******/public_html/clients/hbf/core/class.hbconfig.php(174): PDOStatement->execute()
#1 /home/*******/public_html/clients/includes/modules/Other/autoupgrade/class.autoupgrade.php(438): HBConfig::setConfig()
#2 /home/*******/public_html/clients/includes/modules/Other/autoupgrade/admin/class.autoupgrade_controller.php(92): AutoUpgrade->performUpgrade()
#3 /home/*******/public_html/clients/hbf/core/class.controller.php(253): AutoUpgrade_Controller->performupgrade()
#4 /home/*******/public_html/clients/hbf/core/types/class.admin_frontcontroller.php(129): Controller::dispatchControl()
#5 /home/*******/public_html/clients/hbf/core/class.frontcontroller.php(124): Admin_FrontController->dispatch()
#6 /home/*******/public_html/clients/hbf/core/class.frontcontroller.php(107): FrontController->handleRequest()
#7 /home/*******/public_html/clients/admin/index.php(14): FrontController::init()
#8 {main}

Uh oh! Something went wrong ...
PHP [Error]: Uncaught exception 'PDOException' with message 'SQLSTATE[HY000]: General error: 2006 MySQL server has gone away' in /home/*******/public_html/clients/hbf/components/hbdebug/class.hberrorlog.php:31
Stack trace:
#0 /home/*******/public_html/clients/hbf/components/hbdebug/class.hberrorlog.php(31): PDOStatement->execute()
#1 /home/*******/public_html/clients/hbf/core/class.hbexception.php(85): HBErrorLog->createEntry()
#2 [internal function]: HBException::php_exception_handler(Object(PDOException))
#3 {main}
thrown IN hbf/components/hbdebug/class.hberrorlog.php(31)


I submitted a ticket for this (before they started charging for them!) and went through the hoops of giving them my admin password/logins, etc. that they always ask for but they've never fixed it. The ticket is still open to this day.

There are no errors in the error log in HB.

Even though I get this error, if I just go BACK in the browser it goes back to the admin page, shows the updated version number and things seem to be running fine.

Any ideas?

Thanks!

[Patrick]

It's pretty weird, we haven't had any issues so far dating back to V2 i believe it was.  I find it a little weird that small server configuration differences would cause so many upgrade issues because you're not the only one with this problem, that's for sure.  I see so many reports of this and it's pretty worrying and opening a support ticket is useless even if paid.  Like you said it remains open and nothing comes of it.

I think i've given them admin access twice now and never once did they log in to fix an issue.  Canned response and leave the ticket to rot.   For this very reason, i think we're done updating now that we have what seems to be a decently stable release (sort of minus a few little things). 

I know my answer isn't what you're looking for but i do hope you get it figured out and please update the thread if you get an answer.  These types of errors are increasing and for that reason alone i'd like to know what's causing it myself

[sth-chris]

I posted the same problem on the official HB forum and got a couple replies, but they all said the same thing:

check your php.ini config. When I asked what specifically I should be looking for, nobody had a clue and couldn't give me a straight answer. I gave up. But, I still want it fixed. So, if anyone has any ideas on what I should be looking for with php config (if that's even the source of the problem), then I'm open for suggestions.

Thanks!

[pcardoso]

We have the same problem.
Tried to increase mysql timeout but that didn't fixed it too...

[Lawrence]

I think it has something to do with the database password. Try this,

1. Install a fresh HostBill install (If possible) with a password containing numbers, letters, and special characters, about 15+ characters long.
2. Install a fresh HostBill install just with letters (lowercase) and numbers.

In scenario #2, I've had no issues installing HostBill. In scenario #1, I can't seem to get HostBill to install.

I'm thinking it may have something to do with that during the install / update process.

The only thing I can suggest is try changing the password to something simple (alphanumeric, and numbers. Lowercase letters). Then, try to update. If the problem persists, then it's not that and I'm at a loss as well. I don't use the auto update feature, so I haven't experienced this issue.

[sth-chris]

I don't want to doubt you, but that sounds a little out there....  I'd think if it had a problem with the DB password it would fail to upgrade at all. It does do the upgrade, but just results in that error.

[Lawrence]

I don't want to doubt you, but that sounds a little out there....  I'd think if it had a problem with the DB password it would fail to upgrade at all. It does do the upgrade, but just results in that error.

I can understand where you're coming from. I've just always had issues with HostBill and installing with complex passwords. It was worth a mention. Hope someone else has resolved this issue so you can get a solution. I don't use the auto upgrade unfortunately.

Did you need assistance upgrading manually? It's pretty straight forward.

[nibb]

What is your PHP version?

Your MYSQL is crashing, this is your error, check your MYSQL logs, and server logs to see what is causing this.

[tallship]

Uh oh! Something went wrong ...
Exception: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away IN

Try adjusting your RAM in your /etc/httpd/php.ini file:

Code Select Expand


memory_limit = 512M


That seems to usually fix those kinds of errors for me, and when I have customers in shared hosting environments who are running Drupal sites or other CMS systems that get big, it should be noted that they have their own php.ini files in their ~/ tree, that override many of the default settings.

Or perhaps check for adjustments in the [MYSQL] section?

Code Select Expand


; Query timeout
;mssql.timeout = 60


Lemme know, as I'm interesting in finding out how you resolved the issue

Kindest regards,