cache.py not picking up redis settings
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 377
- Forks
- 280
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 10
Description
misp-modules - INFO - Launch MISP modules server from current directory.
misp-modules - WARNING - Helpers failed cache.py due to Redis not running or not installed. Helper will be disabled.
All Redis settings were setup correctly and working, inc in MISP /servers/serverSettings/MISP. Redis is located on another AWS instance. Connectivity ok. Setting REDIS_BACKEND='redis.cache.amazonaws.com', REDIS_PORT=6379 and REDIS_DATABASE=13 in /var/www/MISP/venv/bin/activate did not help.
Edited /etc/systemd/system/misp-modules.service directly and added in the [Service] section
Environment="REDIS_BACKEND=redis.cache.amazonaws.com"
Environment="REDIS_PORT=6379"
Environment="REDIS_DATABASE=0"
run
systemctl daemon-reload
and
systemctl restart misp-modules
no more warning. The issue has bene fixed by editing misp-modules.service
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with cache.py and inspect how it reads Redis settings when misp-modules runs under systemd. Compare that behavior with the environment variables added to /etc/systemd/system/misp-modules.service, then verify the service starts without the cache.py warning and connects to the configured Redis instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python, redis
- Domain
- backend, databases, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100