SMB on and off

[ajschot]

Hi all,


Since a while, i think it is since 11.2-U3 i have to disable and enable SMB after a reboot. I don't change anything, it just lookslike the service is not started but just shows me it is starten.
I can not find the SMB in my network until i switch the switch in the service panel to disable and then back to enable.
I have no idea what is wrong, it is still not working well on U5 i know it worked well on U2, then it broke.

In advance: Thanks for your help!

 

[dlavigne]

Anything related in /var/log/messages before you restart the service (that is, when you can't connect to the service)?

Are clients connecting by name, IP, or mapped network drive? Using which operating system version?

 

[ajschot]

I will check the log... i did not know where to find.
I will check the log.

Both don’t work so local name and ip don’t work. If i switch smb in services to disable and switch it back on both types of connections work.
I use mainly mac (mojave and High Sierra) and sometimes Windows 10 (mapped network drive).

 

[ajschot]

this is in my log....

Code:

Sep  6 19:07:27 freenas bridge0: Ethernet address: 02:df:c7:34:6e:00
Sep  6 19:07:27 freenas kernel: bridge0: link state changed to UP
Sep  6 19:07:27 freenas kernel: bridge0: link state changed to UP
Sep  6 19:07:27 freenas kernel: vmx0: promiscuous mode enabled
Sep  6 19:07:27 freenas epair0a: Ethernet address: 02:a3:d0:00:04:0a
Sep  6 19:07:27 freenas epair0b: Ethernet address: 02:a3:d0:00:05:0b
Sep  6 19:07:27 freenas kernel: epair0a: link state changed to UP
Sep  6 19:07:27 freenas kernel: epair0a: link state changed to UP
Sep  6 19:07:27 freenas kernel: epair0b: link state changed to UP
Sep  6 19:07:27 freenas kernel: epair0b: link state changed to UP
Sep  6 19:07:27 freenas kernel: epair0a: promiscuous mode enabled
Sep  6 19:07:27 freenas rtsold[2117]: <rtsock_input_ifannounce> interface epair0b removed
Sep  6 19:07:28 freenas kernel: nd6_dad_timer: cancel DAD on epair0b because of ND6_IFF_IFDISABLED.
Sep  6 19:07:28 freenas kernel: nd6_dad_timer: cancel DAD on epair0b because of ND6_IFF_IFDISABLED.
Sep  6 19:07:30 freenas rtsold[2117]: <rtsock_input_ifannounce> interface epair1a removed
Sep  6 19:07:30 freenas epair1a: Ethernet address: 02:a3:d0:00:05:0a
Sep  6 19:07:30 freenas epair1b: Ethernet address: 02:a3:d0:00:06:0b
Sep  6 19:07:30 freenas kernel: epair1a: link state changed to UP
Sep  6 19:07:30 freenas kernel: epair1a: link state changed to UP
Sep  6 19:07:30 freenas kernel: epair1b: link state changed to UP
Sep  6 19:07:30 freenas kernel: epair1b: link state changed to UP
Sep  6 19:07:30 freenas kernel: epair1a: changing name to 'vnet0:2'
Sep  6 19:07:30 freenas rtsold[2117]: <rtsock_input_ifannounce> interface epair1b removed
Sep  6 19:07:31 freenas kernel: epair1b: changing name to 'epair0b'
Sep  6 19:07:31 freenas kernel: vnet0:2: promiscuous mode enabled
Sep  6 17:07:37 freenas /middlewared[237]: dnssd_clientstub DNSServiceRefSockFD called with invalid DNSServiceRef 0x81f82f720 FFFFFFFF DDDDDDDD
Sep  6 17:07:37 freenas /middlewared[237]: dnssd_clientstub DNSServiceRefSockFD called with invalid DNSServiceRef 0x81f82f720 FFFFFFFF DDDDDDDD
Sep  6 19:07:37 freenas rtsold[2117]: <rtsock_input_ifannounce> interface epair2a removed
Sep  6 19:07:37 freenas rtsold[2117]: <rtsock_input_ifannounce> interface epair2b removed
Sep  6 19:07:37 freenas epair2a: Ethernet address: 02:a3:d0:00:06:0a
Sep  6 19:07:37 freenas epair2b: Ethernet address: 02:a3:d0:00:07:0b
Sep  6 19:07:37 freenas kernel: epair2a: link state changed to UP
Sep  6 19:07:37 freenas kernel: epair2a: link state changed to UP
Sep  6 19:07:37 freenas kernel: epair2b: link state changed to UP
Sep  6 19:07:37 freenas kernel: epair2b: link state changed to UP
Sep  6 19:07:37 freenas kernel: epair2a: changing name to 'vnet0:3'
Sep  6 19:07:37 freenas kernel: epair2b: changing name to 'epair0b'
Sep  6 19:07:37 freenas kernel: vnet0:3: promiscuous mode enabled
Sep  6 19:07:41 freenas rtsold[2117]: <rtsock_input_ifannounce> interface epair3a removed
Sep  6 19:07:41 freenas rtsold[2117]: <rtsock_input_ifannounce> interface epair3b removed
Sep  6 19:07:41 freenas epair3a: Ethernet address: 02:a3:d0:00:07:0a
Sep  6 19:07:41 freenas epair3b: Ethernet address: 02:a3:d0:00:08:0b
Sep  6 19:07:41 freenas kernel: epair3a: link state changed to UP
Sep  6 19:07:41 freenas kernel: epair3a: link state changed to UP
Sep  6 19:07:41 freenas kernel: epair3b: link state changed to UP
Sep  6 19:07:41 freenas kernel: epair3b: link state changed to UP
Sep  6 19:07:41 freenas kernel: epair3a: changing name to 'vnet0:4'
Sep  6 19:07:41 freenas kernel: epair3b: changing name to 'epair0b'
Sep  6 19:07:41 freenas kernel: vnet0:4: promiscuous mode enabled
Sep  6 19:07:45 freenas rtsold[2117]: <rtsock_input_ifannounce> interface epair4a removed
Sep  6 19:07:45 freenas rtsold[2117]: <rtsock_input_ifannounce> interface epair4b removed
Sep  6 19:07:45 freenas epair4a: Ethernet address: 02:a3:d0:00:08:0a
Sep  6 19:07:45 freenas epair4b: Ethernet address: 02:a3:d0:00:09:0b
Sep  6 19:07:45 freenas kernel: epair4a: link state changed to UP
Sep  6 19:07:45 freenas kernel: epair4a: link state changed to UP
Sep  6 19:07:45 freenas kernel: epair4b: link state changed to UP
Sep  6 19:07:45 freenas kernel: epair4b: link state changed to UP
Sep  6 19:07:45 freenas kernel: epair4a: changing name to 'vnet0:5'
Sep  6 19:07:45 freenas kernel: epair4b: changing name to 'epair0b'
Sep  6 19:07:45 freenas kernel: vnet0:5: promiscuous mode enabled
Sep  6 19:07:48 freenas rtsold[2117]: <rtsock_input_ifannounce> interface epair5a removed
Sep  6 19:07:48 freenas rtsold[2117]: <rtsock_input_ifannounce> interface epair5b removed
Sep  6 19:07:48 freenas epair5a: Ethernet address: 02:a3:d0:00:09:0a
Sep  6 19:07:48 freenas epair5b: Ethernet address: 02:a3:d0:00:0a:0b
Sep  6 19:07:48 freenas kernel: epair5a: link state changed to UP
Sep  6 19:07:48 freenas kernel: epair5a: link state changed to UP
Sep  6 19:07:48 freenas kernel: epair5b: link state changed to UP
Sep  6 19:07:48 freenas kernel: epair5b: link state changed to UP
Sep  6 19:07:48 freenas kernel: epair5a: changing name to 'vnet0:6'
Sep  6 19:07:49 freenas kernel: epair5b: changing name to 'epair0b'
Sep  6 19:07:49 freenas kernel: vnet0:6: promiscuous mode enabled
Sep  6 19:37:22 freenas smartd[3124]: System clock time adjusted to the past. Resetting next wakeup time.
Sep  7 00:00:00 freenas syslog-ng[2432]: Configuration reload request received, reloading configuration;
Sep  7 00:00:00 freenas syslog-ng[2432]: Configuration reload finished;
Sep  7 03:45:00 freenas ZFS: vdev state changed, pool_guid=6976102516196825739 vdev_guid=9179145430050208162
Sep  8 00:00:00 freenas syslog-ng[2432]: Configuration reload request received, reloading configuration;
Sep  8 00:00:00 freenas syslog-ng[2432]: Configuration reload finished;

nothing seems to be to do with SMB....
And really the only thing i do is, swich SMB off and bak on again and it works...

 

[dlavigne]

Does this issue persist for you after updating to 11.2-U6?

 

[ajschot]

Does this issue persist for you after updating to 11.2-U6?

Hi Sorry I was dealing with some other problems so I could not get into it..... Yes it is still there even on U6.

I just switch SMB off and on again in services page of Freenas that's all but it is still annoying. Because i don't run my server 24/7 anymore just in the weekend because i did not use it during the rest of the week and also did not a lot of work that must be synced everyday to the server.
So that is why it is a hell to switch it on and off everytime.... strange is that it seems to be only my problem.
Then... ok maybe a config issue, but why is it just switch off and back on the SMB service and it works?

 

[dlavigne]

Please create a report at bugs.ixsystems.com and post the issue number here.

 

[ajschot]

Hi all.... since we are now on 11.3-U1 the problem still occours also tried to make a new VM with a clean FreeNAS install and samething happens...
I already made a bug report but it seems to be i am the only one who can create this problem.... maybe a 6.7 esxi issue or an unlocker issue for macos?
Anyway... if someone please know how to fix this... be my guest... i think a delayed start of the SMB service would do it.

 

[ajschot]

Hey pleas eneed help, this service problem is also on AFP.... i already did a bug report but i am seeming to be the only one with this problem?
I already made a clean install again without copy any config back or what so ever, i got the same problem.
I really have no idea seems to be that the service is loaded so fast that the network is not roght or something... strange that only switching off and on the AFP service and SMB service does the trick. Only thing maybe others don't use it the unlocker 3.0 for esxi to get my macos running but i don't why that would be a problem.... it only is a Apple smc emulator

 

[ajschot]

it seems to be solved, i got a new router because i had issues with 5Ghz WiFi and after replacing the router and loading the settings from the old router it seems to work, so a faulty router. I will have to test some more but 2 times reboot and it seems to work

 

[ajschot]

Tested again ... to bad... was just 1 time...

 

[ajschot]

Guys i need help... i found the problem!
Well... not really the problem but i know when this occours, and i know some of you are really super smart i am still a noob.

This is the situation, i use my nas mainly in the weekends for plex etc and making backups and that kind of stuff.
During the rest of the week i want to have it switched off, which is better for the environment and my wallet ;)
I use a raspberry pi to sent a switch on and of command to my motherboards IPMI.
It is a small script that i have made which login via ssh on the ipmi and then uses a cli command to switch on the machine or switch off.

