I pull the latest redisedge docker image and run, It prompts "could not initialize RedisAI_GetAPIVersion" at runtime.
[root@localhost redisedge]# docker run -p 6379:6379 -v /work/redisedge/data:/data redislabs/redisedge
WARNING: IPv4 forwarding is disabled. Networking will not work.
1:C 12 Aug 2019 23:01:36.442 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 12 Aug 2019 23:01:36.442 # Redis version=5.0.5, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 12 Aug 2019 23:01:36.442 # Configuration loaded
1:M 12 Aug 2019 23:01:36.443 Running mode=standalone, port=6379.
1:M 12 Aug 2019 23:01:36.443 # 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 12 Aug 2019 23:01:36.443 # Server initialized
1:M 12 Aug 2019 23:01:36.443 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:M 12 Aug 2019 23:01:36.443 # 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 12 Aug 2019 23:01:36.524 Module 'ai' loaded from /usr/lib/redis/modules/redisai.so
loaded default MAX_SAMPLE_PER_CHUNK policy: 360
1:M 12 Aug 2019 23:01:36.524 Module 'timeseries' loaded from /usr/lib/redis/modules/redistimeseries.so
1:M 12 Aug 2019 23:01:36.525 RedisGears version 0.3.1, git_sha=be5c5fcdf2abaabe5ff62155d9c38e0ecaa97575
1:M 12 Aug 2019 23:01:36.525 PythonHomeDir:/opt/redislabs/lib/modules/python3
1:M 12 Aug 2019 23:01:36.525 MaxExecutions:1000
1:M 12 Aug 2019 23:01:36.525 ProfileExecutions:0
1:M 12 Aug 2019 23:01:36.525 PythonAttemptTraceback:1
could not initialize RedisAI_GetAPIVersion
1:M 12 Aug 2019 23:01:36.525 # could not initialize RediAI api, running without AI support.
could not initialize RediSearch_CheckApiVersionCompatibility
1:M 12 Aug 2019 23:01:36.525 # could not initialize RediSearch api, running without Search support.
1:M 12 Aug 2019 23:01:36.533 Initializing Python environment with: exec(open('/opt/redislabs/lib/modules/python3/.venv/bin/activate_this.py').read(), {'file': '/opt/redislabs/lib/modules/python3/.venv/bin/activate_this.py'})
1:M 12 Aug 2019 23:01:36.553 Module 'rg' loaded from /opt/redislabs/lib/modules/redisgears.so
1:M 12 Aug 2019 23:01:36.553 * Ready to accept connections
Chasing down why that is being logged. If you're using the default config file, RediSearch is not being loaded and RedisAI was already loaded so you can treat this more as a warning for the moment.
I pull the latest redisedge docker image and run, It prompts "could not initialize RedisAI_GetAPIVersion" at runtime. [root@localhost redisedge]# docker run -p 6379:6379 -v /work/redisedge/data:/data redislabs/redisedge WARNING: IPv4 forwarding is disabled. Networking will not work. 1:C 12 Aug 2019 23:01:36.442 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 1:C 12 Aug 2019 23:01:36.442 # Redis version=5.0.5, bits=64, commit=00000000, modified=0, pid=1, just started 1:C 12 Aug 2019 23:01:36.442 # Configuration loaded 1:M 12 Aug 2019 23:01:36.443 Running mode=standalone, port=6379. 1:M 12 Aug 2019 23:01:36.443 # 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 12 Aug 2019 23:01:36.443 # Server initialized 1:M 12 Aug 2019 23:01:36.443 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. 1:M 12 Aug 2019 23:01:36.443 # 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 12 Aug 2019 23:01:36.524 Module 'ai' loaded from /usr/lib/redis/modules/redisai.so loaded default MAX_SAMPLE_PER_CHUNK policy: 360 1:M 12 Aug 2019 23:01:36.524 Module 'timeseries' loaded from /usr/lib/redis/modules/redistimeseries.so 1:M 12 Aug 2019 23:01:36.525 RedisGears version 0.3.1, git_sha=be5c5fcdf2abaabe5ff62155d9c38e0ecaa97575
1:M 12 Aug 2019 23:01:36.525 PythonHomeDir:/opt/redislabs/lib/modules/python3
1:M 12 Aug 2019 23:01:36.525 MaxExecutions:1000
1:M 12 Aug 2019 23:01:36.525 ProfileExecutions:0
1:M 12 Aug 2019 23:01:36.525 PythonAttemptTraceback:1
could not initialize RedisAI_GetAPIVersion
1:M 12 Aug 2019 23:01:36.525 # could not initialize RediAI api, running without AI support.
could not initialize RediSearch_CheckApiVersionCompatibility
1:M 12 Aug 2019 23:01:36.525 # could not initialize RediSearch api, running without Search support.
1:M 12 Aug 2019 23:01:36.533 Initializing Python environment with: exec(open('/opt/redislabs/lib/modules/python3/.venv/bin/activate_this.py').read(), {'file': '/opt/redislabs/lib/modules/python3/.venv/bin/activate_this.py'})
1:M 12 Aug 2019 23:01:36.553 Module 'rg' loaded from /opt/redislabs/lib/modules/redisgears.so
1:M 12 Aug 2019 23:01:36.553 * Ready to accept connections