STATUS=daemon 'smbd' finished starting up and ready to serve connectionscreate_connection_session_in

[JJT211]

I just recently started getting this error and after a bit of trial and error I think I got it to go away. The error would pop up anytime I accessed my CIFS share.

I had openvpn installed in a jail but im not quite completely finished configuring the service. I had it turned off but I took one of the FreeNAS updates and when the system rebooted it autostarted the jail. I turned off CIFS, deleted Windows share in GUI, stopped the openvpn jail, recreated Windows share, and restarted CIFS. So far so good.

Oops, had allow guest access checked for some reason.

 

[JJT211]

Set them up the usual way - GUI -> Shares -> set preferences

Only change I made was unchecking the hostnames lookups as suggested by a friend of mine. I'll attach a screen of the CIFS settings...

If you unchecked "hostname lookups", you should also uncheck "local master browser". Restart CIFS service.

From documentation

Local Master - determines whether or not the system participates in a browser election; should be disabled when network contains an AD or LDAP server and is not necessary if Vista or Windows 7 machines are present

http://doc.freenas.org/9.3/freenas_services.html#cifs

And BTW, you should definitely be updating your FreeNAS through the GUI since you're on 9.3. Your storage/data/HD's are completely separate from the actual FreeNAS OS (which is located on your usb flash drive). Which means your FreeNAS OS can completely crash, but your data would remain unaffected. You can always revert back to a previous system version if you have any issues with an upgrade anyway.

 

[ShinobiX9X]

Hello,

maybe someone can help, i have the exact same message, everything seems to work though.

it's an intel cpu, and the hostnames lookup is checked.
if you need a log or something, i'll give it right away

thanks in advance

 

[JJT211]

Uncheck both "Hostname lookups" and "local master browser". Restart CIFS

See my post above which references documentation and explains why.

I know you prob dont want to hear this, but if everything is working fine, then dont worry about it. Trust me, its way more trouble than ita worth. I cant count how many hours ive spent on small insignificant probs like this to only screw everything up and cause even more probs that do effect performance.

Theres even a chance that the error is just some minor glitch with FreeNAS itself that can only be fixed by an update.

It may be something minor with your permissions. Just make sure that every device that accesses your CIFS shares has a user account.

 

[ShinobiX9X]

Ok, thanks a lot for the quick response

 

[Crotalus]

UPDATE:

Ok... so this IS still an issue.. but not continuous.

New error message reads as follows:

STATUS=daemon 'smbd' finished starting up and ready to serve connectionsget_ea_dos_attribute: Cannot get attribute from EA on file ./..: Error = Operation not supported.


Does anyone know what this means or where I should start looking to figure it out?

It is a problem with the Samba configuration file or most likely the way Samba is implemented in FreeNAS . Live with the error messages as it is causing no harm except for the log file. FreeNAS does not give you the option through the GUI to change the config file nor does it support swat. You could try the following in the "global", but don't say I told you.

If you wish to see what the config file looks like run "testparm" from a command line.

The Samba feature to map Windows/DOS specific file attributes onto Unix files and directories depends upon the use of extended file system attributes.

To avoid any mappings of DOS attributes to unix file permissions, use the following in the smb4.conf and it may go away. I didn't tell you to do this. Of course any updates may wipe this off the config file?

ea support = yes
store dos attributes = Yes
map archive = No
map hidden = No
map system = No
map readonly = No

From the Samba forums!

Måtte hell og lykke følge deg.|!

 

[paradoxiom]

It is a problem with the Samba configuration file or most likely the way Samba is implemented in FreeNAS . Live with the error messages as it is causing no harm except for the log file.

I get this too and tried the methods described to fix it and no dice, so thanks for that. However, since changing the options "Local Master: = off'" and "Hostnames lookups: = off" did nothing to fix it, should I put them back on? or if everything works fine without them, should I leave it as it is? it does say hostname lookups is 'expensive' and so as I say if everything works fine with it turned off, just leave it off then? along with local master, or put that back on?

Thanks in advance.

 

[cyberjock]

