/
Redis and Opmantek Applications
Redis and Opmantek Applications
Redis is currently an optional dependency for opEvents and the real-time events feature.
Check if the process is running
ps -ef | grep redis root 3272 32083 0 11:18 pts/3 00:00:00 grep redis redis 30666 1 0 08:32 ? 00:00:06 /usr/bin/redis-server 127.0.0.1:6379
Check the Redis Version
redis-server -v redis server v=3.2.6 sha=00000000:0 malloc=jemalloc-3.6.0 bits=64 build=36cfef259bdc87c
Check if you can connect to redis using redis-cli
You can find your redis password in "/etc/redis/redis.conf" and look for requirepass
redis-cli -a myUnguessablePazzzzzword123 ping PONG
The server should respond with PONG
For more details on the redis cli please see https://redis.io/topics/rediscli
Check the password between both applications
Find the redis password in "/etc/redis/redis.conf" and find the value set under requirepass
Find the redis password "/usr/local/omk/conf/opCommon.json" and find the value under redis_password
They need to be the same for our applications to connect.
If you change either password, both redis, omkd and opeventsd will need to be restarted.
Check if OMK applications can connect to Redis
Browse to https://example.com/en/omk/opCore/redisinfo
, multiple selections available,
Related content
opEvents Realtime Events
opEvents Realtime Events
More like this
opEvents Configuration Settings
opEvents Configuration Settings
More like this
Create remote event
Create remote event
More like this
opEvents - Solution Guide - System Configuration for a Production Environment
opEvents - Solution Guide - System Configuration for a Production Environment
More like this
opEvents 2 Getting Started
opEvents 2 Getting Started
More like this
Opmantek Synergy - opEvents Triggers opConfig to Collect Targeted Diagnostic Data
Opmantek Synergy - opEvents Triggers opConfig to Collect Targeted Diagnostic Data
More like this