Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Netatalk "Failed to add service: Local name collision" #4

Closed
dideldumthecat opened this issue May 23, 2018 · 0 comments
Closed

Netatalk "Failed to add service: Local name collision" #4

dideldumthecat opened this issue May 23, 2018 · 0 comments

Comments

@dideldumthecat
Copy link
Contributor

With Netatalk 3.1.11 it is not necessary anymore to create the file /etc/avahi/services/afpd.service, because it leads to an error on rebooting in the syslog:

May 22 13:58:12 raspberrypi netatalk[481]: Netatalk AFP server starting
May 22 13:58:12 raspberrypi netatalk[481]: Failed to add service: Local name collision
May 22 13:58:12 raspberrypi netatalk[481]: Registered with Zeroconf

After removing the file and restarting netatalk, the error disappears on reboot.

See

dideldumthecat added a commit to dideldumthecat/raspberrypi-timemachine that referenced this issue May 23, 2018
With netatalk 3.1.11, it is not necessary to create the file
 `/etc/avahi/services/afpd.service` anymore, it leads to an error in the
syslog on rebooting/restarting netatalk:

"Failed to add service: Local name collision"
mr-bt added a commit that referenced this issue May 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant