cancel
Showing results for 
Search instead for 
Did you mean: 

Internal Server Error after upgrading from magento 2.3.0 to 2.3.3

SOLVED

Internal Server Error after upgrading from magento 2.3.0 to 2.3.3

I had upgraded my dev store from magento 2.3.0 to 2.3.3 after that i am getting below error Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@dev.vitalticks.in to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

If i rename or delete the .htaccess file only home page is loading when i click on any other links again i am getting above error only.

For reference please find the Url dev.vitalticks.in

Log File

[2019-11-28 01:31:35] main.CRITICAL: Warning: Invalid argument supplied for foreach() in /home/vitalticks/public_html/dev/app/code/Mageplaza/Search/Helper/Data.php on line 345 [] [] [2019-11-28 03:52:05] main.CRITICAL: Warning: Invalid argument supplied for foreach() in /home/vitalticks/public_html/dev/app/code/Mageplaza/Search/Helper/Data.php on line 345 [] [] [2019-11-28 05:37:25] main.CRITICAL: Warning: Invalid argument supplied for foreach() in /home/vitalticks/public_html/dev/app/code/Mageplaza/Search/Helper/Data.php on line 345 [] [] [2019-11-28 05:38:28] main.ERROR: Unable to proceed: the maintenance mode is enabled. [] [] [2019-11-28 06:16:11] main.WARNING: Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size or decrease batch size value (which decreases memory usages for the temporary table). Current batch size: 100000; Allocated memory size: 50000000 bytes; InnoDB buffer pool size: 134217728 bytes. [] [] [2019-11-28 06:16:11] main.WARNING: Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size or decrease batch size value (which decreases memory usages for the temporary table). Current batch size: 100000; Allocated memory size: 50000000 bytes; InnoDB buffer pool size: 134217728 bytes. [] [] [2019-11-28 06:16:11] main.WARNING: Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size or decrease batch size value (which decreases memory usages for the temporary table). Current batch size: 100000; Allocated memory size: 50000000 bytes; InnoDB buffer pool size: 134217728 bytes. [] [] [2019-11-28 06:16:11] main.WARNING: Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size or decrease batch size value (which decreases memory usages for the temporary table). Current batch size: 100000; Allocated memory size: 50000000 bytes; InnoDB buffer pool size: 134217728 bytes. [] [] [2019-11-28 06:16:12] main.WARNING: Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size or decrease batch size value (which decreases memory usages for the temporary table). Current batch size: 100000; Allocated memory size: 50000000 bytes; InnoDB buffer pool size: 134217728 bytes. [] [] [2019-11-28 06:16:12] main.WARNING: Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size or decrease batch size value (which decreases memory usages for the temporary table). Current batch size: 100000; Allocated memory size: 50000000 bytes; InnoDB buffer pool size: 134217728 bytes. [] [] [2019-11-28 06:16:12] main.WARNING: Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size or decrease batch size value (which decreases memory usages for the temporary table). Current batch size: 1667; Allocated memory size: 40008000 bytes; InnoDB buffer pool size: 134217728 bytes. [] [] [2019-11-28 06:18:00] main.CRITICAL: Warning: Invalid argument supplied for foreach() in /home/vitalticks/public_html/dev/app/code/Mageplaza/Search/Helper/Data.php on line 345 [] [] [2019-11-28 06:18:28] main.CRITICAL: Warning: Invalid argument supplied for foreach() in /home/vitalticks/public_html/dev/app/code/Mageplaza/Search/Helper/Data.php on line 345 [] [] [2019-11-28 06:34:57] main.CRITICAL: Warning: Invalid argument supplied for foreach() in /home/vitalticks/public_html/dev/app/code/Mageplaza/Search/Helper/Data.php on line 345 [] [] [2019-11-28 06:35:03] main.CRITICAL: Warning: Invalid argument supplied for foreach() in /home/vitalticks/public_html/dev/app/code/Mageplaza/Search/Helper/Data.php on line 345 [] [] [2019-11-28 06:46:41] main.WARNING: Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size or decrease batch size value (which decreases memory usages for the temporary table). Current batch size: 100000; Allocated memory size: 50000000 bytes; InnoDB buffer pool size: 134217728 bytes. [] [] [2019-11-28 06:46:41] main.WARNING: Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size or decrease batch size value (which decreases memory usages for the temporary table). Current batch size: 100000; Allocated memory size: 50000000 bytes; InnoDB buffer pool size: 134217728 bytes. [] [] [2019-11-28 06:46:41] main.WARNING: Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size or decrease batch size value (which decreases memory usages for the temporary table). Current batch size: 100000; Allocated memory size: 50000000 bytes; InnoDB buffer pool size: 134217728 bytes. [] [] [2019-11-28 06:46:41] main.WARNING: Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size or decrease batch size value (which decreases memory usages for the temporary table). Current batch size: 100000; Allocated memory size: 50000000 bytes; InnoDB buffer pool size: 134217728 bytes. [] [] [2019-11-28 06:46:41] main.WARNING: Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size or decrease batch size value (which decreases memory usages for the temporary table). Current batch size: 100000; Allocated memory size: 50000000 bytes; InnoDB buffer pool size: 134217728 bytes. [] [] [2019-11-28 06:46:41] main.WARNING: Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size or decrease batch size value (which decreases memory usages for the temporary table). Current batch size: 100000; Allocated memory size: 50000000 bytes; InnoDB buffer pool size: 134217728 bytes. [] [] [2019-11-28 06:46:42] main.WARNING: Memory size allocated for the temporary table is more than 20% of innodb_buffer_pool_size. Please update innodb_buffer_pool_size or decrease batch size value (which decreases memory usages for the temporary table). Current batch size: 1667; Allocated memory size: 40008000 bytes; InnoDB buffer pool size: 134217728 bytes. [] []

