netatalk
netatalk copied to clipboard
DSI DISCONNECTED endless loop with two IPv4 interfaces
On FreeBSD, if an IFACE has two IPv4 and at the afp.conf we set afp listen parameter to the secondary IPv4, the client after a while can't connect at the afp share anymore.
Making some debugs, what I could see is the following: When the issue happens I can see at the logs a error with a Bad file descriptor: Jan 25 01:46:03.616514 afpd[6413] {socket.c:152} (debug:AFPDaemon): select: Bad file descriptor
And right after the DSI_DISCONNECTED get in a big loop: Jan 25 03:20:14.946287 afpd[10346] {afp_dsi.c:297} (maxdebug:AFPDaemon): alarm: tickles: 163, flags: -|-|-|-|DSI_DISCONNECTED|-|-|-|- Jan 25 03:20:16.977678 afpd[10346] {afp_dsi.c:297} (maxdebug:AFPDaemon): alarm: tickles: 164, flags: -|-|-|-|DSI_DISCONNECTED|-|-|-|- Jan 25 03:20:18.986211 afpd[10346] {afp_dsi.c:297} (maxdebug:AFPDaemon): alarm: tickles: 165, flags: -|-|-|-|DSI_DISCONNECTED|-|-|-|-
it goes till: tickles number 1801.
I'm using the latest version of netatalk3 with FreeBSD 10.3-Stable. If you guys need any more extra debug or information, feel free to ping me back.
Best,
@araujobsd This bug report is quite aged now. Would you be able to test if this still reproduces with the latest Netatalk code?