I just upgraded my CentOS 7 system from Netatalk 3.1.12 to version 3.1.13 via the EPEL repository.
With version 3.1.13, when I try to connect to the server via AFP and log in with my user it causes a segfault with the following backtrace:
Apr 6 10:46:44 gir afpd[2934]: Login by alien (AFP3.4)
Apr 6 10:46:44 gir afpd[2934]: ===============================================================
Apr 6 10:46:44 gir afpd[2934]: INTERNAL ERROR: Signal 11 in pid 2934 (3.1.13)
Apr 6 10:46:44 gir afpd[2934]: ===============================================================
Apr 6 10:46:44 gir afpd[2934]: PANIC: internal error
Apr 6 10:46:44 gir afpd[2934]: BACKTRACE: 12 stack frames:
Apr 6 10:46:44 gir afpd[2934]: #0 /lib64/libatalk.so.18(netatalk_panic+0x37) [0x7f6e0d891df7]
Apr 6 10:46:44 gir afpd[2934]: #1 /lib64/libatalk.so.18(+0x38f48) [0x7f6e0d891f48]
Apr 6 10:46:44 gir afpd[2934]: #2 /lib64/libc.so.6(+0x36400) [0x7f6e0975b400]
Apr 6 10:46:44 gir afpd[2934]: #3 /lib64/libatalk.so.18(+0x17c40) [0x7f6e0d870c40]
Apr 6 10:46:44 gir afpd[2934]: #4 /lib64/libatalk.so.18(ad_open+0xfee) [0x7f6e0d872c4e]
Apr 6 10:46:44 gir afpd[2934]: #5 /usr/sbin/afpd(+0x31b6c) [0x564d342c6b6c]
Apr 6 10:46:44 gir afpd[2934]: #6 /usr/sbin/afpd(+0x32905) [0x564d342c7905]
Apr 6 10:46:44 gir afpd[2934]: #7 /usr/sbin/afpd(afp_openvol+0x500) [0x564d342c81e0]
Apr 6 10:46:44 gir afpd[2934]: #8 /usr/sbin/afpd(afp_over_dsi+0x58e) [0x564d342a4f7e]
Apr 6 10:46:44 gir afpd[2934]: #9 /usr/sbin/afpd(main+0xd29) [0x564d342a31e9]
Apr 6 10:46:44 gir afpd[2934]: #10 /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f6e09747555]
Apr 6 10:46:44 gir afpd[2934]: #11 /usr/sbin/afpd(+0xe250) [0x564d342a3250]
This happens consistently. I have downgraded back to version 3.1.12 and all works as expected.
I made no changes to my config file between version changes but did look at the release notes. I also looked over the upgrade notes, but since they specifically refer to upgrading from version 2.x and I was doing a minor version update from 3.1.12 to 3.1.13 it didn't appear that any of it was relevant.
As I've said, I've downgraded to 3.1.12 and it's working as expected again, but I prefer to keep software up to date, especially when the updates address security issues so any and all assistance with this will be greatly appreciated.
Please let me know if you need any additional information.
Kind regards,
Alan Premselaar
I am seeing the same issue on Fedora Core 34, downgrading to 3.1.12 fixed it as well. No config changes, local user account.
We expect this to have been fixed with 3.1.14 so let me close this as completed for now. If you still encounter issues after upgrading, please raise a new issue ticket in the GitHub tracker: https://github.com/Netatalk/Netatalk/issues