Zentyal Forum, Linux Small Business Server
Zentyal Server => Installation and Upgrades => Topic started by: hakunamatata on October 24, 2013, 04:28:55 pm
-
Whenever I try to save a new user for the acces control in the shares or when I change the rights and permissions of the file sharing section, the samba module hangs, it never saves to 100%.
The window states:
Saving changes in modules
Current operation: Saving samba module
67% ( hangs at this point... doesn't continue to 100% :-\ )
2 of 3 operations performed
Any Ideas how to solve this?
Help would be appreciated.
Thanks in advance!
-
Have you updated to zentyal-samba 3.2.6 yet?
-
Nop!
I think I'll do that right away!
I'll inform you if this upgrade solved the problem.
TnX for your quick reply!
Greetings from Amsterdam, The Netherlands
-
I've downloaded the files https://launchpad.net/~jacalvo/+archive/zentyal/+build/5120537 (https://launchpad.net/~jacalvo/+archive/zentyal/+build/5120537) and upgraded the 3.2.6. samba with the terminal command: "sudo dpkg -i zentyal-samba_3.2.6_all.deb"
but same problem still exist, Samba hangs on 67%, doesn't continue to 100%...
-
I updated to it more easily using Zentyal's Web Interface.
I've had a lot of issues with Samba since upgrading to 3.2. At this point, they seem to be fixing some of the issues. I haven't experienced your exact issue and that may be due to some of these steps I did:
http://forum.zentyal.org/index.php?topic=18179.30
However, this my be unrelated to your issue. I hope it turns out to be helpful in some way.
-
Hi Lonniebiz,
Thanks for your suggestion, I've read it and tried it but it didn't work for me.
There was an update in the web interface. I've applied this samba update today but still no solution! :(
I'm working on it and keep you infromed... stay in touch!
-
I wonder if it would save if you deleted users, custom groups, and shares.
Obviously, this may not be practical. If you delete a user, and then add them back later, that user may not be able to consume his previous user-folder (the one created upon logging into a Windows workstation).
The idea is too remove stuff from it until you're able to save 100% and then add things back (saving after each thing you add). This would answer the question "which thing is corrupting samba's ability to save". Or, doing this may lead to it working correctly. Maybe a previous version did some corrupted thing, and the updates are unable to correct that action.
Hopefully, someone will contribute a nicer solution, but since no one has yet, I thought I'd share this painful idea with you :)
-
Today I noticed a new update in the Zentyal Web Interface:
File Sharing and Domain Service 3.2.7.
Got that one yet? Plus, there was a Samba update today too (all can be installed via Zentyal Web Interface).
-
Not hangs really is slow, if you wait a while, ends well.
You can see a smbd process working while seems it is hanged.
http://forum.zentyal.org/index.php/topic,18276.0.html
-
I am having a similar problem but with just enabling the file sharing module. After enabling the module the saving changes stops at 80% - 4 out of 5 operations.
This is a vanilla install of zentyal as a guest on virtualbox, I have tried both the 32bit abs 64bit version with the same problem. I am currently using zentyal-samba 3,2,8
-
I am having a similar problem but with just enabling the file sharing module. After enabling the module the saving changes stops at 80% - 4 out of 5 operations.
This is a vanilla install of zentyal as a guest on virtualbox, I have tried both the 32bit abs 64bit version with the same problem. I am currently using zentyal-samba 3,2,8
Im having the same problem on virtualbox.
The weird thing is i had this problem on my work pc since 3.2 (win7 64bit), tryed like 10 fresh installs on virtualbox, the outcome is the same.
If i do the exact same steps (install zentyal and test it) on my home pc (win7 32bit) it works 100%, i export the virtualbox zentyal image to my other laptop (win xp 32bit), still works 100%, then i took the same copy and tryed on my work pc - its broken...kinda running out of ideas.
-
It would be interesting if people with win7(64) and virtual box could post whether or not this is happening.
Also any other 64bit versions running virtualbox just to see if its a Win7 prob.
I can't help as bare metal but will download and give it a go.
I guess you all have processors with virtual support? Might be good to list processor as well.
-
Was reading more posts about it in the forum and found this post:
http://forum.zentyal.org/index.php/topic,12229.msg50894.html#msg50894
so i tested myself on VMware Player (exported virtualbox image [the same, what was not working]) and now everything works.
Seems to be hardware/virtualbox/something??? problem?
That been said, Zentyal 3.2x is working great on my live server (wihtout any problems so far).
-
It would be interesting if people with win7(64) and virtual box could post whether or not this is happening.
Also any other 64bit versions running virtualbox just to see if its a Win7 prob.
I can't help as bare metal but will download and give it a go.
I guess you all have processors with virtual support? Might be good to list processor as well.
I am running virtualbox 4.2.18 on Ubuntu 12.04 LTS 64bit host
Host hardware is an Quad-Core AMD Opteron(tm) Processor 1352, 4 cores with 8GB RAM and 4x160GB HDD in a software raid10
-
Was reading more posts about it in the forum and found this post:
http://forum.zentyal.org/index.php/topic,12229.msg50894.html#msg50894
so i tested myself on VMware Player (exported virtualbox image [the same, what was not working]) and now everything works.
Seems to be hardware/virtualbox/something??? problem?
That been said, Zentyal 3.2x is working great on my live server (wihtout any problems so far).
I had forgotten about that. Yeah we hit this in 3.0 and being a windows client apols but I have to work with them swapping to vmware player did the job.
It was as confusing then as it is now. But combinations of virtual box and hardware always pop out with samba.
What confused me the most was it seemed to change over time sometimes working and sometimes not.
Its not the ISO or Zentyal bare metal but somewhere there is this weird virtual problem that is limited to virtualbox.
-
It would be interesting if people with win7(64) and virtual box could post whether or not this is happening.
Also any other 64bit versions running virtualbox just to see if its a Win7 prob.
I can't help as bare metal but will download and give it a go.
I guess you all have processors with virtual support? Might be good to list processor as well.
I have exactly the same issue under ESXi. Always hangs saving the Samba module. So it looks like not just vitualbox, but still something to do with running virtual.
And I'm in the same boat of not having any other bare metal around to test this version on.
Cheers.
-
I can't really find anything definitive with googling for samba errors. There are errors with samba4 and virtual machines but I am thinking there should be more reports from the amount of people hitting it with Zentyal.
Its definately virtual and its not just virtual box. Why it will work on vmplayer and not virtualbox makes me even more confused.
http://web.archiveorange.com/archive/v/IPyW4y9gzW7izSO8VbwQ
I don't think its just zentyal after some browsing as there seem to be a few common area's pointing at with not being able to bind to dns.
What the cure is another matter :(
-
Interestingly there are no problems when running Zentyal as a guest in KVM ???
It would be interesting if people with win7(64) and virtual box could post whether or not this is happening.
Also any other 64bit versions running virtualbox just to see if its a Win7 prob.
I can't help as bare metal but will download and give it a go.
I guess you all have processors with virtual support? Might be good to list processor as well.
It's not just limited to Win7(64) as I was running VB on Ubuntu 12.04 64bit host, I haven't tried a 32bit host yet
-
UPDATE
I have managed to get Zentyal 3.3 to work on Virtualbox, the samba module loads properly. I am using Virtualbox 4.2.14 on Ubuntu 12.04 64bit server edition
-
December 21, 2013 I've updated my machine to Zentyal 3.3 and the Samba "Hang" problem when changing the acces control and saving the module, still exist!
No clues in /var/log/zentyal/... logfiles
Don't know what it is. I keep on searching
-
December 21, 2013 I've updated my machine to Zentyal 3.3 and the Samba "Hang" problem when changing the acces control and saving the module, still exist!
I had this "67% problem" on one machine with Zentyal 3.2 and with approx 150 GB data in small files. On the first tests I thought something is wrong, something is crashed in the background. The "solution" in my case was easy: just wait. After several hours (!) it finished and all ACL were correct. (Nevertheless: this is an ill behavior.)
Best regards
-
Hi Udo,
Thanks for your suggestion.
it's not the way it should work.
But I'll keep it as an option.
I'll search for the right way first.
Greetz from Amsterdam, The Netherlands
-
Hello,
I do have this same behaviour in a bare metal installation of Zentyal 3.2.
It's a home appliance, so I do have a small server. A Dell Vostro 200 with 150GB disk and 4GB RAM. All other modules seems to work fine, however I'm stuck in this 67% issue when doing any interaction with Samba.
I rebooted the server and the shares seems to work. I'm creating some shares in a 3TB Seagate Backup USB desktop drive (which I mapped on fstab) and once I reboot the machine, I have all shares with all modifications back.
I'm opened for any suggestions as well.
Thanks,
- Barizon
-
It is not a virtualization issue. I have installed zentyal 3.3.2 in 2 proliant MicroServer and same problem.
I have 3 shares with a total of 1.5Tb of mixed small and large files.
The saving changes windows is at 67% for 12h, so i think it is not running.
I have stopped the migration of 3 more servers until this issue is resolved.
This release is not ready for production because file sharing is a basic service in any environement.
-
The problem is related to the number of files in shares.
A share with 750 large files (total 750Gb) is procesed in a few seconds.
A share with 30.000 small files (150Gb) is procesed in 2 minutes.
A share with 230.000 mixed files (420Gb) hangs at 67%
-
Confirmed same issue in 3.2.
I have left it run for 48h+ and same 67% progress so i think some process hangs with large number of files shares. It is probably related to ACL.
This is a severe issue in a basic service...
ticket:
http://trac.zentyal.org/ticket/7972
-
Realy strange issue. In the problematic share, i had a folder called "system" with backup of old /etc folders of two previous servers. I saved these folders as reference for some manualy installed services (asterisk...)
I have deleted this folder and now the saving takes aprox 10min, but complete successfuly.
In a working share, you can see in a ssh session how the owner, group and acl are aplied folder by folder.
With this folder in my share, none of the folders are modified. once removed, the folders are modified as expected.
I have no idea what is the problem with this folder.
This is a newly installed 3.3, but i installed over previous lvm volumes where i have deleted everything but the shares folders.
-
I had the same issue on a fresh installed system (Version 3.3.2) without any virtualization. As described Samba stops working at 67%. Waiting for hours or days doesn't help at all. In my case all data/shares (except the system itself) are stored on RAID 10, 4 HDs, each 1 TB.
I had a look at samba.log (/var/log/samba/samba.log) and analyzed the last error occurs when samba stopped working.
I find out two things:
1. The files were for some reason old dated e.g. <1990
2. Or the files were migrated from an old filesystem e.g. FAT with the name convention 8.3. In some cases the file was renamed by some old migrations to e.g. "abcdefg~.doc".
On this old file Samba just stops to work. The solution for me was to copy each file to a new one and rename it. Especially files containing "~"-Sign.
Files causing this problem on my system were almost documents so they can easily be renamed. I have no issue any more but it cost me several days to find out :-)
-
Nice. For me it takes 3 full working days to find the problematic folder.
This is a severe problem. The shares i use was working in 3.0. The problem is from 3.2 on.
-
I had the same issue on a fresh installed system (Version 3.3.2) without any virtualization. As described Samba stops working at 67%. Waiting for hours or days doesn't help at all. In my case all data/shares (except the system itself) are stored on RAID 10, 4 HDs, each 1 TB.
I had a look at samba.log (/var/log/samba/samba.log) and analyzed the last error occurs when samba stopped working.
I find out two things:
1. The files were for some reason old dated e.g. <1990
2. Or the files were migrated from an old filesystem e.g. FAT with the name convention 8.3. In some cases the file was renamed by some old migrations to e.g. "abcdefg~.doc".
On this old file Samba just stops to work. The solution for me was to copy each file to a new one and rename it. Especially files containing "~"-Sign.
Files causing this problem on my system were almost documents so they can easily be renamed. I have no issue any more but it cost me several days to find out :-)
This is the piece of information that allowed me to track down my issue. I too had the "stuck at 67%" issue when trying to make any modifications to my Samba configuration. After digging through Samba's log files I found that certain characters in some file names were causing samba to abort the application of the ACLs or even crash Samba altogether. The files that I was trying to share was an achieve of old data that dates back 20 years so it had a whole bunch of different encoding on the file names. So I just used convmv to make sure that all the files names were in unicode. There were quite a few that weren't and after I fix them Samba applied the ACLs without an issue. Here is the command I used. Just make sure you point it to the files you want to convert.
convmv -r -f cp1252 -t utf8 --notest ./
I hope this helps someone.
-
+1 would of never thought about unicode.
I suppose you wouldn't have an idea on the cause of this?
http://forum.zentyal.org/index.php/topic,20220.msg77063.html#msg77063