samba4.Samba4Alert

[tfran1990]

freenas /alert.py: [system.alert:393] Alert module '<samba4.Samba4Alert object at 0x814cc9b70>' failed: Call timeout

the log doesnt tell much.

what does it mean, is it ok?
my system light at the top right is showing green?

 

[Ericloewe]

You might want to file a bug report. Post the issue number here, please.

 

[mvcad]

I am having the same issue. Did you find a solution?

 

[anodos]

Do you have AD monitoring enabled?

 

[anodos]

Okay. That looks like a middleware timeout. I've seen a couple in my logs. There are more efficient and less problematic ways of doing the logical tests in that alert. I'll try to get a PR in tomorrow related to it if I have time. Please update this thread if the error becomes a regular occurrence.

 

[mvcad]

Do you have AD monitoring enabled?

I don't know what that is to be honest. unless it is enabled by default I would say no.

 

[mvcad]

I've found some similar bug here :https://redmine.ixsystems.com/issues/27581, will try later when I get back home.

FYI, I posted my issue here: https://forums.freenas.org/index.php?threads/error-failed-connection-handshake.64237/

you can see a snapshot of my error which occurs every 10 min roughly and my system becomes unresponsive.

 

[mvcad]

Well, I tried the solution posted of the bug above mentioned, although zfs_space, zfsacl and streams_xattr modules were already enabled on all my SMB shares, hence the issue still persists.

 

[mvcad]

These are my error messages

Code:

Jun  8 20:10:46 freenas dhclient: New Subnet Mask (em0): 255.255.255.0		 
Jun  8 20:10:46 freenas dhclient: New Broadcast Address (em0): 192.168.1.255	
Jun  8 20:10:46 freenas dhclient: New Routers (em0): 192.168.1.1				
Jun  8 12:10:46 freenas python3.6: dnssd_clientstub DNSServiceProcessResult call
ed with invalid DNSServiceRef 0x81f41a480 FFFFFFFF DDDDDDDD					 
Jun  8 20:12:47 freenas /alert.py: [system.alert:393] Alert module '<samba4.Samb
a4Alert object at 0x814ccbd30>' failed: Failed connection handshake			 
Jun  8 20:14:25 freenas uwsgi: [plugins.utils:88] Couldn't retrieve https://192.
168.1.66/plugins/plexmediaserver/1/_s/status: The read operation timed out	 
Jun  8 20:14:38 freenas uwsgi: [plugins.utils:88] Couldn't retrieve https://192.
168.1.66/plugins/syncthing/2/_s/status: The read operation timed out			
Jun  8 20:14:52 freenas uwsgi: [plugins.utils:88] Couldn't retrieve https://192.
168.1.66/plugins/nextcloud/3/_s/status: The read operation timed out			
Jun  8 20:19:10 freenas /alert.py: [system.alert:393] Alert module '<samba4.Samb
a4Alert object at 0x814ccbd30>' failed: Failed connection handshake			 
Jun  8 20:25:45 freenas /alert.py: [system.alert:393] Alert module '<samba4.Samb
a4Alert object at 0x814ccbd30>' failed: Failed connection handshake			 
Jun  8 20:31:05 freenas kernel: arp: 192.168.1.66 moved from 02:07:50:00:06:0a t
o 70:85:c2:44:1a:9d on epair1b												 
Jun  8 20:32:17 freenas /alert.py: [system.alert:393] Alert module '<samba4.Samb
a4Alert object at 0x814ccbd30>' failed: Failed connection handshake			 
Jun  8 20:35:22 freenas /alert.py: [system.alert:393] Alert module '<samba4.Samb
a4Alert object at 0x814ccbd30>' failed: Failed connection handshake	   

 

[anodos]

These are my error messages

Code:

Jun  8 20:10:46 freenas dhclient: New Subnet Mask (em0): 255.255.255.0		
Jun  8 20:10:46 freenas dhclient: New Broadcast Address (em0): 192.168.1.255	
Jun  8 20:10:46 freenas dhclient: New Routers (em0): 192.168.1.1				
Jun  8 12:10:46 freenas python3.6: dnssd_clientstub DNSServiceProcessResult call
ed with invalid DNSServiceRef 0x81f41a480 FFFFFFFF DDDDDDDD					
Jun  8 20:12:47 freenas /alert.py: [system.alert:393] Alert module '<samba4.Samb
a4Alert object at 0x814ccbd30>' failed: Failed connection handshake			
Jun  8 20:14:25 freenas uwsgi: [plugins.utils:88] Couldn't retrieve https://192.
168.1.66/plugins/plexmediaserver/1/_s/status: The read operation timed out	
Jun  8 20:14:38 freenas uwsgi: [plugins.utils:88] Couldn't retrieve https://192.
168.1.66/plugins/syncthing/2/_s/status: The read operation timed out			
Jun  8 20:14:52 freenas uwsgi: [plugins.utils:88] Couldn't retrieve https://192.
168.1.66/plugins/nextcloud/3/_s/status: The read operation timed out			
Jun  8 20:19:10 freenas /alert.py: [system.alert:393] Alert module '<samba4.Samb
a4Alert object at 0x814ccbd30>' failed: Failed connection handshake			
Jun  8 20:25:45 freenas /alert.py: [system.alert:393] Alert module '<samba4.Samb
a4Alert object at 0x814ccbd30>' failed: Failed connection handshake			
Jun  8 20:31:05 freenas kernel: arp: 192.168.1.66 moved from 02:07:50:00:06:0a t
o 70:85:c2:44:1a:9d on epair1b												
Jun  8 20:32:17 freenas /alert.py: [system.alert:393] Alert module '<samba4.Samb
a4Alert object at 0x814ccbd30>' failed: Failed connection handshake			
Jun  8 20:35:22 freenas /alert.py: [system.alert:393] Alert module '<samba4.Samb
a4Alert object at 0x814ccbd30>' failed: Failed connection handshake	  

Can you PM me a debug file? I'll take a look at it.

 

[mvcad]

Can you PM me a debug file? I'll take a look at it.

I am generating the debug file right now but it has been more than 30 min already. doe it take that long? anyway, if it ever finishes I'll send it to you. thanks.

Also, the monitor attached to the FreeNAS box show no signal. Is this normal while writing the debug file?

 

[mvcad]

Debug file sent

 

[mvcad]

Problem fixed by rolling back a windows 10 update on my PC. Thanks Microsoft, you made me waste 1 week and rebuild my NAS for nothing.

 

[CH4Pz]

Dont suppose u know which update? im having same issue on 11.1 u6 ??

 

[mvcad]

don't suppose u know which update? im having same issue on 11.1 u6 ??

U5

 

[anodos]

don't suppose u know which update? im having same issue on 11.1 u6 ??

Can you PM me a debug file?

 

[CH4Pz]

U5

sorry i meant which MS update

Can you PM me a debug file?

Yep, will do. i also noticed it using (some, under 1gb) swap util. memory, not sure if related. also getting time outs with jails and loading ui

 

[anodos]

Some instances I've seen of this bug seem to be related to io timeouts on the boot device. If your server isn't already configured this way, try moving your system dataset to your data pool, then rebooting the server.

 

[CH4Pz]

Some instances I've seen of this bug seem to be related to io timeouts on the boot device. If your server isn't already configured this way, try moving your system dataset to your data pool, then rebooting the server.

excuse my noobiness, but how would i do that? can it be done through ui?

 

[CH4Pz]

excuse my noobiness, but how would i do that? can it be done through ui?

nvm, i found it, but it was already set to "Z2_datasaet"