Issue with installation of SuiteCRM-Upgrade-7.11.x-to-7.11.19

Hi
We are currently trying to install the SuiteCRM-Upgrade-7.11.x-to-7.11.19 and we are running into the folowing error messages:
ERROR: There was an error during your upload, please contact an administrator for help.

  • Size of Upload (55364761 bytes) Exceeded Allowed Maximum: 8388608 bytes

We have increased the file size access through our server to upload_max_filesize to 80M.
What else can we do to fix this issue.
Please and Thanks
Ken

@TOCK
What value do you have here?

I have the same as in the screen shot,

Do I need to change this to a higher number

@TOCK
Perhaps. And check post_max_size in php.ini .

The post_max_size is set to 8m

I’m not sure that setting of Upload max size from the UI is taking effect. You can check from Admin / Diagnostics / phpinfo.

If needed, change it from php.ini.

@TOCK
You should set value more.

1 Like

which value the Maximum upload size or the post_max_size increased from 8M

@TOCK

upload_max_filesize and post_max_size are analyzing together. They value should be more then file. “Maximum upload size” is using perhaps.

We have increased the max_size and now we are getting the following error message.

This site can’t be reached

The webpage at https://toc-crm.azurewebsites.net/suitecrm/index.php might be temporarily down or it may have moved permanently to a new web address.

ERR_HTTP2_PROTOCOL_ERROR

@TOCK
Looks at personal account on Azure. Maybe it has some limits.

Hi Team,

My colleague tried loading the SuiteCRM-Upgrade-7.11.x-to-7.11.19 zip file using using FTP access and managed to get the file uploaded when he tried to complete the process he got a “504-Gateway Time-Out”.
I have tryed to access the Upgrade Wizard this morning and I keep getting the following message:

Database failure. Please refer to suitecrm.log for details.

I have checked the error log in System settings, please see error:

Thu May 27 05:35:23 2021 [41][-none-][FATAL] Mysqli_query failed. Thu May 27 05:35:23 2021 [41][-none-][FATAL] Retrieving record by id users:1831297b-6ad8-9a9b-e0a0-5fdb6f88fa07 found Query Failed: SELECT users.* FROM users WHERE users.id = ‘1831297b-6ad8-9a9b-e0a0-5fdb6f88fa07’ AND users.deleted=0 LIMIT 0,1: MySQL error 2006: MySQL server has gone away Thu May 27 05:37:40 2021 [150][1831297b-6ad8-9a9b-e0a0-5fdb6f88fa07][FATAL] SugarBean::populateDefaultValues $field_defs should be an array Thu May 27 05:37:41 2021 [150][1831297b-6ad8-9a9b-e0a0-5fdb6f88fa07][FATAL] SugarBean::populateDefaultValues $field_defs should be an array Thu May 27 05:37:41 2021 [150][1831297b-6ad8-9a9b-e0a0-5fdb6f88fa07][FATAL] SugarBean::populateDefaultValues $field_defs should be an array Thu May 27 05:41:16 2021 [177][1831297b-6ad8-9a9b-e0a0-5fdb6f88fa07][FATAL] Mysqli_query failed. Thu May 27 05:41:16 2021 [177][1831297b-6ad8-9a9b-e0a0-5fdb6f88fa07][FATAL] Query Failed: SELECT id FROM upgrade_history ORDER BY date_entered desc: MySQL error 2006: MySQL server has gone away Thu May 27 05:41:16 2021 [177][1831297b-6ad8-9a9b-e0a0-5fdb6f88fa07][FATAL] Exception handling in /home/site/wwwroot/suitecrm/include/MVC/Controller/SugarController.php:400 Thu May 27 05:41:16 2021 [177][1831297b-6ad8-9a9b-e0a0-5fdb6f88fa07][FATAL] Exception in Controller: Database failure. Please refer to suitecrm.log for details. Thu May 27 05:41:16 2021 [177][1831297b-6ad8-9a9b-e0a0-5fdb6f88fa07][FATAL] backtrace: #0 /home/site/wwwroot/suitecrm/include/database/DBManager.php(353): sugar_die(‘Database failur…’) #1 /home/site/wwwroot/suitecrm/include/database/DBManager.php(328): DBManager->registerError(’ Query Failed: …’, ’ Query Failed: …’, true) #2 /home/site/wwwroot/suitecrm/include/database/MysqliManager.php(179): DBManager->checkError(’ Query Failed: …’, true) #3 /home/site/wwwroot/suitecrm/data/SugarBean.php(5507): MysqliManager->query(‘SELECT id FROM …’, true) #4 /home/site/wwwroot/suitecrm/modules/Administration/UpgradeHistory.php(177): SugarBean->build_related_list(‘SELECT id FROM …’, Object(UpgradeHistory)) #5 /home/site/wwwroot/suitecrm/modules/Administration/UpgradeHistory.php(172): UpgradeHistory->getList(‘SELECT id FROM …’) #6 /home/site/wwwroot/suitecrm/modules/UpgradeWizard/index.php(308): UpgradeHistory->getAll() #7 /home/site/wwwroot/suitecrm/include/MVC/View/SugarView.php(839): include_once(’/home/site/wwwr…’) #8 /home/site/wwwroot/suitecrm/include/MVC/View/views/view.classic.php(72): SugarView->includeClassicFile(‘modules/Upgrade…’) #9 /home/site/wwwroot/suitecrm/include/MVC/View/SugarView.php(226): ViewClassic->display() #10 /home/site/wwwroot/suitecrm/include/MVC/Controller/SugarController.php(435): SugarView->process() #11 /home/site/wwwroot/suitecrm/include/MVC/Controller/SugarController.php(375): SugarController->processView() #12 /home/site/wwwroot/suitecrm/include/MVC/SugarApplication.php(113): SugarController->execute() #13 /home/site/wwwroot/suitecrm/index.php(52): SugarApplication->execute() #14 {main} Thu May 27 05:41:16 2021 [54][-none-][FATAL] Mysqli_query failed. Thu May 27 05:41:16 2021 [54][-none-][FATAL] Retrieving record by id users:1831297b-6ad8-9a9b-e0a0-5fdb6f88fa07 found Query Failed: SELECT users.* FROM users WHERE users.id = ‘1831297b-6ad8-9a9b-e0a0-5fdb6f88fa07’ AND users.deleted=0 LIMIT 0,1: MySQL error 2006: MySQL server has gone away

This only happens when I try to access the Upgrade Wizard option in the Admin panel all other options work correctly e.g. User Management, System Setting, Import Wizard

Thanks

Ken Clancy

The post_max_size 8M is this sufficient for the upgrade process, this figure is from our current DIAGNOSTIC TOOL Getting phpinfo().

If the upgrade package is, for example, 60M, make both the post_max_size and the upload_max_size bigger than that value, it’s simple.

1 Like

You should upgrade the timeout (in seconds) for server answer:

  • for apache
    – in file httpd.conf set Timeout 600
  • for nginx
    proxy_connect_timeout 600;
    proxy_send_timeout 600;
    proxy_read_timeout 600;
    send_timeout 600;
  • for php
    – in php.ini set max_execution_time 600

You should check database maybe there are some problem with data. For start check - users.id = '1831297b-6ad8-9a9b-e0a0-5fdb6f88fa07'