Howard Miller

Thought this sounded familiar

I've never used cPanel, so I cannot comment on that.

Every time I have used Redis it has been via TCP/IP. So, like the instructions say, I would expect to see something like 127.0.0.1:6379 (or whatever IP it lives on). But the Redis extension documents imply that the socket address should be an option. BUT... I have never tried it and I don't know if anybody else has with Moodle. So, if you choose to do that then you are entirely on your own.

I'm also concerned that you are attemting to get BOTH Redis sessions and Redis Caches working at the same time. For the avoidance of confusion, I would pick one and concentrate on that. There's nothing wrong with setting up both but they are completely unrelated. So it makes sense (to me) to approach them one at a time.

From Redis_cache_store...

 

 

 

 

Ok - so you've configred Redis for sessions in config.php. It sounds like that is what's causing you the problems.

 

I'm somewhat surprised that you gave a socket path for the redis_host. I would expect a network hostname. Why do you think giving a filepath should work? 

Again, on the MUC page, that still isn't the final step. You would then need to edit the mappings to point cache stores to Redis. Did you do that?

I should mention "Session caches" on the MUC page are nothing whatever to do with session storage that you set up in config.php. I've seen this cause confusion many times. It just means a session store that lasts the lifetime of the session. They could have come up with a better name.

A 500 error will be logged *somewhere*. Check your web server error log. If it's not logged then something is wrong with your logging configuration. A 500 error just says "it went wrong" and is little or no help.