SOLVED AFP issue

[adrianwi]

I've suddendly started getting some afp message in the console, and not sure what's causing this. Upgraded to 9.3 last weekend, so could be related?

Dec 24 10:57:03 freenas1 netatalk[70224]: Restarting 'afpd' (restarts: 120)
Dec 24 10:57:03 freenas1 netatalk[70224]: Restarting 'cnid_metad' (restarts: 120)
Dec 24 10:57:03 freenas1 cnid_metad[71468]: tsockfd_create: no suitable network config localhost:4700
Dec 24 10:57:03 freenas1 afpd[71467]: dsi_tcp_init: no suitable network config for TCP socket
Dec 24 10:57:03 freenas1 afpd[71467]: dsi_tcp_init: no suitable network config for TCP socket
Dec 24 10:57:03 freenas1 afpd[71467]: no suitable network address found, use "afp listen" or "afp interfaces"
Dec 24 10:57:03 freenas1 afpd[71467]: main: no servers configured

I can still connect to the shared datasets, although sometimes have to restart the afp service as my iMac won't connect to freenas through finder (no issues accessing the WUI)

Any ideas?

 

[adrianwi]

A reboot seems to have sorted this out. Just need to work out how to automatically restart all services in my new jails after a reboot. Something to do with rc.conf I think.....

 

[Karl Hubner]

I was observing the same behaviour.

Short of rebooting...
I found a had (at least one)
/usr/local/sbin/cnid_metad -d -F /usr/local/etc/afp.conf
running (even after stopping the AFP Service).

Killing all the cnid_metad processes allowed me to start the AFP Service, again.

 

[MtK]

I was observing the same behaviour.

Short of rebooting...
I found a had (at least one)
/usr/local/sbin/cnid_metad -d -F /usr/local/etc/afp.conf
running (even after stopping the AFP Service).

Killing all the cnid_metad processes allowed me to start the AFP Service, again.

this issue seems to be happening here as well.

and after killing those running processes the AFPd starts, but the network mount is far from stable.
very noticeable with timemachine backup...

 

[Free as in Nas]

Hit the exact same issue. Killing the service and restarting didn't do anything, even when I cleaned up a rogue cnid_metad process mentioned by @Karl Hubner. I ended up doing a full system reboot and worked fine on startup.

 

[jchan94]

is anyone still seeing this issue? Because I'm having a lot of AFP connection issues.

 

[cyberjock]

Most everyone I know has stopped using AFP except for time capsules because Apple is in the process of retiring the protocol in favor of SMB/CIFS.

 

[adrianwi]

And when they do retire it, and change Time Machine to use SMB, so will I :p

 

[jchan94]

Most everyone I know has stopped using AFP except for time capsules because Apple is in the process of retiring the protocol in favor of SMB/CIFS.

So as far as securing the shares, what protocol are you using for OS X machines?

 

[cyberjock]

So as far as securing the shares, what protocol are you using for OS X machines?

I have no OSX machines. I'm not an Apple tool. /zing!

 

[jgreco]

I have no OSX machines. I'm not an Apple tool. /zing!

Perhaps you should be evicted from the thread, then?

 

[cyberjock]

Perhaps you should be evicted from the thread, then? :)

Well, I have no good comeback for that argument.

Wait... I do support for people that use OSX. Does that count? :D

 

[jgreco]

Well, I have no good comeback for that argument.

Wait... I do support for people that use OSX. Does that count? :D

Yeah, it makes you an Apple tool.

 

[cyberjock]

Yeah, it makes you an Apple tool.

/sadpanda

 

[jgreco]

Better than an Apple fool.

 

[proto]

hi,
an old thread but I had the same problem in freenas 9.3.1

Code:

Oct 16 08:04:28 purp netatalk[6441]: Restarting 'afpd' (restarts: 753)
Oct 16 08:04:29 purp afpd[8391]: dsi_tcp_init: no suitable network config for TCP socket
Oct 16 08:04:29 purp afpd[8391]: no suitable network address found, use "afp listen" or "afp interfaces"
Oct 16 08:04:29 purp afpd[8391]: main: no servers configured

I stopped AFP services and reconfigured the service to listen to my main interface address in:

Bind IP Addresses:

and I moved my IP from Available to Selected
then I restarted the service:

Code:

Oct 16 08:04:56 purp notifier: Starting netatalk.
Oct 16 08:04:56 purp netatalk[8915]: Netatalk AFP server starting
Oct 16 08:04:56 purp netatalk[8915]: Registered with Zeroconf
Oct 16 08:04:56 purp cnid_metad[8918]: CNID Server listening on localhost:4700
Oct 16 08:04:57 purp afpd[8917]: Netatalk AFP/TCP listening on 10.1.1.109:548

It's the first time I use netatalk in two decades!

 

[jmas]

Hi. I am experiencing the same problem, using FreeNAS 9.3-STABLE chain.

I found out that there is an open bug about this issue: https://bugs.freenas.org/issues/12967

After restarting the server, afpd binds to the IP address just fine. But at some point it begins to fail.

 

[Spearfoot]

I have this problem, too, running FreeNAS-9.3-STABLE-201604150515

 

[Hassan Aftab]

The same problem; AFP is not able to bind on one of the interfaces and defaults back to the first IP (Native VLAN). Restarting AFP service doesn't solve the problem. Don't want to resolve the problem via a restart, as its not a solution.
Any suggestions?

 

[warriorcookie]

The same problem; AFP is not able to bind on one of the interfaces and defaults back to the first IP (Native VLAN). Restarting AFP service doesn't solve the problem. Don't want to resolve the problem via a restart, as its not a solution.
Any suggestions?
View attachment 17963

I know it's an old issue that keeps getting resurrected, but I just ran into it and this is from earlier this year....

AFP was working just fine for several months, than all of sudden on a reboot it was showing on my network and freenas was showing the "afpd no suitable network config" error discussed in a few posts above.

Solution for me was to stop AFP, edit AFP service, scroll to bottom and the bind IP address was unchecked, I just checked the box for the only one available. Started AFP again and all works fine.

CIFs did the same thing to me at the same time. Same solution.



I have a feeling this is DHCP related. CIFs and AFP survives multiple reboots just fine. But when I loose power in my house and my DHCP/DNS server(pfsense) goes down, then my freenas box gets a new IP address. This doesn't always take out CIF and AFP, but occasionally does and the fix has been the same every time. Once I put this box into production I'll set a static IP and perhaps that will resolve the issue?