Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Updated to 2.3 : Error messages when editing firewall rules

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    6 Posts 3 Posters 1.9k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      netsysadmin
      last edited by

      Hello,

      I upgraded to 2.3 from 2.2.6 since about 1 week.
      I noticed that everytime I edit a firewall rule, the following error messages appear on top of the page:

      Warning: dns_get_record(): DNS Query failed in /etc/inc/notices.inc on line 431 Call Stack: 0.0000 230184 1\. {main}() /usr/local/www/firewall_rules_edit.php:0 0.0218 2138312 2\. return_gateway_groups_array() /usr/local/www/firewall_rules_edit.php:325 0.0312 2168512 3\. notify_via_growl() /etc/inc/gwlb.inc:941 0.0314 2174624 4\. dns_get_record() /etc/inc/notices.inc:431 Warning: dns_get_record(): DNS Query failed in /etc/inc/notices.inc on line 431 Call Stack: 0.0000 230184 1\. {main}() /usr/local/www/firewall_rules_edit.php:0 0.0218 2138312 2\. return_gateway_groups_array() /usr/local/www/firewall_rules_edit.php:325 0.0312 2168512 3\. notify_via_growl() /etc/inc/gwlb.inc:941 0.1008 2174624 4\. dns_get_record() /etc/inc/notices.inc:431 Warning: dns_get_record(): DNS Query failed in /etc/inc/notices.inc on line 431 Call Stack: 0.0000 230184 1\. {main}() /usr/local/www/firewall_rules_edit.php:0 0.0218 2138312 2\. return_gateway_groups_array() /usr/local/www/firewall_rules_edit.php:325 0.1513 2174808 3\. notify_via_growl() /etc/inc/gwlb.inc:941 0.1514 2175192 4\. dns_get_record() /etc/inc/notices.inc:431 Warning: dns_get_record(): DNS Query failed in /etc/inc/notices.inc on line 431 Call Stack: 0.0000 230184 1\. {main}() /usr/local/www/firewall_rules_edit.php:0 0.0218 2138312 2\. return_gateway_groups_array() /usr/local/www/firewall_rules_edit.php:325 0.1513 2174808 3\. notify_via_growl() /etc/inc/gwlb.inc:941 0.1791 2175192 4\. dns_get_record() /etc/inc/notices.inc:431 Warning: dns_get_record(): DNS Query failed in /etc/inc/notices.inc on line 431 Call Stack: 0.0000 230184 1\. {main}() /usr/local/www/firewall_rules_edit.php:0 0.0218 2138312 2\. return_gateway_groups_array() /usr/local/www/firewall_rules_edit.php:325 0.1847 2175280 3\. notify_via_growl() /etc/inc/gwlb.inc:941 0.1848 2175664 4\. dns_get_record() /etc/inc/notices.inc:431 Warning: dns_get_record(): DNS Query failed in /etc/inc/notices.inc on line 431 Call Stack: 0.0000 230184 1\. {main}() /usr/local/www/firewall_rules_edit.php:0 0.0218 2138312 2\. return_gateway_groups_array() /usr/local/www/firewall_rules_edit.php:325 0.1847 2175280 3\. notify_via_growl() /etc/inc/gwlb.inc:941 0.1889 2175664 4\. dns_get_record() /etc/inc/notices.inc:431 Warning: dns_get_record(): DNS Query failed in /etc/inc/notices.inc on line 431 Call Stack: 0.0000 230184 1\. {main}() /usr/local/www/firewall_rules_edit.php:0 0.0218 2138312 2\. return_gateway_groups_array() /usr/local/www/firewall_rules_edit.php:325 0.1932 2175280 3\. notify_via_growl() /etc/inc/gwlb.inc:960 0.1933 2175664 4\. dns_get_record() /etc/inc/notices.inc:431 Warning: dns_get_record(): DNS Query failed in /etc/inc/notices.inc on line 431 Call Stack: 0.0000 230184 1\. {main}() /usr/local/www/firewall_rules_edit.php:0 0.0218 2138312 2\. return_gateway_groups_array() /usr/local/www/firewall_rules_edit.php:325 0.1932 2175280 3\. notify_via_growl() /etc/inc/gwlb.inc:960 0.1973 2175664 4\. dns_get_record() /etc/inc/notices.inc:431

      Can this be corrected or should I wait for 2.3.1?

      Thank you

      1 Reply Last reply Reply Quote 0
      • P
        phil.davis
        last edited by

        In System->Advanced, Notifications, check the Growl settings section. In particular there is likely to be some invalid URL string in the IP Address field. Fix it up and those warning messages will go away.

        The warning has been handled better for 2.3.1. This commit: https://github.com/pfsense/pfsense/commit/642c6023fea2957bb646b1290371ead508f5cc67

        If you have fixed up the bad Growl setting, then you probably won't need or care about the underlying fix, but if you do care then you can install the System Patches package and apply the fix from the commit above.

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

        1 Reply Last reply Reply Quote 0
        • N
          netsysadmin
          last edited by

          Hello Phil,

          Sorry for the late reply.
          Actually, I have never used Growl before and don't know much about it.

          The "IP Address" field is blank. If we have to fill it up, which IP address should this be set to?

          1 Reply Last reply Reply Quote 0
          • P
            phil.davis
            last edited by

            No, you don't want anything in any of the Growl settings. Make sure the IP address field really is blank (no blank spaces in there).

            Some people had been on that GUI page in the past, and their browser had pre-filled that IP Address field with a username like "admin". When they pressed save (intending to save something else on the page), it also saved the dud value in IP Address.

            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

            1 Reply Last reply Reply Quote 0
            • C
              cmb
              last edited by

              Yeah, what Phil said. Seems like that field must have something in it (maybe even a stray space or something), otherwise it'd never try to do a growl notification and wouldn't hit that.

              Regardless, the issue's harmless and fixed in 2.3.1. It's safe to ignore in the mean time.

              1 Reply Last reply Reply Quote 0
              • N
                netsysadmin
                last edited by

                Hello all,

                FYI: I have disabled Growl notifications and also the IP address field is blank.

                No issue any more.

                Thanks for your help.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.