numpy on redis gears docker

Hi,

I tried to install numpy on the redis Gears docker with no success.

Is there another alternative?

What I can be doing wrong?

Thanks

Can you specify the error you are getting and the log file? I see there is a general issue with installing dependencies on docker latest (v0.9.0) which is not related to numpy.

Notice that on edge I could successfully do it (it took a while though to download it):
127.0.0.1:6379> RG.PYEXECUTE “import numpy; log(str(numpy))” REQUIREMENTS numpy

OK

RedisLogs:
1:M 12 Apr 2020 15:01:24.327 * Executing : mkdir -p /var/opt/redislabs/lib/modules/python3/.venv/numpy

1:M 12 Apr 2020 15:01:24.334 * Executing : /bin/bash -c “source /var/opt/redislabs/lib/modules/python3/.venv/bin/activate;cd /var/opt/redislabs/lib/modules/python3/.venv/numpy;python -m pip wheel numpy”

WARNING: The directory ‘/home/redis/.cache/pip’ or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you may want sudo’s -H flag.

1:M 12 Apr 2020 15:01:26.629 * Collecting numpy

1:M 12 Apr 2020 15:01:27.002 * Downloading numpy-1.18.2-cp37-cp37m-manylinux1_x86_64.whl (20.2 MB)

1:M 12 Apr 2020 15:05:21.364 * Saved ./numpy-1.18.2-cp37-cp37m-manylinux1_x86_64.whl

1:M 12 Apr 2020 15:05:21.371 * Skipping numpy, due to already being wheel.

1:M 12 Apr 2020 15:05:21.804 * Executing : /bin/bash -c “source /var/opt/redislabs/lib/modules/python3/.venv/bin/activate;cd /var/opt/redislabs/lib/modules/python3/.venv/numpy;python -m pip install numpy-1.18.2-cp37-cp37m-manylinux1_x86_64.whl”

WARNING: The directory ‘/home/redis/.cache/pip’ or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you may want sudo’s -H flag.

1:M 12 Apr 2020 15:05:22.129 * Processing ./numpy-1.18.2-cp37-cp37m-manylinux1_x86_64.whl

1:M 12 Apr 2020 15:05:22.675 * Installing collected packages: numpy

1:M 12 Apr 2020 15:05:24.731 * Successfully installed numpy-1.18.2

1:M 12 Apr 2020 15:06:21.337 * GEARS: <module ‘numpy’ from ‘/var/opt/redislabs/lib/modules/python3/.venv/lib/python3.7/site-packages/numpy/init.py’>

``

Hi, I am running a redislabs/redismod docker. I tried executing the command you provided:
127.0.0.1:6379> RG.PYEXECUTE "import numpy; log(str(numpy))" REQUIREMENTS numpy (error) Could not satisfy requirments (26.57s) 127.0.0.1:6379>

I am new to Redis and couldn’t figure out how to access the log file, but I think I managed to activate the RedisGears venv and try to manually install numpy:
root@9c16dc7bf5b4:/var/opt/redislabs/lib/modules/python3/bin# source /var/opt/redislabs/lib/modules/python3/.venv/bin/activate (python3) root@9c16dc7bf5b4:/var/opt/redislabs/lib/modules/python3# pip install numpy WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available. WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/numpy/ WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/numpy/ WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/numpy/ WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/numpy/ WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/numpy/ Could not fetch URL https://pypi.org/simple/numpy/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/numpy/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) - skipping ERROR: Could not find a version that satisfies the requirement numpy (from versions: none) ERROR: No matching distribution found for numpy WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available. Could not fetch URL https://pypi.org/simple/pip/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/pip/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) - skipping (python3) root@9c16dc7bf5b4:/var/opt/redislabs/lib/modules/python3#

Any idea how to fix this?

@Damian_Danev you running with RedisGears latest (v0.9.0)? As I said there is an issue with latest, deps installation failing. Try using the edge tag and it should work. We will release a new version this week.

