Zentyal Forum, Linux Small Business Server
Zentyal Server => Installation and Upgrades => Topic started by: maxter on March 17, 2010, 05:20:52 pm
-
i've encountered some strange problems reading and writing files on samba shares from xp and win2000.
it is possible to write a file to the mounted share, and copy the file back to the local pc or delete it, but trying to read or write this file on the share is impossible.
every application report a different error.
notepad opens the file but trying to save after some changes report that 'there is not enough memory'.
open office can't open the file and trying to save a file directly to the share report an I/O error.
image preview simply can't open any image.
and so on.
there are no errors on the logs.
i downgraded to the hardy default samba versions, and now all works fine.
the downgrade also removed the ebox-samba package, and now i can't manage users and group from the ebox interface, so any suggestion to solve this problem is really appreciated :)
many thanks
-
bump! :)
i now that the information i provided are generic, but really i don't know how further investigate and provide more information.
the problem is surely related with the the samba version, but the lack of errors in log stops my efforts to provide more informations.
i must solve this problem, i don't need the last version of samba so i will be happy also if i'll manage to reinstall samba management in ebox or even if i'll know how to add new users samba settings from command line...
so any suggestion is really appreciated
many thanks
-
I have a similar problem with the current ebox-release.
When I try to access a samba share from a Vista-PC (havn't tried with other OS yet) some Tools (e.g. Total Commander) report "Not enough space on disk" when copying a file to the share.
With explorer everything looks fine on the first look, but when I tried to open the files some seem corrupted (e.g. pdf-files).
This is a very serious problem and it is absolutely not possible to use the machine in a productive environment without this problem fixed.
I have installed the system just a few days ago with online updates enabled, so it should be the very ltest release of ebox.
-
I have just installed my first E-box and I have this problem exactly.
Most annoying are the images and PDF-files.
And if I copy the files from the share to my desktop, I can open it just fine.
I have checked the rights and such and it looks perfect.
I can open word files thou.
Just adding that the clients are WinXP with the latest updates.
-
I've spent one day figthing with the same issue. It was (at least in my case) an issue related with the samba vfs object full audit.
Try this (and don't touch the web interface during the proces or it will overwrite your changes):
open /etc/samba/smb.conf and comment all the references to full audit:
# vfs objects = full_audit
# full_audit:success = connect opendir open disconnect unlink mkdir rmdir rename
# full_audit:failure = none
.
.
[homes]
comment = Home Directories
valid users = %S
read only = No
browseable = No
# vfs objects = full audit
.
.
[myshare]
.
.
Then restart samba (/etc/init.d/samba restart) and check if the problem is solved.
If everything works, to prevent the web interface from re-introducing the problem, look at this page:
http://trac.ebox-platform.com/changeset/15674
and apply the changes to:
/usr/share/ebox/stubs/samba/smb.conf.mas
Good luck!
-
Thank you!! ;D
This helped me at least.
In due time too since I couldn't even load the profiles logging in.
-
Same with Ebox 1.4.1 !!!
After the changes which are described here: it works !!
Strange anyway, I have installed the same Ebox 1.4.1 version on a different computer some days ago: doesn't have this problem... I will check the smb.conf files on the other server too.
Anyway: this is a really nasty (but known) bug, I hope the Ebox company makes a new Ebox-version asap...
thanks again !
;-) Arthur ;D
-
Yep, really nasty >:( (nearly ruined weekend level) I'm never going to just download the latest ISO and blindly install it again! let alone update without waiting first.
Obviously I should have come here first to check when I had the error. here's what I was searching for in the wider Google:
"Not enough server storage is available to process this command" samba
EDIT: thank you sidmax you just saved my bacon! and possibly my weekend although probably too late for that :-)
-
Friends all right? Me not very well because I was 3 days with company failure, as the samba was accusing error.
In the end, I got through the help of our friend here on the forum.
My question is!
Do not have a patch to fix the same?
I really need to use the full functions of the audit / vfs
Thank you all.
-
Woah!!!!
Dude, you're a lifesaver! exactly what I needed, some Vista PCs just didn't wanna play nicely. Now they're happy!
-
admins - please patch this.
i don't know if its related, but backups don't run at the moment. anyone else have that problem since applying this fix?
-
my bad - there was a config problem with my ftp backup server
-
@sidmax
Thank you, i had the same isssues, your solution works also for me. :D
In my case it was the logon-script which did not work anymore (after upgrading from 1.2 to 1.4.1).
I could read it, change it and save it, but it was not executed when a user logged in, although it has the correct permissions set.
Now everything seems to be fine again ... :)
-
@sidmax
many many thanks
it seems that this full_audit problem was reported also in samba mailing list, and that it appears randomly, so there is no way for the programmers to reproduce the bug.
really strange.
anyway i think that such a problem that affect some people should at least to be mentioned in the documentation/faq.
any ebox developer/manteiner here? :)
-
@sidmax
many many thanks
it seems that this full_audit problem was reported also in samba mailing list, and that it appears randomly, so there is no way for the programmers to reproduce the bug.
really strange.
anyway i think that such a problem that affect some people should at least to be mentioned in the documentation/faq.
any ebox developer/manteiner here? :)
You are right, I've tested it lots of times and I can't reproduce it. I could reproduce it always with samba 3.4.5, but samba 3.4.6 seems to fix the problem as stated in the changelog.
Anyway, we are not forgetting this and we'll do something about it as soon as possible.
-
You are right, I've tested it lots of times and I can't reproduce it. I could reproduce it always with samba 3.4.5, but samba 3.4.6 seems to fix the problem as stated in the changelog.
Anyway, we are not forgetting this and we'll do something about it as soon as possible.
Hmmm ... that's strange. I'm having the same problem on samba 3.4.6. Still trying to fix the full_audit problem. Can I leave the "vfs objects = vscan-clamav" in each share? My users likes to collect viruses while surfing porn :P
-
This problem is still not going away!!!!!
I am using Ebox 1.4.4
I did the following:
open /etc/samba/smb.conf and comment all the references to full audit:
# vfs objects = full_audit
# full_audit:success = connect opendir open disconnect unlink mkdir rmdir rename
# full_audit:failure = none
.
.
[homes]
comment = Home Directories
valid users = %S
read only = No
browseable = No
# vfs objects = full audit
.
.
[myshare]
.
.
I restart samba (/etc/init.d/samba restart) and the problem is solved. Now, this next step is where
the whole thing starts all over
I closed the web interface to prevent it from re-introducing the problem and follow the next page:
http://trac.ebox-platform.com/changeset/15674
I applied the changes to:
/usr/share/ebox/stubs/samba/smb.conf.mas
and as soon as I start the web interface page, click on restart File Sharing, the following error pops up, and down goes the file sharing. I have double checked my /usr/share/ebox/stubs/samba/smb.conf.mas
to make sure I did exactly like the http://trac.ebox-platform.com/changeset/15674 says
The new error:
A really nasty bug has occurred
Exception
Template samba/smb.conf.mas failed with Error during compilation of : Global symbol "$objects" requires explicit package name at (eval 2319) line 215. Global symbol "$key" requires explicit package name at (eval 2319) line 226. Global symbol "$key" requires explicit package name at (eval 2319) line 230. Global symbol "$group" requires explicit package name at (eval 2319) line 239. Global symbol "$group" requires explicit package name at (eval 2319) line 244. Global symbol "$group" requires explicit package name at (eval 2319) line 249. Global symbol "$group" requires explicit package name at (eval 2319) line 254. Global symbol "$group" requires explicit package name at (eval 2319) line 259. Global symbol "$objects" requires explicit package name at (eval 2319) line 280. Global symbol "$key" requires explicit package name at (eval 2319) line 291. Global symbol "$key" requires explicit package name at (eval 2319) line 295. Global symbol "$printer" requires explicit package name at (eval 2319) line 308. Global symbol "$printer" requires explicit package name at (eval 2319) line 316. Global symbol "$share" requires explicit package name at (eval 2319) line 326. Global symbol "$share" requires explicit package name at (eval 2319) line 331. Global symbol "$share" requires explicit package name at (eval 2319) line 336. Global symbol "$share" requires explicit package name at (eval 2319) line 341. Global symbol "$share" requires explicit package name at (eval 2319) line 346. Global symbol "$share" requires explicit package name at (eval 2319) line 351. Global symbol "$share" requires explicit package name at (eval 2319) line 356. Global symbol "$objects" requires explicit package name at (eval 2319) line 376. Global symbol "$key" requires explicit package name at (eval 2319) line 387. Global symbol "$key" requires explicit package name at (eval 2319) line 391. Stack: [/usr/share/perl5/HTML/Mason/Interp.pm:631] [/usr/share/perl5/EBox/Module/Base.pm:866] [/usr/share/perl5/Error.pm:416] [/usr/share/perl5/EBox/Module/Base.pm:871] [/usr/share/perl5/EBox/Module/Service.pm:697] [/usr/share/perl5/EBox/Samba.pm:487] [/usr/share/perl5/EBox/Module/Base.pm:824] [/usr/share/perl5/EBox/Module/Service.pm:599] [/usr/share/perl5/EBox/Module/Service.pm:627] [/usr/share/perl5/Error.pm:416] [/usr/share/perl5/EBox/Module/Service.pm:634] [/usr/share/perl5/EBox/CGI/EBox/RestartService.pm:51] [/usr/share/perl5/EBox/CGI/Base.pm:262] [/usr/share/perl5/Error.pm:416] [/usr/share/perl5/EBox/CGI/Base.pm:278] [/usr/share/perl5/EBox/CGI/Run.pm:120] [/usr/share/ebox/cgi/ebox.cgi:19] [/usr/share/perl5/Error.pm:416] [/usr/share/ebox/cgi/ebox.cgi:42] [/usr/lib/perl5/ModPerl/RegistryCooker.pm:204] [/usr/lib/perl5/ModPerl/RegistryCooker.pm:170] [/usr/lib/perl5/ModPerl/Registry.pm:31] [-e:0]
Trace
Template samba/smb.conf.mas failed with Error during compilation of :
Global symbol "$objects" requires explicit package name at (eval 2319) line 215.
Global symbol "$key" requires explicit package name at (eval 2319) line 226.
Global symbol "$key" requires explicit package name at (eval 2319) line 230.
Global symbol "$group" requires explicit package name at (eval 2319) line 239.
Global symbol "$group" requires explicit package name at (eval 2319) line 244.
Global symbol "$group" requires explicit package name at (eval 2319) line 249.
Global symbol "$group" requires explicit package name at (eval 2319) line 254.
Global symbol "$group" requires explicit package name at (eval 2319) line 259.
Global symbol "$objects" requires explicit package name at (eval 2319) line 280.
Global symbol "$key" requires explicit package name at (eval 2319) line 291.
Global symbol "$key" requires explicit package name at (eval 2319) line 295.
Global symbol "$printer" requires explicit package name at (eval 2319) line 308.
Global symbol "$printer" requires explicit package name at (eval 2319) line 316.
Global symbol "$share" requires explicit package name at (eval 2319) line 326.
Global symbol "$share" requires explicit package name at (eval 2319) line 331.
Global symbol "$share" requires explicit package name at (eval 2319) line 336.
Global symbol "$share" requires explicit package name at (eval 2319) line 341.
Global symbol "$share" requires explicit package name at (eval 2319) line 346.
Global symbol "$share" requires explicit package name at (eval 2319) line 351.
Global symbol "$share" requires explicit package name at (eval 2319) line 356.
Global symbol "$objects" requires explicit package name at (eval 2319) line 376.
Global symbol "$key" requires explicit package name at (eval 2319) line 387.
Global symbol "$key" requires explicit package name at (eval 2319) line 391.
Stack:
[/usr/share/perl5/HTML/Mason/Interp.pm:631]
[/usr/share/perl5/EBox/Module/Base.pm:866]
[/usr/share/perl5/Error.pm:416]
[/usr/share/perl5/EBox/Module/Base.pm:871]
[/usr/share/perl5/EBox/Module/Service.pm:697]
[/usr/share/perl5/EBox/Samba.pm:487]
[/usr/share/perl5/EBox/Module/Base.pm:824]
[/usr/share/perl5/EBox/Module/Service.pm:599]
[/usr/share/perl5/EBox/Module/Service.pm:627]
[/usr/share/perl5/Error.pm:416]
[/usr/share/perl5/EBox/Module/Service.pm:634]
[/usr/share/perl5/EBox/CGI/EBox/RestartService.pm:51]
[/usr/share/perl5/EBox/CGI/Base.pm:262]
[/usr/share/perl5/Error.pm:416]
[/usr/share/perl5/EBox/CGI/Base.pm:278]
[/usr/share/perl5/EBox/CGI/Run.pm:120]
[/usr/share/ebox/cgi/ebox.cgi:19]
[/usr/share/perl5/Error.pm:416]
[/usr/share/ebox/cgi/ebox.cgi:42]
[/usr/lib/perl5/ModPerl/RegistryCooker.pm:204]
[/usr/lib/perl5/ModPerl/RegistryCooker.pm:170]
[/usr/lib/perl5/ModPerl/Registry.pm:31]
[-e:0]
at /usr/share/perl5/EBox/Module/Base.pm line 870
EBox::Module::Base::writeConfFileNoCheck('/etc/samba/smb.conf', 'samba/smb.conf.mas', 'ARRAY(0xbfc2c30)', 'undef') called at /usr/share/perl5/EBox/Module/Service.pm line 697
EBox::Module::Service::writeConfFile('EBox::Samba=HASH(0x9e945a8)', '/etc/samba/smb.conf', 'samba/smb.conf.mas', 'ARRAY(0xbfc2c30)') called at /usr/share/perl5/EBox/Samba.pm line 487
EBox::Samba::_setConf('EBox::Samba=HASH(0x9e945a8)', 'restart', 1) called at /usr/share/perl5/EBox/Module/Base.pm line 824
EBox::Module::Base::_regenConfig('EBox::Samba=HASH(0x9e945a8)', 'restart', 1) called at /usr/share/perl5/EBox/Module/Service.pm line 599
EBox::Module::Service::_regenConfig('EBox::Samba=HASH(0x9e945a8)', 'restart', 1) called at /usr/share/perl5/EBox/Module/Service.pm line 627
EBox::Module::Service::restartService('EBox::Samba=HASH(0x9e945a8)') called at /usr/share/perl5/EBox/CGI/EBox/RestartService.pm line 51
EBox::CGI::EBox::RestartService::_process('EBox::CGI::EBox::RestartService=HASH(0xc3b04b8)') called at /usr/share/perl5/EBox/CGI/Base.pm line 262
EBox::CGI::Base::run('EBox::CGI::EBox::RestartService=HASH(0xc3b04b8)') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'EBox/RestartService', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 19
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0xc2e2d88)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
eval {...} called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xc37d2d8)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xc37d2d8)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xc2e2d88)') called at -e line 0
eval {...} called at -e line 0
PLEASE HELP!!!
Thank you
-
Download the whole file to make sure its syntax is correct:
http://trac.ebox-platform.com/export/15674/trunk/client/samba/stubs/smb.conf.mas
After that, don't forget to execute "/etc/init.d/ebox samba restart"
-
Hi J. A. Calvo,
If I comment out the VFS Objects in the Samba config file, and replace the smb.conf.mas file with the updated one on the site, and I restart Samba... Will I then be able to use ClamAV virus scanning and "Recycle Bin" support when I select that in the web interface under "filesharing" ?
Basically what I am trying to find out is if I should leave virus scanning and "recycle bin" disabled after I comment out the VFS Modules full_audit option, and restart Samba
Stephan
-
I think the only problematic "vfs" is full_audit, so you can still use antivirus and recyclebin if you left them uncommented.
-
Hi J.A. Calvo
This problem started with the antivirus scanning problem on Ebox 1.2.3. on the 15 April 2010. I have removed the tick at the Samba file scanner in the Web interface, but the problem (access denied for files on the share folder) did not go away. So I backup all the data, captured the configuration of all the users etc, and loaded 1.4. After loaded 1.4 for 2 times with full configuration, restored data to /home, because I thought I made a mistake, I realized I was not to blame. I search the forum and end up on this problem link and try to solve the problem. I have downloaded the smb.conf.mas file like you said, restart Ebox Samba, and same problem pops up. Because this is a server in highly productive company, I could not keep this machine any longer away from the site, already 4 days, so i have reloaded it with Ebox 1.2.2, disable auto updates etc, and it is now working again. Can't this serious bug not be solved by implementing the newest Samba which is available? I am trying very hard to convince my clients to switch from Microsoft servers to Linux (Ebox - great reliable server!), and promised them less downtime. I have 6 Ebox servers running at other sites, and I am now not very keen to upgrade to 1.4, before this problem is not fully resolved.
Thanks for all the effort and time for a further great product!
-
Hi Perske7,
The funny thing is that the newest Samba available has still the same problem...
We thought it was fixed in samba 3.4.6 (they said it in the changelog) so we uploaded it to 1.4-proposed asap, but the problem was not totally fixed, and samba 3.4.7 doesn't fix it either. So we are waiting for 3.4.8...
Thanks for your kind words about the product!
-
Hi again,
I've found a patch in the samba's bugzilla that seems to work. I've patched manually our current samba 3.4.6 package and uploaded a new version.
Anybody can confirm if it solves the problem?
To upgrade, add this line to /etc/apt/sources.list:
deb http://ppa.launchpad.net/ebox/1.4-proposed/ubuntu/ hardy main
And run:
apt-get update
apt-get install samba
-
I consistently get this. I install ebox as a kvm guest on a proxmox distribution and have this problem on more or less every 1.4-1 install.
-
I consistently get this. I install ebox as a kvm guest on a proxmox distribution and have this problem on more or less every 1.4-1 install.
But have you tried to upgrade the samba package as it says in the above message? (http://forum.ebox-platform.com/index.php?topic=3298.msg15496#msg15496)
-
I'm having the same problem and tried the above mentioned. When i run apt-get update, I get:
W: Failed to fetch http://ppa/launchpad.net/ebox/1.4-proposed/unbuntu/dists/hardy/main/binary-i386/Packages.gz 404 Not Found
Any ebox fixes for this coming soon... Will the new samba 3.4.8 being released on may 11th fix this?
-
But have you tried to upgrade the samba package as it says in the above message? (http://forum.ebox-platform.com/index.php?topic=3298.msg15496#msg15496)
To be honest, I've got this in production and if disabling the setting in smb.conf.mas works i am going to choose that all the way... it's a simple fix, on a feature I can live without.
-
I'm having the same problem and tried the above mentioned. When i run apt-get update, I get:
W: Failed to fetch http://ppa/launchpad.net/ebox/1.4-proposed/unbuntu/dists/hardy/main/binary-i386/Packages.gz 404 Not Found
Any ebox fixes for this coming soon... Will the new samba 3.4.8 being released on may 11th fix this?
The URL is wrong, it's "ppa.launchpad.net", not "ppa/launchpad.net".
Yes, I hope samba 3.4.8 will include this same fix, but you can already test our patched 3.4.6.
-
Domain logins seem to work so far with full_audit uncommented. Profiles are updated on logout.
Thanks J.A.
-
I've spent one day figthing with the same issue. It was (at least in my case) an issue related with the samba vfs object full audit.
Try this (and don't touch the web interface during the proces or it will overwrite your changes):
open /etc/samba/smb.conf and comment all the references to full audit:
# vfs objects = full_audit
# full_audit:success = connect opendir open disconnect unlink mkdir rmdir rename
# full_audit:failure = none
.
.
[homes]
comment = Home Directories
valid users = %S
read only = No
browseable = No
# vfs objects = full audit
.
.
[myshare]
.
.
Then restart samba (/etc/init.d/samba restart) and check if the problem is solved.
If everything works, to prevent the web interface from re-introducing the problem, look at this page:
http://trac.ebox-platform.com/changeset/15674
and apply the changes to:
/usr/share/ebox/stubs/samba/smb.conf.mas
Good luck!
this solved my problem with ebox server, i can now open jpg, vsd, dwg files and other and the error "not enough memory etc. etc." is gone now :) thanks bro sidmax!!!
-
@J. A. Calvo:
Updated samba like you described it, but no success.
When i try to open an openoffice file, there is no chance to save the changes back to the samba share. OpenOffice generates a new temp-file for the changes.