This post is more than 5 years old
1 Rookie
•
19 Posts
0
2327
April 14th, 2015 12:00
Unable to create SMB share with webui
I attempted to create smb share and receive error message:
Your share was not created
Error #1: did not get response from server
I then went to the command line and was able to create my share. A little digging and I found the following:
Resolution: seems the webui service stopped responding to smb calls for some reason. The fix is to run the following command:
isi services isi_webui disable
followed by
isi services isi_webui enable
Share creation was then possible from webui
regards,
No Events found!


Yan_Faubert
117 Posts
1
April 15th, 2015 10:00
There was a step missing from the original README file with this patch. A restart of the isi_gconfig_d process was required but missing from the patch instructions. A new version of the patch was uploaded today with the correct README file.
https://download.emc.com/downloads/DL58024_Isilon_OneFS_Patch-140284.tgz
From the updated README:
b_wade
2 Posts
0
April 14th, 2015 22:00
We had the same issue. the below is from EMC Tech Support. Hope it Helps
I want to inform you that these problems are linked and the patch is available.
This issue is due to a known Product Bug (137885) which is fixed and targeted for 7.1.1.3. The fix is also there in 7.1.1.2 with rollup patch 140284.
In OneFS 7.1.1.0 and later, the share configuration is now stored on each node in a local database in the following location:
/var/ifs/isi_gconfig.db
The main database for the cluster is stored under: /ifs/.ifsvar/isi_gconfig/isi_config.db.dump. It is possible for the revision numbers between the local and global databases to be out of sync. When this occurs the shares cannot be listed, created or modified on individual or multiple nodes.
tsap1
1 Rookie
•
19 Posts
0
April 15th, 2015 10:00
Thanks, that is very interesting. I would like to point out that I am running 7.1.1.2 and have patch 140284 applied already. I had no problem viewing shares, I just couldn't create shares. Looks like the problem still persists even with 140284.
Gabe