Yes, I was running the latest tag, I cant start the redislabs/redismod:edge, this is the command with its output:

docker run -it -p 6379:6379 redislabs/redismod:edge

1:C 26 Apr 2020 16:57:32.738 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 1:C 26 Apr 2020 16:57:32.738 # Redis version=5.0.8, bits=64, commit=00000000, modified=0, pid=1, just started 1:C 26 Apr 2020 16:57:32.738 # Configuration loaded _._ _.-``__ ''-._ _.-`` . _. ''-._ Redis 5.0.8 (00000000/0) 64 bit .-`` .-```. ```\/ _.,_ ''-._ ( ' , .- | , ) Running in standalone mode |-.-...- __…-.``-.|’_.-'| Port: 6379 | -._ ._ / _.-' | PID: 1 -._ -._ -./ .-’ .-’
|-._-.
-.__.-' _.-'_.-'| | -.
-._ _.-'_.-' | http://redis.io -._ -._-..-’.-’ .-’
|-._-.
-.__.-' _.-'_.-'| | -.
-._ _.-'_.-' | -._ -._-.
.-’_.-’ _.-’
-._ -..-’ _.-’
-._ _.-' -.
.-’

1:M 26 Apr 2020 16:57:32.739 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 26 Apr 2020 16:57:32.739 # Server initialized
1:M 26 Apr 2020 16:57:32.739 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command ‘echo never > /sys/kernel/mm/transparent_hugepage/enabled’ as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
1:M 26 Apr 2020 16:57:32.740 * Module ‘ai’ loaded from /usr/lib/redis/modules/redisai.so
1:M 26 Apr 2020 16:57:32.740 * RediSearch version 99.99.99 (Git=v1.6.6-69-gf11cca1)
1:M 26 Apr 2020 16:57:32.740 * Low level api version 1 initialized successfully
1:M 26 Apr 2020 16:57:32.740 * concurrent writes: OFF, gc: ON, prefix min length: 2, prefix max expansions: 200, query timeout (ms): 500, timeout policy: return, cursor read size: 1000, cursor max idle (ms): 300000, max doctable size: 1000000, search pool size: 20, index pool size: 8,
1:M 26 Apr 2020 16:57:32.740 * Initialized thread pool!
1:M 26 Apr 2020 16:57:32.740 * Module ‘ft’ loaded from /usr/lib/redis/modules/redisearch.so
1:M 26 Apr 2020 16:57:32.751 * Thread pool created, using 2 threads.
1:M 26 Apr 2020 16:57:32.751 * Module ‘graph’ loaded from /usr/lib/redis/modules/redisgraph.so
1:M 26 Apr 2020 16:57:32.752 * Module ‘timeseries’ loaded from /usr/lib/redis/modules/redistimeseries.so
Now using Redis allocator
1:M 26 Apr 2020 16:57:32.753 * Initializing RediSearch…
1:M 26 Apr 2020 16:57:32.753 * RediSearch initialized successfully.
1:M 26 Apr 2020 16:57:32.753 * Created new data type ‘ReJSON-RL’
1:M 26 Apr 2020 16:57:32.753 * Module ‘ReJSON’ loaded from /usr/lib/redis/modules/rejson.so
1:M 26 Apr 2020 16:57:32.753 * Module ‘bf’ loaded from /usr/lib/redis/modules/redisbloom.so
1:M 26 Apr 2020 16:57:32.755 * RedisGears version 99.99.99, git_sha=d37c60b554c1edb0aaa575a579a6775372ca1ace
1:M 26 Apr 2020 16:57:32.755 * Redis version found by RedisGears : 5.0.8 - oss
1:M 26 Apr 2020 16:57:32.755 * MaxExecutions:1000
1:M 26 Apr 2020 16:57:32.755 * MaxExecutionsPerRegistration:100
1:M 26 Apr 2020 16:57:32.755 * ProfileExecutions:0
1:M 26 Apr 2020 16:57:32.755 * PythonAttemptTraceback:1
1:M 26 Apr 2020 16:57:32.755 * DependenciesUrl:http://redismodules.s3.amazonaws.com/redisgears/redisgears-dependencies.linux-buster-x64.99.99.99.tgz
1:M 26 Apr 2020 16:57:32.755 * DependenciesSha256:ef2b81f999cb4fb2c44a75536e89c949616bd1f07df16625f0a870dde4cbc996
1:M 26 Apr 2020 16:57:32.755 * CreateVenv:0
1:M 26 Apr 2020 16:57:32.755 * ExecutionThreads:3
1:M 26 Apr 2020 16:57:32.755 * ExecutionMaxIdleTime:5000
1:M 26 Apr 2020 16:57:32.755 * PythonInstallationDir:/var/opt/redislabs/modules/rg
1:M 26 Apr 2020 16:57:32.755 * DownloadDeps:1
1:M 26 Apr 2020 16:57:32.755 * ForceDownloadDepsOnEnterprise:0
1:M 26 Apr 2020 16:57:32.755 * PythonHomeDir:/opt/redislabs/lib/modules/python3
1:M 26 Apr 2020 16:57:32.755 # could not initialize RedisAI_TensorGetDataSize

