netatalk / Bugs / #670 INTERNAL ERROR: Signal 11 after upgrade from 3.1.12 -> 3.1.13

Same problem here, but no ldap_auth enabled...
I am running Red Hat Enterprise Linux release 8.5 (Ootpa)

[root@galileo ~]# rpm -qa | grep netatalk
netatalk-3.1.13-1.el8.x86_64

Apr 11 18:11:12 galileo afpd[9338]: ===============================================================
Apr 11 18:11:12 galileo afpd[9338]: INTERNAL ERROR: Signal 11 in pid 9338 (3.1.13)
Apr 11 18:11:12 galileo afpd[9338]: ===============================================================
Apr 11 18:11:12 galileo afpd[9338]: PANIC: internal error
Apr 11 18:11:12 galileo afpd[9338]: BACKTRACE: 12 stack frames:
Apr 11 18:11:12 galileo afpd[9338]:  #0 /lib64/libatalk.so.18(netatalk_panic+0x39) [0x7fd777de0099]
Apr 11 18:11:12 galileo afpd[9338]:  #1 /lib64/libatalk.so.18(+0x421e0) [0x7fd777de01e0]
Apr 11 18:11:12 galileo afpd[9338]:  #2 /lib64/libc.so.6(+0x37400) [0x7fd774d30400]
Apr 11 18:11:12 galileo afpd[9338]:  #3 /lib64/libatalk.so.18(+0x1ac40) [0x7fd777db8c40]
Apr 11 18:11:12 galileo afpd[9338]:  #4 /lib64/libatalk.so.18(ad_open+0x4c6) [0x7fd777dba086]
Apr 11 18:11:12 galileo afpd[9338]:  #5 /usr/sbin/afpd(+0x3255e) [0x55c31849c55e]
Apr 11 18:11:12 galileo afpd[9338]:  #6 /usr/sbin/afpd(+0x332b5) [0x55c31849d2b5]
Apr 11 18:11:12 galileo afpd[9338]:  #7 /usr/sbin/afpd(afp_openvol+0x361) [0x55c31849da81]
Apr 11 18:11:12 galileo afpd[9338]:  #8 /usr/sbin/afpd(afp_over_dsi+0x67e) [0x55c31847b2ee]
Apr 11 18:11:12 galileo afpd[9338]:  #9 /usr/sbin/afpd(main+0x9b8) [0x55c318479188]
Apr 11 18:11:12 galileo afpd[9338]:  #10 /lib64/libc.so.6(__libc_start_main+0xf3) [0x7fd774d1c493]
Apr 11 18:11:12 galileo afpd[9338]:  #11 /usr/sbin/afpd(_start+0x2e) [0x55c3184794ce]

Last edit: Tobias N. Sasse 2022-04-11

I have the exact same issue on Debian (bookworm, latest updates applied today), Linux 5.16.0-6-amd64, netatalk version 3.1.13~ds-1.

Configuration as follows:

[Global]

[XXXX Time Machine]
path = /daten/timemachine/XXXX/
time machine = yes
valid users = XX
vol size limit = 2400000


[YYYY Time Machine]
path = /daten/timemachine/YYYY/
time machine = yes
valid users = YY
vol size limit = 1400000

[Public]
path = /daten/public
valid users = XX YY
force user = YY

[Daten]
path = /daten
valid users = XX

Seiji NAKAMURA - 2022-04-16

I am having the same problem, Netatalk 3.1.12 to version 3.1.13 via the EPEL repository and now I can't log in.

