Re: [Samba] Samba signal 6 panic after upgrade
Thanks, Volker. That fixed it, and now with 3.5.3 I can authenticate Win7 against my domain (with the aid of the two well-known registry changes) where I couldn't with 3.3.4. -Original Message- From: Volker Lendecke [mailto:volker.lende...@sernet.de] Sent: June 1, 2010 7:17 AM To: Dave Beach Cc: samba@lists.samba.org Subject: Re: [Samba] Samba signal 6 panic after upgrade On Tue, Jun 01, 2010 at 06:59:22AM -0400, Dave Beach wrote: I upgraded my Samba PDC from 3.3.4 to 3.5.3. My previous installation was running fine, and I have not changed anything in my smb.conf. The reason for the upgrade was that I was having problems joining a Win 7 client to the domain, and figured a Samba upgrade could only help. Still no luck joining, though, so I started poking around the Samba log files where I noticed in samba_smbd.log: Please also install the just compiled libwbclient. Volker -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba signal 6 panic after upgrade
Hello list! I upgraded my Samba PDC from 3.3.4 to 3.5.3. My previous installation was running fine, and I have not changed anything in my smb.conf. The reason for the upgrade was that I was having problems joining a Win 7 client to the domain, and figured a Samba upgrade could only help. Still no luck joining, though, so I started poking around the Samba log files where I noticed in samba_smbd.log: [2010/06/01 06:21:08.285144, 3] smbd/sec_ctx.c:418(pop_sec_ctx) pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 0 [2010/06/01 06:21:08.285254, 0] lib/fault.c:46(fault_report) === [2010/06/01 06:21:08.285271, 0] lib/fault.c:47(fault_report) INTERNAL ERROR: Signal 6 in pid 1601 (3.5.3) Please read the Trouble-Shooting section of the Samba3-HOWTO [2010/06/01 06:21:08.285289, 0] lib/fault.c:49(fault_report) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2010/06/01 06:21:08.285304, 0] lib/fault.c:50(fault_report) === [2010/06/01 06:21:08.285317, 0] lib/util.c:1465(smb_panic) PANIC (pid 1601): internal error [2010/06/01 06:21:08.286780, 0] lib/util.c:1569(log_stack_trace) BACKTRACE: 18 stack frames: #0 /usr/local/samba/sbin/smbd(log_stack_trace+0x2d) [0xb737a711] #1 /usr/local/samba/sbin/smbd(smb_panic+0x78) [0xb737a85e] #2 /usr/local/samba/sbin/smbd [0xb7369dbc] #3 [0xe400] #4 /lib/libc.so.6(abort+0x101) [0xb6dd1571] #5 /usr/lib/libtalloc.so.1 [0xb6bca3cc] #6 /usr/lib/libtalloc.so.1(talloc_free+0x4a) [0xb6bcca82] #7 /usr/lib/libwbclient.so.0(wbcSidToString+0x102) [0xb6f0861d] #8 /usr/lib/libwbclient.so.0(wbcSidToGid+0x79) [0xb6f07ceb] #9 /usr/local/samba/sbin/smbd(winbind_sid_to_gid+0x38) [0xb7341d79] #10 /usr/local/samba/sbin/smbd(sid_to_gid+0x128) [0xb731fbe1] #11 /usr/local/samba/sbin/smbd(create_local_nt_token+0x31e) [0xb73d2d7f] #12 /usr/local/samba/sbin/smbd(get_root_nt_token+0x15a) [0xb73d3357] #13 /usr/local/samba/sbin/smbd(svcctl_init_keys+0x2e) [0xb727f0ab] #14 /usr/local/samba/sbin/smbd(registry_init_full+0x85) [0xb76b5995] #15 /usr/local/samba/sbin/smbd(main+0xa7a) [0xb76e2c58] #16 /lib/libc.so.6(__libc_start_main+0xe0) [0xb6dbb390] #17 /usr/local/samba/sbin/smbd [0xb70cd591] [2010/06/01 06:21:08.286891, 0] lib/fault.c:326(dump_core) dumping core in /var/log/cores/smbd Rolling back to 3.3.4 works fine, and no panic anymore. Running testparm on my smb.conf file reveals no errors under either version. With 3.5.3, the error occurs every time I reboot. Any ideas where I should look next? Thanks in advance. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Linux member server, or something else?
Hello list! I have a Samba PDC with an LDAP backend password database, against which WinXP clients authenticate. I also have a Ubuntu workstation, which authenticates directly to the same LDAP password database (no Samba). I now wish to have the WinXP clients be able to map shares on the Ubuntu workstation, so I obviously need to get Samba working on it. I can slog through the technical details, but I want to make sure I have the concept properly figured out - will the Ubuntu workstation be a member server, configured as such per the Samba documentation using Winbind, or is there a different way I should be thinking about this? Thanks for any general pointers. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba LDAP, with XP and Linux clients
Hello list! I believe I may not have a Samba problem, but rather an LDAP directory problem. I'm hoping to be redirected towards a more appropriate mailing list to which I can post. I have a Slackware server running Samba and OpenLDAP, and my WinXP clients authenticate just fine. I migrated from an smbpasswd backend to OpenLDAP with a BD backend some time ago, using the migration tools provided with smbldap-tools. Everything has been working fine. I now want to bring a Ubuntu workstation online, and authenticate to the same LDAP database. I've understood that my previous approach was wrong (trying to somehow get the Ubuntu box to join the domain), and that I instead need to use nss and pam to point directly to the LDAP database on the Slackware server. So far, so good. Ubuntu packages sourced and installed. Executing getent group on the Ubuntu client produces the expected results. Executing getent passwd does not; it only shows me a subset of the user accounts (notably, not my own account which was created prior to migration). Fiddling about with a couple of Windows-based ldap query clients, I can see that there seem to be some differences between accounts that were created pre-migration and those created post-migration. As an example, accounts created post-migration seem to have different objectClass attributes and values associated with them than do accounts created pre-migration - and the post-migration accounts are all visible with getent passwd on the Ubuntu client. Also, the pre-migration accounts have the account objectClass associated with them, while the post-migration accounts have the person objectClass associated with them. The post-migration accounts also seem to have the posixAccount object class associated with them. There are other differences, but these strike me (in my ignorance) as possibly being the source of the problem. In case it isn't obvious, I have zero LDAP experience other than this futzing around I'm doing. It seems fairly obvious that I need to somehow alter the pre-migration accounts in some way to make them more like the post-migration accounts, such that I can then log onto the Ubuntu client with the same user ID with which I log onto the WinXp clients. I'm reluctant to do much so far, in fear that I'll manage to irreparably damage the pre-migration accounts (somehow lose the SID, etc) such that they'll need to be re-created, with all the pain that entails on the WinXP clients (I use local profiles only on the WinXP boxes). So, as I said, probably not a Samba problem per se. Would someone be so kind as to suggest the proper list in which I can post this problem? Thanks very much in advance. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Upgrade to 3.3.2
Hello list! I'm upgrading from 3.0.25b to 3.3.2. The package configures and makes with no errors, but on restarting smbd or nmbd I get an error while loading shared libraries: libtalloc.so.1: cannot open shared object file: no such file or directory. Both libtalloc.so and libtalloc.so.1 are in /usr/local/samba/lib, and appear to be the same files as in the 3.3.2 package. Samba appears to properly install in /usr/local/samba. Any help would be greatly appreciated. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
RE: [Samba] Upgrade to 3.3.2
Works like a charm, thanks. -Original Message- From: Volker Lendecke [mailto:volker.lende...@sernet.de] Sent: March 27, 2009 7:05 AM To: Dave Beach Cc: samba@lists.samba.org Subject: Re: [Samba] Upgrade to 3.3.2 On Fri, Mar 27, 2009 at 06:52:38AM -0400, Dave Beach wrote: I'm upgrading from 3.0.25b to 3.3.2. The package configures and makes with no errors, but on restarting smbd or nmbd I get an error while loading shared libraries: libtalloc.so.1: cannot open shared object file: no such file or directory. Both libtalloc.so and libtalloc.so.1 are in /usr/local/samba/lib, and appear to be the same files as in the 3.3.2 package. Samba appears to properly install in /usr/local/samba. Please set the LD_LIBRARY_PATH variable so that it includes /usr/local/samba/lib. Depending on your platform, you might alternatively add /usr/local/samba/lib to /etc/ld.so.conf and re-run ldconfig. Volker -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Samba LDAP, with XP and Linux clients
Hello - I'm not sure if this is the right place to ask, so if not I will be grateful to learn of a more appropriate mailing list. I have a Slackware box (2.6.26 kernel) running Samba 3.0.25b (yes, I know, I'll upgrade soon). This machine provides DC functionality for several Windows XP workstations in my house. I recently changed the backend password database to OpenLDAP (v2.3.33) specifically because I wanted to start introducing Linux clients to the domain as well. I thought everything went well with the database migration, and all the XP clients seemed to continue to interact with the DC normally (it may be relevant here to note that I only use local profiles on the workstations, and no roaming profiles at all). I brought up a Debian (v4.0.x) workstation, and am having problems authenticating on it with a valid domain username. My experiences are causing me to question whether I fully understand my own OpenLDAP implementation and Samba reconfiguration, along with the necessary additions of things like NSS, PAM, etc. I'd like to have a fairly detailed discussion of configurations and steps for just about all of these things, which is why I'm not sure this is exactly the right mailing list. I'd also be very willing to take a discussion offline to e-mail with anyone who may be willing to help out. So, before I post stuff that may be wildly off-topic, I thought I'd ask. Please let me know. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba 3
Hi - I've noticed that my linux box running Samba 3.x seems to have intermittent problems mounting Windows XP shares, where Samba 2.x didn't seem to have problems at all. Nothing's changed on the XP boxes. I realize this is hopelessly vague, but has behaviour of this sort been previously reported? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