1:M 26 Apr 2020 16:57:32.755 # could not initialize RediAI api, running without AI support.
1:M 26 Apr 2020 16:57:32.756 * PYENV_DIR: /var/opt/redislabs/modules/rg//python3_99.99.99/
1:M 26 Apr 2020 16:57:32.756 * PYENV_HOME_DIR: /var/opt/redislabs/modules/rg//python3_99.99.99//.venv/
1:M 26 Apr 2020 16:57:32.756 * PYENV_BIN_DIR: /var/opt/redislabs/modules/rg//python3_99.99.99//.venv//bin
1:M 26 Apr 2020 16:57:32.756 * PYENV_ACTIVATE: /var/opt/redislabs/modules/rg//python3_99.99.99//.venv//bin/activate_this.py
1:M 26 Apr 2020 16:57:32.756 * PYENV_ACTIVATE_SCRIPT: /var/opt/redislabs/modules/rg//python3_99.99.99//.venv//bin/activate
1:M 26 Apr 2020 16:57:32.756 * Executing : rm -rf /tmp/deps…ef2b81f999cb4fb2c44a75536e89c949616bd1f07df16625f0a870dde4cbc996.tgz
1:M 26 Apr 2020 16:57:32.758 * Executing : curl -o /tmp/deps…ef2b81f999cb4fb2c44a75536e89c949616bd1f07df16625f0a870dde4cbc996.tgz http://redismodules.s3.amazonaws.com/redisgears/redisgears-dependencies.linux-buster-x64.99.99.99.tgz
sh: 1: curl: not found
1:M 26 Apr 2020 16:57:32.760 # Execution failed command : curl -o /tmp/deps…ef2b81f999cb4fb2c44a75536e89c949616bd1f07df16625f0a870dde4cbc996.tgz http://redismodules.s3.amazonaws.com/redisgears/redisgears-dependencies.linux-buster-x64.99.99.99.tgz
sha256sum: /tmp/deps…ef2b81f999cb4fb2c44a75536e89c949616bd1f07df16625f0a870dde4cbc996.tgz: No such file or directory
1:M 26 Apr 2020 16:57:32.762 # Failed to calculate sha25 on file /tmp/deps…ef2b81f999cb4fb2c44a75536e89c949616bd1f07df16625f0a870dde4cbc996.tgz
1:M 26 Apr 2020 16:57:32.762 # Failed installing python dependencies
1:M 26 Apr 2020 16:57:32.762 # Module /var/opt/redislabs/lib/modules/redisgears.so initialization failed. Module not loaded
1:M 26 Apr 2020 16:57:32.762 # Can’t load module from /var/opt/redislabs/lib/modules/redisgears.so: server aborting`

