[Samba] Update from 3.0.29 to 3.2.3 -- smbd panic
Hello, when I try to update from Samba version 3.0.29 to 3.2.3 smbd crashes (Samba is configured as a PDC and works without problems under 3.0.29). In the smbd log-file I found the following: [2008/09/18 08:09:36, 0, pid=15063] tdb(/opt/samba-3.2.3/var/locks/registry.tdb): tdb_transaction_setup_recovery: failed to write recovery data [2008/09/18 08:09:36, 0, pid=15063] tdb(/opt/samba-3.2.3/var/locks/registry.tdb): tdb_transaction_commit: failed to setup recovery data [2008/09/18 08:09:36, 1, pid=15063] tdb(/opt/samba-3.2.3/var/locks/registry.tdb): tdb_transaction_cancel: no transaction [2008/09/18 08:09:36, 0, pid=15063] PANIC (pid 15063): Cancelling transaction failed [2008/09/18 08:09:36, 0, pid=15063] BACKTRACE: 10 stack frames: #0 /opt/samba/sbin/smbd(log_stack_trace+0x26) [0x893025] #1 /opt/samba/sbin/smbd(smb_panic+0x7b) [0x892ea2] #2 /opt/samba/sbin/smbd(dbwrap_trans_store+0x259) [0x89c1d8] #3 /opt/samba/sbin/smbd(dbwrap_trans_store_int32+0x5b) [0x89c4ad] #4 /opt/samba/sbin/smbd(regdb_init+0x2b4) [0xa72c72] #5 /opt/samba/sbin/smbd(registry_init_common+0x21) [0xa74807] #6 /opt/samba/sbin/smbd(registry_init_full+0x1e) [0xa780b8] #7 /opt/samba/sbin/smbd(main+0x8a4) [0xaa167b] #8 /lib/tls/libc.so.6(__libc_start_main+0xd3) [0x3cede3] #9 /opt/samba/sbin/smbd [0x6a60e9] [2008/09/18 08:09:36, 0, pid=15063] dumping core in /opt/samba-3.2.3/var/cores/smbd Any ideas how to resolve this? Can I just delete the old registry.tdb file? Thanks, Ralf --- Ralf AumuellerTel: 0711/7816-249 IPVS, Univ. Stuttgart Fax: 0711/7816-248 Universitaetsstrasse 38 Email: [EMAIL PROTECTED] D-70569 Stuttgart --- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Moving a Samba PDC from Solaris 2.8 to CentOS 4.4
Hello, I try to move a Samba-PDC (3.0.24) from Solaris 2.8 to CentOS 4.4 with the guidance from: http://www.samba.org/samba/docs/man/Samba-Guide/upgrades.html#id333969 (Replacing a Domain Controller) At the moment I am trying this in a test environment. This means the following (not the real names/IPs. Just for illustration ;-)): smb.conf entries: ... netbios name = smbtest interfaces = 1.1.1.1/255.255.255.0 ... Hostname Solaris: solaris Virtual network interface with ip: 1.1.1.1 Hostname CentOS: smbtest Real network interface with ip: 1.1.1.1 Than I followed the docs expect that I don't power off the Solaris machine. I just stop the samba daemons and delete the virtual network interface. When I did that, the Windows XP clients can't login in the Domain anymore. After some investigation I found out that the SIDs of the domain and of the Linux-host are not the same than before on the Solaris host. When I change the SIDs with net setlocalsid and net setdomainsid to the original ones it seems to work again. Any ideas why that happens? Is this the expected behavior (because of the hostname change)? Do I have something else to change to test the PDC move? Best regards, Ralf -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Move a Samba PDC from Solaris to Linux
Hello, we want to move our Samba PDC controller from a Solaris (2.8) machine to a Linux (CentOS4.4) machine. We have the following plan (on both servers is Samba installed. We use the passdb-backend smbpasswd): 1) Stop Samba on the Solaris machine 2) Copy all machine accounts from Solaris /etc/passwd to Linux /etc/passwd 3) Copy the following files from Solaris to Linux: samba/private/* samba/conf/smb.conf samba/var/locks/*.tdb 4) Poweroff the Solaris machine 5) Change the name of the Linux machine (to the name of the Solaris machine) 6) Start Samba on the Linux machine Will that work? Are the tdb files platform independent? After the move are all Windows clients still in the windows-domain? Thanks. Best regards, Ralf -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Question about Solaris ZFS and ACLs
Hello, if I am right Samba 3.0.23d didn't support ACLs on Suns new filesystem ZFS. Will it be supported in the next Samba version 3.0.24? I found a discussion on samba-technical witch says that in the subversion tree support for ACLs on ZFS is available. (http://lists.samba.org/archive/samba-technical/2006-December/050604.html) But my tests on Solaris 10 X86 failed. I tried branch samba-3_0 and samba-3_0_24 (rev 20796) from subversion with configure option --with-acl-support with no success. With windows-explorer the security tab just says .. can't be viewed. The samba log says: [2007/01/16 11:14:57, 10] modules/vfs_solarisacl.c:solarisacl_sys_acl_get_file(72) solarisacl_sys_acl_get_file called for file 'test3.txt'. getting access acl [2007/01/16 11:14:57, 10] modules/vfs_solarisacl.c:solaris_acl_get_file(582) solaris_acl_get_file called for file 'test3.txt' [2007/01/16 11:14:57, 10] modules/vfs_solarisacl.c:solaris_acl_get_file(592) acl GETACLCNT failed: Operation not applicable [2007/01/16 11:14:57, 10] modules/vfs_solarisacl.c:solaris_acl_get_file(609) solaris_acl_get_file failed. [2007/01/16 11:14:57, 10] modules/vfs_solarisacl.c:solarisacl_sys_acl_get_file(94) solarisacl_sys_acl_get_file failed. Any advice about this topic would be appreciated. Best regards, Ralf -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Can't connect to Samba share when using security = server
Hello, when I try to connect from Client-1 (Windows 2003 Server with AD-Server) to a share on Samba-Server-1 (security = server, password server = Samba-Server-2) I got the error No network provider accepted the given network path. There is no popup for the login information. If I try to access the share from a PC running Windows XP Professional everything works without any problems (after giving my credentials). Even when I change the configuration of Samba-Server-1 to security = user and copy the accout info from smbpasswd file from Samba-Server-2 to Samba-Server-1 I can connect to the share. So the problem seems to be with the authentication forwarding. (All Samba-servers work like expected except if i try to conect from Client-1 with Windows 2003 Server and AD to Samba-Server-1). Name: Client-1 OS: Windows 2003 Server AD-Server for Domain A Name: Samba-Server-1 OS: Solaris 10 with Samba 3.0.23b Samba-configuration: security = server password server = Samba-Server-2 Name: Samba-Server-2 OS: Solaris 10 with Samba 3.0.23b Configured as an PDC for Domain B Hope someone can help, Ralf -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
