On 10 September 2014 10:11, Aled Parry <aled.skyrail@xxxxxxxxx> wrote:
> On 10 September 2014 09:36, dE <de.techno@xxxxxxxxx> wrote:
>>
>>
>> Do you have any DNS names in your firewall rules?
>>
>
> I don't, the setup is quite basic actually with a single zone (public)
> with two services in it (/etc/firewalld/zones/public.xml):
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> <?xml version="1.0" encoding="utf-8"?>
> <zone>
> <short>Public</short>
> <description>For use in public areas...</description>
> <service name="dhcpv6-client"/>
> <service name="ssh"/>
> </zone>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Which are both using the default service XML files found in
> /usr/lib/firewalld/services
>
> Thanks,
Well to help anyone else who may have this issue in the future, I
asked in the #centos channel and JHogarth solved it pretty quickly.
< JHogarth> Skyrail: systemctl stop firewalld ; pkill -f firewalld ;
systemctl start firewalld
< JHogarth> Skyrail: for future reference I find it useful to do a ps
-efc and look for the process if it fails to start
< JHogarth> systemd didn't know about the process that it didn't start
in the first place of course
So running those commands stops the firewall, kills the firewalld
process and restarts it using systemctl so it has full control again.
Makes sense when someone points it out to you!
Thanks to JHogarth for that, hopefully someone else will find this
useful in the future.
--
Aled Parry
aled.skyrail@xxxxxxxxx
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