Just fixed it, try now:

docker pull redislabs/redismod:edge
docker run -p 6379:6379 redislabs/redismod:edge

1 Like

Now it works, but… not sure if I am not doing something wrong or if I got the idea wrong in the first place. The idea of the python module redisgears-py is so that you can set up RedisGears from a separate environment/container than the Redis env/container, right? Being able to right full python scripts, assign RedisGears task from python code, and so on.
I must install redisgears-py in the environment that I am going to be working from and it also must be present in the Redis python interpreter (the redislabs docker image has it set up by default).

I do that, I also have the Redis module installed and I create a connection

import redis
from gearsclient import GearsRemoteBuilder as GearsBuilder

conn = redis.Redis(host='localhost', port=6379)

Executing normal operations works just fine:
conn.set('test', 'test') - > True

BUT when I try to use the GearsBuilder:
res = GearsBuilder(r=conn).run()
ConnectionError: Connection closed by server.

Redis crashes and the container stops with this message:

=== REDIS BUG REPORT START: Cut & paste starting from here ===
1:M 27 Apr 2020 02:02:36.171 # Redis 5.0.8 crashed by signal: 11
1:M 27 Apr 2020 02:02:36.171 # Crashed running the instruction at: 0x7f3b32f1f181
1:M 27 Apr 2020 02:02:36.171 # Accessing address: 0x45
1:M 27 Apr 2020 02:02:36.171 # Failed assertion: <no assertion failed> (<no file>:0)

------ STACK TRACE ------
EIP:
/lib/x86_64-linux-gnu/libc.so.6(+0x15c181)[0x7f3b32f1f181]

Backtrace:
redis-server *:6379(logStackTrace+0x32)[0x55d3f977a592]
redis-server *:6379(sigsegvHandler+0x9e)[0x55d3f977ac6e]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f3b32f96730]
/lib/x86_64-linux-gnu/libc.so.6(+0x15c181)[0x7f3b32f1f181]
/lib/x86_64-linux-gnu/libc.so.6(_IO_vfprintf+0x1fff)[0x7f3b32e149ef]
/lib/x86_64-linux-gnu/libc.so.6(vsnprintf+0x90)[0x7f3b32e3b7a0]
redis-server *:6379(RM_LogRaw+0x93)[0x55d3f97a7ef3]
redis-server *:6379(RM_Log+0x8b)[0x55d3f97a7fdb]
/var/opt/redislabs/lib/modules/redisgears.so(+0x1086a6)[0x7f3b2f1086a6]
redis-server *:6379(RedisModuleCommandDispatcher+0x54)[0x55d3f97a6d84]
redis-server *:6379(call+0x9b)[0x55d3f973635b]
redis-server *:6379(processCommand+0x51e)[0x55d3f9736c1e]
redis-server *:6379(processInputBuffer+0x171)[0x55d3f9746e21]
redis-server *:6379(aeProcessEvents+0x101)[0x55d3f9730311]
redis-server *:6379(aeMain+0x2b)[0x55d3f973071b]
redis-server *:6379(main+0x4ca)[0x55d3f972d57a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)[0x7f3b32de709b]
redis-server *:6379(_start+0x2a)[0x55d3f972d7da]

------ INFO OUTPUT ------
# Server
redis_version:5.0.8
redis_git_sha1:00000000
redis_git_dirty:0
redis_build_id:74b2ecbb164db4bc
redis_mode:standalone
os:Linux 4.19.76-linuxkit x86_64
arch_bits:64
multiplexing_api:epoll
atomicvar_api:atomic-builtin
gcc_version:8.3.0
process_id:1
run_id:f78263ac797c1195d61be3cdedb2e3e92743854d
tcp_port:6379
uptime_in_seconds:13
uptime_in_days:0
hz:10
configured_hz:10
lru_clock:10894652
executable:/data/redis-server
config_file:

