You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When netatalk starts up and has to detect its DSI interface:
Jan 18 16:47:56.523427 afpd[7935] {afp_config.c:221} (debug:AFPDaemon): DSIConfigInit: hostname: net101, listen: -, interfaces: -, port: 548
Jan 18 16:47:56.531404 afpd[7935] {dsi_tcp.c:497} (info:DSI): dsi_tcp_init: getaddrinfo 'net101': No address associated with hostname
Jan 18 16:47:56.531592 afpd[7935] {dsi_tcp.c:287} (info:DSI): dsi_tcp: '192.168.64.10:548' on interface 'wm0' will be used instead.
Jan 18 16:47:56.531671 afpd[7935] {fault.c:123} (severe:Default): ===============================================================
Jan 18 16:47:56.531710 afpd[7935] {fault.c:124} (severe:Default): INTERNAL ERROR: Signal 11 in pid 7935 (4.0.6)
Jan 18 16:47:56.531749 afpd[7935] {fault.c:125} (severe:Default): ===============================================================
Jan 18 16:47:59.587638 netatalk[16057] {afp_mdns.c:251} (error:AFPDaemon): Failed to add service: _afpovertcp._tcp, error=-65563
Jan 18 16:47:59.587755 netatalk[16057] {netatalk.c:515} (note:Default): Registered with Zeroconf
Jan 18 16:47:59.589098 netatalk[16057] {netatalk.c:225} (info:Default): child[7935]: killed by signal 6
This crash has recently started appearing in my NetBSD 10.0 and 10.1 VMs, with any recent version of netatalk (including Hauke's netatalk4 pkgsrc package.) This didn't happen before with the exact same setup, so something else must have changed environmentally.
When setting f.e. afp interfaces = wm0 in afp.conf, netatalk will start up fine.
The text was updated successfully, but these errors were encountered:
When netatalk starts up and has to detect its DSI interface:
This crash has recently started appearing in my NetBSD 10.0 and 10.1 VMs, with any recent version of netatalk (including Hauke's netatalk4 pkgsrc package.) This didn't happen before with the exact same setup, so something else must have changed environmentally.
When setting f.e.
afp interfaces = wm0
in afp.conf, netatalk will start up fine.The text was updated successfully, but these errors were encountered: