Freenas won't work 100%

[runped]

Hello guys!

I and my work is new to freenas. We are trying to set it up as a Time Machine backup for Mac. So after I have added 11 users and 12 shared folders I can't connect to the shared folders. I can't even connect the Time Machine to the shared folders either.

system:
9.1.0 (Since i just get a error at newer versions)
2-4 GB RM. (Can it be becaus I need 8 GB of RAM)

I hope anyone can help me fast since my work needs this to work fast. In a meeting today they told me they wanted it working yesterday...
(Sorry for my bad english)

 

[Whattteva]

I can't guarantee you that it is memory issue, but low RAM can definitely cause all sorts of instability issues.
Unfortunately, we probably can't tell you what exactly is wrong until you can at least rule low RAM completely out of the picture.

 

[runped]

Thanks for the fast reply whattteva.

I'll order 8GB of RAM and see if my problem disappears.
If it ain't the RAM, what can it be then u think?

 

[Whattteva]

It really depends. Can you at least access the web GUI and the shell?
Also, check /var/log/messages for any errors.

Here's the command, just in case: cat /var/log/messages
If it rolls too fast do: cat /var/log/messages|more
That will let you scroll through it slowly.

 

[runped]

Yes, I can access web GUI and shell.
I can't see any problem when i se the log. But I'm not an expert on Freenas.

The second image is the error I get when I try to connect to the freenas from a mac after a while.

 

[Whattteva]

The first image doesn't seem to show the whole message. If you look at the bottom, it indicates that there are "more" lines. You can scroll it down with the down arrow key.

 

[runped]

Helo, I have scrolled down the message. And this is the eorrrs/warnings I get:

Aug 20 04:30:33 freenas root: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Aug 20 04:30:47 freenas avahi-daemon[2168]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Aug 20 05:44:47 freenas avahi-daemon[5121]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns

And several different IP-adresses that is Invali:
Aug 20 06:10:55 freenas avahi-daemon[5121]: Invalid response packet from host 10.144.8.17.

 

[Whattteva]

I don't see anything particularly bad. Just out of curiosity, are you virtualizing FreeNAS?

 

[runped]

Haha.
No, I'm not.
I'm running it on a HP computer with 16 TB hardDrive ;)
And 4 GB of RAM


From runped05

 

[Whattteva]

While AFP service is on the ON position, execute these commands on your shell and post the outputs:
ps -ax|grep afpd
netstat -an|grep -E '548.*LISTEN$'

 

[runped]

Here is what I got:

 

[Whattteva]

My mistake, don't put a space in between the quote and the number 548. I've updated my previous post to reflect this. Sorry again for the mistake.

 

[runped]

haha
It's Ok.
Here is the new message:

 

[Whattteva]

Service looks fine. I'm guessing it's permissions. Is it viable to use other protocols just to see if those work?

 

[runped]

No, I don't think so.
I'm using LDAP now because I'm making it for several users

 

[Whattteva]

Have you tried creating a new shared folder and allow all permissions for any users and see if that works?
Just trying to see if the service can at least connect anyone.

 

[runped]

Hello.
I can create a share and connect with a user I make myself, but when I make one with LDAP user, I can't access the shared folder.
The error or message I get when I try to login is that it's wrong username og password. (But I tried connecting with my personal username and password)

 

[Whattteva]

Ah I see, so your problem is then LDAP authentication. I'm sorry, unfortunately, I don't know too much about LDAP. Hopefully someone else will jump in.

You may have some luck posting in "User Authentication" forums.

 

[cyberjock]

Do NOT create a thread in another section. This section is appropriate. Unfortunately you're going to find nobody really interested in helping until there is 100% assurance that low RAM isn't the problem with LDAP. Low RAM prevents processes from starting as well as terminating inappropriately, so it can still be your problem.