samba4.Samba4Alert

[soleilblanc]

Hello Freenasers!

I've been running freenas for over a year now with very little issues. Now, since my upgrade to 11.1u6, I'm experiencing major slowdowns after 24 hours to the point windows cant connect to my samba shares and it can take up to 30 seconds for ssh shell access (direct, not via webui). So far, I've just rebooted my system twice but before I roll back to u5, wanted some advice.

I have the following in my messages log:

Code:

Sep 12 08:01:41 nas /alert.py: [system.alert:393] Alert module '<samba4.Samba4Alert object at 0x814d4db70>' failed: timed out

approximately 5 minutes after my system bootup.



Appreciating any help



Jon

 

[mvcad]

Try rolling back any windows 10 update on your PC.

 

[soleilblanc]

Rolling back windows patches not really an option, at least not a long term one.

This morning, got the following errors via email notification

Code:

Traceback (most recent call last):
  File "/usr/local/bin/midclt", line 10, in <module>
	sys.exit(main())
  File "/usr/local/lib/python3.6/site-packages/middlewared/client/client.py", line 531, in main
	with Client(uri=args.uri) as c:
  File "/usr/local/lib/python3.6/site-packages/middlewared/client/client.py", line 311, in __init__
	raise e
  File "/usr/local/lib/python3.6/site-packages/middlewared/client/client.py", line 304, in __init__
	self._ws.connect()
  File "/usr/local/lib/python3.6/site-packages/middlewared/client/client.py", line 169, in connect
	rv = super(WSClient, self).connect()
  File "/usr/local/lib/python3.6/site-packages/ws4py/client/__init__.py", line 215, in connect
	bytes = self.sock.recv(128)
socket.timeout: timed out

Also, same behavior this AM, samba shares not accessible and the

Code:

Sep 14 06:17:19 nas /alert.py: [system.alert:393] Alert module '<samba4.Samba4Alert object at 0x814d4ab70>' failed: timed out

Message.

For a change, tried re-starting samba, was able to, i now have access to my shares, but slow. Same thing for shell access, still takes a long time.

Will come back tonight to see if i receive the error 393.

Jon

 

[soleilblanc]

Same error messages, same behavior (timeout on windows shares, long login times via ssh). Rolled back to U5, Problems still occurs.
Found another thread with similar problem https://forums.freenas.org/index.ph...responding-samba4alert-failed-messages.69677/

I have a debug of U6 and U5 if someone want to take a look.

Jon

 

[soleilblanc]

This is solved, at least with my scenario. There was a small bug in freenas (bug 46821) that was causing the error messages, but that was not the root of the problem. I'm running a syncthing jail which use a feature to watch changes on the filesystem. When doing this, i was running out of file descriptors, which was causing all king of weird error messages as well as slowdown. It had over 128000 entries in fstat, which got reduced to 200 after i removed the watcher.

Hope this can help someone else.

Jon