Keywords: WordPress + NGINX + SSL - Google Cloud Platform - Technical issue - Other
bndiagnostic ID: aace01b7-becd-dbb3-2d5f-d74b2818a0e7
bndiagnostic output:
? Wordpress: Found possible issues
? Resources: Found possible issues
? Nginx: Found possible issues
? Php: Found possible issues
https://docs.bitnami.com/general/apps/wordpress/administration/understand-file-permissions/
https://docs.bitnami.com/installer/faq/linux-faq/administration/increase-memory-linux/
https://docs.bitnami.com/installer/infrastructure/nginx/troubleshooting/
https://docs.bitnami.com/general/apps/akeneo/administration/increase-memory-limit/
bndiagnostic failure reason: The tool could not find any issue
Description:
WP CMS Nginx SSL refuses to respond with memory errors - case closed without resolution and well under 14 days of last response.
identical case closed without resolution as well - Wordpress keeps crashing due to lack of memory - #9 by jota
I am reopening this case because the prior case has been closed without resolution.
It is a great disservice and highly insensitive to close these cases with assumptions and no resolution and after spending so much time troubleshooting.
For my particular issue I created a case with Google and Bitnami to ensure that all ends are addressed.
By the time I had created this case, I had already upgraded the server to a n1-standard from g1-small and the issue persisted.
Without resolving the root case, adding additional CPUs or memory will not lead to a resolution. This was one of the recommendations forms he other case and very unhelpful at a minimum given all the details and information in the logs.
As with the other users, this is occurring on an instance that has no content, a new instance so the idea that plugins etc are cause this is far fetched - I have rebuilt this twice with the same outcome.
The last response for this case has not been over 14 days and it is being closed. All this does nto sit well. At a minimum, this is feedback that your image is not functional for users so it’s in everyone’s best interest to resolve this without assumptions.
ISSUE:
Periodically, the whole server becomes completely unresponsive. The only solution is to restart the Server as it down not even respond to SSH.
Requesting assistance on how to resolve.
WPCMS Nginx and Maria DB
The WP CMS theme that I am using is Uncode. The them requires the following server requirements which I are configured. https://support.undsgn.com/hc/en-us/articles/213453949
sudo tail -n 20 /opt/bitnami/wordpress/wp-content/debug.log
[12-Apr-2022 03:58:17 UTC] PHP Notice: Undefined property: stdClass::$plugin in /opt/bitnami/wordpress/wp-includes/class-wp-list-util.php on line 167
[12-Apr-2022 03:58:17 UTC] PHP Notice: Undefined property: stdClass::$plugin in /opt/bitnami/wordpress/wp-includes/class-wp-list-util.php on line 167
[12-Apr-2022 03:12:07 UTC] PHP Warning: Cannot modify header information - headers already sent in /bitnami/wordpress/wp-content/plugins/uncode-privacy/includes/class-uncode-toolkit-privacy-public.php on line 342
[1
[12-Apr-2022 00:15:14 UTC] PHP Fatal error: Out of memory (allocated 2097152) (tried to allocate 2377008 bytes) in /opt/bitnami/wordpress/wp-includes/wp-db.php on line 2162
[12-Apr-2022 00:15:14 UTC] PHP Fatal error: Out of memory (allocated 2097152) (tried to allocate 2377008 bytes) in /opt/bitnami/wordpress/wp-includes/wp-db.php on line 2162
[12-Apr-2022 00:16:25 UTC] PHP Warning: Cannot modify header information - headers already sent in /bitnami/wordpress/wp-content/plugins/uncode-privacy/includes/class-uncode-toolkit-privacy-public.php on line 342
[12-Apr-2022 00:16:25 UTC] PHP Warning: Cannot modify header information - headers already sent in /bitnami/wordpress/wp-content/plugins/uncode-privacy/includes/class-uncode-toolkit-privacy-public.php on line 342
[12-Apr-2022 00:16:44 UTC] PHP Warning: Cannot modify header information - headers already sent in /bitnami/wordpress/wp-content/plugins/uncode-privacy/includes/class-uncode-toolkit-privacy-public.php on line 342
[12-Apr-2022
wp-config.php define( ‘WP_MEMORY_LIMIT’, ‘512M’ ); define( ‘WP_DEBUG’, true );
// Enable Debug logging to the /wp-content/debug.log file
define( ‘WP_DEBUG_LOG’, true );
// Disable display of errors and warnings
define( ‘WP_DEBUG_DISPLAY’, false ); Fix: WordPress Memory Exhausted Error – Increase PHP Memory Fix: WordPress Memory Exhausted Error - Increase PHP Memory
Changes to php.ini nano /opt/bitnami/php/etc/php.ini memory_limit 512M max_input_vars 3000 max_execution_time 120 post_max_size 80M upload_max_filesize 124M allow_url_fopen ON asp_tags OFF — Not available in php.ini
I have added debugging and logging of error messages and the shows memory errors Restarted instance sudo /opt/bitnami/ctlscript.sh restart
Reviewed Modify The Memory Limit Modify the memory limit Memory limit is at 512 in all cases
/opt/bitnami/php/etc/memory.conf . Memory.conf is s below. If you recommend a change, I will need to know the exact values too change pm.max_children=60
pm.start_servers=40
pm.min_spare_servers=40
pm.max_spare_servers=45 pm.max_requests=5000 How can I address the errors below
[11-Apr-2022 22:32:11] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 39 idle, and 53 total children
[11-Apr-2022 22:32:12] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 16 children, there are 39 idle, and 54 total children
[11-Apr-2022 22:32:13] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 39 idle, and 55 total children
[11-Apr-2022 22:32:14] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 39 idle, and 56 total children
[11-Apr-2022 22:32:15] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 39 idle, and 57 total children
[11-Apr-2022 22:32:18] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 39 idle, and 58 total children
[11-Apr-2022 22:32:21] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 39 idle, and 59 total children
[11-Apr-2022 22:32:24] WARNING: [pool www] server reached pm.max_children setting (60), consider raising it
[11-Apr-2022 23:16:02] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 39 idle, and 48 total children
[11-Apr-2022 23:16:03] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 16 children, there are 39 idle, and 49 total children
[11-Apr-2022 23:16:04] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 39 idle, and 50 total children
[12-Apr-2022 00:14:35] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 39 idle, and 48 total children
[12-Apr-2022 00:21:50] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 8 children, there are 39 idle, and 53 total children
[12-Apr-2022 00:21:51] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 16 children, there are 39 idle, and 54 total children
[12-Apr-2022 00:21:52] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 39 idle, and 55 total children
[12-Apr-2022 00:21:53] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 39 idle, and 56 total children
[12-Apr-2022 00:21:55] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 39 idle, and 57 total children
[12-Apr-2022 00:21:56] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 39 idle, and 58 total children
[12-Apr-2022 00:21:57] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 39 idle, and 59 total children
[12-Apr-2022 00:21:58] WARNING: [pool www] server reached pm.max_children setting (60), consider raising it
Links reviewed without solution
Modifying PHP php_max_vars - #4 by gongomgra 1 Modifying PHP php_max_vars