Bug #4874

Cannot stop CIFS in 9.2.1.5

Added by qubit nano about 1 year ago. Updated 10 months ago.

Status:ResolvedStart date:04/24/2014
Priority:ImportantDue date:
Assignee:Josh Paetzel% Done:

0%

Category:Services
Target version:9.2.1.6-BETA
Seen in:9.2.1.5-RELEASE

Description

Stop CIFS on 9.2.1.x and upgrade to 9.2.1.5. After the upgrade, start CIFS and it instantly turns on. There's usually a 1-2 second wait for me with a loading icon in the web GUI but samba seems to start fine and shares are accessible. Turning CIFS off throws the error "The service could not be stopped". Tested on my box and a clean install of 9.2.1.5 in virtualbox.

All was well in 9.2.1.4.1 and previous. Commit 65b8e7fb looks like the only thing CIFS related that might have done something. No directory services are set up on this box and smb4.conf is the same.

fixup.sh.txt Magnifier (807 Bytes) Josh Paetzel, 04/24/2014 11:10 PM

History

#1 Updated by Josh Paetzel about 1 year ago

  • Category set to Services
  • Status changed from Unscreened to Screened
  • Assignee set to Josh Paetzel
  • Priority changed from Nice to have to Important
  • Target version set to 79

Confirmed. Working on a fix.

#2 Updated by Josh Paetzel about 1 year ago

As a workaround set the Directory Services to Domain Controller via the dropdown in system. Of course leave the Directory Services service off.

#3 Updated by Josh Paetzel about 1 year ago

  • Status changed from Screened to Resolved

38f352e3234aad09d2f139cee3f91e102badf704

Just uncovered a two year old bug in the notifier.

#4 Updated by Josh Paetzel about 1 year ago

Attaching a shell script to hot patch a running system.

#5 Updated by Cyber Jock about 1 year ago

Yep. I just encountered this myself... /sadface

Spent over an hour including destroying a pool(twice) and a factory reset to realize 9.2.1.4.1 is what I'm going to have to use to test my Mini. /facepalm

#6 Updated by Dennis Juhler Aagaard about 1 year ago

After applying the patch, the CIFS service successfully disables when clicking the button. But I am now unable to start the service again. I am on 9.2.1.5-RELEASE-x64 (80c1d35)
Reapplying the patch and reloading the UI will enable the CIFS service instantly again and disabling is again an issue. So the patch needs to be applied every time you need to switch the service.
My FN is setup with authentication to a OpenDirectory, so setting the Directory services to Domain Controller is not an option. :-S

#7 Updated by Michael Preissner 12 months ago

I'm also experiencing the same, coupled with an inability to restart directory services. DS initially came online after I upgraded from 9.2.1.3, but after a reboot it will not start. I use domain authentication for access control to my CIFS shares, so I can't access my shares at all...

#8 Updated by Jim Ekleberry 12 months ago

I too am unable to stop the CIFS service on a new install of FreeNAS-9.2.1.5-RELEASE-x64 (80c1d35).

I am also unable to start Active Directory even though I have unchecked "Local Master" and "Time Server for domain" in case they are related.

#9 Updated by Josh Paetzel 12 months ago

  • Target version changed from 79 to 9.2.1.6-BETA

Have you applied the patch?

#10 Updated by Todd Maurer 12 months ago

Running 9.2.1.5. I'm seeing same problem. CIFS not working. Reboot, still not working. Attempt to disable CIFS service and get the message: "

If I apply the patch I can shut off the CIFS service. Then I can't restart it. I get the message "The service could not be stopped". Apply the patch, and the system hangs on the mount command. Power cycle reboot now I can disable the CIFS service.

Attempts to start the CIFS services get:

May 15 10:24:01 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
May 15 10:24:01 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: zfs list -H -o mountpoint,name
May 15 10:24:01 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: zfs list -H -o mountpoint
May 15 10:24:01 freenas last message repeated 3 times
May 15 10:24:01 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmpjbnnJe -e tdbsam:/var/etc/private/passdb.tdb -s /usr/local/etc/smb4.conf
May 15 10:24:01 freenas notifier: winbindd not running? (check /var/run/samba/winbindd.pid).
May 15 10:24:01 freenas notifier: smbd not running? (check /var/run/samba/smbd.pid).
May 15 10:24:01 freenas notifier: nmbd not running? (check /var/run/samba/nmbd.pid).
May 15 10:24:02 freenas notifier: Performing sanity check on Samba configuration: FAILED

Removing smb4.conf doesn't help. All volumes are set to Windows/MAC type of ACL.

#11 Updated by Cyber Jock 12 months ago

Per request.. here's how you apply this patch on 9.2.1.5:

As root and in SSH do the following commands:

  1. cd /tmp
  2. fetch https://bugs.freenas.org/attachments/download/768/fixup.sh.txt
  3. chmod +x fixup.sh.txt
  4. mv fixup.sh.txt fixup.sh
  5. ./fixup.sh

#12 Updated by wylee kiot 11 months ago

nm just did a fresh install as it was faster than waiting

#13 Updated by Anthony Iam 11 months ago

Thanks, I Just followed these instructions and it worked like a charm.

Cyber Jock wrote:

Per request.. here's how you apply this patch on 9.2.1.5:

As root and in SSH do the following commands:

  1. cd /tmp
  2. fetch https://bugs.freenas.org/attachments/download/768/fixup.sh.txt
  3. chmod +x fixup.sh.txt
  4. mv fixup.sh.txt fixup.sh
  5. ./fixup.sh

#14 Updated by Glen Baars 11 months ago

Worked for me.

#15 Updated by Roland LeBlanc 11 months ago

The above step #4874#note-11 still didn't work for me. I am still unable to start CIFS.

Modified.

I was able to take one other step to get this working. I updated from 9.2.1.0 to 9.2.1.5. I didn't yet choose a System dataset pool, as I just upgraded and didn't know what it was used for yet. I received the warning in the online GUI; but I held back temporarily. I wanted to get everything up and running first, especially CIFS. After setting the System dataset pool; I was able to get it up and running.

Step #4874#note-11 was still in place after setting the System dataset pool. I still had to set Directory Services to Domain Controller in the system settings panel.

#16 Updated by Henry Graterol 10 months ago

After script,I can turn CIFS service on/off from webgui. Script did not restart django after it finished running, it stopped at:

Patching file notifier.py using Plan A...
Hunk #1 succeeded at 699.
done
+ mount -ur /

Had to cancel/stop and do: service django start

Also available in: Atom PDF