Thanks in Advance Somu N

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Internal Server Error after upgrading from magento 2.3.0 to 2.3.3

Hello @sekhar_n 

Can you upload default Magento .htaccess file and check?

Also, try disabling mageplaza search extension as @Rahul Gupta suggested.

Delete generation folder.

Clear var/log, cache, report folders.

run all the commands again, ie. upgrade, static deploy, cache and indexing and check once then.

Was my answer helpful? You can accept it as a solution.
175+ Professional Extensions for M1 & M2
Need a developer?Just visit Contact Us Now

View solution in original post

5 REPLIES 5

Re: Internal Server Error after upgrading from magento 2.3.0 to 2.3.3

Hello @sekhar_n 

 

as i see it is a warning.

 

just move to developer mode and test your site.

php bin/magento d:m:set developer

 

and check server log, if it is apache2 then check etc/apache2/error.log

 

 


Problem solved? Click Kudos & Accept as Solution!
Sunil Patel
Magento 2 Certified Professional Developer & Frontend Developer

Re: Internal Server Error after upgrading from magento 2.3.0 to 2.3.3

it is easy apache 4

Re: Internal Server Error after upgrading from magento 2.3.0 to 2.3.3

@sekhar_n try to disable Mageplaza_Search extension and then check if it is working fine.

 

Thanks

Re: Internal Server Error after upgrading from magento 2.3.0 to 2.3.3

Hello @sekhar_n 

Can you upload default Magento .htaccess file and check?

Also, try disabling mageplaza search extension as @Rahul Gupta suggested.

Delete generation folder.

Clear var/log, cache, report folders.

run all the commands again, ie. upgrade, static deploy, cache and indexing and check once then.

Was my answer helpful? You can accept it as a solution.
175+ Professional Extensions for M1 & M2
Need a developer?Just visit Contact Us Now

Re: Internal Server Error after upgrading from magento 2.3.0 to 2.3.3

I had disabled Mageplaza search even though i am getting same error