SAMBA Sharing not working after update to 11.3

[NAS_warrior]

Hi guys,
I have been out for a while.
Lately I rub the updates on my freenass 11.2 to 11.3 and suddenly my share stop working.
I have tried to google some solution but most of found was pretty old or incomplete as finished with PM's.
Can anyone point me in the right direction where to look for solving this?

 

[anodos]

Hi guys,
I have been out for a while.
Lately I rub the updates on my freenass 11.2 to 11.3 and suddenly my share stop working.
I have tried to google some solution but most of found was pretty old or incomplete as finished with PM's.
Can anyone point me in the right direction where to look for solving this?

11.3 isn't in Beta yet. I recommend staying on 11.2.

 

[anodos]

11.3 has samba 4.10.0 on it right now. I plan to upgrade it to 4.10.1 on Monday (or over the weekend).

 

[NAS_warrior]

Well I am all the time on beta
And fight with some problems
Seems to be some problem with config of the service.
Unfortunately cannot move back to previous version - tried but cannot mount the pool since old version reported missing zpool option like spacemap_v2...

 

[NAS_warrior]

Log shows this:
[2019/04/05 03:22:19] (WARNING) middlewared._loop_monitor_thread():1239 - Task seems blocked: File "/usr/local/bin/middlewared", line 10, in <module>
sys.exit(main())
File "/usr/local/lib/python3.7/site-packages/middlewared/main.py", line 1391, in main
startup_seq_path=startup_seq_path,
File "/usr/local/lib/python3.7/site-packages/middlewared/main.py", line 1309, in run
self.__loop.run_forever()
File "/usr/local/lib/python3.7/asyncio/base_events.py", line 528, in run_forever
self._run_once()
File "/usr/local/lib/python3.7/asyncio/base_events.py", line 1764, in _run_once
handle._run()
File "/usr/local/lib/python3.7/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/local/lib/python3.7/site-packages/middlewared/main.py", line 168, in call_method
result = await self.middleware.call_method(self, message)
File "/usr/local/lib/python3.7/site-packages/middlewared/main.py", line 1117, in call_method
return await self._call(message['method'], serviceobj, methodobj, params, app=app, io_thread=False)
File "/usr/local/lib/python3.7/site-packages/middlewared/main.py", line 1065, in _call
return await methodobj(*args)
File "/usr/local/lib/python3.7/site-packages/middlewared/plugins/etc.py", line 298, in generate_all
await self.generate(name)

Seems something in config males the service fail as cannot find parameter.
Any idea???

 

[anodos]

Issue a service middlewared restart What version are you running of nightlies?

 

[anodos]

can you send me a full copy of middlewared.log

 

[NAS_warrior]

Here you are

 

[NAS_warrior]

Hmm line 3406-3411:
[2019/04/05 03:25:03] (DEBUG) smb_configure.hb_command():67 - Commmand 'unlink' failed on path /var/db/samba4 with ([Errno 1] Operation not permitted: '/var/db/samba4')
[2019/04/05 03:25:03] (DEBUG) smb_configure.setup_samba_dirs():104 - Path still exists. Attemping to rename it
[2019/04/05 03:25:03] (DEBUG) smb_configure.setup_samba_dirs():113 - Attempting to create symlink: /var/db/system/samba4 -> /var/db/samba4
[2019/04/05 03:25:04] (DEBUG) smb_configure.import_local_users():256 - User count in config file and passdb is identical. Bypassing import
[2019/04/05 03:25:04] (DEBUG) middleware.notifier._pipeopen():143 - Popen()ing: /usr/local/bin/net groupmap list
[2019/04/05 03:25:05] (ERROR) EtcService.generate():248 - Failed to render py:smb_configure

Could be some miss-configured access.

 

[anodos]

Run the following commands and tell me if you get errors:

Code:

midclt call notifier.groupmap_list
midclt call group.query
midclt call user.query

 

[NAS_warrior]

hmmm no errors.
Here's log file.

 

[anodos]

Did the attempt to list group mappings return Null?

 

[NAS_warrior]

yep, nul indeed

 

[NAS_warrior]

do you want TV to take look straight?

 

[anodos]

What do you see if you run smbd -i? does samba start?

 

[Anda]

I have since the last few Nightlies the same problem. I rolled back to 11.3-MASTER-201902211003. Maybe the logs will help.

 

[anodos]

It appears to be a regression in samba for handling when the statedir is a symlink. Try setting state directory = /var/db/system/samba4 as an auxiliary parameter under Services->SMB.

 

[anodos]

I just made a PR with a fix here: https://github.com/freenas/ports/pull/294
Samba 4.10 became more strict about checking whether /var/db/samba4 was an actual directory (it's a symlink to /var/db/system/samba4 in FreeNAS). I relaxed that restriction a little.

 

[NAS_warrior]

Great
Advised solution was tested and proved working.
Seems is already implemented in the nightly update
Wow this is great

P.S:
Glad to hear I was on the right path about this dir permissions in the log file. Just I'm not so aware of what you guys mix in this freebsd.

 

[anodos]

Great :)
Advised solution was tested and proved working.
Seems is already implemented in the nightly update :)
Wow this is great :)

P.S:
Glad to hear I was on the right path about this dir permissions in the log file. Just I'm not so aware of what you guys mix in this freebsd.

The final solution will probably be slightly different. I'll change how we're compiling samba so that its state dir is /var/db/system/samba4 rather than /var/db/samba4, and keep the symlink in place for compatibility reasons (or at least avoid surprising people who expect things to be there).