Thanks for responding so promptly! I'm always impressed with how
efficent and professional the entire Debian team is.
I think I discovered the issue -- Redis Server doesn't work in a
Podman container. It needs to run outside of that (I can get it to
run easily outside of a Podman container).
This report can be closed.
Perhaps the error that "systemctl status redis" shows can be updated
to note that this module doesn't work under containers (if operating
within a container)? I don't know if this will be a difficult thing
to do, but I suspect it could save a lot of time for a lot of Linux
administrators in the future as containerizatin is becoming more
common.
> tags 1108444 + moreinfo
> thanks
>
> Hey Randolf,
>
> Sorry that you're encountering issues. I'm not yet able to diagnose
> the issue with just the information you provided, however:
>
> > * What exactly did you do (or not do) that was effective (or
> > ineffective)?
> >
> > I attempted to run Redis using the "systemctl start redis-server"
> > cammand
> >
> > * What was the outcome of this action?
> >
> > Error messages about the restart count exceeding 5
>
> Where did you see these messages? Can you provide any helpful logging
> info from, say, "journalctl -u redis-server.service" after calling
> "start" again.
>
>
> Regards,
>
> --
> ,''`.
> : :' : Chris Lamb
> `. `'` [email protected] chris-lamb.co.uk
> `-
>
Randolf Richardson, CNA - [email protected]
Inter-Corporate Computer & Network Services, Inc.
Beautiful British Columbia, Canada
https://www.inter-corporate.com/
