Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter clip1492

    (@clip1492)

    I’ve enabled WP_DEBUG and the 503 doesn’t returns any error debug.log. I already checked this, and i would be more than happy if the system returns a clue about what is happening. Also no errors stated on redis.log.

    To recover the site, deleting object-cache-php is not enough, nor restarting redis service from terminal, but I must restart Apache and then things get back to normal.

    • This reply was modified 1 month ago by clip1492.
    • This reply was modified 1 month ago by clip1492.
    • This reply was modified 1 month ago by clip1492.
    Thread Starter clip1492

    (@clip1492)

    Today I discovered that the unsolicited install of WPforms even bloated the WP database with 4 tables on my production site, which have not been removed after uninstalling WPforms:

    _wpforms_payment
    _wpforms_payment_meta
    _wpforms_tasks
    _wpforms_tasks_meta

    Maybe this is useful for other folks who had the same issue and like to have their database tidy. I hope this chapter ends here.

    • This reply was modified 1 month ago by clip1492.
    • This reply was modified 1 month ago by clip1492.
    • This reply was modified 1 month ago by clip1492.
    Thread Starter clip1492

    (@clip1492)

    As Total Server Memory is 16GB, Swap: 4Gb, Free: 2.6 Gb , Buffer/Cache: 7Gb (this can be liberated)

    Then I’ve edited redis.config with:

    maxmemory 1024mb
    maxmemory-policy allkeys-lru

    then sudo systemctl restart redis which shows status active.

    Issued: redis-cli FLUSHALL again, just in case.
    Updated the plugin to the latest version released hours ago.

    Website works well, plugin shows: Status: Not enabled Filesystem: Writeable Redis: Reachable

    Clicking on “Enable Object Cache” issues again “Service Unavailable – 503” on all website pages (Admin and frontend).

    Deleting the object-cache.php on wp-contents this time doesn’t removes the 503, so I reboot the server, and everything goes back to normal, but without object cache.

    While wp error.log doens’t whows errors at the time of the 503, logs on redis.log show this:





    26313:M 16 Oct 2024 13:23:09.643 * DB loaded from disk: 0.002 seconds

    26313:M 16 Oct 2024 13:23:09.643 * Ready to accept connections tcp

    26313:M 16 Oct 2024 13:23:09.643 * Ready to accept connections unix

    26313:M 16 Oct 2024 13:24:26.072 * DB saved on disk

    26313:signal-handler (1729078073) Received SIGTERM scheduling shutdown...

    26313:M 16 Oct 2024 13:27:53.601 * User requested shutdown...

    26313:M 16 Oct 2024 13:27:53.601 * Saving the final RDB snapshot before exiting.

    26313:M 16 Oct 2024 13:27:55.104 * DB saved on disk

    26313:M 16 Oct 2024 13:27:55.104 * Removing the pid file.

    26313:M 16 Oct 2024 13:27:55.104 * Removing the unix socket file.

    26313:M 16 Oct 2024 13:27:55.104 # Redis is now ready to exit, bye bye...

    1333:C 16 Oct 2024 13:28:56.280 * Supervised by systemd. Please make sure you set appropriate values for TimeoutStartSec and TimeoutStopSec in your service unit.

    1333:C 16 Oct 2024 13:28:56.281 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo

    1333:C 16 Oct 2024 13:28:56.281 * Redis version=7.2.5, bits=64, commit=00000000, modified=0, pid=1333, just started

    1333:C 16 Oct 2024 13:28:56.281 * Configuration loaded

    1333:M 16 Oct 2024 13:28:56.282 * monotonic clock: POSIX clock_gettime

    1333:M 16 Oct 2024 13:28:56.283 # Failed to write PID file: Permission denied

    1333:M 16 Oct 2024 13:28:56.283 * Running mode=standalone, port=6379.

    1333:M 16 Oct 2024 13:28:56.284 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.

    1333:M 16 Oct 2024 13:28:56.284 * Server initialized

    1333:M 16 Oct 2024 13:28:56.285 * Loading RDB produced by version 7.2.5

    1333:M 16 Oct 2024 13:28:56.285 * RDB age 63 seconds

    1333:M 16 Oct 2024 13:28:56.285 * RDB memory usage when created 1.43 Mb

    1333:M 16 Oct 2024 13:28:56.288 * Done loading RDB, keys loaded: 2, keys expired: 0.

    1333:M 16 Oct 2024 13:28:56.288 * DB loaded from disk: 0.004 seconds

    1333:M 16 Oct 2024 13:28:56.289 * Ready to accept connections tcp

    1333:M 16 Oct 2024 13:28:56.289 * Ready to accept connections unix

    Any clue about how to solve it? Much appreciated in advance.

    • This reply was modified 1 month, 1 week ago by clip1492.
    • This reply was modified 1 month, 1 week ago by clip1492.
    Thread Starter clip1492

    (@clip1492)

    Forgot to mention also the diagnostics on Redis plugin:

    Status: Not enabled
    Filesystem: Writeable
    Redis: Reachable

    Status: Not enabled Client: Drop-in: Not installed Disabled: No PhpRedis: Not loaded Relay: Not loaded Predis: 2.1.2 Credis: Not loaded PHP Version: 8.3.12 Plugin Version: 2.5.3 Redis Version: Unknown Multisite: No Metrics: Disabled Metrics recorded: 0 Filesystem: Writable WP_REDIS_PLUGIN_PATH: “/home/smokings/public_html/wp-content/plugins/redis-cache” Drop-ins: []

    I’m experiencing the same issue on woocommerce product pages. When opening the theme customizer, the page keeps flashing while reloading in a loop .

    I’m using Astra theme and Beaver Builder as theme editor. I doens’t happens on shop page or other pages, I only replicated the issue at the product page.

    I deactivated all plugins until found the source of the issue was Query Monitor.

    It would be great a fix, if you can replicate the error.

    • This reply was modified 1 year, 9 months ago by clip1492.

    Same question here.

    Odd that you didn’t got an answer since you asked the question 5 months ago.

Viewing 6 replies - 1 through 6 (of 6 total)