(((REDIS))) “Connection refused [tcp:\/\/127.0.0.1:6379]”

  • Resolved heriton

    (@heriton)


    3 years ago

    Status: Not connected
Client: 
Drop-in: Valid
Disabled: No
Ping: 
Connection Exception: Connection refused [tcp://127.0.0.1:6379] (Predis\Connection\ConnectionException)
Errors: [
    "Connection refused [tcp:\/\/127.0.0.1:6379]"
]
PhpRedis: Not loaded
Predis: 1.1.6
Credis: Not loaded
PHP Version: 7.4.25
Plugin Version: 2.0.21
Redis Version: Unknown
Multisite: No
Metrics: Disabled
Metrics recorded: null
Filesystem: Working
Global Prefix: "wpeu_"
Blog Prefix: "wpeu_"
Global Groups: [
    "blog-details",
    "blog-id-cache",
    "blog-lookup",
    "global-posts",
    "networks",
    "rss",
    "sites",
    "site-details",
    "site-lookup",
    "site-options",
    "site-transient",
    "users",
    "useremail",
    "userlogins",
    "usermeta",
    "user_meta",
    "userslugs",
    "redis-cache"
]
Ignored Groups: [
    "counts",
    "plugins",
    "themes",
    "blog-details",
    "blog-id-cache",
    "blog-lookup",
    "global-posts",
    "networks",
    "rss",
    "sites",
    "site-details",
    "site-lookup",
    "site-options",
    "site-transient",
    "users",
    "useremail",
    "userlogins",
    "usermeta",
    "user_meta",
    "userslugs",
    "redis-cache",
    "blog_meta"
]
Unflushable Groups: []
Drop-ins: [
    "advanced-cache.php v by ",
    "Redis Object Cache Drop-In v2.0.21 by Till Krüss"
]

    The plugin was working perfectly with mine (CENTOS 7 linux); until I install the cloudaflare plugins and change the domain dns; when entering my site, the mistake has already been made!
    I installed and uninstalled the plugin several times and the error persists!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    Hi there!

    It looks like Redis Server is not running on 127.0.0.1:6379 according to your Connection refused error message. Make sure Redis has been started.

    Thread Starter heriton

    (@heriton)

    I entered the SSH terminal, used the command “redis-server” and got the following result:

    30231:C 12 Nov 2021 22:31:54.746 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
30231:C 12 Nov 2021 22:31:54.746 # Redis version=6.2.6, bits=64, commit=00000000, modified=0, pid=30231, just started
30231:C 12 Nov 2021 22:31:54.746 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
30231:M 12 Nov 2021 22:31:54.747 * Increased maximum number of open files to 10032 (it was originally set to 4096).
30231:M 12 Nov 2021 22:31:54.747 * monotonic clock: POSIX clock_gettime
30231:M 12 Nov 2021 22:31:54.748 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
30231:M 12 Nov 2021 22:31:54.748 # Failed listening on port 6379 (TCP), aborting.


    I also used the following command “sudo systemctl status redis” and got the following result:

    redis.service - Redis persistent key-value database
   Loaded: loaded (/usr/lib/systemd/system/redis.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/redis.service.d
           └─limit.conf
   Active: active (running) since Wed 2021-11-10 00:39:55 -03; 2 days ago
 Main PID: 31835 (redis-server)
   Status: "Ready to accept connections"
   CGroup: /system.slice/redis.service
           └─31835 /usr/bin/redis-server 127.0.0.1:6379

Current command vanished from the unit file, execution of t...med.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Hint: Some lines were ellipsized, use -l to show in full.


    Do you have any idea what might be causing the error? And how to fix it?

    • This reply was modified 3 years ago by heriton.
    Plugin Author Till Krüss

    (@tillkruess)

    
Failed listening on port 6379 (TCP), aborting.

    Your hosting provider can assist you with this. It’s unfortunately outside the support scope for this plugin.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘(((REDIS))) “Connection refused [tcp:\/\/127.0.0.1:6379]”’ is closed to new replies.