[Samba] Samba 3.6.13 - System freeze CIFS VFS
Hi everyone, our Samba (3.6.13, 64 bit on SLES 11 SP2, SerNet Repos) server did a full system freeze last night. The whole system had to be rebooted and after the startup I scrolled through the /var/log/messages to find the following part. Apr 16 23:30:30 samba3 kernel: [1164350.551256] CIFS VFS: sends on sock 88041972f080 stuck for 15 seconds Apr 16 23:30:30 samba3 kernel: [1164350.551259] CIFS VFS: Error -11 sending data on socket to server Apr 16 23:30:45 samba3 kernel: [1164365.543869] CIFS VFS: sends on sock 88041972f080 stuck for 15 seconds Apr 16 23:30:45 samba3 kernel: [1164365.543874] CIFS VFS: Error -11 sending data on socket to server Those were the last words before the freeze it seems. Anyone got a clue what the reason for the lockup could be? Bug or just some failure in general? Best regards, Florian Götz -- Mit freundlichen Grüßen Florian Götz - Dipl.-Inf. (FH) Florian Götz Rechenzentrum Hochschule Mannheim Paul-Wittsack-Straße 10 68163 Mannheim Tel: 0621/292-6232 EMail: f.go...@hs-mannheim.de Internet: http://www.rz.hs-mannheim.de - -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba4 fails to work following upgrade - library version errors
Hi Andrew, I performed another upgrade yesterday First a git clean, then a git pull, a ./configure --enable-selftest --enable-debug --enable-avahi, a make, and finally a make install After this had completed, I found that an older version of samba and smbclient had been copied into /usr/bin/ overwriting the symbolic links I had put in there. So I had exactly the same problem as before. I hadn't made any other changes to the system, so I know it's something to do with the Samba4 upgrade/install process. The correct file path for samba and smbclient is /usr/local/samba/sbin - the installation process correctly installs the current version of those commands into that path. Is there something in the configure/make/make install process that copies files into /usr/bin/, or is something else happening? I'd look for it myself and contribute to the project if I only knew what I was doing :) Kind regards Graeme From: Andrew Bartlett abart...@samba.org To: Michael Wood esiot...@gmail.com Cc: Graeme Porter graeme.por...@yahoo.co.uk; samba@lists.samba.org samba@lists.samba.org Sent: Saturday, 6 April 2013, 10:49 Subject: Re: [Samba] Samba4 fails to work following upgrade - library version errors On Fri, 2013-04-05 at 16:54 +0200, Michael Wood wrote: Hi It sounds like the samba binary on your PATH is the old version. Well spotted Michael, this one really had me stumped! Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba4 fails to work following upgrade - library version errors
Hi On 17 April 2013 12:01, Graeme Porter graeme.por...@yahoo.co.uk wrote: Hi Andrew, I performed another upgrade yesterday First a git clean, then a git pull, a ./configure --enable-selftest --enable-debug --enable-avahi, a make, and finally a make install After this had completed, I found that an older version of samba and smbclient had been copied into /usr/bin/ overwriting the symbolic links I had put in there. So I had exactly the same problem as before. I hadn't made any other changes to the system, so I know it's something to do with the Samba4 upgrade/install process. The samba build system does not copy things to /usr/bin (unless you fiddle with things like --prefix etc.) How exactly did you make the symlinks? -- Michael Wood esiot...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba4 fails to work following upgrade - library version errors
Hi On 5 April 2013 17:19, Graeme Porter graeme.por...@yahoo.co.uk wrote: Thanks Michael, I've got my domain controller back! I'm now rather distinctly annoyed. I *was* using a symbolic link in /usr/bin called samba that was pointing to /usr/local/samba/sbin/samba - this was the only way I found so far that I could avoid typing the whole command path every time - probably because I still can't see a way to persistently and globally add entries to the path variable (every time I tried this previously, if I logged out and logged in as a different user, my changes to the path were missing, and wouldn't even reappear when I logged back in as myself). Changing environment variables by typing something like this at the shell prompt will only affect the shell you are currently running the command in and other processes started by that shell (and processes started by those processes etc.): $ export PATH=/usr/local/samba/bin:/usr/local/samba/sbin:$PATH e.g. if you open two terminal windows and you type the above command into one and then type echo $PATH into the other, you will see that the second window doesn't see the updated PATH. This is because when each process starts it gets its own copy of the environment from its parent. Updating the environment of a process can only affect that process and its children. So if you want to affect the environment for all processes you have to change file that will be read by the shell when it starts. e.g. /etc/environment or /home/user/.profile. See also the System-wide environment variables section here: https://help.ubuntu.com/community/EnvironmentVariables -- Michael Wood esiot...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba4 fails to work following upgrade - library version errors
The symlinks were made by entering: ln /usr/local/samba/sbin/samba /usr/bin/samba ln /usr/local/samba/sbin/smbclient /usr/bin/smbclient I realise this isn't the correct way of doing things (obviously the correct way would be to update the system PATH environment variable), but at the same time I can't see why it's a bad idea. Unless something happens to the symlink that I wasn't expecting when the file it is linking to is removed or altered? Kind regards Graeme From: Michael Wood esiot...@gmail.com To: Graeme Porter graeme.por...@yahoo.co.uk Cc: Andrew Bartlett abart...@samba.org; samba@lists.samba.org samba@lists.samba.org Sent: Wednesday, 17 April 2013, 12:12 Subject: Re: [Samba] Samba4 fails to work following upgrade - library version errors Hi On 17 April 2013 12:01, Graeme Porter graeme.por...@yahoo.co.uk wrote: Hi Andrew, I performed another upgrade yesterday First a git clean, then a git pull, a ./configure --enable-selftest --enable-debug --enable-avahi, a make, and finally a make install After this had completed, I found that an older version of samba and smbclient had been copied into /usr/bin/ overwriting the symbolic links I had put in there. So I had exactly the same problem as before. I hadn't made any other changes to the system, so I know it's something to do with the Samba4 upgrade/install process. The samba build system does not copy things to /usr/bin (unless you fiddle with things like --prefix etc.) How exactly did you make the symlinks? -- Michael Wood esiot...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba4 fails to work following upgrade - library version errors
On 17 April 2013 13:41, Graeme Porter graeme.por...@yahoo.co.uk wrote: The symlinks were made by entering: ln /usr/local/samba/sbin/samba /usr/bin/samba ln /usr/local/samba/sbin/smbclient /usr/bin/smbclient That's what I suspected :) Those are hard links, not symbolic/soft links. You need to use ln -s source destination to create symlinks. I realise this isn't the correct way of doing things (obviously the correct way would be to update the system PATH environment variable), but at the same time I can't see why it's a bad idea. Unless something happens to the symlink that I wasn't expecting when the file it is linking to is removed or altered? If you create a hard link to a file, the original file name and the new hard link are indistinguishable from each other. They are both names that point to the actual file. If you remove one of them (e.g. by running make install) the other one will still be there, pointing to the original file on disk. i.e. hard links point to the actual file. Symbolic links are names that point to other names. -- Michael Wood esiot...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba4 fails to work following upgrade - library version errors
Whoops :( Well, every day's a school day - pretty much the reason why I got the Raspberry Pi in the first place was to learn Linux, so thanks for the tip! Also love the Roald Dahl reference in your e-mail address. Kind regards Graeme From: Michael Wood esiot...@gmail.com To: Graeme Porter graeme.por...@yahoo.co.uk Cc: Andrew Bartlett abart...@samba.org; samba@lists.samba.org samba@lists.samba.org Sent: Wednesday, 17 April 2013, 12:54 Subject: Re: [Samba] Samba4 fails to work following upgrade - library version errors On 17 April 2013 13:41, Graeme Porter graeme.por...@yahoo.co.uk wrote: The symlinks were made by entering: ln /usr/local/samba/sbin/samba /usr/bin/samba ln /usr/local/samba/sbin/smbclient /usr/bin/smbclient That's what I suspected :) Those are hard links, not symbolic/soft links. You need to use ln -s source destination to create symlinks. I realise this isn't the correct way of doing things (obviously the correct way would be to update the system PATH environment variable), but at the same time I can't see why it's a bad idea. Unless something happens to the symlink that I wasn't expecting when the file it is linking to is removed or altered? If you create a hard link to a file, the original file name and the new hard link are indistinguishable from each other. They are both names that point to the actual file. If you remove one of them (e.g. by running make install) the other one will still be there, pointing to the original file on disk. i.e. hard links point to the actual file. Symbolic links are names that point to other names. -- Michael Wood esiot...@gmail.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Migration Samba to AD
I have a pdc samba 3+openldap+debian 5 and I need to migrate the ad windows (2003,2008 or 2012). How can I do this? -- Atenciosamente, Thiago Fortes Administrador de Redes DigithoBrasil 67 3345-6565 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba4: force user issue
I have a pair of CentOS 6.4 servers running Samba 4.0.3 as DC, and a set of member file servers, also CentOS 6, running Samba 3.6.9, joined to the Samba4 domain and running sssd. Birds sing and violins play. Everyone is happy. Until... A share definition such as: [g_sysmgr] path = /fs/europa/g_sysmgr valid users = +sysgrp works fine from both Linux and Windows clients, eg: % smbclient //icse/g_sysmgr -U smt Enter smt's password: Domain=[EUROPA] OS=[Unix] Server=[Samba 3.6.9-151.el6] smb: \ The addition of the force user directive causes a failure (the user sysmgr is a member of the sysgrp group and owns all files and directories): [g_sysmgr] path = /fs/europa/g_sysmgr valid users = +sysgrp force user = sysmgr % smbclient //icse/g_sysmgr -U smt Enter smt's password: Domain=[EUROPA] OS=[Unix] Server=[Samba 3.6.9-151.el6] tree connect failed: NT_STATUS_INTERNAL_DB_CORRUPTION Qualifying the forced user name with the domain name has no effect. There is _nothing_ in the Samba logs, even at level 10. Any ideas? -Steve -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] sssd getent problem with Samba 4.0
On 04/14/2013 09:52 PM, steve wrote: On 14/04/13 21:22, Eric PEYREMORTE wrote: Le 14/04/2013 17:37, steve a écrit : ve even got getent group to list not only the gidNumber, but group members too:) I'll test an Ubuntu client tomorrow, but it's looking good. Maybe I'll put some together. Steve Don't you need enumerate = true in sssd.conf ? Just an idea Hi Yes we tried that. It works for the first time after the restart but then fails upon subsequent attempts. We've tried leaving it running for the cache/buffer to fill but still nada. Maybe it's time to get over on the sssd list. I'll report back here if I get any progress on it. Cheers, Steve Hi I got just about everything sorted out with sssd and gssapi for Samba 4.0. Thanks to everyone here and over on the sssd list. I've documented it here: http://linuxcostablanca.blogspot.com.es/2013/04/sssd-in-samba-40.html HTH Steve -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba4 internal dns update
Hello Last week we changed our ip range, every computer was shutdown and everything is working, but we are still getting the old ip address on the dns, my version is samba 4.0.3 and i am using internal dns This is the actual smb.conf [global] workgroup = MYCOMPANY realm = MYCOMPANY.COM.CO netbios name = DOMINIO server role = active directory domain controller idmap_ldb:use rfc2307 = yes dns forwarder = 8.8.8.8 wins support = Yes log level = 1 allow dns updates = True Any suggestions? Thanks -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Rsyncing Samba4 Roaming Profiles between servers
Hi folks, I've got a bit of an issue with roaming profiles and I wondered if someone might be able to help please? :-) We've started rolling out Samba 4 across our network. Currently it's on 3 of our 4 sites, one site has two Samba servers and two sites have one Samba server each (well one site has two Samba 4 servers but one of the servers was an oldish test box which I'm planning on removing from AD when I can work out how to, but that's a separate issue). I've managed to get roaming profiles working for the users on each site. Each user is currently configured to store their roaming profile on the server on the site that they're based at. This seems to work pretty well with our Windows 7 clients and the users are happy that they can now login to any PC and get their desktop icons etc. Now my boss would like the ability to be able to login to a PC on a remote site (as in, not the site where his roaming profile is stored) and have the profile available. It seems to work without making any changes but it is quite slow logging on and off (I put this down to the fairly slow ADSL links we have between the sites). I was giving the issue some thought and tried creating a test user and changing the profile path to %logonserver%\profiles\user.name which when logging on created a profile on the logon server of whichever site I was at. However, I tried then rsyncing this profile across from one server at one site to another server (I've also tried it between two servers on the same site) but the permissions seem to get corrupted... If I look at the permissions in a Linux terminal I get the following... Output from ls -lh on Server 1: drwxrwx---+ 14 360 users 4.0K Apr 17 16:15 charles.carmichael.V2 Output from ls -lh on Server 2: drwxrwx---+ 14 360 users 4.0K Apr 17 16:15 charles.carmichael.V2 So the permissions look okay to me unless I'm missing something. If I check the permissions of the two profile folders in Windows 7 I get the following: Server 1 Permissions: SYSTEM - Full Control Charles.Carmichael - Full Control Server 2 Permissions: Everyone - None RANDOMPC$ - Full Control Random Group - Full Control Domain Users - None CREATOR OWNER - Special CREATOR GROUP - Special On Server 1 the owner is the user of the profile, on Server 2 the owner is RANDOMPC$. Both Server 1 and Server 2 are running Samba 4.0.3, Debian Squeeze AMD64 with the kernel 2.6.32-5-amd64. If it helps the filesystems are ext4 and have the options user_xattr,acl,barrier=1 in fstab. What we'd like to do is run an rsync overnight and copy the differences between the servers, but as we're coming across these issues we're a bit stuck. If anyone could help, or maybe suggest another way of syncing the roaming profiles between the servers that would be great. Thanks in advance, Rob -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba4 internal dns update
Hey Cristian: This sounds exactly like the issue I had, documented in: https://lists.samba.org/archive/samba/2013-April/172611.html When computers are first joined, it appears as though samba sets *static* DNS entries for them, even though their IPs are likely to change. I haven't yet had a chance to check the proposed fixes (either deleting/updating the entries via the Windows DNS console, or setting each client to update their DNS). The DNS settings is called Register this connection's addresses in DNS and looks like: http://imgur.com/B33UYhI Not sure if this is a bug -- seems odd, since many clients are DHCP assigned. - Nick On Wed, Apr 17, 2013 at 10:28 AM, Cristian Saavedra c...@asualcance.comwrote: Hello Last week we changed our ip range, every computer was shutdown and everything is working, but we are still getting the old ip address on the dns, my version is samba 4.0.3 and i am using internal dns This is the actual smb.conf [global] workgroup = MYCOMPANY realm = MYCOMPANY.COM.CO netbios name = DOMINIO server role = active directory domain controller idmap_ldb:use rfc2307 = yes dns forwarder = 8.8.8.8 wins support = Yes log level = 1 allow dns updates = True Any suggestions? Thanks -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] SaMBa 4 - dbcheck
Hi all, I migrated a base Samba3 to Samba4 with classicupgrade and then ran the DBCHECK. Is returning the error bellow. This occurs when we have accented characters in basis. How do I fix this? root@samba: # samba-tool dbcheck Checking 8987 objects Conversion error: Illegal multibyte sequence(�mella x,y) ERROR(runtime): uncaught exception - (31, 'WERR_GENERAL_FAILURE') File /usr/local/lib/python2.7/site-packages/samba/netcmd/__init__.py, line 175, in _run return self.run(*args, **kwargs) File /usr/local/lib/python2.7/site-packages/samba/netcmd/dbcheck.py, line 117, in run controls=controls, attrs=attrs) File /usr/local/lib/python2.7/site-packages/samba/dbchecker.py, line 87, in check_database error_count += self.check_object(object.dn, attrs=attrs) File /usr/local/lib/python2.7/site-packages/samba/dbchecker.py, line 834, in check_object normalised = self.samdb.dsdb_normalise_attributes(self.samdb_schema, attrname, [val]) File /usr/local/lib/python2.7/site-packages/samba/samdb.py, line 623, in dsdb_normalise_attributes return dsdb._dsdb_normalise_attributes(ldb, ldap_display_name, ldif_elements) Thanks -- Celso Vianna BSD User: 51318 http://www.bsdcounter.org Palmas/TO -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba4 Seize Roles
I have a samba4.0.0alpha making problems, now i decide update to samba4.0.3 with the following step 1. Compile and install samba 4.0.3 in a new machine 2. provision with samba-tool domain join NEWDC DC -UAdministrator 3. now seize roles with samba-tool fsmo seize --role=all 4. all roles except one are transfer to new dc # samba-tool fsmo show InfrastructureMasterRole owner: CN=NTDS Settings,CN=NEWDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=myname,DC=com,DC=co RidAllocationMasterRole owner: CN=NTDS Settings,CN=NEWDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=myname,DC=com,DC=co PdcEmulationMasterRole owner: CN=NTDS Settings,CN=NEWDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=myname,DC=com,DC=co DomainNamingMasterRole owner: CN=NTDS Settings,CN=OLDDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=myname,DC=com,DC=co SchemaMasterRole owner: CN=NTDS Settings,CN=NEWDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=myname,DC=com,DC=co now when try yo seize the last role i get a error i dont know how to fix # samba-tool fsmo seize --role=naming Attempting transfer... ERROR(ldb): uncaught exception - Failed FSMO transfer: WERR_BADFILE File /usr/local/samba/lib/python2.7/site-packages/samba/netcmd/__init__.py, line 175, in _run return self.run(*args, **kwargs) File /usr/local/samba/lib/python2.7/site-packages/samba/netcmd/fsmo.py, line 160, in run self.seize_role(role, samdb, force) File /usr/local/samba/lib/python2.7/site-packages/samba/netcmd/fsmo.py, line 126, in seize_role transfer_role(self.outf, role, samdb) File /usr/local/samba/lib/python2.7/site-packages/samba/netcmd/fsmo.py, line 53, in transfer_role samdb.modify(m) can help me with this error -- Julian Reyes -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba4 Seize Roles
Am 17.04.2013 18:51, schrieb Julian: now when try yo seize the last role i get a error i dont know how to fix # samba-tool fsmo seize --role=naming This bug is not fixed yet: https://bugzilla.samba.org/show_bug.cgi?id=9461 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Migration Samba to AD
Hello, Am 17.04.2013 15:13, schrieb Thiago Fortes: I have a pdc samba 3+openldap+debian 5 and I need to migrate the ad windows (2003,2008 or 2012). How can I do this? Have you already started with the AD howto (http://wiki.samba.org/index.php/Samba_AD_DC_HOWTO). There is also a s3 migration howto linked. Regards, Marc -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Freebsd 3.5-4 New Server Profile Paths Lost
I am migrating a Freebsd 8.2 Samba 3.5.11 system to Freebsd 9.1 Samba 4.0.4. I copied over all of the users home directories, local accounts, and the tdb files. I ran the classic upgrade tool, got the server up and running, and users could login however they were on fresh local profiles rather than roaming profiles. In the log file for the station, I found the following message [2013/04/13 15:42:48.565068, 3] ../source3/smbd/password.c:138(register_homes_share) No home directory defined for user 'DOMAINNAME\johndoe' From there, I pulled up the user data in pdbedit and found that several fields were not populated from the old server to the new. I tried manually filling in the fields, and verified the config still pointed to the profile path in the same place, however the user account still could not connect to the roaming profile directory. From the original server : #pdbedit -L -v johndoe Full Name:John Doe Home Directory: \\server1\johndoe HomeDir Drive:h: Logon Script: Profile Path: \\server1\johndoe\profile Domain: DOMAINNAME And the new Server : # pdbedit -L -v johndoe Full Name:John Doe Home Directory: HomeDir Drive:(null) Logon Script: Profile Path: Domain: I can only perform testing in the off hours, as the new server already has several other services running on it. The new server will take over the ip address and network name of the old server on its 2nd nic when it is placed into production. Any ideas? Thanks -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba4: force user issue
Am 17.04.2013 16:24, schrieb Steve Thompson: The addition of the force user directive causes a failure (the user sysmgr is a member of the sysgrp group and owns all files and directories): [g_sysmgr] path = /fs/europa/g_sysmgr valid users = +sysgrp force user = sysmgr % smbclient //icse/g_sysmgr -U smt Enter smt's password: Domain=[EUROPA] OS=[Unix] Server=[Samba 3.6.9-151.el6] tree connect failed: NT_STATUS_INTERNAL_DB_CORRUPTION Maybe related to https://bugzilla.samba.org/show_bug.cgi?id=9746 ? Regards, Marc -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Can we update idmap documentation for 3.6?
Am 17.04.2013 05:49, schrieb Heather Choi: Now I'm not really sure anymore what to reference for 3.6's latest id mapping configuration file changes.. This works for my 3.6 member servers in a samba 4 AD. http://wiki.samba.org/index.php/Samba4/Domain_Member#Setting_up_a_basic_smb.conf But I also had problems when switching from 3.5 to 3.6, because some idmap parameters were already deprecated and 3.6 required to make changes in smb.conf. I had the same problem, to find a working solution. So I agree to your wish and maybe somebody with more knowledge about idmapping can create a wiki page about that topic. Regards, Marc -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Migration Samba to AD
Am 17.04.2013 23:15, schrieb Julian: Migration from Samba 4.0.0 alphaGIT version on Centos to Samba 4.0.3 on Ubuntu 12.04 Ok. Then first you have to join your new installation as DC to the domain: http://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC Make sure, that replication, etc. works. Then you have to seize roles. http://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC#FSMO_role_transfer But currently there is a bug (#9461), and the naming role doesn't seize without error. # samba-tool fsmo seize --role=rid Attempting transfer... FSMO transfer of 'rid' role successful ERROR: Failed to initiate role seize of 'rid' role: objectclass: modify message must have elements/attributes! Why the rid role fails on your installation I can't tell. What alpha is your old installation? Maybe it's better to bring that old alpha to the latest version and then try it again (but transfering the naming role will still fail on the latest version. But the others worked here fine). Did you get this error on your first try? Or did you already tried to seize multiple times or maybe already back to the old host? What does 'samba-tool fsmo show' say? Do you just replace an old installation? Maybe then it's easier to move your whole samba 4 installation to the new host, which have the same IP and hostname. Regards, Marc -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Can we update idmap documentation for 3.6?
Hi Heather, On 2013-04-16 at 22:49 -0500, Heather Choi wrote: Just when I thought I had idmap changes correct for 3.6, I realize I have a setup that's not quite right: getent passwd -No AD users getent passwd DOMAINA\\aduser aduser:*:1001601:1000513::/home/aduser:/bin/bash Shouldn't getent passwd show both local and AD users? This is not an idmap misconfiguration, but by design: You only get enumeration of AD users (groups), when you set winbind enum users = yes (winbind enum groups = yes) in your config. They are turned off by default. Please see the corresponding entries in the smb.conf manpage. Samba has had such an identity crisis over the years with idmap documentation. Depending, on where you look, even samba.org, different documentation states outdated configuration examples if you are using 3.6. And some of it almost even seems to contradict each other? Now I'm not really sure anymore what to reference for 3.6's latest id mapping configuration file changes.. The smb.conf manpage and the idmap_* manpages that come with your samba 3.6 documentation. They are complete and up to date. Please also see my talk from sambaXP 2011: http://www.samba.org/~obnox/presentations/sambaXP-2011/sambaxp-2011-talk-idmap-handout.pdf For instance, I'm not sure which one is correct anymore: is it: idmap config * : backend = tdb idmap config * : range = 900-999 idmap config DOMAINA : backend = rid idmap config DOMAINA : range = 100 - 199 idmap config DOMAINB : backend = rid idmap config DOMAINB : range = 200 - 299 This is a valid configuration. or: idmap config * : backend = tdb idmap config * : range = 100-299 idmap config DOMAINA : backend = rid idmap config DOMAINA : range = 100 - 199 idmap config DOMAINB : backend = rid idmap config DOMAINB : range = 200 - 299 This is syntactically correct, but it is not valid since the default (*) range contains the other ranges. Instead, the ranges should be mutually disjoint (non-overlapping) as in the first example. Can we have a sane effort to publish updated documentation for id mapping that's relevant to Samba 3.6? Firstly, I do again want to point you to the manual pages shipped with the samba version as the authoritative source of documentation for the release. Secondly, I do understand the request for updated documentation on wiki/websites, etc. I will see what I can do. Contributions are highly welcome! Cheers - Michael signature.asc Description: Digital signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba4: force user issue
On Wed, 17 Apr 2013, Marc Muehlfeld wrote: Am 17.04.2013 16:24, schrieb Steve Thompson: The addition of the force user directive causes a failure (the user sysmgr is a member of the sysgrp group and owns all files and directories): [g_sysmgr] path = /fs/europa/g_sysmgr valid users = +sysgrp force user = sysmgr % smbclient //icse/g_sysmgr -U smt Enter smt's password: Domain=[EUROPA] OS=[Unix] Server=[Samba 3.6.9-151.el6] tree connect failed: NT_STATUS_INTERNAL_DB_CORRUPTION Maybe related to https://bugzilla.samba.org/show_bug.cgi?id=9746 ? Mmm, not sure about that. It occurs only when the server is a member of a Samba4 domain and I am using security=ads. With a samba3 domain and security=user, it works (with the same Samba version and share definition). I believe that I omitted to mention that I am connecting as the user smt, and that user is also a member of the sysgrp group. Steve -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Rsyncing Samba4 Roaming Profiles between servers
See the plus on drwxrwx---+, that means you have either extended attributes or ACL's (my guess would be ACL's) so, I am willing to bet you haven't told rsync to preserve xattribs or acl's in your script. getfacl, setfacl, getfattr, and setfattr will be helpful in sorting this out. Good luck, Ricky On Wed, Apr 17, 2013 at 10:32 AM, Rob Beard r...@mareandfoal.org wrote: Hi folks, I've got a bit of an issue with roaming profiles and I wondered if someone might be able to help please? :-) We've started rolling out Samba 4 across our network. Currently it's on 3 of our 4 sites, one site has two Samba servers and two sites have one Samba server each (well one site has two Samba 4 servers but one of the servers was an oldish test box which I'm planning on removing from AD when I can work out how to, but that's a separate issue). I've managed to get roaming profiles working for the users on each site. Each user is currently configured to store their roaming profile on the server on the site that they're based at. This seems to work pretty well with our Windows 7 clients and the users are happy that they can now login to any PC and get their desktop icons etc. Now my boss would like the ability to be able to login to a PC on a remote site (as in, not the site where his roaming profile is stored) and have the profile available. It seems to work without making any changes but it is quite slow logging on and off (I put this down to the fairly slow ADSL links we have between the sites). I was giving the issue some thought and tried creating a test user and changing the profile path to %logonserver%\profiles\user.name which when logging on created a profile on the logon server of whichever site I was at. However, I tried then rsyncing this profile across from one server at one site to another server (I've also tried it between two servers on the same site) but the permissions seem to get corrupted... If I look at the permissions in a Linux terminal I get the following... Output from ls -lh on Server 1: drwxrwx---+ 14 360 users 4.0K Apr 17 16:15 charles.carmichael.V2 Output from ls -lh on Server 2: drwxrwx---+ 14 360 users 4.0K Apr 17 16:15 charles.carmichael.V2 So the permissions look okay to me unless I'm missing something. If I check the permissions of the two profile folders in Windows 7 I get the following: Server 1 Permissions: SYSTEM - Full Control Charles.Carmichael - Full Control Server 2 Permissions: Everyone - None RANDOMPC$ - Full Control Random Group - Full Control Domain Users - None CREATOR OWNER - Special CREATOR GROUP - Special On Server 1 the owner is the user of the profile, on Server 2 the owner is RANDOMPC$. Both Server 1 and Server 2 are running Samba 4.0.3, Debian Squeeze AMD64 with the kernel 2.6.32-5-amd64. If it helps the filesystems are ext4 and have the options user_xattr,acl,barrier=1 in fstab. What we'd like to do is run an rsync overnight and copy the differences between the servers, but as we're coming across these issues we're a bit stuck. If anyone could help, or maybe suggest another way of syncing the roaming profiles between the servers that would be great. Thanks in advance, Rob -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] samba4 internal dns update
Sounds like you are hitting this bug ... https://bugzilla.samba.org/show_bug.cgi?id=9216 There are instructions there on how to work around this issue. Ricky On Wed, Apr 17, 2013 at 11:03 AM, Nick Semenkovich seme...@alum.mit.eduwrote: Hey Cristian: This sounds exactly like the issue I had, documented in: https://lists.samba.org/archive/samba/2013-April/172611.html When computers are first joined, it appears as though samba sets *static* DNS entries for them, even though their IPs are likely to change. I haven't yet had a chance to check the proposed fixes (either deleting/updating the entries via the Windows DNS console, or setting each client to update their DNS). The DNS settings is called Register this connection's addresses in DNS and looks like: http://imgur.com/B33UYhI Not sure if this is a bug -- seems odd, since many clients are DHCP assigned. - Nick On Wed, Apr 17, 2013 at 10:28 AM, Cristian Saavedra c...@asualcance.com wrote: Hello Last week we changed our ip range, every computer was shutdown and everything is working, but we are still getting the old ip address on the dns, my version is samba 4.0.3 and i am using internal dns This is the actual smb.conf [global] workgroup = MYCOMPANY realm = MYCOMPANY.COM.CO netbios name = DOMINIO server role = active directory domain controller idmap_ldb:use rfc2307 = yes dns forwarder = 8.8.8.8 wins support = Yes log level = 1 allow dns updates = True Any suggestions? Thanks -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Freebsd 3.5-4 New Server Profile Paths Lost
These attributes should be defined in Active Directory Users and Computers, take a look at https://wiki.samba.org/index.php/Samba_AD_management_from_windows for how to get it running, then you can select all your users and define them using the %USERNAME% variable, for home directory \\server\%USERNAME% and for profiles \\server\%USERNAME%\profile Ricky On Wed, Apr 17, 2013 at 1:46 PM, David Menzel da...@jbautotech.com wrote: I am migrating a Freebsd 8.2 Samba 3.5.11 system to Freebsd 9.1 Samba 4.0.4. I copied over all of the users home directories, local accounts, and the tdb files. I ran the classic upgrade tool, got the server up and running, and users could login however they were on fresh local profiles rather than roaming profiles. In the log file for the station, I found the following message [2013/04/13 15:42:48.565068, 3] ../source3/smbd/password.c:** 138(register_homes_share) No home directory defined for user 'DOMAINNAME\johndoe' From there, I pulled up the user data in pdbedit and found that several fields were not populated from the old server to the new. I tried manually filling in the fields, and verified the config still pointed to the profile path in the same place, however the user account still could not connect to the roaming profile directory. From the original server : #pdbedit -L -v johndoe Full Name:John Doe Home Directory: \\server1\johndoe HomeDir Drive:h: Logon Script: Profile Path: \\server1\johndoe\profile Domain: DOMAINNAME And the new Server : # pdbedit -L -v johndoe Full Name:John Doe Home Directory: HomeDir Drive:(null) Logon Script: Profile Path: Domain: I can only perform testing in the off hours, as the new server already has several other services running on it. The new server will take over the ip address and network name of the old server on its 2nd nic when it is placed into production. Any ideas? Thanks -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Can't join domain as additional domain controller
I'm trying to join an existing domain as an additional domain controller but I keep getting errors. Existing domain controller is an old Win2K server named 'Server'. [root@Server1 samba4]# samba-tool domain join HERSCHLAUREN DC -U administrator --realm=HERSCHLAUREN.COM Finding a writeable DC for domain 'HERSCHLAUREN' Found DC SERVER.HERSCHLAUREN Failed to connect to ldap URL 'ldap://SERVER.HERSCHLAUREN' - LDAP client internal error: NT_STATUS_OBJECT_NAME_NOT_FOUND Failed to connect to 'ldap://SERVER.HERSCHLAUREN' with backend 'ldap': (null) ERROR(ldb): uncaught exception - None File /usr/local/samba/lib64/python2.6/site-packages/samba/netcmd/__init__.py, line 175, in _run return self.run(*args, **kwargs) File /usr/local/samba/lib64/python2.6/site-packages/samba/netcmd/domain.py, line 552, in run machinepass=machinepass, use_ntvfs=use_ntvfs, dns_backend=dns_backend) File /usr/local/samba/lib64/python2.6/site-packages/samba/join.py, line 1082, in join_DC machinepass, use_ntvfs, dns_backend, promote_existing) File /usr/local/samba/lib64/python2.6/site-packages/samba/join.py, line 78, in __init__ credentials=ctx.creds, lp=ctx.lp) File /usr/local/samba/lib64/python2.6/site-packages/samba/samdb.py, line 56, in __init__ options=options) File /usr/local/samba/lib64/python2.6/site-packages/samba/__init__.py, line 114, in __init__ self.connect(url, flags, options) File /usr/local/samba/lib64/python2.6/site-packages/samba/samdb.py, line 71, in connect options=options) Am I doing something wrong here or is this functionality not quite working yet? Cheers, Phil Quesinberry Q Systems Engineering, Inc. Embedded Systems Hardware/Software Development and VoIP Business Telephone Hosting Improve your business telephone services and save money (410) 969-8002 http://www.qsystemsengineering.com http://www.qsystemsengineering.com/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[SCM] Samba Shared Repository - branch v4-0-test updated
The branch, v4-0-test has been updated via 9bfcb9f Ensure we test the dirsort module in make test. via 2870ba2 Remove unneeded initializations (we already talloc_zero). via a677246 Remove the use of dirfd inside the vfs_dirsort.c. via b8712d0 Convert mtime from a time_t to a struct timespec. via f8da00d Check SMB_VFS_NEXT_OPENDIR return in dirsort_opendir(). via 38858df Clean error paths in opendir and fd_opendir by only setting handle data on success. via c0b62e9 Protect open_and_sort_dir() from the directory changing size. via bb3a65a Use an index i rather than re-using a state variable. via c483976 Protect against early error in SMB_VFS_NEXT_READDIR. via d95f2b0 Change source3/modules/vfs_dirsort.c from MALLOC - TALLOC. via 284f579 s3:smbd: do not access data behind req-buf+req-buflen in srvstr_pull_req_talloc() via c22b34a s3:smbd: convert srvstr_pull_req_talloc() into a function via 8394dd2 s3:smbd: do not access data behind req-buf+req-buflen in srvstr_get_path_req_wcard() from 86dbc31 BUG 9766: Cache name_to_sid/sid_to_name correctly. http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v4-0-test - Log - commit 9bfcb9f43c36419d60368086a0f21d04cf9ecca8 Author: Jeremy Allison j...@samba.org Date: Tue Apr 9 16:56:24 2013 -0700 Ensure we test the dirsort module in make test. Signed-off-by: Jeremy Allison j...@samba.org Reviewed-by: Andreas Schneider a...@samba.org Autobuild-User(master): Jeremy Allison j...@samba.org Autobuild-Date(master): Thu Apr 11 21:17:21 CEST 2013 on sn-devel-104 The last 10 patches address bug #9777 - vfs_dirsort uses non-stackable calls, dirfd(), malloc instead of talloc and doesn't cope with directories being modified whilst reading. Autobuild-User(v4-0-test): Karolin Seeger ksee...@samba.org Autobuild-Date(v4-0-test): Wed Apr 17 10:43:37 CEST 2013 on sn-devel-104 commit 2870ba20d69abec387cbbfe4f8c97ed3fdcdb44f Author: Jeremy Allison j...@samba.org Date: Tue Apr 9 11:02:58 2013 -0700 Remove unneeded initializations (we already talloc_zero). Signed-off-by: Jeremy Allison j...@samba.org Reviewed-by: Andreas Schneider a...@samba.org commit a6772469a42db5f8a7a0bd2d4787bd4a07cfc1ef Author: Jeremy Allison j...@samba.org Date: Tue Apr 9 10:50:55 2013 -0700 Remove the use of dirfd inside the vfs_dirsort.c. Signed-off-by: Jeremy Allison j...@samba.org Reviewed-by: Andreas Schneider a...@samba.org commit b8712d02665163dad4b922c4966803019931aeaa Author: Jeremy Allison j...@samba.org Date: Tue Apr 9 10:43:53 2013 -0700 Convert mtime from a time_t to a struct timespec. In preparation for removing the dirfd and using fsp_stat() and VFS_STAT functions. Signed-off-by: Jeremy Allison j...@samba.org Reviewed-by: Andreas Schneider a...@samba.org commit f8da00db45e3b81d8b0a6c0c62f113c64e0e40fe Author: Jeremy Allison j...@samba.org Date: Tue Apr 9 10:38:24 2013 -0700 Check SMB_VFS_NEXT_OPENDIR return in dirsort_opendir(). Signed-off-by: Jeremy Allison j...@samba.org Reviewed-by: Andreas Schneider a...@samba.org commit 38858df51b2c10f80a0ac539f90d3bd4dd7a4b42 Author: Jeremy Allison j...@samba.org Date: Tue Apr 9 10:29:47 2013 -0700 Clean error paths in opendir and fd_opendir by only setting handle data on success. Pass extra struct dirsort_privates * to open_and_sort_dir() function to avoid it having to re-read the handle data. Signed-off-by: Jeremy Allison j...@samba.org Reviewed-by: Andreas Schneider a...@samba.org commit c0b62e9b8c7a4b41dbc2d3600cd9cc67931165a2 Author: Jeremy Allison j...@samba.org Date: Mon Apr 8 16:40:35 2013 -0700 Protect open_and_sort_dir() from the directory changing size. Otherwise there could be an error between initial count, allocation and re-read. Signed-off-by: Jeremy Allison j...@samba.org Reviewed-by: Andreas Schneider a...@samba.org commit bb3a65a572133a1a479ce8f3948d61367ed9aa31 Author: Jeremy Allison j...@samba.org Date: Mon Apr 8 16:38:03 2013 -0700 Use an index i rather than re-using a state variable. Signed-off-by: Jeremy Allison j...@samba.org Reviewed-by: Andreas Schneider a...@samba.org commit c4839767316a9e74a26e0691873e4e84357905a2 Author: Jeremy Allison j...@samba.org Date: Mon Apr 8 16:31:53 2013 -0700 Protect against early error in SMB_VFS_NEXT_READDIR. Signed-off-by: Jeremy Allison j...@samba.org Reviewed-by: Andreas Schneider a...@samba.org commit d95f2b085098c1d5e637beaea6eda5bcb03ac197 Author: Jeremy Allison j...@samba.org Date: Mon Apr 8 15:11:28 2013 -0700 Change source3/modules/vfs_dirsort.c from MALLOC - TALLOC. Signed-off-by: Jeremy Allison j...@samba.org Reviewed-by: Andreas
[SCM] CTDB repository - branch master updated - ctdb-2.1-51-g5808f07
The branch, master has been updated
via 5808f0778b39b79ab7a5c7f53ad27947131386ec (commit)
via e691df43d20871468142c8fb83f7c7303c4ec307 (commit)
from 043e18a8324ccb2c8ddd7b323ebedb5b0de1298d (commit)
http://gitweb.samba.org/?p=ctdb.git;a=shortlog;h=master
- Log -
commit 5808f0778b39b79ab7a5c7f53ad27947131386ec
Author: Amitay Isaacs ami...@gmail.com
Date: Thu Apr 11 13:20:09 2013 +1000
traverse: Ensure backward compatibility for CTDB_CONTROL_TRAVERSE_ALL
This makes sure that CTDB_CONTROL TRAVERSE_ALL is compatible with older
versions
of CTDB (i.e. 1.2.39 and 1.2.40 branches).
Signed-off-by: Amitay Isaacs ami...@gmail.com
Reviewed-by: Michael Adam ob...@samba.org
commit e691df43d20871468142c8fb83f7c7303c4ec307
Author: Amitay Isaacs ami...@gmail.com
Date: Thu Apr 11 13:18:36 2013 +1000
traverse: Add CTDB_CONTROL_TRAVERSE_ALL_EXT to support withemptyrecords
Signed-off-by: Amitay Isaacs ami...@gmail.com
Reviewed-by: Michael Adam ob...@samba.org
---
Summary of changes:
include/ctdb_private.h |1 +
include/ctdb_protocol.h |1 +
server/ctdb_control.c |3 +
server/ctdb_traverse.c | 101 +--
4 files changed, 94 insertions(+), 12 deletions(-)
Changeset truncated at 500 lines:
diff --git a/include/ctdb_private.h b/include/ctdb_private.h
index 7e46603..ecdf257 100644
--- a/include/ctdb_private.h
+++ b/include/ctdb_private.h
@@ -1015,6 +1015,7 @@ int32_t ctdb_control_traverse_start_ext(struct
ctdb_context *ctdb,
int32_t ctdb_control_traverse_start(struct ctdb_context *ctdb, TDB_DATA
indata,
TDB_DATA *outdata, uint32_t srcnode,
uint32_t client_id);
int32_t ctdb_control_traverse_all(struct ctdb_context *ctdb, TDB_DATA data,
TDB_DATA *outdata);
+int32_t ctdb_control_traverse_all_ext(struct ctdb_context *ctdb, TDB_DATA
data, TDB_DATA *outdata);
int32_t ctdb_control_traverse_data(struct ctdb_context *ctdb, TDB_DATA data,
TDB_DATA *outdata);
int32_t ctdb_control_traverse_kill(struct ctdb_context *ctdb, TDB_DATA indata,
TDB_DATA *outdata, uint32_t srcnode);
diff --git a/include/ctdb_protocol.h b/include/ctdb_protocol.h
index cc3ea3f..9302c7b 100644
--- a/include/ctdb_protocol.h
+++ b/include/ctdb_protocol.h
@@ -402,6 +402,7 @@ enum ctdb_controls {CTDB_CONTROL_PROCESS_EXISTS =
0,
CTDB_CONTROL_GET_DB_STATISTICS = 132,
CTDB_CONTROL_SET_DB_STICKY = 133,
CTDB_CONTROL_RELOAD_PUBLIC_IPS = 134,
+ CTDB_CONTROL_TRAVERSE_ALL_EXT= 135,
};
/*
diff --git a/server/ctdb_control.c b/server/ctdb_control.c
index 9708acd..b567865 100644
--- a/server/ctdb_control.c
+++ b/server/ctdb_control.c
@@ -264,6 +264,9 @@ static int32_t ctdb_control_dispatch(struct ctdb_context
*ctdb,
case CTDB_CONTROL_TRAVERSE_ALL:
return ctdb_control_traverse_all(ctdb, indata, outdata);
+ case CTDB_CONTROL_TRAVERSE_ALL_EXT:
+ return ctdb_control_traverse_all_ext(ctdb, indata, outdata);
+
case CTDB_CONTROL_TRAVERSE_DATA:
return ctdb_control_traverse_data(ctdb, indata, outdata);
diff --git a/server/ctdb_traverse.c b/server/ctdb_traverse.c
index df0afb0..d9aed2b 100644
--- a/server/ctdb_traverse.c
+++ b/server/ctdb_traverse.c
@@ -232,6 +232,14 @@ struct ctdb_traverse_all {
uint32_t pnn;
uint32_t client_reqid;
uint64_t srvid;
+};
+
+struct ctdb_traverse_all_ext {
+ uint32_t db_id;
+ uint32_t reqid;
+ uint32_t pnn;
+ uint32_t client_reqid;
+ uint64_t srvid;
bool withemptyrecords;
};
@@ -277,6 +285,7 @@ static struct ctdb_traverse_all_handle
*ctdb_daemon_traverse_all(struct ctdb_db_
int ret;
TDB_DATA data;
struct ctdb_traverse_all r;
+ struct ctdb_traverse_all_ext r_ext;
uint32_t destination;
state = talloc(start_state, struct ctdb_traverse_all_handle);
@@ -294,15 +303,26 @@ static struct ctdb_traverse_all_handle
*ctdb_daemon_traverse_all(struct ctdb_db_
talloc_set_destructor(state, ctdb_traverse_all_destructor);
- r.db_id = ctdb_db-db_id;
- r.reqid = state-reqid;
- r.pnn = ctdb-pnn;
- r.client_reqid = start_state-reqid;
- r.srvid = start_state-srvid;
- r.withemptyrecords = start_state-withemptyrecords;
+ if (start_state-withemptyrecords) {
+ r_ext.db_id = ctdb_db-db_id;
+ r_ext.reqid = state-reqid;
+ r_ext.pnn = ctdb-pnn;
+ r_ext.client_reqid = start_state-reqid;
+ r_ext.srvid = start_state-srvid;
+ r_ext.withemptyrecords = start_state-withemptyrecords;
-
[SCM] CTDB repository - branch master updated - ctdb-2.1-55-g4c0cbfb
The branch, master has been updated
via 4c0cbfbe8b19f2e6fe17093b52c734bec63dd8b7 (commit)
via 2e92deef5221ee651028ef87138b3113f1fece91 (commit)
via 9f01b8db72780acf2f88f1392bc0a796dd4c6176 (commit)
via e96acf19b4d1e0f951ab92b88869a01ff06398be (commit)
from 5808f0778b39b79ab7a5c7f53ad27947131386ec (commit)
http://gitweb.samba.org/?p=ctdb.git;a=shortlog;h=master
- Log -
commit 4c0cbfbe8b19f2e6fe17093b52c734bec63dd8b7
Author: Michael Adam ob...@samba.org
Date: Mon Apr 15 12:50:42 2013 +0200
logging: fix comment typo
Signed-off-by: Michael Adam ob...@samba.org
Reviewed-by: Amitay Isaacs ami...@gmail.com
commit 2e92deef5221ee651028ef87138b3113f1fece91
Author: Michael Adam ob...@samba.org
Date: Wed Apr 3 14:03:32 2013 +0200
ctdbd: unimplement the unused SET_DMASTER control
Signed-off-by: Michael Adam ob...@samba.org
Reviewed-by: Amitay Isaacs ami...@gmail.com
commit 9f01b8db72780acf2f88f1392bc0a796dd4c6176
Author: Michael Adam ob...@samba.org
Date: Fri Mar 22 17:48:00 2013 +0100
recoverd: remove bogus comment qqq from add prototype new banning code
Signed-off-by: Michael Adam ob...@samba.org
Reviewed-by: Amitay Isaacs ami...@gmail.com
commit e96acf19b4d1e0f951ab92b88869a01ff06398be
Author: Michael Adam ob...@samba.org
Date: Fri Apr 5 16:55:18 2013 +0200
build: silence building of porting_test
Signed-off-by: Michael Adam ob...@samba.org
Reviewed-by: Amitay Isaacs ami...@gmail.com
---
Summary of changes:
Makefile.in |2 +-
include/ctdb_private.h |1 -
include/ctdb_protocol.h |2 +-
server/ctdb_control.c |4 ++-
server/ctdb_logging.c |2 +-
server/ctdb_recover.c | 53 ---
server/ctdb_recoverd.c |1 -
7 files changed, 6 insertions(+), 59 deletions(-)
Changeset truncated at 500 lines:
diff --git a/Makefile.in b/Makefile.in
index 9511e90..87a3bd3 100755
--- a/Makefile.in
+++ b/Makefile.in
@@ -260,7 +260,7 @@ tests/bin/ctdb_persistent: $(CTDB_CLIENT_OBJ)
tests/src/ctdb_persistent.o
tests/bin/ctdb_porting_tests: $(CTDB_CLIENT_OBJ) tests/src/ctdb_porting_tests.o
@echo Linking $@
- $(CC) $(CFLAGS) -o $@ tests/src/ctdb_porting_tests.o $(CTDB_CLIENT_OBJ)
$(LIB_FLAGS)
+ @$(CC) $(CFLAGS) -o $@ tests/src/ctdb_porting_tests.o
$(CTDB_CLIENT_OBJ) $(LIB_FLAGS)
tests/bin/ctdb_transaction: $(CTDB_CLIENT_OBJ) tests/src/ctdb_transaction.o
@echo Linking $@
diff --git a/include/ctdb_private.h b/include/ctdb_private.h
index ecdf257..d0c4234 100644
--- a/include/ctdb_private.h
+++ b/include/ctdb_private.h
@@ -1042,7 +1042,6 @@ struct ctdb_rec_data *ctdb_marshall_loop_next(struct
ctdb_marshall_buffer *m, st
int32_t ctdb_control_pull_db(struct ctdb_context *ctdb, TDB_DATA indata,
TDB_DATA *outdata);
int32_t ctdb_control_push_db(struct ctdb_context *ctdb, TDB_DATA indata);
-int32_t ctdb_control_set_dmaster(struct ctdb_context *ctdb, TDB_DATA indata);
int32_t ctdb_control_set_recmode(struct ctdb_context *ctdb,
struct ctdb_req_control *c,
diff --git a/include/ctdb_protocol.h b/include/ctdb_protocol.h
index 9302c7b..751fe32 100644
--- a/include/ctdb_protocol.h
+++ b/include/ctdb_protocol.h
@@ -283,7 +283,7 @@ enum ctdb_controls {CTDB_CONTROL_PROCESS_EXISTS =
0,
CTDB_CONTROL_SET_DEBUG = 8,
CTDB_CONTROL_GET_DBMAP = 9,
CTDB_CONTROL_GET_NODEMAPv4 = 10, /* obsolete */
- CTDB_CONTROL_SET_DMASTER = 11,
+ CTDB_CONTROL_SET_DMASTER = 11, /* obsolete */
/* #12 removed */
CTDB_CONTROL_PULL_DB = 13,
CTDB_CONTROL_PUSH_DB = 14,
diff --git a/server/ctdb_control.c b/server/ctdb_control.c
index b567865..99b3dc4 100644
--- a/server/ctdb_control.c
+++ b/server/ctdb_control.c
@@ -169,7 +169,9 @@ static int32_t ctdb_control_dispatch(struct ctdb_context
*ctdb,
case CTDB_CONTROL_SET_DMASTER:
CHECK_CONTROL_DATA_SIZE(sizeof(struct
ctdb_control_set_dmaster));
- return ctdb_control_set_dmaster(ctdb, indata);
+ DEBUG(DEBUG_ERR, (The SET_DMASTER control is not implemented
+ any more.\n));
+ return -1;
case CTDB_CONTROL_PUSH_DB:
return ctdb_control_push_db(ctdb, indata);
diff --git a/server/ctdb_logging.c b/server/ctdb_logging.c
index dfb5063..0b6ac12 100644
--- a/server/ctdb_logging.c
+++ b/server/ctdb_logging.c
@@ -65,7 +65,7 @@ static void ctdb_syslog_handler(struct event_context *ev,
struct fd_event *fde,
}
-/* called when the pipd from the main daemon
[SCM] CTDB repository - branch master updated - ctdb-2.1-60-g06ac62f
The branch, master has been updated via 06ac62f890299021220214327f1b611c3cf00145 (commit) via b1577a11d548479ff1a05702d106af9465921ad4 (commit) via 2438f3a4944f7adbcae4cc1b9d5452714244afe7 (commit) via cad3107b12e8392f786f9a758ee38cf3a3d58538 (commit) via feb1d40b21a160737aead22e398f3c34ff3be8de (commit) from 4c0cbfbe8b19f2e6fe17093b52c734bec63dd8b7 (commit) http://gitweb.samba.org/?p=ctdb.git;a=shortlog;h=master - Log - commit 06ac62f890299021220214327f1b611c3cf00145 Author: Michael Adam ob...@samba.org Date: Wed Apr 17 13:08:49 2013 +0200 tests: add a comment to recovery db corruption test The comment explains that we use ctdb stop and ctdb continue but we should use ctdb setcrecmasterrole off. Signed-off-by: Michael Adam ob...@samba.org commit b1577a11d548479ff1a05702d106af9465921ad4 Author: Amitay Isaacs ami...@gmail.com Date: Thu Apr 11 16:59:36 2013 +1000 tests: Add a test for subsequent recoveries corrupting databases Signed-off-by: Amitay Isaacs ami...@gmail.com Reviewed-by: Michael Adam ob...@samba.org commit 2438f3a4944f7adbcae4cc1b9d5452714244afe7 Author: Amitay Isaacs ami...@gmail.com Date: Thu Apr 11 16:58:34 2013 +1000 tests: Support waiting for recovered state in tests Signed-off-by: Amitay Isaacs ami...@gmail.com Reviewed-by: Michael Adam ob...@samba.org commit cad3107b12e8392f786f9a758ee38cf3a3d58538 Author: Michael Adam ob...@samba.org Date: Wed Apr 3 12:02:59 2013 +0200 ctdb_call: don't bump the rsn in ctdb_become_dmaster() any more This is now done in ctdb_ltdb_store_server(), so this extra bump can be spared. Signed-off-by: Michael Adam ob...@samba.org Reviewed-By: Amitay Isaacs ami...@gmail.com commit feb1d40b21a160737aead22e398f3c34ff3be8de Author: Michael Adam ob...@samba.org Date: Wed Apr 3 11:40:25 2013 +0200 Fix a severe recovery bug that can lead to data corruption for SMB clients. Problem: Recovery can under certain circumstances lead to old record copies resurrecting: Recovery selects the newest record copy purely by RSN. At the end of the recovery, the recovery master is the dmaster for all records in all (non-persistent) databases. And the other nodes locally hold the complete copy of the databases. The bug is that the recovery process does not increment the RSN on the recovery master at the end of the recovery. Now clients acting directly on the Recovery master will directly change a record's content on the recmaster without migration and hence without RSN bump. So a subsequent recovery can not tell that the recmaster's copy is newer than the copies on the other nodes, since their RSN is the same. Hence, if the recmaster is not node 0 (or more precisely not the active node with the lowest node number), the recovery will choose copies from nodes with lower number and stick to these. Here is how to reproduce: - assume we have a cluster with at least 2 nodes - ensure that the recmaster is not node 0 (maybe ensure with onnode 0 ctdb setrecmasterrole off) say recmaster is node 1 - choose a new database name, say test1.tdb (make sure it is not yet attached as persistent) - choose a key name, say key1 - all clustere nodes should ok and no recovery running - now do the following on node 1: 1. dbwrap_tool test1.tdb store key1 uint32 1 2. dbwrap_tool test1.tdb fetch key1 uint32 == 1 3. ctdb recover 4. dbwrap_tool test1.tdb store key1 uint32 2 5. dbwrap_tool test1.tdb fetch key1 uint32 == 2 4. ctdb recover 7. dbwrap_tool test1.tdb fetch key1 uint32 == 1 == BUG This is a very severe bug, since when applied to Samba's locking.tdb database, it means that for SMB clients on clustered Samba there is the potential for locking out oneself from previously opened files or even worse, data corruption: Case 1: locking out - client on recmaster opens file - recovery propagates open file handle (entry in locking.tdb) to other nodes - client closes file - client opens the same file - recovery resurrects old copy of open file record in locking.tdb from lower node - client closes file but fails to delete entry in locking.tdb - client tries to open same file again but fails, since the old record locks it out (since the client is still connected) Case 2: data corruption - clien1 on recmaster opens file - recovery propagates open file info to other nodes - client1 closes the file and disconnects - client2 opens the same file - recovery resurrects old copy of locking.tdb record, where client2 has no entry, but client1 has. - but client2 believes it still has a handle - client3
[SCM] Samba Shared Repository - branch master updated
The branch, master has been updated
via 0fa404c Bug 9807 - wbinfo: fix segfault in wbinfo_pam_logon
from f340795 Cleanup. Remove unused function dptr_DirCacheAdd(). Make
DirCacheAdd() static.
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -
commit 0fa404c7d5c8de826d31958613b3e97587f0835d
Author: David Disseldorp dd...@samba.org
Date: Wed Apr 17 10:39:12 2013 -0700
Bug 9807 - wbinfo: fix segfault in wbinfo_pam_logon
wbinfo_pam_logon() incorrectly assumes that wbcLogonUser() always
returns an allocated wbcAuthErrorInfo struct on failure.
Signed-off-by: David Disseldorp dd...@samba.org
Reviewed-by: Jeremy Allison j...@samba.org
Autobuild-User(master): Jeremy Allison j...@samba.org
Autobuild-Date(master): Wed Apr 17 21:29:29 CEST 2013 on sn-devel-104
---
Summary of changes:
nsswitch/wbinfo.c |7 +++
1 files changed, 3 insertions(+), 4 deletions(-)
Changeset truncated at 500 lines:
diff --git a/nsswitch/wbinfo.c b/nsswitch/wbinfo.c
index cd6de34..8b17859 100644
--- a/nsswitch/wbinfo.c
+++ b/nsswitch/wbinfo.c
@@ -1749,7 +1749,7 @@ static bool wbinfo_pam_logon(char *username)
{
wbcErr wbc_status = WBC_ERR_UNKNOWN_FAILURE;
struct wbcLogonUserParams params;
- struct wbcAuthErrorInfo *error;
+ struct wbcAuthErrorInfo *error = NULL;
char *s = NULL;
char *p = NULL;
TALLOC_CTX *frame = talloc_tos();
@@ -1800,16 +1800,15 @@ static bool wbinfo_pam_logon(char *username)
d_printf(plaintext password authentication %s\n,
WBC_ERROR_IS_OK(wbc_status) ? succeeded : failed);
- if (!WBC_ERROR_IS_OK(wbc_status)) {
+ if (!WBC_ERROR_IS_OK(wbc_status) (error != NULL)) {
d_fprintf(stderr,
error code was %s (0x%x)\nerror message was: %s\n,
error-nt_string,
(int)error-nt_status,
error-display_string);
wbcFreeMemory(error);
- return false;
}
- return true;
+ return WBC_ERROR_IS_OK(wbc_status);
}
/* Save creds with winbind */
--
Samba Shared Repository
autobuild: intermittent test failure detected
The autobuild test system has detected an intermittent failing test in the current master tree. The autobuild log of the failure is available here: http://git.samba.org/autobuild.flakey/2013-04-18-0229/flakey.log The samba3 build logs are available here: http://git.samba.org/autobuild.flakey/2013-04-18-0229/samba3.stderr http://git.samba.org/autobuild.flakey/2013-04-18-0229/samba3.stdout The source4 build logs are available here: http://git.samba.org/autobuild.flakey/2013-04-18-0229/samba.stderr http://git.samba.org/autobuild.flakey/2013-04-18-0229/samba.stdout The top commit at the time of the failure was: commit 0fa404c7d5c8de826d31958613b3e97587f0835d Author: David Disseldorp dd...@samba.org Date: Wed Apr 17 10:39:12 2013 -0700 Bug 9807 - wbinfo: fix segfault in wbinfo_pam_logon wbinfo_pam_logon() incorrectly assumes that wbcLogonUser() always returns an allocated wbcAuthErrorInfo struct on failure. Signed-off-by: David Disseldorp dd...@samba.org Reviewed-by: Jeremy Allison j...@samba.org Autobuild-User(master): Jeremy Allison j...@samba.org Autobuild-Date(master): Wed Apr 17 21:29:29 CEST 2013 on sn-devel-104
[SCM] Samba Shared Repository - branch master updated
The branch, master has been updated via 406450d smbd: Remove NTSTATUS based create_synthetic_smb_fname via cc0b835 smbd: Convert create_file_unixpath to synthetic_smb_fname via 940ad94 smbd: Convert is_visible_file to synthetic_smb_fname via 59cfbc7 smbd: Convert dptr_create to synthetic_smb_fname via 235a309 smbd: Convert print_spool_open to synthetic_smb_fname via ea519ec smbd: Convert driver_unlink_internals to synthetic_smb_fname via 2b97eb1 vfstest: Convert cmd_set_nt_acl to synthetic_smb_fname via 6f7d9b2 vfstest: Convert cmd_utime to synthetic_smb_fname via 6624095 vfstest: Convert cmd_lstat to synthetic_smb_fname via 7d54030 vfstest: Convert cmd_stat to synthetic_smb_fname via a6985e6 vfstest: Convert cmd_rename to synthetic_smb_fname via 434885a vfstest: Convert cmd_pathfunc to synthetic_smb_fname via 1f6b0af vfstest: Convert cmd_open to synthetic_smb_fname via 0cb0564 vfs: Convert dirsort_opendir to synthetic_smb_fname via 730c57b vfs: Convert vfs_scannedonly to synthetic_smb_fname via d70de07 smbd: Convert set_create_timespec_ea to synthetic_smb_fname via fb211c3 smbd: Convert unix_mode to synthetic_smb_fname via af40d23 smbd: Convert rmdir_internals to synthetic_smb_fname via f5873c9 smbd: Convert recursive_rmdir to synthetic_smb_fname via 39470c8 smbd: Convert delete_all_streams to synthetic_smb_fname via 421eeef smbd: Convert open_streams_for_delete to synthetic_smb_fname via 66beff7 smbd: Convert msg_file_was_renamed to synthetic_smb_fname via 39c5a77 smbd: Convert change_dir_owner_to_parent to synthetic_smb_fname via d003f2f smbd: Convert change_dir_owner_to_parent to synthetic_smb_fname via c9a220b smbd: Convert change_file_owner_to_parent to synthetic_smb_fname via 81e9c01 smbd: Convert make_connection_snum to synthetic_smb_fname via 10d8d7d smbd: Convert rename_internals_fsp to synthetic_smb_fname via 862c561 smbd: Convert remove_msdfs_link to synthetic_smb_fname via 576df87 smbd: Convert create_msdfs_link to synthetic_smb_fname via 01b8f34 smbd: Convert can_delete_file_in_directory to synthetic_smb_fname via e3a7f70 smbd: Convert file_new to synthetic_smb_fname via 2d76ce3 smbd: Convert open_dir_with_privilege to synthetic_smb_fname via fe79862 smbd: Convert open_np_file to synthetic_smb_fname via fa3f2fd smbd: Convert smb_file_rename_information to synthetic_smb_fname via 419dd4f smbd: Convert smb_file_rename_information to synthetic_smb_fname via 9cf8d69 smbd: Convert smb2_file_rename_information to synthetic_smb_fname via 381bd97 smbd: Convert smb_set_file_dosmode to synthetic_smb_fname via edb7293 smbd: Convert call_trans2qfilepathinfo to synthetic_smb_fname via aa52340 smbd: Convert posix_sys_acl_blob_get_file to synthetic_smb_fname via 1dc2920 pysmbd: Convert py_smbd_unlink to synthetic_smb_fname via 204d971 pysmbd: Convert set_nt_acl_conn to synthetic_smb_fname via 1675bf3 smbd: Convert filename_convert_internal to synthetic_smb_fname via 0b14720 smbd: Convert vfs_lstat_smb_fname to synthetic_smb_fname via 9041f3d smbd: Convert vfs_stat_smb_fname to synthetic_smb_fname via bde53d8 smbd: Convert check_reduced_name_with_privilege to synthetic_smb_fname via e086675 smbd: Convert vfs_GetWd to synthetic_smb_fname via 75911f9 smbd: Convert vfs_default_durable_reconnect to synthetic_smb_fname via 97d006f vfs: Convert non_posix_sys_acl_blob_get_file_helper to synthetic_smb_fname via 3d05622 vfs: Convert vfswrap_fs_capabilities to synthetic_smb_fname via a613074 vfs: Convert streams_depot_streaminfo to synthetic_smb_fname via 952d348 vfs: Convert collect_one_stream to synthetic_smb_fname via 83e6ff1 vfs: Convert streams_depot_rmdir to synthetic_smb_fname via 87d9209 vfs: Convert streams_depot_unlink to synthetic_smb_fname via 1729d78 vfs: Convert streams_depot_open to synthetic_smb_fname via 3794574 vfs: Convert stream_smb_fname to synthetic_smb_fname via 987ebb1 vfs: Convert stream_dir to synthetic_smb_fname via 441467c vfs: Convert fake_acls_sys_acl_delete_def_file to synthetic_smb_fname via 63f3980 vfs: Convert vfs_gpfs_chmod to synthetic_smb_fname via 58bb3ae vfs: Convert gpfsacl_emu_chmod to synthetic_smb_fname via 19e88da vfs: Convert recycle_unlink to synthetic_smb_fname via 3dafdd3 vfs: Convert streams_xattr_streaminfo to synthetic_smb_fname via bef6c76 vfs: Convert streams_xattr_open to synthetic_smb_fname via ec5ac90 vfs: Convert streams_xattr_fstat to synthetic_smb_fname via 7d57b8a vfs: Convert xattr_tdb_get_file_id to synthetic_smb_fname via 9b4
[SCM] CTDB repository - branch master updated - ctdb-2.1-68-ge7a4b7e
The branch, master has been updated via e7a4b7e35a1e4b826846e2494a3803abb57065ee (commit) via 1e989894764e4cd1d551c44784d91cb295cd790d (commit) via abb64f62efaa70df4b87c030b96300eafd98e6a3 (commit) via 90cb337e5ccf397b69a64298559a428ff508f196 (commit) via 687e2eace4f48400cf5029914f62b6ddabb85378 (commit) via 996e74d3db0c50f91b320af8ab7c43ea6b1136af (commit) via ba8866d40125bab06391a17d48ff06a4a9f9da89 (commit) via 59b019a97aad9a731f9080ea5be14d0dbdfe03d6 (commit) from 06ac62f890299021220214327f1b611c3cf00145 (commit) http://gitweb.samba.org/?p=ctdb.git;a=shortlog;h=master - Log - commit e7a4b7e35a1e4b826846e2494a3803abb57065ee Author: Martin Schwenke mar...@meltin.net Date: Mon Apr 15 19:15:22 2013 +1000 initscript: Remove duplicate setting of $ctdbd Signed-off-by: Martin Schwenke mar...@meltin.net Reviewed-by: Michael Adam ob...@samba.org commit 1e989894764e4cd1d551c44784d91cb295cd790d Author: Martin Schwenke mar...@meltin.net Date: Tue Apr 16 11:40:55 2013 +1000 util: Removed unused declaration of ctdbd_start() Signed-off-by: Martin Schwenke mar...@meltin.net Reviewed-by: Michael Adam ob...@samba.org commit abb64f62efaa70df4b87c030b96300eafd98e6a3 Author: Martin Schwenke mar...@meltin.net Date: Mon Apr 15 13:31:42 2013 +1000 include: Move ctdb_start_daemon() from ctdb_client.h to ctdb_private.h It really is internal. Signed-off-by: Martin Schwenke mar...@meltin.net Pair-programmed-with: Amitay Isaacs ami...@gmail.com Reviewed-by: Michael Adam ob...@samba.org commit 90cb337e5ccf397b69a64298559a428ff508f196 Author: Martin Schwenke mar...@meltin.net Date: Mon Apr 15 15:42:55 2013 +1000 scripts: ctdb-crash-cleanup.sh uses initscript to see if ctdbd is running ctdb ping can time out. How many times should we try? Instead, depend on the initscript to implement something sane. Signed-off-by: Martin Schwenke mar...@meltin.net Reviewed-by: Michael Adam ob...@samba.org commit 687e2eace4f48400cf5029914f62b6ddabb85378 Author: Martin Schwenke mar...@meltin.net Date: Mon Apr 15 15:18:12 2013 +1000 initscript: Use a PID file to implement the status option Using ctdb ping and ctdb status is fraught with danger. These commands can timeout when ctdbd is running, leading callers to believe that ctdbd is not running. Timeouts could be increased but we would still have to handle potential timeouts. Everything else in the world implements the status option by checking if the relevant process is running. This change makes CTDB do the same thing and uses standard distro functions. This change is backward compatible in sense that a missing /var/run/ctdb/ directory means that we don't do a PID file check but just depend on the distro's checking method. Therefore, if CTDB was started with an older version of this script then service ctdb status will still work. This script does not support changing the value of CTDB_VALGRIND between calls. If you start with CTDB_VALGRIND=yes then you need to check status with the same setting. CTDB_VALGRIND is a debug variable, so this is acceptable. This also adds sourcing of /lib/lsb/init-functions to make the Debian function status_of_proc() available. Signed-off-by: Martin Schwenke mar...@meltin.net Pair-programmed-with: Amitay Isaacs ami...@gmail.com Reviewed-by: Michael Adam ob...@samba.org commit 996e74d3db0c50f91b320af8ab7c43ea6b1136af Author: Martin Schwenke mar...@meltin.net Date: Mon Apr 15 13:32:57 2013 +1000 ctdbd: Add --pidfile option Default is not to create a pid file. Signed-off-by: Martin Schwenke mar...@meltin.net Pair-programmed-with: Amitay Isaacs ami...@gmail.com Reviewed-by: Michael Adam ob...@samba.org commit ba8866d40125bab06391a17d48ff06a4a9f9da89 Author: Martin Schwenke mar...@meltin.net Date: Mon Apr 15 16:14:40 2013 +1000 util: ctdb_fork() should call ctdb_set_child_info() For now we pass NULL as the child name. Later we'll give ctdb_fork() and friends an extra argument and pass that through. Signed-off-by: Martin Schwenke mar...@meltin.net Pair-programmed-with: Amitay Isaacs ami...@gmail.com Reviewed-by: Michael Adam ob...@samba.org commit 59b019a97aad9a731f9080ea5be14d0dbdfe03d6 Author: Martin Schwenke mar...@meltin.net Date: Tue Apr 16 11:11:11 2013 +1000 util: New functions ctdb_set_child_info() and ctdb_is_child_process() Must be called by all child processes. Signed-off-by: Martin Schwenke mar...@meltin.net Reviewed-by: Michael Adam ob...@samba.org --- Summary of changes: common/ctdb_fork.c | 24