===============================================================
Apr 13 16:56:56.035511 afpd[9724] {fault.c:124} (severe:Default): INTERNAL ERROR: Signal 11 in pid 9724 (3.1.13)
Apr 13 16:56:56.035514 afpd[9724] {fault.c:125} (severe:Default): ===============================================================
Apr 13 16:56:56.035598 afpd[9724] {fault.c:96} (severe:Default): PANIC: internal error
Apr 13 16:56:56.035602 afpd[9724] {fault.c:97} (severe:Default): BACKTRACE: 12 stack frames:
Apr 13 16:56:56.035604 afpd[9724] {fault.c:103} (severe:Default): #0 /lib64/libatalk.so.18(netatalk_panic+0x39) [0x7f7574ebe099]
Apr 13 16:56:56.035606 afpd[9724] {fault.c:103} (severe:Default): #1 /lib64/libatalk.so.18(+0x421e0) [0x7f7574ebe1e0]
Apr 13 16:56:56.035609 afpd[9724] {fault.c:103} (severe:Default): #2 /lib64/libc.so.6(+0x37400) [0x7f7571e0e400]
Apr 13 16:56:56.035611 afpd[9724] {fault.c:103} (severe:Default): #3 /lib64/libatalk.so.18(+0x1ac40) [0x7f7574e96c40]
Apr 13 16:56:56.035613 afpd[9724] {fault.c:103} (severe:Default): #4 /lib64/libatalk.so.18(ad_open+0x4c6) [0x7f7574e98086]
Apr 13 16:56:56.035615 afpd[9724] {fault.c:103} (severe:Default): #5 /usr/sbin/afpd(+0x3255e) [0x563d4954355e]
Apr 13 16:56:56.035617 afpd[9724] {fault.c:103} (severe:Default): #6 /usr/sbin/afpd(+0x332b5) [0x563d495442b5]
Apr 13 16:56:56.035619 afpd[9724] {fault.c:103} (severe:Default): #7 /usr/sbin/afpd(afp_openvol+0x361) [0x563d49544a81]
Apr 13 16:56:56.035621 afpd[9724] {fault.c:103} (severe:Default): #8 /usr/sbin/afpd(afp_over_dsi+0x67e) [0x563d495222ee]
Apr 13 16:56:56.035624 afpd[9724] {fault.c:103} (severe:Default): #9 /usr/sbin/afpd(main+0x9b8) [0x563d49520188]
Apr 13 16:56:56.035626 afpd[9724] {fault.c:103} (severe:Default): #10 /lib64/libc.so.6(__libc_start_main+0xf3) [0x7f7571dfa493]
Apr 13 16:56:56.035628 afpd[9724] {fault.c:103} (severe:Default): #11 /usr/sbin/afpd(_start+0x2e) [0x563d495204ce]

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Francis - 2022-04-25

Same issue

Apr 25 19:23:03.249120 afpd[5307] {auth.c:235} (note:AFPDaemon): Login by backups (AFP3.4)
Apr 25 19:23:03.268576 afpd[5307] {fault.c:123} (severe:Default): ===============================================================
Apr 25 19:23:03.269008 afpd[5307] {fault.c:124} (severe:Default): INTERNAL ERROR: Signal 11 in pid 5307 (3.1.13)
Apr 25 19:23:03.269198 afpd[5307] {fault.c:125} (severe:Default): ===============================================================

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

esvaf - 2022-04-27

Same problem on Centos 7 with netatalk 3.1.13 from EPEL

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Seiji NAKAMURA - 2022-05-23

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263743#c9

Fixed in 3.1.13_2.

I hope epel will be supported soon.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Seiji NAKAMURA - 2022-05-25

https://centos.pkgs.org/8/epel-x86_64/netatalk-devel-3.1.13-1.el8.x86_64.rpm.html

In EPEL Testing on CentOS8, the
netatalk-devel-3.1.13-3.el8.x86_64.rpm
is testing, and after adding it, I was able to log in!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

NikoGeschka - 2022-05-29

3.1.13-3 Fixed it. Yeah.....

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Seiji NAKAMURA - 2022-05-29

I am able to log in, but starting with InDesignCS6, I am unable to save to the server or suddenly encounter cases of unmounting. When I looked at the log, I found the following error

cat /var/log/netatalk.log

invalid metadata EA this is now being treated as a fatal error.

if you see this log entry, please file a bug ticket with your upstream vendor and attach the generated core file.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

NikoGeschka - 2022-05-29

Yes, get same error.

May 29 13:12:47.905393 afpd[16493] {ad_open.c:821} (error:ad): ad_header_read_ea("/backup/TimeMachine"): invalid metadata EA this is now being treated as a fatal error. if you see this log entry, please file a bug ticket with your upstream vendor and attach the generated core file.
May 29 13:12:47.905432 afpd[16493] {ad_open.c:1283} (error:ad): ad_open_hf_ea: unexpected: Invalid argument

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Daniel Markstedt - 2023-02-11

3.1.14 has been released recently https://github.com/Netatalk/Netatalk/releases/tag/netatalk-3-1-14

Please test if your errors persist with this version.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Daniel Markstedt - 2023-02-12

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

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Daniel Markstedt - 2023-02-12

status: open --> closed

Group: -->
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

INTERNAL ERROR: Signal 11 after upgrade from 3.1.12 -> 3.1.13

Group

Searches

Help

#670 INTERNAL ERROR: Signal 11 after upgrade from 3.1.12 -> 3.1.13

Related

Discussion