On Tue, Feb 12, 2019 at 11:17 PM, Chris Lamb <la...@debian.org> wrote:
Hi Pirate,
Initially I tried editing /lib/systemd/system/redis-server.service
and
later I edited /lib/systemd/system/redis-server\@.service as well
(edited both these files)
> b) Exactly how you are editing the shipped .service file.
I tried adding changing true to false initially, then adding # in
front
of the options
Ah, so you are not using:
systemctl edit --full
You are likely not actually testing the service file you believe
you are, leading to a misleading report. You might need a "systemctl
daemon-reload" too.
I did daemon-reload, systemctl does not allow to start redis without
daemon-reload if service file changed on disk.
apparmor was at 2.11.1-4, updating it to 2.13.2-7 fixed the above
error, but redis still can't be started like before (same error
message) even after stopping apparmor on the host.
^^^^^^^^
Don't you mean disabled with aa-disable or something? I'm not 100%
certain but simply stopping the service may not be enough. A reboot
with the service disabled, etc. might be what is needed (perhaps
consult the Debian Wiki on this?)
(ie. I don't think you can rule out apparmor either just yet.)
yes, culprit is apparmor only. After aa-teardown, I can start redis
service.
pravi@nishumbha:~$ sudo aa-teardown
Unloading AppArmor profiles
pravi@nishumbha:~$ sudo ss-status
sudo: ss-status: command not found
pravi@nishumbha:~$ sudo aa-status
apparmor module is loaded.
0 profiles are loaded.
0 profiles are in enforce mode.
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
