samba failure on 1.4

[peterr]

I was trying to upgrade from 1.3 to 1.4 but gave up and just reinstalled.
I have a working master and two working slaves - yesterday I set up file sharing on one slave, all seemed to go well and I got as far as creating a share with one group having read-only access and another group having administrator rights.
Today I started to find the problems - I then found there was a samba update available so I installed that this morning and started checking what did or did not work.
On my linux computer I have my username and password stored in my samba settings - this used to let me browse the folders on the old ebox server (those I was allowed to anyway).
Now I can enter the samba server but can not access the share I created (I am in the group with admin rights and also in the read-only groups) and I can not see my own shared folder. I get prompted for a username and password - entering my username and password does not give me access.
Looking in my user settings (on the ebox server) I noticed I do not have administrator rights on PDC/file share so I ticked the box and clicked change

Code: [Select]

A really nasty bug has occurred
Exception
Unknown error at EBox::UsersAndGroups::addUserToGroup Referral received
Trace
Unknown error at EBox::UsersAndGroups::addUserToGroup Referral received at /usr/share/perl5/EBox/Ldap.pm line 712
EBox::Ldap::_errorOnLdap('Net::LDAP::Modify=HASH(0xa91d38c)', 'HASH(0xa8cb77c)') called at /usr/share/perl5/EBox/Ldap.pm line 373
EBox::Ldap::modify('EBox::Ldap=HASH(0xa7044b0)', 'cn=Domain Admins,ou=Groups,dc=web,dc=dcmc', 'HASH(0xa8cb77c)') called at /usr/share/perl5/EBox/UsersAndGroups.pm line 1732
EBox::UsersAndGroups::addUserToGroup('EBox::UsersAndGroups=HASH(0xa08fadc)', 'peter.roots', 'Domain Admins') called at /usr/share/perl5/EBox/Samba.pm line 844
EBox::Samba::setAdminUser('EBox::Samba=HASH(0x9a3efe0)', 'peter.roots', 'yes') called at /usr/share/perl5/EBox/CGI/Samba/ActiveSharing.pm line 79
EBox::CGI::Samba::ActiveSharing::_user('EBox::CGI::Samba::ActiveSharing=HASH(0xa8cfc38)') called at /usr/share/perl5/EBox/CGI/Samba/ActiveSharing.pm line 86
EBox::CGI::Samba::ActiveSharing::_process('EBox::CGI::Samba::ActiveSharing=HASH(0xa8cfc38)') called at /usr/share/perl5/EBox/CGI/Base.pm line 262
EBox::CGI::Base::run('EBox::CGI::Samba::ActiveSharing=HASH(0xa8cfc38)') called at /usr/share/perl5/EBox/CGI/Run.pm line 120
EBox::CGI::Run::run('EBox::CGI::Run', 'Samba/ActiveSharing', '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(0xa90d1c4)') 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(0xa84e7f0)') called at /usr/lib/perl5/ModPerl/RegistryCooker.pm line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xa84e7f0)') called at /usr/lib/perl5/ModPerl/Registry.pm line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xa90d1c4)') called at -e line 0
eval {...} called at -e line 0Currently I have no shares other than the one I created under filesharing>shares so I went to userandgroups>groups and tried to edit a group (created on the master before I set up the file share slave). One group is for everyone and the others are more limited - the attempt to edit any group (wanted to add a file share to each one) gave this

Code: [Select]

A really nasty bug has occurred
Exception
Can't call method "get_value" on an undefined value
Trace
Can't call method "get_value" on an undefined value at /usr/share/perl5/EBox/SambaLdapUser.pm line 740.So basically samba is not working properly - to the extent of being able to see the server and some shared folders but that is about it, can't enter any of them.
Any ideas where to go next?
All 3 servers are up to date as of this morning

[Saturn2888]

I had that issue before. I purged it and re-installed. I think that fixed it, but I can't remember. I ended up purging everything including slapd.

[Saturn2888]

Code: [Select]

sudo /usr/share/ebox-usersandgroups/ebox-usersandgroups-reinstall
sudo /usr/share/ebox/ebox-unconfigure-module samba
Just so you know, the ebox-usersandgroups-reinstall has a bug and doesn't resolve dependencies on usersandgroups so you'll need to unconfigure samba which is why I included that other part.

[peterr]

Thanks for the suggestion, unfortunately it did not work - still exactly the same problem

[Saturn2888]

If you can't enter folders, your users have to be admins and then try. It's a good tester. Another thing is, if the folder is not created in /home/samba/shares or /home/samba/users, you definitely can't get it to work because you can't see a folder that does not exist.

[peterr]

My users can not become admins on any group folders as I can not create group folders (I get the error I printed earlier).
A user can not become a samba user with admin rights as I get the other error I printed earlier
After a complete reinstall today it is still not working
My users sync with the master without problems it is just that the file share is totally broken
All I have is the samba server (showing up in the correct workgroup) that contains two shared folders that I can see ebox-internal-backups and ebox-quarantine plus any I create seperatly to the group ones or the users own folders.
The folder I have created has readonly access rights for all users. I am in a group with admin rights on it and I just gave myself read write access to it - can't enter the folder (it is in home/samba/shares)
Changing my access right to admin still does not let me in.
Interestingly there are no folders under /home/samba/users though so that is worth looking into

[Saturn2888]

I was saying make an admin user to test. By making folders, I meant

Code: [Select]

mkdir /home/samba/users/[USERNAME]
chgrp __USERS__
chown ebox
chmod 670
Then you're good.

[peterr]

No luck

Part of the problem (I guess) is that when I installed ebox on this server I used the simple install - this did not format the hard drive (not that I realised that at the time) but while trouble shooting this I found some of my old samba shares still present.
Samba failed with them - I deleted them, it still failed. I tried stripping out all ebox software, settings and related folder and reinstalled.
In the end I reinstalled the whole lot but used the expert mode and deleted all the partitions and recreated them.

That finally fixed it

[philmills]

I have the same problem, but i have around 80 users, 10 groups, 10 shares, and 10 printers configured. A complete reinstall is gonna set me back days....

are there any other solutions to this issue?

[Saturn2888]

Yes, you can make a backup of your eBox %gconf.xml files and whatever else is needed. Did my solution not fix it?

[philmills]

whats the path to the files i need to backup?

[Saturn2888]

1. /etc
2. /var/lib/ebox/gconf/ebox/modules
Those are two folders I know need to backup. Others will know more.

[peterr]

Saturn2888 - no unfortunately your fix did not work for me, hence my reinstall

Phillmills - sorry to hear you came unstuck too!
As my failed samba server was a slave I got all my users and groups back again when I reinstalled and the new install did its first sync with the master - obviously shares and printers won't get included in this.
The other issue is that existing users who sync across do so before you are able to set up the file share so they default to a quota of 0 (ie no limit) so if you are expecting to limit you users to share space that will need to be put back.
I have yet to try it out but what about the ebox backup? Mind you it might take more than you want over, I suppose, and restore a broken setup up

[can79]

I have the same problem.
I see no real solution here.

it is pretty simple configuration.
Master: only "usersandgroups" module
slave: samba + usersandgroups module

on master you don't have a option for Administrations Rights So at this slave check you option for user Administrations Rights on. and bingo ERROR.

what is solution?
i think if no solution then it is a bug.

[philmills]

I'm not certain that what can79 reports is on the same topic as this thread.
this thread is about upgrading, rather than clean install.
but the problem is very similar indeed.
see this thread http://forum.ebox-platform.com/index.php?topic=2968