On 2017-01-02 06:16, Tom H wrote:
On Mon, Jan 2, 2017 at 4:03 AM, jdow <j...@earthlink.net> wrote:systemctl unmask firewalld failed.I run "systemctl disable firewalld" before running "systemctl unmask firewalld" because otherwise the logs have the "firewalld is masked" messages.
Thought I did it in that order. But I'm not sure. (stop, disable, unmask.) I believe I also noticed that with it stopped I'd suddenly find a mishmash of my firewall and firewalld's firewall. Firewalld had started back up. So that might have left me in a "smash it over the head" frame of mind. I've discovered with the projects I worked on that if there is a command like mask it would stop, disable, then put a very heavy stone coffin around it. (I'd drive the stake through it, last, only if "uninstall" was indicated.) So it's likely I could have made a rash assumption somewhere. I need to remember that's doing multiple "things" in one command which is not the 'ix way, I suppose.
Did you run "systemctl enable firewalld" after running "systemctl unmask firewalld"? Having to re-install firewalld doesn't make sense.
Indeed, it didn't make sense to me either. I got the same error message that was flopping around in the logs.
{^_^}
