Good morning everyone . I did some man-ing and goggling , but maybe someone can help and point me in the right direction.
On my fed 18 workstation I was having troubles , my first thought was to look at my logs.. I found i had no way to output logs from firewall d
Would someone point out my short comings / acknowledge my blonde moment ? p.s it was not a firewalld / iptables issue if you care . but it got me thinking how do i trouble shoot ..!!
Thanks, Tom
Hi,
On 02/07/2013 01:57 PM, Greaser, Tom wrote:
Good morning everyone . I did some man-ing and goggling , but maybe someone can help and point me in the right direction.
On my fed 18 workstation I was having troubles , my first thought was to look at my logs.. I found i had no way to output logs from firewall d
Firewalld logs into /var/log/firewalld There are no debug messages by default. If you want to enable debug messages you have to add --debug or even --debug=2 command line option to firewalld.
On Fedora this can be generally done 2 ways: Because Fedora has been using systemd, take a look into /usr/lib/systemd/system/firewalld.service there you'll see ExecStart=/usr/sbin/firewalld --nofork $FIREWALLD_ARGS which tells systemd how to run firewalld
so you can either - cp /usr/lib/systemd/system/firewalld.service /etc/systemd/system see [1] - edit /etc/systemd/system/firewalld.service - add --debug to ExecStart= line so it looks like ExecStart=/usr/sbin/firewalld --nofork --debug=2 - systemctl --system daemon-reload - service firewalld restart
or - edit /etc/sysconfig/firewalld - add --debug=2 to FIREWALLD_ARGS variable so it looks like FIREWALLD_ARGS=--debug=2 - service firewalld restart
-- Jiri
[1] http://www.freedesktop.org/wiki/Software/systemd/FrequentlyAskedQuestions
Many thanks Jiri !!!
Thanks, Tom For current list of network alerts please visit. http://www.hsc.wvu.edu/its/Help/Alerts.aspx ________________________________________ From: firewalld-users-bounces@lists.fedorahosted.org [firewalld-users-bounces@lists.fedorahosted.org] On Behalf Of Jiri Popelka [jpopelka@redhat.com] Sent: Thursday, February 07, 2013 8:25 AM To: Firewalld users discussion list Subject: Re: Firewalld logging
Hi,
On 02/07/2013 01:57 PM, Greaser, Tom wrote:
Good morning everyone . I did some man-ing and goggling , but maybe someone can help and point me in the right direction.
On my fed 18 workstation I was having troubles , my first thought was to look at my logs.. I found i had no way to output logs from firewall d
Firewalld logs into /var/log/firewalld There are no debug messages by default. If you want to enable debug messages you have to add --debug or even --debug=2 command line option to firewalld.
On Fedora this can be generally done 2 ways: Because Fedora has been using systemd, take a look into /usr/lib/systemd/system/firewalld.service there you'll see ExecStart=/usr/sbin/firewalld --nofork $FIREWALLD_ARGS which tells systemd how to run firewalld
so you can either - cp /usr/lib/systemd/system/firewalld.service /etc/systemd/system see [1] - edit /etc/systemd/system/firewalld.service - add --debug to ExecStart= line so it looks like ExecStart=/usr/sbin/firewalld --nofork --debug=2 - systemctl --system daemon-reload - service firewalld restart
or - edit /etc/sysconfig/firewalld - add --debug=2 to FIREWALLD_ARGS variable so it looks like FIREWALLD_ARGS=--debug=2 - service firewalld restart
-- Jiri
[1] https://console.mxlogic.com/redir/?178IfCzBWXxJMQsCzBVVd5US02tz_EvgHeGT00sci... _______________________________________________ firewalld-users mailing list firewalld-users@lists.fedorahosted.org https://console.mxlogic.com/redir/?hOb3VEVuKUrsd79EVuujhudAVPmEBC7OFeDe-xmeA...
firewalld-users@lists.fedorahosted.org
-
Greaser, Tom -
Jiri Popelka