I'd recommend you read up on what those features do and see if they apply to you. Having those off (or on) is a function of your network and how you want it to function. I could give examples where setting either of those to off or on would be incorrect.

 

[Crotalus]

I get this too and tried the methods described to fix it and no dice, so thanks for that. However, since changing the options "Local Master: = off'" and "Hostnames lookups: = off" did nothing to fix it, should I put them back on? or if everything works fine without them, should I leave it as it is? it does say hostname lookups is 'expensive' and so as I say if everything works fine with it turned off, just leave it off then? along with local master, or put that back on?

Thanks in advance.

Sorry for not getting back soon. I was doing some reading from the posts on the forum. When I attempted to do a search a screen came up with the following;

"401 Unauthorized
Your IPaddress is temporarily locked out due to DOS attempts."

I must have offended someone by reading to much information. It is now working again.

Put things back the way it was. As I said earlier the only problem appears to be excess writes to the log file and some extra CPU cycles. I don't know if FreeNAS uses the boot drive for the log files or that they are stored on the RAID drives. After some research I have found that other uses of Samba version 4 have had some problems. Samba version4 added an active directory domain controller while Version 36 does not have that capability. FreeNAS uses, at least on mine;

From "pkg info"
samba-nsupdate-9.8.6_1 nsupdate utility with GSS-TSIG support
samba41-4.1.18 Free SMB/CIFS and AD/DC server and client for Unix

From "pkg version"
samba-nsupdate-9.8.6_1 =
samba41-4.1.18 =

On the FreeBSD ports site there are four Samba versions available, Samba36, Samba4, Samba41, and Samba42. People with Samba36 have not reported any problems except for the way they have set up the config file. Lots of problems with Samba4's reported. Samba4 added the active directory for a

You can spend a lot of time chasing problems that have no real impact on the way the system works. So don't fret over it.

 

[Black Ninja]

You are not the only one with this problem. In fact everybody should have it, because is not related to what hardware you use it. I can setup a freenas in as virtual machine in ESXI 5.5 and it will do exactly these message when you access you share. I try realy hard to find out why, ask about it , read about it , but no luck.
Here are some facts:
When you make new install of freenas everything set by default and access cifs share you get the hostname lookup mismatch errors. When you remove "hostname lookups" then you get the E/a DOS attributes errors. Yes they are not related , but that's what happens.

I challenge anybody who claims his freenas works without these errors on CIFS share with default settings.


P.S. I run "clean"freenas no jails , no nothing, everything on default settings as much as possible.

P.S. I am very annoyed about this issue , If IX systems people offer paid support I'll be happy go try their help ?!

 

[SweetAndLow]

My cifs server is default and I don't have any errors. My network users dnsmasq so my hostname lookups with and I don't know what you are taking about with your ea errors. Maybe your client has attributes set that are not supported.

 

[Black Ninja]

My cifs server is default and I don't have any errors. My network users dnsmasq so my hostname lookups with and I don't know what you are taking about with your ea errors. Maybe your client has attributes set that are not supported.

My dns is unbound with pfsense, but I had the "hostname lookup mismatch error" long before that with my other shelf router.

Is your CIFS share set with "local master=on" and "Hostnames lookups=on" ?

P.S. I am not sure if this matters but I left my freenas cifs share to be Share type = unix share and permissions=unix ,this was by default but I don't see anything wrong to use unix permissions.

 

[SweetAndLow]

Local master, hostname lookup and UNIX permissions with freenas 9.3 is my setup.

I also use Windows homes share as well as normal shares.

If you got the hostname error then your DNS must be goofed in some way. Could always try manually resolving the names from freenas to see how it's working.

 

[Black Ninja]

You have Unix permission on the dataset too, but what about the "Share type" on the dataset ? I have this option left on by default "share type=UNIX" .
I don't even know what difference this option make , the freenas manual doesn't say much either except :"set it to windows if used on windows share"

You mean you use Windows Homegroup sharing , and regular password sharing I assume ? Do you access freenas by hostname, does your windows login match the freenas login and do you save your credentials in Windows for freenas ?