Thank you for pointing me in the right direction with your previous posts.
In case anyone hits this error, here is what solved the problem in my installation.
Check the redis-cache log with:
tail -n50 /home/frappe/frappe-bench/logs/redis-cache.error.log
Brings up this error:
FATAL CONFIG FILE ERROR ***
Reading the configuration file, at line 6 >>> ‘save “”’ Bad directive or wrong number of arguments
Now edit the redis_cache.conf with:
nano /home/frappe/frappe-bench/config/redis_cache.conf
Remove line 6: save “”
sudo supervisorctl status
frappe:frappe-web RUNNING pid 21320, uptime 0:42:54
frappe:frappe-worker RUNNING pid 21319, uptime 0:42:54
frappe:frappe-workerbeat RUNNING pid 21327, uptime 0:42:54
node-socketio RUNNING pid 21344, uptime 0:42:53
redis-async-broker RUNNING pid 21336, uptime 0:42:54
redis-cache FATAL Exited too quickly (process log may have details)
sudo supervisorctl reload
sudo supervisorctl status
frappe:frappe-web RUNNING pid 22460, uptime 0:00:02
frappe:frappe-worker RUNNING pid 22459, uptime 0:00:02
frappe:frappe-workerbeat RUNNING pid 22461, uptime 0:00:02
node-socketio RUNNING pid 22463, uptime 0:00:02
redis-async-broker RUNNING pid 22462, uptime 0:00:02
redis-cache RUNNING pid 22464, uptime 0:00:02
Problem solved.
Interestingly, this problem does not appear on our productive instance of erpnext.
Is the save “” directive a config option from a previous version of redis? Are we running soon into this issue when upgrading the productive system?
Hope this helps someone.