Forum Replies Created

Viewing 15 replies - 106 through 120 (of 336 total)
  • Plugin Contributor CodeBard

    (@codebard)

    You didnt see a warning that comes out if your site is using api v1, saying that it would cause errors then? It appears during post sync setup and also in post sync section in options page.

    https://www.patreondevelopers.com/t/how-to-upgrade-your-patreon-wordpress-to-use-api-v2/3249

    In any case, the above tutorial will help you upgrade to v2 to fix the error and start using post sync.

    Plugin Contributor CodeBard

    (@codebard)

    Please note support is provided for this plugin at its official forum:

    https://www.patreondevelopers.com/c/patreon-wordpress-plugin-support/11

    The plugin uses Patreon avatar if no avatar is present. We are aware of the gravatar situation and this will be looked into in the next few weeks.

    Plugin Contributor CodeBard

    (@codebard)

    Our pleasure. Sorry for the discomfort.

    Plugin Contributor CodeBard

    (@codebard)

    This was already resolved Sascha – you can just delete the existing plugin and reinstall 1.5.6 and it should work.

    Plugin Contributor CodeBard

    (@codebard)

    Sorry for the discomfort. Yes, it was fixed post haste.

    Thread Starter CodeBard

    (@codebard)

    Chasing that particular error message did not avail, neither playing with the cluster configuration.

    Instead, i moved to using redis + sentinel, configured it without password (accessible only in-cluster) and configured the plugin to use sentinel port and read only port for servers.

    Now it works and properly stores keys in db. The config i used:

    define( 'WP_REDIS_CLIENT', 'predis' );
    define( 'WP_REDIS_SENTINEL', 'mymaster' );
    define( 'WP_REDIS_SERVERS', [
        'tcp://redis-headless:26379',
        'tcp://redis-headless:6379',
    ] );
    
    define( 'WP_CACHE', true );
    // define( 'WP_REDIS_CLIENT', 'pecl' );
    // define( 'WP_REDIS_PASSWORD', 'SOMEPASSWORDHERE' );
    define( 'WP_REDIS_DATABASE', '0' );
    define( 'WP_CACHE_KEY_SALT', 'SOMEKEYHERE' );
    define( 'WP_REDIS_SELECTIVE_FLUSH', true );

    This uses Bitnami’s redis helm chart below.

    https://github.com/bitnami/charts/tree/master/bitnami/redis

    Installed with…

    helm install /root/custom-chart-location -n redis -f /root/custom-chart-location/values.yaml –set cluster.enabled=true –set sentinel.enabled=true –set usePassword=false

    The values.yaml has Bitnami’s production values, except with network policy disabled.

    Redis client at web nodes is installed via pecl. Version of php-redis installed is 5.2.2

    These may help somebody.

    • This reply was modified 6 years ago by CodeBard.
    • This reply was modified 6 years ago by CodeBard.
    Thread Starter CodeBard

    (@codebard)

    Using

    define( 'WP_REDIS_CLUSTER', [
        'tcp://redis-cluster:6379?database=0&alias=node-01',
    ] );

    Instead of…

    define( 'WP_REDIS_HOST', 'redis-cluster' );

    I get…

    Connection Exception: Couldn't map cluster keyspace using any provided seed (RedisClusterException)

    Thread Starter CodeBard

    (@codebard)

    redis-cluster:6379> INFO
    # Server
    redis_version:5.0.9
    redis_git_sha1:00000000
    redis_git_dirty:0
    redis_build_id:19c09cb14abb2b16
    redis_mode:cluster
    os:Linux 4.19.0-0.bpo.6-amd64 x86_64
    arch_bits:64
    multiplexing_api:epoll
    atomicvar_api:atomic-builtin
    gcc_version:8.3.0
    process_id:1
    run_id:fac89c6f3024d0b95953da813edead2fe2a3e1d7
    tcp_port:6379
    uptime_in_seconds:84263
    uptime_in_days:0
    hz:10
    configured_hz:10
    lru_clock:12175140
    executable:/opt/bitnami/redis/bin/redis-server
    config_file:
    
    # Clients
    connected_clients:1
    client_recent_max_input_buffer:2
    client_recent_max_output_buffer:0
    blocked_clients:0
    
    # Memory
    used_memory:2658648
    used_memory_human:2.54M
    used_memory_rss:12488704
    used_memory_rss_human:11.91M
    used_memory_peak:3465568
    used_memory_peak_human:3.31M
    used_memory_peak_perc:76.72%
    used_memory_overhead:2578594
    used_memory_startup:1463320
    used_memory_dataset:80054
    used_memory_dataset_perc:6.70%
    allocator_allocated:3114320
    allocator_active:3411968
    allocator_resident:10473472
    total_system_memory:8366104576
    total_system_memory_human:7.79G
    used_memory_lua:37888
    used_memory_lua_human:37.00K
    used_memory_scripts:0
    used_memory_scripts_human:0B
    number_of_cached_scripts:0
    maxmemory:0
    maxmemory_human:0B
    maxmemory_policy:noeviction
    allocator_frag_ratio:1.10
    allocator_frag_bytes:297648
    allocator_rss_ratio:3.07
    allocator_rss_bytes:7061504
    rss_overhead_ratio:1.19
    rss_overhead_bytes:2015232
    mem_fragmentation_ratio:4.77
    mem_fragmentation_bytes:9872056
    mem_not_counted_for_evict:82
    mem_replication_backlog:1048576
    mem_clients_slaves:16922
    mem_clients_normal:49694
    mem_aof_buffer:82
    mem_allocator:jemalloc-5.1.0
    active_defrag_running:0
    lazyfree_pending_objects:0
    
    # Persistence
    loading:0
    rdb_changes_since_last_save:2
    rdb_bgsave_in_progress:0
    rdb_last_save_time:1589149208
    rdb_last_bgsave_status:ok
    rdb_last_bgsave_time_sec:0
    rdb_current_bgsave_time_sec:-1
    rdb_last_cow_size:4530176
    aof_enabled:1
    aof_rewrite_in_progress:0
    aof_rewrite_scheduled:0
    aof_last_rewrite_time_sec:-1
    aof_current_rewrite_time_sec:-1
    aof_last_bgrewrite_status:ok
    aof_last_write_status:ok
    aof_last_cow_size:0
    aof_current_size:195
    aof_base_size:154
    aof_pending_rewrite:0
    aof_buffer_length:0
    aof_rewrite_buffer_length:0
    aof_pending_bio_fsync:0
    aof_delayed_fsync:0
    
    # Stats
    total_connections_received:34227
    total_commands_processed:153402
    instantaneous_ops_per_sec:1
    total_net_input_bytes:4832952
    total_net_output_bytes:2379022
    instantaneous_input_kbps:0.04
    instantaneous_output_kbps:0.00
    rejected_connections:0
    sync_full:1
    sync_partial_ok:0
    sync_partial_err:1
    expired_keys:0
    expired_stale_perc:0.00
    expired_time_cap_reached_count:0
    evicted_keys:0
    keyspace_hits:238
    keyspace_misses:0
    pubsub_channels:0
    pubsub_patterns:0
    latest_fork_usec:1043
    migrate_cached_sockets:0
    slave_expires_tracked_keys:0
    active_defrag_hits:0
    active_defrag_misses:0
    active_defrag_key_hits:0
    active_defrag_key_misses:0
    
    # Replication
    role:master
    connected_slaves:1
    slave0:ip=10.244.11.19,port=6379,state=online,offset=117585,lag=0
    master_replid:25b1900f429338f116f3534e9152bc5912037aba
    master_replid2:0000000000000000000000000000000000000000
    master_repl_offset:117585
    second_repl_offset:-1
    repl_backlog_active:1
    repl_backlog_size:1048576
    repl_backlog_first_byte_offset:1
    repl_backlog_histlen:117585
    
    # CPU
    used_cpu_sys:70.030822
    used_cpu_user:59.647139
    used_cpu_sys_children:0.079644
    used_cpu_user_children:0.143280
    
    # Cluster
    cluster_enabled:1
    
    # Keyspace
    Thread Starter CodeBard

    (@codebard)

    I refreshed the site’s pages and visited some other urls in order to effect a cache read/write after flushing the db.

    Thread Starter CodeBard

    (@codebard)

    Below INFO stat outputs show the stats before and after db was flushed with FLUSHALL

    redis-cluster:6379> INFO stats
    # Stats
    total_connections_received:33500
    total_commands_processed:150132
    instantaneous_ops_per_sec:2
    total_net_input_bytes:4729375
    total_net_output_bytes:2340663
    instantaneous_input_kbps:0.07
    instantaneous_output_kbps:0.01
    rejected_connections:0
    sync_full:1
    sync_partial_ok:0
    sync_partial_err:1
    expired_keys:0
    expired_stale_perc:0.00
    expired_time_cap_reached_count:0
    evicted_keys:0
    keyspace_hits:238
    keyspace_misses:0
    pubsub_channels:0
    pubsub_patterns:0
    latest_fork_usec:1043
    migrate_cached_sockets:0
    slave_expires_tracked_keys:0
    active_defrag_hits:0
    active_defrag_misses:0
    active_defrag_key_hits:0
    active_defrag_key_misses:0
    
    redis-cluster:6379> INFO stats
    # Stats
    total_connections_received:33506
    total_commands_processed:150159
    instantaneous_ops_per_sec:1
    total_net_input_bytes:4730216
    total_net_output_bytes:2341410
    instantaneous_input_kbps:0.05
    instantaneous_output_kbps:0.01
    rejected_connections:0
    sync_full:1
    sync_partial_ok:0
    sync_partial_err:1
    expired_keys:0
    expired_stale_perc:0.00
    expired_time_cap_reached_count:0
    evicted_keys:0
    keyspace_hits:238
    keyspace_misses:0
    pubsub_channels:0
    pubsub_patterns:0
    latest_fork_usec:1043
    migrate_cached_sockets:0
    slave_expires_tracked_keys:0
    active_defrag_hits:0
    active_defrag_misses:0
    active_defrag_key_hits:0
    active_defrag_key_misses:0
    

    Currently DBSIZE outputs 0.

    Thread Starter CodeBard

    (@codebard)

    The thing is that the plugin seems to be able to see the redis server and ping it, right? It returns 1. And when i was using another version of Redis client (phpredis) it was ponging to ‘ping’. So connectivity should be there? Or is there any other particular pitfall that mmay be aside from connectivity?

    Thread Starter CodeBard

    (@codebard)

    Im wondering if this has anything to do with Bitnami’s Redis cluster for Kubernetes.

    Thread Starter CodeBard

    (@codebard)

    The later bit of code prints out absolutely nothing. Not even an empty array.

    Thread Starter CodeBard

    (@codebard)

    thanks Till – with that file…

    object(Redis)#1 (0) { }

    …is the output.

    Plugin Contributor CodeBard

    (@codebard)

    Invalid key type message doesnt seem to be coming from the plugin or Patreon. Neither that ‘Error for site owner’ seems to be.

    It may be some other plugin, or something from your host. You should check and confirm that it is relevant to this plugin or Patreon.

Viewing 15 replies - 106 through 120 (of 336 total)