Jump to content

Edit History

rhandom

rhandom

@El Patron tried to do a database backup from advanved paramters and got

LEVEL
FATAL ERROR
INFO
Allowed memory size of 536870912 bytes exhausted (tried to allocate 4096 bytes)
FILE
/vol/site/current/classes/db/DbPDO.php
LINE
156

ON 15.08.25, 08:23

Not sure if and where I can upgrade PHP Memory usage beyond 512MB. I checked via shell as root and saw

cat  /etc/php/7.4/cli/php.ini |grep memory_limit
memory_limit = -1

so we seem to be at max but not sure if and now I could get more. Also, why the database dump needed that much. But I do see several very large tables with PHPMyAdmin:



Table	Action	Rows  	Type	Collation	Size  Descending	Overhead
	ps_guest	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~95,110,861	InnoDB	utf8mb3_general_ci	9.3 GiB	-
	ps_connections	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~48,993,675	InnoDB	utf8mb3_general_ci	5.8 GiB	-
	ps_connections_source	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~1,805,698	InnoDB	utf8mb3_general_ci	869.0 MiB	-
	ps_pagenotfound	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~6,594,855	InnoDB	utf8mb3_general_ci	724.6 MiB	-
	ps_search_index	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~7,809,921	InnoDB	utf8mb3_general_ci	566.8 MiB	-
	ps_product_lang	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~225,295	InnoDB	utf8mb3_general_ci	498.6 MiB	-
	ps_storecom_imagefile	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~1,295,805	InnoDB	utf8mb3_general_ci	454.0 MiB	-
	ps_presta_ts_emp_live_feed_update_value	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~6,417,949	InnoDB	utf8mb3_general_ci	444.9 MiB	-
	ps_stripe_official_processlogger	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~188,657	InnoDB	utf8mb4_general_ci	168.6 MiB	-
	ps_presta_ts_employee_live_feed_data	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~716,301	InnoDB	utf8mb3_general_ci	133.7 MiB	-
	ps_statssearch	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~2,100,347	InnoDB	utf8mb3_general_ci	109.6 MiB	-

Some or all of the large ones seems to be statics related. Still learning more about them But perhaps I can remove them somehow unless client has issues with it and we lose nothing vital.

As for general upgrade, I still cannot use it using the Update Module. Prestahop mentioned this

Quote

We have reapplied rights and ensured everything is ok server-side, we haven't found anything that can explain this behavior.
Your problem seems more related to an applicative issue.
Our support do not handle applicative issues, only server/infrastructure issues.
I can route your ticket to the applicative support team "Prestashop Care", do you want to be put in touch with them ?

I however am taking over this project / site and did not change files / directories. Just made a clone of the production site as we need to upgrade . And I still cannot press the button to upgrade  Perhaps I need to upgrade to Prestashop 1.7.8 the manual way by updating the Gitlab repository and testing on development .

Screenshot 2025-08-15 at 08.32.16.png

rhandom

rhandom

@El Patron tried to do a database backup from advanved paramters and got

LEVEL
FATAL ERROR
INFO
Allowed memory size of 536870912 bytes exhausted (tried to allocate 4096 bytes)
FILE
/vol/site/current/classes/db/DbPDO.php
LINE
156

ON 15.08.25, 08:23

Not sure if and where I can upgrade PHP Memory usage beyond 512MB. I checked via shell as root and saw

cat  /etc/php/7.4/cli/php.ini |grep memory_limit
memory_limit = -1

so we seem to be at max but not sure if and now I could get more. Also, why the database dump needed that much. But I do see several very large tables with PHPMyAdmin:



Table	Action	Rows  	Type	Collation	Size  Descending	Overhead
	ps_guest	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~95,110,861	InnoDB	utf8mb3_general_ci	9.3 GiB	-
	ps_connections	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~48,993,675	InnoDB	utf8mb3_general_ci	5.8 GiB	-
	ps_connections_source	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~1,805,698	InnoDB	utf8mb3_general_ci	869.0 MiB	-
	ps_pagenotfound	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~6,594,855	InnoDB	utf8mb3_general_ci	724.6 MiB	-
	ps_search_index	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~7,809,921	InnoDB	utf8mb3_general_ci	566.8 MiB	-
	ps_product_lang	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~225,295	InnoDB	utf8mb3_general_ci	498.6 MiB	-
	ps_storecom_imagefile	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~1,295,805	InnoDB	utf8mb3_general_ci	454.0 MiB	-
	ps_presta_ts_emp_live_feed_update_value	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~6,417,949	InnoDB	utf8mb3_general_ci	444.9 MiB	-
	ps_stripe_official_processlogger	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~188,657	InnoDB	utf8mb4_general_ci	168.6 MiB	-
	ps_presta_ts_employee_live_feed_data	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~716,301	InnoDB	utf8mb3_general_ci	133.7 MiB	-
	ps_statssearch	  	 Browse Browse	 Structure Structure	 Search Search	Insert Insert	 Empty Empty	 Drop Drop	~2,100,347	InnoDB	utf8mb3_general_ci	109.6 MiB	-

As for general upgrade, I still cannot use it using the Update Module. Prestahop mentioned this

Quote

We have reapplied rights and ensured everything is ok server-side, we haven't found anything that can explain this behavior.
Your problem seems more related to an applicative issue.
Our support do not handle applicative issues, only server/infrastructure issues.
I can route your ticket to the applicative support team "Prestashop Care", do you want to be put in touch with them ?

I however am taking over this project / site and did not change files / directories. Just made a clone of the production site as we need to upgrade . And I still cannot press the button to upgrade  Perhaps I need to upgrade to Prestashop 1.7.8 the manual way by updating the Gitlab repository and testing on development .

Screenshot 2025-08-15 at 08.32.16.png

rhandom

rhandom

@El Patron tried to do a database backup from advanved paramters and got

LEVEL
FATAL ERROR
INFO
Allowed memory size of 536870912 bytes exhausted (tried to allocate 4096 bytes)
FILE
/vol/site/current/classes/db/DbPDO.php
LINE
156

ON 15.08.25, 08:23

Not sure if and where I can upgrade PHP Memory usage beyond 512MB. I checked via shell as root and saw

cat  /etc/php/7.4/cli/php.ini |grep memory_limit
memory_limit = -1

so we seem to be at max but not sure if and now I could get more. Also, why the database dump needed that much. But it is 38MB or more I think.

As for general upgrade, I still cannot use it using the Update Module. Prestahop mentioned this

Quote

We have reapplied rights and ensured everything is ok server-side, we haven't found anything that can explain this behavior.
Your problem seems more related to an applicative issue.
Our support do not handle applicative issues, only server/infrastructure issues.
I can route your ticket to the applicative support team "Prestashop Care", do you want to be put in touch with them ?

I however am taking over this project / site and did not change files / directories. Just made a clone of the production site as we need to upgrade . And I still cannot press the button to upgrade  Perhaps I need to upgrade to Prestashop 1.7.8 the manual way by updating the Gitlab repository and testing on development .

Screenshot 2025-08-15 at 08.32.16.png

×
×
  • Create New...