slate
Forum Replies Created
-
Forum: Plugins
In reply to: [LiteSpeed Cache] redis connection test failed UNIX socketSorry but this is a default installation of redis I rather think, that the guide is completely unfinished and lacks a lot of steps that still need to be done.
I dont need help from my hosting provider, I am the hosting provider.Forum: Plugins
In reply to: [LiteSpeed Cache] redis connection test failed UNIX socketGotcha, checked the redis log and it says:
146979:C 08 Jun 2020 20:38:33.909 # Can’t chdir to ‘/var/lib/redis’: Permission denied
How outdated is this guide? It misses tons of things obviously. Do I now manually edit all of redis permissions? I feel something is very wrong with this guide. the directory /var/lib/redis is owned by redis:nobody, so now really proceed to mess around with all these permissions manually?Forum: Plugins
In reply to: [LiteSpeed Cache] redis connection test failed UNIX socketYou are not reading my messages completely. I have already set the location to /home/”NAMEOFPHPUSER”/redis/logs/redis.log and then I get:
Failed to start Redis persistent key-value database.Forum: Plugins
In reply to: [LiteSpeed Cache] redis connection test failed UNIX socketAs per the guide you sent me i edited /etc/systemd/system/redis.service and put in the user who is also running php, thus i assume this user is now also running redis. – so assuming this is correct that user should have access to his own home directory.
probably this guide is just very outdated and not working properly. so how to proceed?
Forum: Plugins
In reply to: [LiteSpeed Cache] redis connection test failed UNIX socketI had seen that one too before and had tried it. After step 4 upon restarting redis I get:
‘logfile /var/log/redis/redis.log
Can’t open the log file: Permission denied
Then first I tried to chown this logfile to the php user, it fails with permission error again.
Then when I create a new logfile at the home of the php-user and point to this logfile inside redis.conf I get “failed to start Redis persistent key-value database.”- This reply was modified 4 years, 5 months ago by slate.
Forum: Plugins
In reply to: [LiteSpeed Cache] redis connection test failed UNIX socketthen i dont understand of what I have to change the ownership of, I have posted you a screenshot, the socket file itself is owned by redis:nobody, please clarify.
Forum: Plugins
In reply to: [LiteSpeed Cache] redis connection test failed UNIX socketfound it:
2020-06-08 20:18:42.605801 [NOTICE] [1.2.3.4:60539#mysite.io-443:lsapi] [STDERR] PHP Fatal error: Uncaught RedisException: Permission denied in /home/admin/domains/mysite.io/public_html/info.php:3
how to proceed?
Forum: Plugins
In reply to: [LiteSpeed Cache] redis connection test failed UNIX socketI have updated the path, yes, which log do I have to check for the 500 error?
Forum: Plugins
In reply to: [LiteSpeed Cache] redis connection test failed UNIX socketThe reason for the 500 is the snippet? All other pages work fine.
- This reply was modified 4 years, 5 months ago by slate.
Forum: Plugins
In reply to: [LiteSpeed Cache] redis connection test failed UNIX socketForum: Plugins
In reply to: [LiteSpeed Cache] redis connection test failed UNIX socketYes, I had seen it and have just read it again.
See here: permissions are on redis:nobody for var/run/redis/redis-server.sock, how to proceed?Forum: Plugins
In reply to: [LiteSpeed Cache] redis connection test failed UNIX socketif sshing to the server as root and doing:
nc -U /var/run/redis/redis-server.sock
infoI get the following, so apparently redis itself is running on that socket, really cant find the cause of why the connection test fails though.
$3461 # Server redis_version:5.0.3 redis_git_sha1:00000000 redis_git_dirty:0 redis_build_id:8c0bf22bfba82c8f redis_mode:standalone os:Linux 4.18.0-147.8.1.el8_1.x86_64 x86_64 arch_bits:64 multiplexing_api:epoll atomicvar_api:atomic-builtin gcc_version:8.2.1 process_id:6025 run_id:5d8536d29865f9fa60bb091178254125480cd279 tcp_port:0 uptime_in_seconds:59880 uptime_in_days:0 hz:10 configured_hz:10 lru_clock:14487544 executable:/usr/bin/redis-server config_file:/etc/redis.conf # Clients connected_clients:1 client_recent_max_input_buffer:4 client_recent_max_output_buffer:0 blocked_clients:0 # Memory used_memory:1357280 used_memory_human:1.29M used_memory_rss:9965568 used_memory_rss_human:9.50M used_memory_peak:1817832 used_memory_peak_human:1.73M used_memory_peak_perc:74.66% used_memory_overhead:840926 used_memory_startup:791040 used_memory_dataset:516354 used_memory_dataset_perc:91.19% allocator_allocated:1348104 allocator_active:1531904 allocator_resident:5877760 total_system_memory:67203321856 total_system_memory_human:62.59G 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.14 allocator_frag_bytes:183800 allocator_rss_ratio:3.84 allocator_rss_bytes:4345856 rss_overhead_ratio:1.70 rss_overhead_bytes:4087808 mem_fragmentation_ratio:7.58 mem_fragmentation_bytes:8650304 mem_not_counted_for_evict:0 mem_replication_backlog:0 mem_clients_slaves:0 mem_clients_normal:49694 mem_aof_buffer:0 mem_allocator:jemalloc-5.1.0 active_defrag_running:0 lazyfree_pending_objects:0 # Persistence loading:0 rdb_changes_since_last_save:0 rdb_bgsave_in_progress:0 rdb_last_save_time:1591486029 rdb_last_bgsave_status:ok rdb_last_bgsave_time_sec:0 rdb_current_bgsave_time_sec:-1 rdb_last_cow_size:4595712 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:65600127 aof_base_size:65600127 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:1 total_commands_processed:0 instantaneous_ops_per_sec:0 total_net_input_bytes:5 total_net_output_bytes:0 instantaneous_input_kbps:0.00 instantaneous_output_kbps:0.00 rejected_connections:0 sync_full:0 sync_partial_ok:0 sync_partial_err:0 expired_keys:0 expired_stale_perc:0.00 expired_time_cap_reached_count:0 evicted_keys:0 keyspace_hits:0 keyspace_misses:0 pubsub_channels:0 pubsub_patterns:0 latest_fork_usec:392 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:0 master_replid:2d96452c1ad28fd8b55f3723fa8086b81a811801 master_replid2:0000000000000000000000000000000000000000 master_repl_offset:0 second_repl_offset:-1 repl_backlog_active:0 repl_backlog_size:1048576 repl_backlog_first_byte_offset:0 repl_backlog_histlen:0 # CPU used_cpu_sys:6.612010 used_cpu_user:9.203538 used_cpu_sys_children:0.001423 used_cpu_user_children:0.000000 # Cluster cluster_enabled:0 # Keyspace db0:keys=4,expires=0,avg_ttl=0
Forum: Fixing WordPress
In reply to: Recommended SQL modes for managed DBsIm familiar with mysql-tuner, it shows me some different values though. I did read in some forums, that there are a couple mysql-modes wordpress is not compatible with, such as ANSI, so i want to make sure this time i will set it up correctly. why are you using mariadb over mysql?
Forum: Fixing WordPress
In reply to: Recommended SQL modes for managed DBsIm using MySQL 8, did have some problems in the past with collation and zeroes in dates which required me to do a lot of digging. So now I want to find out the recommended modes. Currently im only using:
ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTIONDespite you haven’t replied to this ticket it seems the new woocommerce update made it possible to use coinpayments for subscriptions. Though when activating trials on checkout the customers get
"ERROR: No 'amountf' set in the button or amount is <= 0 (and allow_amount is set to 0)!"
For now I have deactivated trials but it would be nice to have them activated again, so the system can handle them automatically