[Bug 263743] net/netatalk3: Update to 3.1.13 resulted failures and crashes
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 02 May 2022 22:39:19 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263743 Bug ID: 263743 Summary: net/netatalk3: Update to 3.1.13 resulted failures and crashes Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: marcus@FreeBSD.org Reporter: cyclaero@gmail.com Assignee: marcus@FreeBSD.org Flags: maintainer-feedback?(marcus@FreeBSD.org) I updated net/netatalk3 from the ports to 3.1.13_1,1. I always build netatalk with all options disabled (no dbus, no kerberos, no tcpwrap, no avahi). Since the update, after a successful login from macOS, I see a bunch of error messages in /var/log/messages, like: May 2 19:24:06 server afpd[32094]: ad_header_read_ea("/usr/files"): invalid metadata EA May 2 19:24:06 server afpd[32094]: ad_header_read_ea("/usr/files"): deleted invalid metadata EA ... Besides "/usr/files“, there are other shares, which show the same. When I browse on my Mac into the sub-directories, then each path gives the ... invalid metadata EA/deleted combo. On some not quite specific occasions, the afp daemon crashes: May 2 19:41:59 server afpd[33903]: =============================================================== May 2 19:41:59 server afpd[33903]: INTERNAL ERROR: Signal 11 in pid 33903 (3.1.13) May 2 19:41:59 server afpd[33903]: =============================================================== I reverted netatalk to 3.1.12_4,1, and everything is back to normal. -- You are receiving this mail because: You are the assignee for the bug.