question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: Server at 127.0.0.1:11211 not available

See original GitHub issue

LOG

Error: Server at 127.0.0.1:11211 not available
at Client.memcachedCommand [as command] (/home/hello.com/node_modules/memcached/lib/memcached.js:306:70)
at Client.get (/home/hello.com/node_modules/memcached/lib/memcached.js:830:10)

But Memcached active.

# service memcached status
● memcached.service - memcached daemon
   Loaded: loaded (/lib/systemd/system/memcached.service; disabled)
   Active: active (running) since Thu 2017-03-23 08:35:35 EDT; 10s ago
 Main PID: 1538 (memcached)
   CGroup: /system.slice/memcached.service
           └─1538 /usr/bin/memcached -m 64 -p 11211 -u memcache -l 127.0.0.1

Mar 23 08:35:35 trampamp systemd[1]: Starting memcached daemon...
Mar 23 08:35:35 trampamp systemd[1]: Started memcached daemon.
# telnet 127.0.0.1 11211
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
stats
STAT pid 1538
STAT uptime 876
STAT time 1490273409
STAT version 1.4.21
STAT libevent 2.0.21-stable
STAT pointer_size 64
STAT rusage_user 0.025996
STAT rusage_system 0.006998
STAT curr_connections 5
STAT total_connections 8
STAT connection_structures 6
STAT reserved_fds 20
STAT cmd_get 0
STAT cmd_set 0
STAT cmd_flush 2
STAT cmd_touch 0
STAT get_hits 0
STAT get_misses 0
STAT delete_misses 0
STAT delete_hits 0
STAT incr_misses 0
STAT incr_hits 0
STAT decr_misses 0
STAT decr_hits 0
STAT cas_misses 0
STAT cas_hits 0
STAT cas_badval 0
STAT touch_hits 0
STAT touch_misses 0
STAT auth_cmds 0
STAT auth_errors 0
STAT bytes_read 46
STAT bytes_written 15
STAT limit_maxbytes 67108864
STAT accepting_conns 1
STAT listen_disabled_num 0
STAT threads 4
STAT conn_yields 0
STAT hash_power_level 16
STAT hash_bytes 524288
STAT hash_is_expanding 0
STAT malloc_fails 0
STAT bytes 0
STAT curr_items 0
STAT total_items 0
STAT expired_unfetched 0
STAT evicted_unfetched 0
STAT evictions 0
STAT reclaimed 0
STAT crawler_reclaimed 0
STAT lrutail_reflocked 0
END

Issue Analytics

  • State:open
  • Created 6 years ago
  • Reactions:7
  • Comments:17

github_iconTop GitHub Comments

4reactions
funduckcommented, Oct 17, 2018

Looks like I got it!
this is how my memcached is started

memcached -p 11212 -m 256 -c 1024 -I 20m

and this was the client creation

new Memcached(
    options.host + ':' + options.port, {
        maxValue: 33554432
    }
);

when i corrected maxValue to the value <= 20Mb, for example 10485760
in logs instead of those unexpected errors i sometimes see for too big items

Error: The length of the value is greater than 10485760

which is perfectly fine and all other write operations succeed

0reactions
surajudaycommented, Nov 14, 2022

Can somebody explain how to reproduce this? I followed the jest code, all it tells is a ERROR response was received Error: Received an ERROR response at Socket.error (/Users/sudayashankar/repos/cassi/node_modules/memcached/lib/memcached.js:452:16) at Client.rawDataReceived (/Users/sudayashankar/repos/cassi/node_modules/memcached/lib/memcached.js:744:51) at Client.BufferBuffer (/Users/sudayashankar/repos/cassi/node_modules/memcached/lib/memcached.js:678:12) at Socket.bowlofcurry (/Users/sudayashankar/repos/cassi/node_modules/memcached/lib/utils.js:126:15) at Socket.emit (events.js:400:28) at addChunk (internal/streams/readable.js:290:12) at readableAddChunk (internal/streams/readable.js:261:11) at Socket.Readable.push (internal/streams/readable.js:204:10) at TCP.onStreamRead (internal/stream_base_commons.js:188:23)

Read more comments on GitHub >

github_iconTop Results From Across the Web

devilbox/Lobby - Gitter
services.memcd.ports is invalid: Invalid port "127.0.0.111211:11211", ... Hi all, there is any way to reverse proxy using nginx to some server on the...
Read more >
Error: couldn't connect to server 127.0.0.1:27017 - MongoDB
0.1 : 27017 ” is a general error message indicating that your client/driver cannot connect to a server on the specified hostname/IP and...
Read more >
mongo - couldn't connect to server 127.0.0.1:27017
I fixed this problem by trying to repair the mongodb, there I found that the directory required for the db to run was...
Read more >
Cannot connect to 127.0.0.1, localhost, or linux IP address
when I run NoSQLBooster for MongoDB in windows I get the error: "message" : "failed to connect to server [localhost:27027] on first connect ......
Read more >
MemcacheD、Repcached在centos上的安装步骤 - CSDN博客
This system is not registered withRHN. ... No package memcached available. ... for the Apache web server using a MySQL database.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found