# Clients
connected_clients:1
client_recent_max_input_buffer:4
client_recent_max_output_buffer:0
blocked_clients:0

# Memory
used_memory:5601032
used_memory_human:5.34M
used_memory_rss:24211456
used_memory_rss_human:23.09M
used_memory_peak:5601032
used_memory_peak_human:5.34M
used_memory_peak_perc:100.05%
used_memory_overhead:5585038
used_memory_startup:5535344
used_memory_dataset:15994
used_memory_dataset_perc:24.35%
allocator_allocated:5813104
allocator_active:6393856
allocator_resident:12488704
total_system_memory:2085896192
total_system_memory_human:1.94G
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:580752
allocator_rss_ratio:1.95
allocator_rss_bytes:6094848
rss_overhead_ratio:1.94
rss_overhead_bytes:11722752
mem_fragmentation_ratio:4.37
mem_fragmentation_bytes:18676096
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:1587952943
rdb_last_bgsave_status:ok
rdb_last_bgsave_time_sec:-1
rdb_current_bgsave_time_sec:-1
rdb_last_cow_size:0
aof_enabled:0
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

# Stats
total_connections_received:19
total_commands_processed:20
instantaneous_ops_per_sec:0
total_net_input_bytes:6593
total_net_output_bytes:1332
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:0
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:712ac61e90a8009b2ca4caa3e0ccca45b1d3c223
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:0.036964
used_cpu_user:0.232774
used_cpu_sys_children:0.000000
used_cpu_user_children:0.000000

# Commandstats
cmdstat_info:calls=1,usec=333,usec_per_call=333.00
cmdstat_host::calls=18,usec=9,usec_per_call=0.50
cmdstat_config:calls=1,usec=103,usec_per_call=103.00

# Cluster
cluster_enabled:0

# Keyspace

------ CLIENT LIST OUTPUT ------
id=29 addr=172.17.0.1:58918 fd=13 name= age=0 idle=0 flags=N db=0 sub=0 psub=0 multi=-1 qbuf=221 qbuf-free=32547 obl=0 oll=0 omem=0 events=r cmd=rg.pyexecuteremote

------ CURRENT CLIENT INFO ------
id=29 addr=172.17.0.1:58918 fd=13 name= age=0 idle=0 flags=N db=0 sub=0 psub=0 multi=-1 qbuf=221 qbuf-free=32547 obl=0 oll=0 omem=0 events=r cmd=rg.pyexecuteremote
argv[0]: 'RG.PYEXECUTEREMOTE'
argv[1]: '���'

------ REGISTERS ------
1:M 27 Apr 2020 02:02:36.171 #
RAX:0000000000000020 RBX:00007ffdab2d85e0
RCX:0000000000000005 RDX:0000000000000045
RDI:0000000000000045 RSI:00007ffdab2d81b0
RBP:00007ffdab2d85d0 RSP:00007ffdab2d8058
R8 :0000000000000045 R9 :00007f3b32f3de80
R10:0000000000000000 R11:00007f3b32f3df00
R12:0000000000000031 R13:00007ffdab2d8b88
R14:0000000000000000 R15:0000000000000073
RIP:00007f3b32f1f181 EFL:0000000000010283
CSGSFS:002b000000000033
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d8067) -> 00007ffd00000000
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d8066) -> 0000000000000045
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d8065) -> 00007f3b2c0a7920
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d8064) -> 00007ffdab2d8690
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d8063) -> 00007ffd00000000
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d8062) -> 0000000000000000
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d8061) -> 0000000000000000
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d8060) -> ffffffffffffffff
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d805f) -> 00007ffdab2d81b0
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d805e) -> 00007f3b00000000
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d805d) -> 0000000000000000
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d805c) -> 0000000000000000
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d805b) -> 0000000000000000
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d805a) -> 00007ffdab2d8640
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d8059) -> 00007ffdab2d8700
1:M 27 Apr 2020 02:02:36.171 # (00007ffdab2d8058) -> 00007f3b32e149ef

