|
Ciao, ho atteso un pò a rispondere perchè mi sono interfacciato con l'hosting corrente con il fine di risolvere il problema, ma per ora nulla di fatto.
Premessa: in questo hosting (Pressable) non è possibile aumentare la memoria oltre a 512MB, questa la loro risposta:
....
"In the Pressable environment, auto-scaling is used. This means that memory is allocated per worker thread, and each worker thread is allocated a maximum of 512Mb. The site can scale to a maximum of 110 threads, each with 512Mb, meaning that in practice, the equivalent static server would be running something over 55Gb of RAM.
That's the theoretical math, but you can see from this that the limit is far more than a site should naturally be using, and if the site is running out of memory, there have to be other factors at play.
Pressable can see that certain options on the site are using considerable resource. They can also see that the site was recently upgraded to PHP 8.3, and have suggested switching that back if you feel that this has triggered more errors."
....
A questo punto abbiamo portato la versione alla 8.1, ma ovviamente non è cambiato nulla.
Abbiamo ricontattato l'assistenza del server e ci dicono:
....
One thing to note: WPML is currently preventing the caching system from running. This is putting extreme pressure on the servers, as all pages are delivered dynamically, rather than leveraging cache.
There is also an issue in your theme functions.php file which is causing issues: it appears that, on some occasions, the contstant ICL_LANGUAGE_CODE is called but is not defined.
We recommend wrapping this code block in a try{}catch(Exception $ex){} block to defend against these fatal errors, or adding other defensive code to prevent this from causing a crash should the constant not be defined.
....
Ho corretto il codice come da loro indicazione e il warning è sparito. Ma l'errore sulla memoria rimane.
Detto ciò mi dicono:
....
This prevents Batcache from setting the WPML cookies as skip cookies (by default, Batcache will exclude from memcached any cookie starting with wp).
It also sets the memcached caching period to 1800 seconds (30 minutes) and ensures that the page is cached on the first visit.
//Batcache Customizations
global $batcache;
//Check if batcache params are in an object or an array, apply customizations accordingly
if ( is_object( $batcache ) ) {
$batcache->max_age = 1800; // Seconds the cached render of a page will be stored
$batcache->seconds = 0; // Time number of visitors required to cache, 0 = instant
$batcache->times = 1; // Number of visitors required to cache
$batcache->noskip_cookies = array( 'wordpress_test_cookie','wp-wpml_current_language','wpml_browser_redirect_test' ); // Cookies that prevent caching
} elseif ( is_array( $batcache ) ) {
$batcache['max_age'] = 1800; // Seconds the cached render of a page will be stored
$batcache['seconds'] = 0; // Time number of visitors required to cache, 0 = instant
$batcache['times'] = 1; // Number of visitors required to cache
$batcache['noskip_cookies'] = array( 'wordpress_test_cookie','wp-wpml_current_language','wpml_browser_redirect_test' ); // Cookies that prevent caching
}
// End Batcache Customizations
This appears to be working well on staging but I have not tested extensively. Could you take a look at this for me, test, and decide?
Then: on the live server we see Nitropack using setcookie to handle the currency cookies. On staging, Nitropack is not enabled, and caching, with the changes above, is working well. However, the way Nitropack is handling these cookies is preventing the advanced-cache.php from working correctly.
Memcached is an in-memory caching system that allows your site to store cached pages in server RAM. It also interacts with the Pressable edge caching system. However, Nitropack is using setcookie on every request, which is preventing the caching from taking place.
....
Replico sul sito live e non risolve e mi dicono nuovamente:
....
Regarding the Out of Memory (OOM) errors, when I checked the site it appeared that you had not disabled the autoloading options as suggested by my colleague. I went ahead and created an on demand backup of your database and then turned off autoload for the following options:
all siteground_* options
duplicator_pro_package_active
ws_menu_editor_pro
otgs-installer
rank-math*
wp_rocket_settings
br_ce_options
9d05698bc2c834e9623f132819ab2830
reVAndESTOehiLdOwdr_user_roles
Since disabling those I have not been able to replicate additional OOM errors. Can you please check the site and see if this is also the case for you? If you do experience one of these errors, please share exactly what you were doing on the site when it occurred so that we can more easily try to replicate the case.
....
Non risolve e come ultima loro risposta ho questo:
Thank you for sharing that video. I was able to duplicate this but not consistently.
Digging a bit more on the site, the only other thing I was able to turn up is a request that appears to be tied to WPML authentication:
|Toggle|2.684,3 ms|385.3 ms|POST|link nascosto 38&website_uuid=36363531-6636-5532-b634-313236336363&ui_language_code= it&site_key=OQUsTQZi2c&signature=qBkq80QKbBQBf79dQpS3nm6zdHA%3D|426|
Associated with that request I see the following which seems to indicate that WPML still has the wrong URL set:
"status":426,"title":"Api error non-matching site finger print","fingerprint_confirmed":true,"stored_fingerprint":{"wp_url":"https ://difiaba.presentazionesitoweb.com"},"identical_url_before_movement":false,"site_moved":false,"received_fingerprint":"{\"wp_url\":\"https:\\/\\/difiaba.it\" }"}],"cw_request_id":"9a08a13bd21c487d8e95e7096bf56954"}
I'm also seeing a notice in the WPML status logs that indicates the same but there appears to be no way to update this via the UI.
2024/09/04 10:45:25 PM
ATE Server Communication
WPML has detected a change in your site's URL. To continue translating your site, go to your WordPress Dashboard and tell WPML if your site has been moved or copied.
0 0 {"url":"https:\/\/ate.wpml.org\/api\/wpml\/languages\/check_pairs","requestArgs":{"method":"POST","body":[{"source_language":"it","target_languages":["en","fr","es"]}]},"status":426}
Can you please check with WPML what the recommended next steps might be here? I beleive you may need to delete the otgs_wpml_tm_ate_cloned_site_lock option but since this is not a plugin made by us I'm not sure.
Il link del video è questo che mostro cosa succede: link nascosto
Potete aiutarmi a risolvere? Perchè se tutto è legato alla memoria allora non lo risolveremo mai se non viene aumentata.
Grazie
|
