Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I am trying to set up a NFS server on an AWS instance running SLES11.

After installing nfs-utils, I tried to export a test share. Here is what my /etc/exports file looks like:

/opt/share1 ec2-50-16-224-79.compute-1.amazonaws.com(rw,async)

export -ar returns the following message:

exportfs: internal: no supported addresses in nfs_client
domU-12-31-38-04-7E-02.compute-1.internal:/opt/share1: No such file or directory

Any idea what the no supported addresses error means? Thanks!

share|improve this question

2 Answers 2

I've just had exactly the same problem and it was just a simple matter of starting the nfs service in order to fix it.

share|improve this answer

If I saw these errors, I don't think I'd pay any attention to the no supported addresses error until the other error (No such file or directory) was resolved. Often times, error messages like this come about because one program generated an error, then prints out the actual error from the system - that is, one of the errors is an obtuse repeating of the other.

If you fix the No such file or directory error, I would suggest that the other error would vanish as well. It also states that the error is "internal" which suggests that the true error is the following one.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.