Uploaded image for project: 'TrueNAS'
  1. TrueNAS
  2. NAS-103297

Refuse to bind netatalk to invalid IP addresses

    XMLWordPrintable

    Details

      Description

      problem description:

      migrated freenas primary IP to a different subnet.

      in new web UI went to: services -> AFP -> Bind interfaces and selected the new IP address. Note that the old IP address does not show in the UI and can not be deselected.

       

      impact:

      netatalk can't be stopped via the web UI. netatalk process does not respond to SIGTERM. AFP shares are functional, but netatalk is hogging 1 CPU thread at 100%. I am guessing it is trying to bing to the non-existing IP address in a busy beaver fashion.

       

      workaround:

      edit /etc/local/afp.conf

      and remove old ip address from

      afp listen =

       

      CAVEAT: not sure yet whether workaround is stable across reboots of afp

       

      Potential ways to address this: when generating afp.conf double check that IP addresses destined for afp listen are actually available on the system and remove from config database if not.

       

        Attachments

          Attachments

            JEditor

              Activity

                People

                Assignee:
                awalker Andrew Walker
                Reporter:
                stingray Andy Stenger
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: