magento commands don't function any more

[Manthan Dave]

Hi @Texasbull

I think you are on correct path but you still need to increase max_allowed_packet.

change max_allowed_packet value to 512M

Sometimes - it requires huge memory if you have large scale data or any other third party themes and extensions are installed.

so if possible increase max_execution_time value and make it max_execution_time = 18000

Hope it helps !!

[Texasbull]

[mysqld]
default-storage-engine=MyISAM
innodb_file_per_table=1
performance-schema=0
max_allowed_packet=1G
open_files_limit=10000
tmp_table_size=250M
max_heap_table_size=250M
innodb_lock_wait_timeout=1000000
innodb_autoinc_lock_mode=2

Above you will find the contents of my.cnf 

max_execution_time was an unrecognized variable which created errors on restart.

---

@Manthan Dave wrote:

Hi @Texasbull

I think you are on correct path but you still need to increase max_allowed_packet.

change max_allowed_packet value to 512M

Sometimes - it requires huge memory if you have large scale data or any other third party themes and extensions are installed.

so if possible increase max_execution_time value and make it max_execution_time = 18000

Hope it helps !!

---

[Sunil Patel]

Hello @Texasbull

can you please increase below two value into mysql

net_read_timeout = 360net_write_timeout = 360

[Texasbull]

---

@Sunil Patel wrote:

Hello @Texasbull

can you please increase below two value into mysql

net_read_timeout = 360net_write_timeout = 360

---

ACTION: The 2 lines were inserted in the my.cnf and mysql restarted.

RESULT: Same Exception

[Texasbull]

The issue turns out to be a corrupted database that I am trying to recover as much data out of as possible on a new installation of Magento 2.1.5. Oddly trying to install Magento 2.2.4 did not allow me to get to the setup wizard.

Any ideas on how to facilitate the copy of uncorrupted portions of the old database to the new one is appreciated.