Apparently thought this works great, and yes it dows power on an poeroff, and when i monitor in esxi it does a soft power off, but for a reason it is still a partly hard shutdown it seems. So when i shutdown FreeNAS and the shut down the machine an power it on again it starts all services the right way so i don't have to restart all services manually.

Is there anybody who has an idea? Is this an IPMI problem or is this an ESXi problem?
Or is there someone using the same sort of setup or dit i made a mistake somewhere?

 

[Samuel Tai]

These are known bugs. The SMB one is fixed in 11.3-U3.1. The AFP one will be fixed in U4.

 

[ajschot]

These are known bugs. The SMB one is fixed in 11.3-U3.1. The AFP one will be fixed in U4.

Ah thank you very much! When i reported the bug almost a year ago i got back that it was unknown and they could not replicate that.
Thank your very very much! This is why it is working suddenly, and yes when i was treying al those things i also did an update to 11.3-U3.1

 

[ajschot]

These are known bugs. The SMB one is fixed in 11.3-U3.1. The AFP one will be fixed in U4.

sorry it is not fixed. Still with a soft shutdown in ipmi of my supermicroboard will give me a not working smb service.
So this ‘fix’ is not working, i will try to fill a bug report but last times i only got back that it was my problem and not a bug, but it really is, i was not clear maybe that i was shutting down via ipmitool

 

[Samuel Tai]

Try updating to U3.2, released a few hours ago.

 

[ajschot]

Try updating to U3.2, released a few hours ago.

ok i will!, i would be so happy! Hope my other annoying issues will be solved one day too

 

[ajschot]

Try updating to U3.2, released a few hours ago.

Just checked... too bad it does not seem to be solved.
seems to be solved i am sooooooo happy! one problem solved!