• Resolved Jaime Matos

    (@jimykx)


    I cloned my website to a different server in order to create a staging/test copy of the website.
    Everything seems to be right aside that Post SMTP always started to make the following errors,
    This one when completing a Woocommerce order:
    “An internal server error occurred. Please contact site administrator. (500)”

    [26-Apr-2022 11:02:53 UTC] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 5165008 bytes) in /home/runcloud/webapps/Evolt-clone/wp-includes/wp-db.php on line 2162
    [26-Apr-2022 11:02:53 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT autoload FROM wp_options WHERE option_name = '_transient_wc_layered_nav_counts_pa_diametro-do-nozzle' feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Cache_Helper::delete_transients_on_shutdown, delete_transient, delete_option
    [26-Apr-2022 11:02:53 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT autoload FROM wp_options WHERE option_name = '_transient_wc_layered_nav_counts_pa_material' feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Cache_Helper::delete_transients_on_shutdown, delete_transient, delete_option
    [26-Apr-2022 11:02:53 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT autoload FROM wp_options WHERE option_name = '_transient_wc_layered_nav_counts_pa_modelo-do-nozzle' feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Cache_Helper::delete_transients_on_shutdown, delete_transient, delete_option
    [26-Apr-2022 11:02:53 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT autoload FROM wp_options WHERE option_name = '_transient_wc_layered_nav_counts_pa_marca' feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Cache_Helper::delete_transients_on_shutdown, delete_transient, delete_option
    [26-Apr-2022 11:02:53 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT autoload FROM wp_options WHERE option_name = '_transient_wc_layered_nav_counts_pa_caracteristicas' feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Cache_Helper::delete_transients_on_shutdown, delete_transient, delete_option
    [26-Apr-2022 11:02:53 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT autoload FROM wp_options WHERE option_name = '_transient_wc_layered_nav_counts_pa_fornecedor' feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Cache_Helper::delete_transients_on_shutdown, delete_transient, delete_option
    [26-Apr-2022 11:02:53 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT autoload FROM wp_options WHERE option_name = '_transient_wc_layered_nav_counts_pa_diametro-do-filamento-3d' feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Cache_Helper::delete_transients_on_shutdown, delete_transient, delete_option
    [26-Apr-2022 11:02:53 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT autoload FROM wp_options WHERE option_name = '_transient_wc_layered_nav_counts_pa_cor' feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Cache_Helper::delete_transients_on_shutdown, delete_transient, delete_option
    [26-Apr-2022 11:02:53 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT autoload FROM wp_options WHERE option_name = '_transient_wc_layered_nav_counts_pa_peso' feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Cache_Helper::delete_transients_on_shutdown, delete_transient, delete_option
    [26-Apr-2022 11:02:53 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SHOW FULL COLUMNS FROM <code>wp_woocommerce_sessions</code> feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Session_Handler->save_data
    [26-Apr-2022 11:02:53 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SHOW FULL COLUMNS FROM <code>wp_woocommerce_sessions</code> feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, WC_Session_Handler->save_data, WC_Session_Handler->delete_session
    [26-Apr-2022 11:03:18 UTC] PHP Warning:  file_exists(): open_basedir restriction in effect. File(/home/runcloud/webapps/Evolt-clone/wp-content/db.php) is not within the allowed path(s): (/home/runcloud/webapps/Evolt-clone:/var/lib/php/session:/tmp) in /home/runcloud/webapps/Evolt-clone/wp-includes/load.php on line 548

    It also makes the following error now when visiting the Email Log page:

    [26-Apr-2022 11:06:31 UTC] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 5165008 bytes) in /home/runcloud/webapps/Evolt-clone/wp-includes/wp-db.php on line 2162
    [26-Apr-2022 11:06:31 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT option_value FROM wp_options WHERE option_name = 'acp_periodic_license_check' LIMIT 1 feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, ACP\Controller\License->handle_daily_update_subscription_details, AC\Storage\Timestamp->is_expired, AC\Storage\Timestamp->get, AC\Storage\Option->get, get_option
    [26-Apr-2022 11:06:31 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT autoload FROM wp_options WHERE option_name = 'acp_subscription_details' feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, ACP\Controller\License->handle_daily_update_subscription_details, ACP\Controller\License->update_subscription_details, ACP\LicenseRepository->delete, ACP\LicenseRepository->delete_option, delete_option
    [26-Apr-2022 11:06:31 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT autoload FROM wp_options WHERE option_name = 'acp_subscription_details_key' feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, ACP\Controller\License->handle_daily_update_subscription_details, ACP\Controller\License->update_subscription_details, ACP\LicenseRepository->delete, ACP\LicenseRepository->delete_option, delete_option
    [26-Apr-2022 11:06:31 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query INSERT INTO <code>wp_options</code> (<code>option_name</code>, <code>option_value</code>, <code>autoload</code>) VALUES ('acp_periodic_license_check', '1651057591', 'no') ON DUPLICATE KEY UPDATE <code>option_name</code> = VALUES(<code>option_name</code>), <code>option_value</code> = VALUES(<code>option_value</code>), <code>autoload</code> = VALUES(<code>autoload</code>) feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, ACP\Controller\License->handle_daily_update_subscription_details, AC\Storage\Timestamp->save, AC\Storage\Option->save, update_option, add_option
    [26-Apr-2022 11:06:31 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SHOW FULL COLUMNS FROM <code>wp_options</code> feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->maybe_dispatch_async_request, ActionScheduler_OptionLock->set, update_option
    [26-Apr-2022 11:06:31 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT COUNT(DISTINCT claim_id) FROM wp_actionscheduler_actions WHERE claim_id != 0 AND status IN ( 'pending', 'in-progress') feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->maybe_dispatch_async_request, ActionScheduler_AsyncRequest_QueueRunner->maybe_dispatch, ActionScheduler_AsyncRequest_QueueRunner->allow, ActionScheduler_Abstract_QueueRunner->has_maximum_concurrent_batches, ActionScheduler_DBStore->get_claim_count
    [26-Apr-2022 11:06:31 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT a.action_id FROM wp_actionscheduler_actions a WHERE 1=1 AND a.status IN ('pending') AND a.scheduled_date_gmt <= '2022-04-26 11:06:31' LIMIT 0, 5 feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->maybe_dispatch_async_request, ActionScheduler_AsyncRequest_QueueRunner->maybe_dispatch, ActionScheduler_AsyncRequest_QueueRunner->allow, ActionScheduler_Store->has_pending_actions_due, ActionScheduler_DBStore->query_actions

    I am not sure why did this start happening and what can I do in order to start fixing these errors, so some advice would be great!!

    I have already ran a WordPress database optimization but nothing changed.
    Even though these errors are generated and the order is not placed, emails strangely seem to be going through.
    If I Disable Post SMTP plugin, no errors happen and the order is processed, except then I do not send emails.

    Thank you in advance for the attention and advice!

    Here is a Diagnostic Test:

    Mailer: phpmailer
    HostName: stagingxlg2.evolt.pt
    cURL Version: 7.68.0
    OpenSSL Version: OpenSSL/1.1.1f
    OS: Linux v2202204173222186433 5.4.0-107-generic #121-Ubuntu SMP Thu Mar 24 16:04:27 UTC 2022 x86_64
    PHP: Linux 7.4.29 C
    PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=No, zlib_encode=Yes
    WordPress: 5.9.3 pt_PT UTF-8
    WordPress Theme: Twenty Sixteen
    WordPress Plugins: Admin Columns Pro - Advanced Custom Fields (ACF), Admin Columns Pro - WooCommerce, Admin Columns Pro, Admin Menu Editor Pro, Advanced Custom Fields PRO, Advanced Database Cleaner PRO, Advanced Dynamic Pricing for WooCommerce (Pro), FiboSearch - AJAX Search for WooCommerce (Pro), Akismet Anti-Spam, All-in-One WP Migration, Better Search Replace, CheckoutWC, Cron Logger, Cookie and Consent Solution for the GDPR & ePrivacy, My Custom Functionality, Oxygen Elements for WooCommerce, Oxygen, Post SMTP, WooCommerce Advanced Shipping, Advanced Order Export For WooCommerce (Pro), WooCommerce, WP-Optimize - Clean, Compress, Cache
    WordPress wp_mail Owner: /home/runcloud/webapps/Evolt-clone/wp-includes/pluggable.php
    WordPress wp_mail Filter(s): PostsmtpMailer->get_mail_args
    WordPress phpmailer_init Action(s): PostsmtpMailer->phpmailer_smtp_init
    Postman: 2.0.26
    Postman Sender Domain (Envelope|Message): evolt.pt | evolt.pt
    Postman Prevent Message Sender Override (Email|Name): No | No
    Postman Active Transport: SMTP (smtp:tls:plain://echo.mxrouting.net:587)
    Postman Active Transport Status (Ready|Connected): Yes | No
    Postman Deliveries (Success|Fail): 7768 | 13
    Postman Email Log (Enabled|Limit|Transcript Size): Yes | 1000 | 128
Viewing 15 replies - 1 through 15 (of 20 total)
  • Plugin Support M Haseeb

    (@haseeb0001)

    Hi @jimykx ,

    Hope you are doing good.

    In regards to the error that you are receiving ‘Fatal error: The Allowed memory size of 536870912 bytes exhausted’ this error is caused by the PHP memory being set too low, and needing to be increased on your hosting account. This setting is typically controlled by editing the wp-config.php or php.ini file and increasing the allocated memory.

    If you aren’t sure how to change this setting, we would recommend contacting your hosting provider for additional assistance.

    After increasing the memory if you still face this issue, then share the use case of this issue, I will test it on my staging websites.

    Thanks

    Thread Starter Jaime Matos

    (@jimykx)

    Thank you for the answer M Haseeb, I appreciate it.
    This staging website has set the same memory limit 512MB ( those 536870912 bytes ) as my live production website. I believe this should be more than enough memory, especially considering how the live website has the exact same memory setting, on top of that has all plugins enabled (I disabled all plugins in Staging aside from Post SMTP ) and does not have this issue.

    The error message is also “Allowed memory size of 536870912 bytes exhausted (tried to allocate 5165008 bytes)”
    This is also a strange error message because If it tried to allocate just 5165008 bytes, then that’s far smaller than the available memory size of 536870912 bytes.

    If you wish I can send you full access to this staging website and you are free to do as you need with it!

    Thank you once again in advance for the attention and advice.

    Plugin Support M Haseeb

    (@haseeb0001)

    @jimykx ok, can you share the plugin names you are using ? specially using with woocommerce or WooCommrece addon? then I will reduce this on my staging website and share updates with you.

    Thread Starter Jaime Matos

    (@jimykx)

    I have currently only the absolute essential plugins for the basic functioning of the website which are:
    – Advanced Custom Fields
    – Oxygen builder
    – Woocommerce
    – Post SMPT

    Only enabling/disabling Post SMTP seems to affect this issue

    My main website with these plugins (and plenty more) works fully well with Post SMTP, it was only after creating a copy of it on another server, I tried to both clone the website and use All in One WP Migration but the result in this error on the copied website is the same.

    Thread Starter Jaime Matos

    (@jimykx)

    Also, how to fully Uninstall Post SMTP plugin?
    I tried to re-instal but when I do it seems that settings are already saved.
    How to delete the plugin and fully delete all plugin data, including leftover database entries?

    I wanted to try this because maybe a fresh installation of the plugin could fix the problem.

    Thread Starter Jaime Matos

    (@jimykx)

    On a different copy/staging site I created, although on the same server (instead of on a different server) I still get an error 500 when completing orders, but I receive this error instead:

    [27-Apr-2022 11:10:43 UTC] PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 5443592 bytes) in /home/runcloud/webapps/Evolt-airIwSDx-staging/wp-includes/wp-db.php on line 2162
    [27-Apr-2022 11:10:43 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT p.ID FROM wp_posts p INNER JOIN wp_term_relationships tr ON tr.object_id=p.ID INNER JOIN wp_term_taxonomy tt ON tr.term_taxonomy_id=tt.term_taxonomy_id INNER JOIN wp_terms t ON tt.term_id=t.term_id AND t.slug='woocommerce-webhooks' WHERE post_type='scheduled-action' AND p.post_title='woocommerce_deliver_webhook_async' AND p.post_content='{\"webhook_id\":84,\"arg\":49498}' AND p.post_status IN ('in-progress') ORDER BY p.post_date_gmt ASC LIMIT 0, 1 feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, wc_webhook_execute_queue, WC_Action_Queue->get_next, as_next_scheduled_action, ActionScheduler_Store->query_action, ActionScheduler_HybridStore->query_actions, ActionScheduler_wpPostStore->query_actions
    [27-Apr-2022 11:10:43 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT a.action_id FROM wp_actionscheduler_actions a LEFT JOIN wp_actionscheduler_groups g ON g.group_id=a.group_id WHERE 1=1 AND g.slug='woocommerce-webhooks' AND a.hook='woocommerce_deliver_webhook_async' AND a.args='{\"webhook_id\":84,\"arg\":49498}' AND a.status IN ('in-progress') ORDER BY a.scheduled_date_gmt ASC LIMIT 0, 1 feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, wc_webhook_execute_queue, WC_Action_Queue->get_next, as_next_scheduled_action, ActionScheduler_Store->query_action, ActionScheduler_HybridStore->query_actions, ActionScheduler_DBStore->query_actions
    [27-Apr-2022 11:10:43 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT p.ID FROM wp_posts p INNER JOIN wp_term_relationships tr ON tr.object_id=p.ID INNER JOIN wp_term_taxonomy tt ON tr.term_taxonomy_id=tt.term_taxonomy_id INNER JOIN wp_terms t ON tt.term_id=t.term_id AND t.slug='woocommerce-webhooks' WHERE post_type='scheduled-action' AND p.post_title='woocommerce_deliver_webhook_async' AND p.post_content='{\"webhook_id\":84,\"arg\":49498}' AND p.post_status IN ('pending') ORDER BY p.post_date_gmt ASC LIMIT 0, 1 feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, wc_webhook_execute_queue, WC_Action_Queue->get_next, as_next_scheduled_action, ActionScheduler_Store->query_action, ActionScheduler_HybridStore->query_actions, ActionScheduler_wpPostStore->query_actions
    [27-Apr-2022 11:10:43 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT a.action_id FROM wp_actionscheduler_actions a LEFT JOIN wp_actionscheduler_groups g ON g.group_id=a.group_id WHERE 1=1 AND g.slug='woocommerce-webhooks' AND a.hook='woocommerce_deliver_webhook_async' AND a.args='{\"webhook_id\":84,\"arg\":49498}' AND a.status IN ('pending') ORDER BY a.scheduled_date_gmt ASC LIMIT 0, 1 feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, wc_webhook_execute_queue, WC_Action_Queue->get_next, as_next_scheduled_action, ActionScheduler_Store->query_action, ActionScheduler_HybridStore->query_actions, ActionScheduler_DBStore->query_actions
    [27-Apr-2022 11:10:43 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SELECT group_id FROM wp_actionscheduler_groups WHERE slug='woocommerce-webhooks' feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, wc_webhook_execute_queue, WC_Action_Queue->add, WC_Action_Queue->schedule_single, as_schedule_single_action, ActionScheduler_ActionFactory->single, ActionScheduler_ActionFactory->store, ActionScheduler_HybridStore->save_action, ActionScheduler_DBStoreMigrator->save_action, ActionScheduler_DBStore->save_action, ActionScheduler_DBStore->get_group_id
    [27-Apr-2022 11:10:43 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query SHOW FULL COLUMNS FROM <code>wp_actionscheduler_groups</code> feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, wc_webhook_execute_queue, WC_Action_Queue->add, WC_Action_Queue->schedule_single, as_schedule_single_action, ActionScheduler_ActionFactory->single, ActionScheduler_ActionFactory->store, ActionScheduler_HybridStore->save_action, ActionScheduler_DBStoreMigrator->save_action, ActionScheduler_DBStore->save_action, ActionScheduler_DBStore->get_group_id, ActionScheduler_DBStore->create_group
    [27-Apr-2022 11:10:43 UTC] Erro na base de dados do WordPress Commands out of sync; you can't run this command now na query INSERT INTO <code>wp_actionscheduler_actions</code> (<code>hook</code>, <code>status</code>, <code>scheduled_date_gmt</code>, <code>scheduled_date_local</code>, <code>schedule</code>, <code>group_id</code>, <code>args</code>) VALUES ('woocommerce_deliver_webhook_async', 'pending', '2022-04-27 11:10:43', '2022-04-27 12:10:43', 'O:30:\"ActionScheduler_SimpleSchedule\":2:{s:22:\"\0*\0scheduled_timestamp\";i:1651057843;s:41:\"\0ActionScheduler_SimpleSchedule\0timestamp\";i:1651057843;}', '0', '{\"webhook_id\":84,\"arg\":49498}') feita por shutdown_action_hook, do_action('shutdown'), WP_Hook->do_action, WP_Hook->apply_filters, wc_webhook_execute_queue, WC_Action_Queue->add, WC_Action_Queue->schedule_single, as_schedule_single_action, ActionScheduler_ActionFactory->single, ActionScheduler_ActionFactory->store, ActionScheduler_HybridStore->save_action, ActionScheduler_DBStoreMigrator->save_action, ActionScheduler_DBStore->save_action
    [27-Apr-2022 11:10:43 UTC] PHP Fatal error:  Uncaught RuntimeException: Erro ao guardar a acção: Erro ao guardar a acção: Commands out of sync; you can't run this command now in /home/runcloud/webapps/Evolt-airIwSDx-staging/wp-content/plugins/woocommerce/packages/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php:44
    Stack trace:
    #0 /home/runcloud/webapps/Evolt-airIwSDx-staging/wp-content/plugins/woocommerce/packages/action-scheduler/classes/data-stores/ActionScheduler_HybridStore.php(242): ActionScheduler_DBStoreMigrator->save_action()
    #1 /home/runcloud/webapps/Evolt-airIwSDx-staging/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_ActionFactory.php(177): ActionScheduler_HybridStore->save_action()
    #2 /home/runcloud/webapps/Evolt-airIwSDx-staging/wp-content/plugins/woocommerce/packages/action-scheduler/classes/ActionScheduler_ActionFactory.php(84): ActionScheduler_ActionFactory->store()
    #3 /home/runcloud/webapps/Evolt-airIwSDx-staging/wp-content/plugins/woocommerce/packages/action-scheduler/function in /home/runcloud/webapps/Evolt-airIwSDx-staging/wp-content/plugins/woocommerce/packages/action-scheduler/classes/migration/ActionScheduler_DBStoreMigrator.php on line 44
    Plugin Support M Haseeb

    (@haseeb0001)

    @jimykx Thanks for sharing details, let me talk to my team, will get back to you shortly

    Thread Starter Jaime Matos

    (@jimykx)

    @haseeb0001 Thank you, once again if you would like to have direct access to my staging servers and be able to look at the issue directly I have no problem giving you this access.

    Plugin Support M Haseeb

    (@haseeb0001)

    Hi @jimykx

    We are not allowed to ask for site access on this platform, we are trying to reproduce this issue on our staging websites, will get back to you soon.

    thanks

    Thread Starter Jaime Matos

    (@jimykx)

    @haseeb0001 I have also noticed on this moved installation I receive an exception amount of these open_basedir errors, which do not show up on the main site:

    [02-May-2022 13:05:44 UTC] PHP Warning:  file_exists(): open_basedir restriction in effect. File(/home/runcloud/webapps/Evolt-clone/wp-content/db.php) is not within the allowed path(s): (/home/runcloud/webapps/Evolt-clone:/var/lib/php/session:/tmp) in /home/runcloud/webapps/Evolt-clone/wp-includes/load.php on line 548
    [02-May-2022 13:05:44 UTC] PHP Warning:  file_exists(): open_basedir restriction in effect. File(/block-templates/index.html) is not within the allowed path(s): (/home/runcloud/webapps/Evolt-clone:/var/lib/php/session:/tmp) in /home/runcloud/webapps/Evolt-clone/wp-includes/class-wp-theme.php on line 1512
    [02-May-2022 13:05:44 UTC] PHP Warning:  file_exists(): open_basedir restriction in effect. File(/templates/index.html) is not within the allowed path(s): (/home/runcloud/webapps/Evolt-clone:/var/lib/php/session:/tmp) in /home/runcloud/webapps/Evolt-clone/wp-includes/class-wp-theme.php on line 1512
    [02-May-2022 13:05:44 UTC] PHP Warning:  file_exists(): open_basedir restriction in effect. File(/block-templates/index.html) is not within the allowed path(s): (/home/runcloud/webapps/Evolt-clone:/var/lib/php/session:/tmp) in /home/runcloud/webapps/Evolt-clone/wp-includes/class-wp-theme.php on line 1512
    [02-May-2022 13:05:44 UTC] PHP Warning:  file_exists(): open_basedir restriction in effect. File(/templates/index.html) is not within the allowed path(s): (/home/runcloud/webapps/Evolt-clone:/var/lib/php/session:/tmp) in /home/runcloud/webapps/Evolt-clone/wp-includes/class-wp-theme.php on line 1512
    Plugin Support M Haseeb

    (@haseeb0001)

    @jimykx thanks, i have share it with my team, will get back to you shortly.

    Thread Starter Jaime Matos

    (@jimykx)

    @haseeb0001 I believe I have further progressed on this issue,
    This seems to be a Time-out issue of connecting to the SMTP server, however there are no indicative/appropriate errors printed out from POST SMTP pointing to this directly.

    Running a Telnet on the original server (which has no issues) connects immediately to the SMTP server, however on this new server it takes some 3-5 minutes to connect to Telnet, it never times out but on WordPress it seems to be reflected as a memory size exeeded

    https://serverfault.com/questions/725962/how-to-investigate-causes-for-a-very-slow-telnet

    Plugin Support M Haseeb

    (@haseeb0001)

    @jimykx

    Can you disable the Admin Table Pro plugin and then test It ? or try to disable other plugins one by one and let me know which plugin is conflicting?

    Thread Starter Jaime Matos

    (@jimykx)

    @haseeb0001 While that plugin might have been enabled recently due to me making other tests on the website in the meanwhile, I can guarantee this plugin has been disabled during all my reported testings 🙂

    In fact I have tested it with only these plugins enabled:

    – Oxygen builder
    – Woocommerce
    – Post SMPT

    Thread Starter Jaime Matos

    (@jimykx)

    I have managed to work out through all the other errors which apparently are unrelated
    at this point I have just plain cloned the website with all plugins disabled and only

    – Woocommerce
    – Post SMPT

    plugins running, and the only errors I keep getting at this point, when finishing an order, or running the test email are the memory exhausted errors.
    Which as I said before are really weird because everything is working well on my normal /main site

    [10-May-2022 07:15:03 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 4944640 bytes) in /home/runcloud/webapps/Evolt-clone/wp-includes/wp-db.php on line 2162
    [10-May-2022 07:15:11 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 4944640 bytes) in /home/runcloud/webapps/Evolt-clone/wp-includes/wp-db.php on line 2162

Viewing 15 replies - 1 through 15 (of 20 total)
  • The topic ‘Error 500 when placing Woocommerce orders after Cloning website’ is closed to new replies.