------ FAST MEMORY TEST ------
1:M 27 Apr 2020 02:02:36.171 # Bio thread for job type #0 terminated
1:M 27 Apr 2020 02:02:36.172 # Bio thread for job type #1 terminated
1:M 27 Apr 2020 02:02:36.172 # Bio thread for job type #2 terminated
*** Preparing to test memory region 55d3f98a8000 (2248704 bytes)
*** Preparing to test memory region 55d3fb59f000 (135168 bytes)
*** Preparing to test memory region 7f3b29ef8000 (8388608 bytes)
*** Preparing to test memory region 7f3b2a6f9000 (8388608 bytes)
*** Preparing to test memory region 7f3b2aefa000 (8388608 bytes)
*** Preparing to test memory region 7f3b2b6fb000 (8388608 bytes)
*** Preparing to test memory region 7f3b2befb000 (9437184 bytes)
*** Preparing to test memory region 7f3b2c7fc000 (8388608 bytes)
*** Preparing to test memory region 7f3b2cffd000 (8388608 bytes)
*** Preparing to test memory region 7f3b2d7fe000 (8388608 bytes)
*** Preparing to test memory region 7f3b2dfff000 (8388608 bytes)
*** Preparing to test memory region 7f3b2e800000 (8388608 bytes)
*** Preparing to test memory region 7f3b2f425000 (139264 bytes)
*** Preparing to test memory region 7f3b2f8ec000 (8192 bytes)
*** Preparing to test memory region 7f3b2f8ef000 (8388608 bytes)
*** Preparing to test memory region 7f3b300f0000 (8388608 bytes)
*** Preparing to test memory region 7f3b311b2000 (12288 bytes)
*** Preparing to test memory region 7f3b311b6000 (8388608 bytes)
*** Preparing to test memory region 7f3b31bfc000 (12288 bytes)
*** Preparing to test memory region 7f3b31c00000 (8388608 bytes)
*** Preparing to test memory region 7f3b32400000 (8388608 bytes)
*** Preparing to test memory region 7f3b32d22000 (4096 bytes)
*** Preparing to test memory region 7f3b32dbd000 (24576 bytes)
*** Preparing to test memory region 7f3b32f80000 (16384 bytes)
*** Preparing to test memory region 7f3b32fa1000 (16384 bytes)
*** Preparing to test memory region 7f3b32fae000 (4096 bytes)
*** Preparing to test memory region 7f3b33141000 (8192 bytes)
*** Preparing to test memory region 7f3b3316f000 (4096 bytes)
.O.O.O.O.O.O.O.O.O.O.O.O.O.O.O.O.O.O.O.O.O.O.O.O.O.O.O.O
Fast memory test PASSED, however your memory can still be broken. Please run a memory test for several hours if possible.

------ DUMPING CODE AROUND EIP ------
Symbol: (null) (base: (nil))
Module: /lib/x86_64-linux-gnu/libc.so.6 (base 0x7f3b32dc3000)
$ xxd -r -p /tmp/dump.hex /tmp/dump.bin
$ objdump --adjust-vma=(nil) -D -b binary -m i386:x86-64 /tmp/dump.bin
------

=== REDIS BUG REPORT END. Make sure to include from START to END. ===

       Please report the crash by opening an issue on github:

           http://github.com/antirez/redis/issues

  Suspect RAM error? Use redis-server --test-memory to verify it.
1 Like

@Damian_Danev yes you got it right, you can send the python code from anywhere to redis, the fact that its crashing is a bug and I need to give some attention to this python client cause I haven’t tested it in a while and I plan to change its implementation anyway.
I use gears-cli (https://github.com/RedisGears/gears-cli) which is a very simple python client that gets a python file and sends the python code using rg.pyexecute (the redisgears-py uses another internal command and this is what failing). I suggest you to use it as well. Once the python client is fixed I will tag a version and let you know.

1 Like