Re: [Samba] unable to join w2k3 SP1 to samba 3 domain.
> Hi, my user is a domain admin, ie. a member of group RID 512. > When I try to join the domain, I'm prompted for username and password. > This means that the Windows server has successfully located the Samba > PDC using Wins resolution. > So far so good, but when I enter my credentials I get the error > message after 3-5 secs. That means the credentials you're entering don't have enough access. > ## Add Samba machine account > sudo useradd -g 515 -d /dev/null -s /bin/false devsrv01$ > sudo pdbedit -a -u devsrv01$ Here you're adding the machine account as root, but are you entering in root's username and password when adding the machine to the domain? I'm not familiar enough with how all the Samba permissions are set up, but I would guess that your domain admin account doesn't have the access it should. If you can add the machine to the domain as the SAMBAPC\root user or the like then that would definitely be the case. Cheers, Adam. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Restart Winbind
> I wish I can put gdb, but when tdb files get corrupted, I cant login to > the host even as a local user on console. Winbind seems to be locking > the whole authentication stream. I don't understand why even the local > user cant login. It's because normally (depending on /etc/nsswitch.conf) winbind will be queried first before local files like /etc/passwd. If you swap the order you can make it check local auth files first. Alternatively you should be able to get around that by either leaving a console or SSH connection open to the server 24/7 until it breaks, or perhaps using SSH with public keys, which should bypass the normal authentication scheme. Of course then even something like "ls" will probably lock up, since it will query winbind to map UIDs back to usernames... > Thats the I'm working on a script to run w/ cron, so that when winbind > consumes more than 40% cpu, I want to restart the cpu. Short of tracking down the bug with gdb and fixing it, this is probably the only alternative. > I wanted to ask another question on the same subject. When I start the > winbind using the init script, it forks 4 processes. The pid on > /var/run/winbindd.pid is the parent process. So is that the pid I need > to monitor to capture the true cpu utilization? I'm afraid I can't answer that, but it's possible that any of the instances might lock up, so you would probably need to monitor all of them. Perhaps an easier option could be to time how long it takes to run a command, and when winbind locks up and that command doesn't complete, then you know winbind must be restarted. (Even something like "rm /tmp/heartbeat; ls; touch /tmp/heartbeat" would mean that if /tmp/heartbeat disappeared for more than a few seconds you know something is wrong. "monit" probably has a test for this already and would save cronjob scripting. Cheers, Adam. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Panic when attempting to connect using OS X cli ent (3.3.7)
On Thu, Sep 10, 2009 at 06:06:22PM -0700, Doug Sampson wrote: > > Not being a FreeBSD wizard, I'd hazard a guess that the nss_wins.so came > with the FreeBSD port of Samba 3.3.x. All of the other FBSD servers I'm > running here that does not have Samba installed doesn't have that file. > > I'm not sure how to go about filing a bug report with Timur. Here's hoping > he reads this! > > Am looking at using "name resolve order = hosts wins bcast" line in the > smb.conf file. Does it accept "dns" as well? Also, it looks like the Samba > server does check with the WINS server simply by parsing the "wins server = > x.x.x.x" line in smb.conf. It should accept "dns". It does on Linux. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Panic when attempting to connect using OS X cli ent (3.3.7)
> -Original Message- > From: Jeremy Allison [mailto:j...@samba.org] > Sent: Thursday, September 10, 2009 05:47 PM > To: Doug Sampson > Cc: 'Jeremy Allison'; 'samba@lists.samba.org' > Subject: Re: [Samba] Samba Panic when attempting to connect using OS X > cli ent (3.3.7) > > > On Thu, Sep 10, 2009 at 05:14:33PM -0700, Doug Sampson wrote: > > > > > > === > > > > > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(41) > > > > > INTERNAL ERROR: Signal 11 in pid 52669 (3.3.7) > > > > > Please read the Trouble-Shooting section of the Samba3-HOWTO > > > > > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(43) > > > > > > > > > > From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf > > > > > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(44) > > > > > > === > > > > > [2009/09/04 12:26:19, 0] lib/util.c:smb_panic(1673) > > > > > PANIC (pid 52669): internal error > > > > > [2009/09/04 12:26:19, 0] lib/util.c:log_stack_trace(1777) > > > > > BACKTRACE: 15 stack frames: > > > > >#0 0x2b43c5 at /usr/local/sbin/smbd > > > > >#1 0x29d27a at /usr/local/sbin/smbd > > > > >#2 0xbfbfffb4 > > > > >#3 0x20a4012f <__nss_wins_freebsd_gethostbyname_r+47> at > > > > > /usr/local/lib/nss_wins.so.1 > > > > >#4 0x207d28d4 at /lib/libc.so.7 > > > > >#5 0x207d2230 at /lib/libc.so.7 > > > > >#6 0x207d235f at /lib/libc.so.7 > > > > >#7 0x207b51f6 at /lib/libc.so.7 > > > > >#8 0x207b3647 at /lib/libc.so.7 > > > > >#9 0x29f992 at /usr/local/sbin/smbd > > > > >#10 0x2b92c9 at /usr/local/sbin/smbd > > > > >#11 0x2a4c76 at /usr/local/sbin/smbd > > > > >#12 0xdde58 at /usr/local/sbin/smbd > > > > >#13 0x4feb94 at /usr/local/sbin/smbd > > > > >#14 0x64949 <_start+137> at /usr/local/sbin/smbd > > > > > > This looks like a problem with the interface > > > between the nss wins plugin library on FreeBSD. > > > > > > Remove "wins" from the "hosts:" line in your > > > nsswitch.conf. > > > > > > Jeremy. > > > > > > > That did it. Removing 'wins' from the host: line allowed OS > X clients to > > connect. > > > > Is this unique to FreeBSD or to Samba in general? Or even > OS X clients? > > > > What am I going to do for browsing while we operate in NT > domain model until > > we upgrade to AD? > > That doesn't have anything to do with browsing (smbd doesn't browse > anyway). The 3.3.x code doesn't have the symbol > _nss_wins_freebsd_gethostbyname_r > in it at all, so this doesn't look like our code. > > Can you find out what package installed the libnss_wins.so library ? > > Looks like it might have come from here: > > http://www.nabble.com/-PATCH---FreeBSD-1--nss_wins-support-for > -FreeBSD-td23910214.html > > which is code that never made it into the main Samba tree. Is > this part of the Samba FreeBSD ports system ? > > > Jeremy. > Not being a FreeBSD wizard, I'd hazard a guess that the nss_wins.so came with the FreeBSD port of Samba 3.3.x. All of the other FBSD servers I'm running here that does not have Samba installed doesn't have that file. I'm not sure how to go about filing a bug report with Timur. Here's hoping he reads this! Am looking at using "name resolve order = hosts wins bcast" line in the smb.conf file. Does it accept "dns" as well? Also, it looks like the Samba server does check with the WINS server simply by parsing the "wins server = x.x.x.x" line in smb.conf. Thanks for your help, Jeremy. ~Doug -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Panic when attempting to connect using OS X cli ent (3.3.7)
On Thu, Sep 10, 2009 at 05:14:33PM -0700, Doug Sampson wrote: > > > > === > > > > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(41) > > > > INTERNAL ERROR: Signal 11 in pid 52669 (3.3.7) > > > > Please read the Trouble-Shooting section of the Samba3-HOWTO > > > > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(43) > > > > > > > > From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf > > > > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(44) > > > > === > > > > [2009/09/04 12:26:19, 0] lib/util.c:smb_panic(1673) > > > > PANIC (pid 52669): internal error > > > > [2009/09/04 12:26:19, 0] lib/util.c:log_stack_trace(1777) > > > > BACKTRACE: 15 stack frames: > > > >#0 0x2b43c5 at /usr/local/sbin/smbd > > > >#1 0x29d27a at /usr/local/sbin/smbd > > > >#2 0xbfbfffb4 > > > >#3 0x20a4012f <__nss_wins_freebsd_gethostbyname_r+47> at > > > > /usr/local/lib/nss_wins.so.1 > > > >#4 0x207d28d4 at /lib/libc.so.7 > > > >#5 0x207d2230 at /lib/libc.so.7 > > > >#6 0x207d235f at /lib/libc.so.7 > > > >#7 0x207b51f6 at /lib/libc.so.7 > > > >#8 0x207b3647 at /lib/libc.so.7 > > > >#9 0x29f992 at /usr/local/sbin/smbd > > > >#10 0x2b92c9 at /usr/local/sbin/smbd > > > >#11 0x2a4c76 at /usr/local/sbin/smbd > > > >#12 0xdde58 at /usr/local/sbin/smbd > > > >#13 0x4feb94 at /usr/local/sbin/smbd > > > >#14 0x64949 <_start+137> at /usr/local/sbin/smbd > > > > This looks like a problem with the interface > > between the nss wins plugin library on FreeBSD. > > > > Remove "wins" from the "hosts:" line in your > > nsswitch.conf. > > > > Jeremy. > > > > That did it. Removing 'wins' from the host: line allowed OS X clients to > connect. > > Is this unique to FreeBSD or to Samba in general? Or even OS X clients? > > What am I going to do for browsing while we operate in NT domain model until > we upgrade to AD? That doesn't have anything to do with browsing (smbd doesn't browse anyway). The 3.3.x code doesn't have the symbol _nss_wins_freebsd_gethostbyname_r in it at all, so this doesn't look like our code. Can you find out what package installed the libnss_wins.so library ? Looks like it might have come from here: http://www.nabble.com/-PATCH---FreeBSD-1--nss_wins-support-for-FreeBSD-td23910214.html which is code that never made it into the main Samba tree. Is this part of the Samba FreeBSD ports system ? Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] 2.6.31-rc8: CIFS with 5 seconds hiccups
On Thu, 10 Sep 2009 17:27:53 -0400 (EDT) Christoph Lameter wrote: > Right. 32 bit cannot mount the clameter directory for strange reasons. I > have to go one level higher. [...] > One other issue that may be important: The mounting operation is very slow > on 32 bit. Could it be that the handshake does not work out? Ok, looks like the 64 bit client is using a different level of interest than the 32 bit on the FIND_FIRST call. I suspect that that difference may account for the difference in response time. It's not completely clear to me why that would be. Maybe a windows bug that causes a slowdown with that LOI? In any case, I think we need to look closely at what's happening at mount time. First, I'll need some other info: 1) output of "/sbin/mount.cifs -V" from both machines 2) mount options that you're using on both boxes 3) wire captures from mount attempts on both machines. Try to mount the "clameter" dir on both boxes and do captures of each attempt. Maybe this time use -s 0 with tcpdump so we get all of the traffic. There may be crackable password hashes in the captures, so you may want to send them to me privately and not cc the list. Thanks, -- Jeff Layton -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Panic when attempting to connect using OS X cli ent (3.3.7)
> > > > > > Am running Samba 3.3.7 on FreeBSD 7.1. All Windows clients > > > (W2K & WXP) can > > > connect fine but cannot connect any OS X clients (version > > > 10.4 & 10.5). > > > These OS X client receive an error message saying it cannot > > > connect. The log > > > indicates the following: > > > > > > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(40) > > > === > > > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(41) > > > INTERNAL ERROR: Signal 11 in pid 52669 (3.3.7) > > > Please read the Trouble-Shooting section of the Samba3-HOWTO > > > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(43) > > > > > > From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf > > > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(44) > > > === > > > [2009/09/04 12:26:19, 0] lib/util.c:smb_panic(1673) > > > PANIC (pid 52669): internal error > > > [2009/09/04 12:26:19, 0] lib/util.c:log_stack_trace(1777) > > > BACKTRACE: 15 stack frames: > > >#0 0x2b43c5 at /usr/local/sbin/smbd > > >#1 0x29d27a at /usr/local/sbin/smbd > > >#2 0xbfbfffb4 > > >#3 0x20a4012f <__nss_wins_freebsd_gethostbyname_r+47> at > > > /usr/local/lib/nss_wins.so.1 > > >#4 0x207d28d4 at /lib/libc.so.7 > > >#5 0x207d2230 at /lib/libc.so.7 > > >#6 0x207d235f at /lib/libc.so.7 > > >#7 0x207b51f6 at /lib/libc.so.7 > > >#8 0x207b3647 at /lib/libc.so.7 > > >#9 0x29f992 at /usr/local/sbin/smbd > > >#10 0x2b92c9 at /usr/local/sbin/smbd > > >#11 0x2a4c76 at /usr/local/sbin/smbd > > >#12 0xdde58 at /usr/local/sbin/smbd > > >#13 0x4feb94 at /usr/local/sbin/smbd > > >#14 0x64949 <_start+137> at /usr/local/sbin/smbd > > This looks like a problem with the interface > between the nss wins plugin library on FreeBSD. > > Remove "wins" from the "hosts:" line in your > nsswitch.conf. > > Jeremy. > That did it. Removing 'wins' from the host: line allowed OS X clients to connect. Is this unique to FreeBSD or to Samba in general? Or even OS X clients? What am I going to do for browsing while we operate in NT domain model until we upgrade to AD? ~Doug -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Domain Member Server connecting to Samba PDC
On Thu, Sep 10, 2009 at 04:13:55PM -0600, Anthony Powell wrote: > Hello: > > I'm trying to set up a small domain on my home network. The goal is > to have a domain member server connect to my samba PDC using winbind > for authentication against a tdbsam database. I've tried reading the > official howto, and a few help sites, but I'm still having difficulty > accomplishing my goal. I'm using Samba 3.3.2 on Fedora 11 for both > computers. There had been some bugs in 3.3.2 preventing that unfortunately. We are currently preparing an update to 3.4.1 for F11. Could you please give https://admin.fedoraproject.org/updates/F11/FEDORA-2009-9443 a try (and leave positive feedback if it works for you) ? Thanks, Guenther -- Günther DeschnerGPG-ID: 8EE11688 Red Hat gdesch...@redhat.com Samba Team g...@samba.org pgpRYz1Xg1ape.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Share homes folders with samba4
Hi, How do I share homes folders with samba 4 ? Thanks. Ricardo -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Domain Member Server connecting to Samba PDC
Hello: I'm trying to set up a small domain on my home network. The goal is to have a domain member server connect to my samba PDC using winbind for authentication against a tdbsam database. I've tried reading the official howto, and a few help sites, but I'm still having difficulty accomplishing my goal. I'm using Samba 3.3.2 on Fedora 11 for both computers. On the DMS, connecting to the domain (net rpc join) reports that it has connected successfully. On the server, these errors are logged (though I suspect most are not actual errors): [2009/09/10 16:08:06, 0] rpc_server/srv_netlog_nt.c:get_md4pw(306) get_md4pw: Workstation TV$: no account in domain [2009/09/10 16:08:06, 0] rpc_server/srv_netlog_nt.c:_netr_ServerAuthenticate2(528) _netr_ServerAuthenticate2: failed to get machine password for account TV$: NT_STATUS_ACCESS_DENIED [2009/09/10 16:08:06, 0] rpc_server/srv_netlog_nt.c:get_md4pw(306) get_md4pw: Workstation TV$: no account in domain [2009/09/10 16:08:06, 0] rpc_server/srv_netlog_nt.c:_netr_ServerAuthenticate2(528) _netr_ServerAuthenticate2: failed to get machine password for account TV$: NT_STATUS_ACCESS_DENIED [2009/09/10 16:08:09, 2] auth/auth.c:check_ntlm_password(308) check_ntlm_password: authentication for user [root] -> [root] -> [root] succeeded [2009/09/10 16:08:09, 2] libsmb/credentials.c:netlogon_creds_server_check(223) netlogon_creds_server_check: credentials check failed. [2009/09/10 16:08:09, 0] rpc_server/srv_netlog_nt.c:_netr_ServerAuthenticate2(546) _netr_ServerAuthenticate2: netlogon_creds_server_check failed. Rejecting auth request from client TV machine account TV$ [2009/09/10 16:08:09, 2] libsmb/credentials.c:netlogon_creds_server_check(223) netlogon_creds_server_check: credentials check failed. [2009/09/10 16:08:09, 0] rpc_server/srv_netlog_nt.c:_netr_ServerAuthenticate2(546) _netr_ServerAuthenticate2: netlogon_creds_server_check failed. Rejecting auth request from client TV machine account TV$ Checking the join on the DMS (net rpc testjoin) produces no local errors, but this error on the PDC: [2009/09/10 16:07:22, 2] libsmb/credentials.c:netlogon_creds_server_check(223) netlogon_creds_server_check: credentials check failed. [2009/09/10 16:07:22, 0] rpc_server/srv_netlog_nt.c:_netr_ServerAuthenticate2(546) _netr_ServerAuthenticate2: netlogon_creds_server_check failed. Rejecting auth request from client TV machine account TV$ wbinfo -u and -g produce (maybe) a more meaningful error, but not one I can find an answer to with google: [2009/09/10 16:08:29, 2] auth/auth.c:check_ntlm_password(308) check_ntlm_password: authentication for user [TV$] -> [TV$] -> [tv$] succeeded [2009/09/10 16:08:29, 2] auth/auth.c:check_ntlm_password(308) check_ntlm_password: authentication for user [TV$] -> [TV$] -> [tv$] succeeded [2009/09/10 16:08:29, 2] rpc_server/srv_samr_nt.c:access_check_samr_function(247) _samr_OpenDomain: ACCESS DENIED (granted: 0x00020010; required: 0x0020) Can anyone help? I originally thought it was an IDMAP problem, but the errors are not suggesting that in any comprehensible way to me. Thanks! Anthony -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Panic when attempting to connect using OS X cli ent (3.3.7)
On Thu, Sep 10, 2009 at 12:07:04PM -0700, Doug Sampson wrote: > Can someone help me out here? > > I've recompiled and made changes to the smb.conf to no avail. > > ~Doug > > > -Original Message- > > From: samba-boun...@lists.samba.org > > [mailto:samba-boun...@lists.samba.org]on Behalf Of Doug Sampson > > Sent: Friday, September 04, 2009 12:41 PM > > To: 'samba@lists.samba.org' > > Subject: [Samba] Samba Panic when attempting to connect using OS X > > client (3.3.7) > > > > > > Hi, > > > > Am running Samba 3.3.7 on FreeBSD 7.1. All Windows clients > > (W2K & WXP) can > > connect fine but cannot connect any OS X clients (version > > 10.4 & 10.5). > > These OS X client receive an error message saying it cannot > > connect. The log > > indicates the following: > > > > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(40) > > === > > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(41) > > INTERNAL ERROR: Signal 11 in pid 52669 (3.3.7) > > Please read the Trouble-Shooting section of the Samba3-HOWTO > > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(43) > > > > From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf > > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(44) > > === > > [2009/09/04 12:26:19, 0] lib/util.c:smb_panic(1673) > > PANIC (pid 52669): internal error > > [2009/09/04 12:26:19, 0] lib/util.c:log_stack_trace(1777) > > BACKTRACE: 15 stack frames: > >#0 0x2b43c5 at /usr/local/sbin/smbd > >#1 0x29d27a at /usr/local/sbin/smbd > >#2 0xbfbfffb4 > >#3 0x20a4012f <__nss_wins_freebsd_gethostbyname_r+47> at > > /usr/local/lib/nss_wins.so.1 > >#4 0x207d28d4 at /lib/libc.so.7 > >#5 0x207d2230 at /lib/libc.so.7 > >#6 0x207d235f at /lib/libc.so.7 > >#7 0x207b51f6 at /lib/libc.so.7 > >#8 0x207b3647 at /lib/libc.so.7 > >#9 0x29f992 at /usr/local/sbin/smbd > >#10 0x2b92c9 at /usr/local/sbin/smbd > >#11 0x2a4c76 at /usr/local/sbin/smbd > >#12 0xdde58 at /usr/local/sbin/smbd > >#13 0x4feb94 at /usr/local/sbin/smbd > >#14 0x64949 <_start+137> at /usr/local/sbin/smbd This looks like a problem with the interface between the nss wins plugin library on FreeBSD. Remove "wins" from the "hosts:" line in your nsswitch.conf. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] 2.6.31-rc8: CIFS with 5 seconds hiccups
On Thu, 10 Sep 2009 15:42:28 -0400 (EDT) Christoph Lameter wrote: > On Thu, 10 Sep 2009, Jeff Layton wrote: > > > I assume that the 32 and 64 bit clients you have are calling "ls" in > > the same dir. If so, maybe a similar capture from a 64-bit client might > > help us see the difference? > > 64 bit trace attached. A couple of differences. First, the "ls's" were done in different directories since they had different search patterns: 32 == \* 64 == \clameter\* ...did they also mount different shares from the server? The 64-bit capture was done in a directory with only 50 files, whereas the other one had at least 600-700 files (capture ends before it finished listing the files). That may make quite a bit of difference on the server (not sure how windows works internally in this case). The only other substantive difference I see is that the Level of Interest that the client is requesting is different: 32 == SMB_FIND_FILE_DIRECTORY_INFO 64 == SMB_FIND_FILE_ID_FULL_DIR_INFO That probably means that the 32 bit client has disabled CIFS_MOUNT_SERVER_INUM for some reason. That means that it's not asking the server for the windows equivalent of inode numbers. We typically disable that flag automatically if a query for the inode number of a path fails. Since these are the same server, that may be an indicator that the server is serving out info from two different filesystem types (maybe FAT vs. NTFS, or maybe even a CDROM or something). If so, then that may help explain some of the performance delta there. I'd be more interested to see how the 64 bit client behaves when it mounts the exact same share and does an ls in the same directory as the 32 bit client. Cheers, -- Jeff Layton -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] 2.6.31-rc8: CIFS with 5 seconds hiccups
On Thu, 10 Sep 2009 14:53:12 -0400 (EDT) Christoph Lameter wrote: > On Wed, 9 Sep 2009, Jeff Layton wrote: > > > Well, I can see the delays in the capture, but the snarflen for the > > capture is a little too small to tell much else. Can you redo the > > capture with a larger snarflen (maybe -s 512 or so)? > > -s 1000 version attached. > > > Also, were you able to tell anything from a server-side capture? Is the > > server issuing oplock breaks at those times? > > Thats a pretty busy system. They have not gotten around to do any logging > on that end. Ok. I had a look at the capture. The stalls seem to be occurring on FIND_FILE requests. Those are similar to READDIRPLUS requests in NFS, it returns a list of files that match a particular set of criteria and their attributes. Each time the client is making one of these calls to the server, it requests a set of up to 150 files. The server grinds for 5s each time and then responds. The calls themselves seem to be sane AFAICT. I don't see any problems with the parameters we're sending for the search. I also had a look over the FIND_FIRST code and it doesn't seem to have any obvious word size related problems. I assume that the 32 and 64 bit clients you have are calling "ls" in the same dir. If so, maybe a similar capture from a 64-bit client might help us see the difference? Thanks, -- Jeff Layton -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba Panic when attempting to connect using OS X cli ent (3.3.7)
Can someone help me out here? I've recompiled and made changes to the smb.conf to no avail. ~Doug > -Original Message- > From: samba-boun...@lists.samba.org > [mailto:samba-boun...@lists.samba.org]on Behalf Of Doug Sampson > Sent: Friday, September 04, 2009 12:41 PM > To: 'samba@lists.samba.org' > Subject: [Samba] Samba Panic when attempting to connect using OS X > client (3.3.7) > > > Hi, > > Am running Samba 3.3.7 on FreeBSD 7.1. All Windows clients > (W2K & WXP) can > connect fine but cannot connect any OS X clients (version > 10.4 & 10.5). > These OS X client receive an error message saying it cannot > connect. The log > indicates the following: > > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(40) > === > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(41) > INTERNAL ERROR: Signal 11 in pid 52669 (3.3.7) > Please read the Trouble-Shooting section of the Samba3-HOWTO > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(43) > > From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(44) > === > [2009/09/04 12:26:19, 0] lib/util.c:smb_panic(1673) > PANIC (pid 52669): internal error > [2009/09/04 12:26:19, 0] lib/util.c:log_stack_trace(1777) > BACKTRACE: 15 stack frames: >#0 0x2b43c5 at /usr/local/sbin/smbd >#1 0x29d27a at /usr/local/sbin/smbd >#2 0xbfbfffb4 >#3 0x20a4012f <__nss_wins_freebsd_gethostbyname_r+47> at > /usr/local/lib/nss_wins.so.1 >#4 0x207d28d4 at /lib/libc.so.7 >#5 0x207d2230 at /lib/libc.so.7 >#6 0x207d235f at /lib/libc.so.7 >#7 0x207b51f6 at /lib/libc.so.7 >#8 0x207b3647 at /lib/libc.so.7 >#9 0x29f992 at /usr/local/sbin/smbd >#10 0x2b92c9 at /usr/local/sbin/smbd >#11 0x2a4c76 at /usr/local/sbin/smbd >#12 0xdde58 at /usr/local/sbin/smbd >#13 0x4feb94 at /usr/local/sbin/smbd >#14 0x64949 <_start+137> at /usr/local/sbin/smbd > [2009/09/04 12:26:19, 0] lib/talloc_stack.c:talloc_tos(126) > no talloc stackframe around, leaking memory > [2009/09/04 12:26:19, 0] lib/fault.c:dump_core(231) > dumping core in /var/log/samba/cores/smbd > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(40) > === > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(41) > INTERNAL ERROR: Signal 11 in pid 52670 (3.3.7) > Please read the Trouble-Shooting section of the Samba3-HOWTO > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(43) > > From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf > [2009/09/04 12:26:19, 0] lib/fault.c:fault_report(44) > === > [2009/09/04 12:26:19, 0] lib/util.c:smb_panic(1673) > PANIC (pid 52670): internal error > [2009/09/04 12:26:19, 0] lib/util.c:log_stack_trace(1777) > BACKTRACE: 15 stack frames: >#0 0x2b43c5 at /usr/local/sbin/smbd >#1 0x29d27a at /usr/local/sbin/smbd >#2 0xbfbfffb4 >#3 0x20a4012f <__nss_wins_freebsd_gethostbyname_r+47> at > /usr/local/lib/nss_wins.so.1 >#4 0x207d28d4 at /lib/libc.so.7 >#5 0x207d2230 at /lib/libc.so.7 >#6 0x207d235f at /lib/libc.so.7 >#7 0x207b51f6 at /lib/libc.so.7 >#8 0x207b3647 at /lib/libc.so.7 >#9 0x29f992 at /usr/local/sbin/smbd >#10 0x2b92c9 at /usr/local/sbin/smbd >#11 0x2a4c76 at /usr/local/sbin/smbd >#12 0xdde58 at /usr/local/sbin/smbd >#13 0x4feb94 at /usr/local/sbin/smbd >#14 0x64949 <_start+137> at /usr/local/sbin/smbd > [2009/09/04 12:26:19, 0] lib/talloc_stack.c:talloc_tos(126) > no talloc stackframe around, leaking memory > [2009/09/04 12:26:19, 0] lib/fault.c:dump_core(231) > dumping core in /var/log/samba/cores/smbd > > The contents of smb.conf is as follows: > > [global] > workgroup = DSP > server string = Samba %v > security = DOMAIN > log file = /var/log/samba/log.%m > max log size = 100 > smb ports = 139 > socket options = SO_RCVBUF=8192 SO_SNDBUF=8192 > os level = 33 > local master = No > dns proxy = No > wins server = 192.168.x.x > host msdfs = No > idmap uid = 15000-2 > idmap gid = 15000-2 > template homedir = /usr/home/%D/%U > template shell = /bin/bash > winbind separator = - > winbind cache time = 10 > inherit acls = Yes > hosts allow = 192.168.x., 192.168.x., 127., 10.8.x. > fake oplocks = Yes > locking = No > > [homes] > comment = Home Directories > read only = No > create mask = 0770 > directory mask = 0770 > browseable = No > > [printers] > comment = All Printers > path = /var/spool/samba > printable = Yes > browseable = No > > [install-public] > c
Re: [Samba] compiling samba-3.4.x on RHEL4
Werner Maes kirjoitti: no I haven't yet. perhaps I will try that tomorrow. but I'm wondering if I'm the only one with this error? No, looks like this problem comes also with my environment running Centos 5.3 32bit. (rhel 5 clone) I think that is bug in make rpms system. -- Eero -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] compiling samba-3.4.x on RHEL4
Folks, I am running into this same problem -- the source of the problem appears (to me) to be earlier in the compile, before the warnings/errors that Werner quoted. I found reference to being unable to load "config.h". The compile appears to be being executed with a current directory of 'samba-3.4.1/source3/', and is directly compiling replace.c and talloc.c in their respective directories. Both fail without access to "config.h". To test, I set the current directory into the BUILD/samba-3.4.1/source3/ directory, and re-executed the gcc command from the output. With this, I was able to duplicate the warning/error output from the package build. When I appended " -Iinclude" to the same command, the compile completed successfully -- without any errors or warnings. Therefore, I have to conclude that the include paths are not being set correctly for these component compiles. I have not had the time yet to dig any deeper into the Makefile/specfile structure to determine where this problem lies. -D --On Thursday, September 10, 2009 4:37 PM +0200 Werner Maes wrote: replace.h is in /usr/src/redhat/BUILD/samba-3.4.1/lib/replace/ The Makefile can be found in /usr/src/redhat/BUILD/samba-3.4.1/source3/ so -I./../lib/replace should point to the folder where replace.h can be found? Or am I missing sometmhing? CPPFLAGS=-DHAVE_CONFIG_H -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/talloc -I./../lib/tevent -I./../lib/tdb/include -I./libaddns -I./librpc -I./.. -I./../lib/popt -DLDAP_DEPRECATED werner ps: in samba 3.2.x & 3.3.x the folder lib/replace was situated in the source/ folder, but in samba 3.4.x it is no longer there but one directory up ! Donald L. Meyer - Technical System Manager, ACES TeleNet Service - Technical Lead, ACES Web Infrastructure Information Technology and Communication Services, College of ACES University of Illinois at Urbana-Champaign Video/H.323: 0012172445653 (GDS) Phone:+1.217.244.5653 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] compiling samba-3.4.x on RHEL4
no I haven't yet. perhaps I will try that tomorrow. but I'm wondering if I'm the only one with this error? w. > -Original Message- > From: Ralf Hornik Mailings [mailto:r...@best.homeunix.org] > Sent: donderdag 10 september 2009 16:56 > To: Werner Maes > Cc: samba@lists.samba.org > Subject: Re: [Samba] compiling samba-3.4.x on RHEL4 > > Werner Maes wrote: > > > replace.h is in /usr/src/redhat/BUILD/samba-3.4.1/lib/replace/ > > > > The Makefile can be found in /usr/src/redhat/BUILD/samba- > 3.4.1/source3/ > > > > so -I./../lib/replace should point to the folder where replace.h can > > be found? Or am I missing sometmhing? > > > > CPPFLAGS=-DHAVE_CONFIG_H -D_LARGEFILE64_SOURCE > > -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Iinclude -I./include -I. -I. > > -I./../lib/replace -I./../lib/talloc -I./../lib/tevent > > -I./../lib/tdb/include -I./libaddns -I./librpc -I./.. > > -I./../lib/popt -DLDAP_DEPRECATED > > Have you already tried to compile by hand? (just for reproducing) > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] compiling samba-3.4.x on RHEL4
Werner Maes wrote: replace.h is in /usr/src/redhat/BUILD/samba-3.4.1/lib/replace/ The Makefile can be found in /usr/src/redhat/BUILD/samba-3.4.1/source3/ so -I./../lib/replace should point to the folder where replace.h can be found? Or am I missing sometmhing? CPPFLAGS=-DHAVE_CONFIG_H -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/talloc -I./../lib/tevent -I./../lib/tdb/include -I./libaddns -I./librpc -I./.. -I./../lib/popt -DLDAP_DEPRECATED Have you already tried to compile by hand? (just for reproducing) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] compiling samba-3.4.x on RHEL4
replace.h is in /usr/src/redhat/BUILD/samba-3.4.1/lib/replace/ The Makefile can be found in /usr/src/redhat/BUILD/samba-3.4.1/source3/ so -I./../lib/replace should point to the folder where replace.h can be found? Or am I missing sometmhing? CPPFLAGS=-DHAVE_CONFIG_H -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/talloc -I./../lib/tevent -I./../lib/tdb/include -I./libaddns -I./librpc -I./.. -I./../lib/popt -DLDAP_DEPRECATED werner ps: in samba 3.2.x & 3.3.x the folder lib/replace was situated in the source/ folder, but in samba 3.4.x it is no longer there but one directory up ! > -Original Message- > From: Ralf Hornik [mailto:r...@ralf-hornik.de] > Sent: donderdag 10 september 2009 16:20 > To: Werner Maes > Cc: 'Michael Wood'; samba@lists.samba.org > Subject: Re: [Samba] compiling samba-3.4.x on RHEL4 > > Werner Maes wrote: > > > so it seems that it should find replace.h> > > can't figure out what's wrong her :( > > So where is your replace.h located? > > Ralf > -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Compiling 3.4.0 on SPARC Solaris 9
Thanks Michael. We tried 3.4.1 which made no difference. However, we discovered that Makefile-noincludes will install but needs LD_LIBRARY_PATH set to work. We're now moving on to try and get it to compile with ADS support - whole extra bag of worms! Nigel Nigel Pain The Scottish Government Corporate Systems Support Information Systems and Information Services (ISIS) Victoria Quay EDINBURGH EH6 6QQ UK Tel +44 131 244 7237 Mob. +44 7795 618362 Pedal for Scotland 2009: Glasgow to Edinburgh, 13th September for Maggie's Centres. Please sponsor me: http://www.justgiving.com/nigel_pain This e-mail (and any files or other attachments transmitted with it) is intended solely for the attention of the addressee(s). Unauthorised use, disclosure, storage, copying or distribution of any part of this e-mail is not permitted. If you are not the intended recipient please destroy the email, remove any copies from your system and inform the sender immediately by return. Communications with the Scottish Government may be monitored or recorded in order to secure the effective operation of the system and for other lawful purposes. The views or opinions contained within this e-mail may not necessarily reflect those of the Scottish Government. The original of this email was scanned for viruses by the Government Secure Intranet virus scanning service supplied by Cable&Wireless in partnership with MessageLabs. (CCTM Certificate Number 2009/09/0052.) On leaving the GSi this email was certified virus free. Communications via the GSi may be automatically logged, monitored and/or recorded for legal purposes. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] compiling samba-3.4.x on RHEL4
Werner Maes wrote: so it seems that it should find replace.h can't figure out what's wrong her :( So where is your replace.h located? Ralf -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] compiling samba-3.4.x on RHEL4
well in the Makefile I see: CPPFLAGS=-DHAVE_CONFIG_H -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Iinclude -I./include -I. -I. -I./../lib/replace -I./../lib/talloc -I./../lib/tevent -I./../lib/tdb/include -I./libaddns -I./librpc -I./.. -I./../lib/popt -DLDAP_DEPRECATED so it seems that it should find replace.h can't figure out what's wrong her :( werner > -Original Message- > From: Michael Wood [mailto:esiot...@gmail.com] > Sent: donderdag 10 september 2009 13:55 > To: Werner Maes > Subject: Re: [Samba] compiling samba-3.4.x on RHEL4 > > 2009/9/10 Werner Maes : > > hello > > > > when I try to compile samba-3.4.x on RHEL4 with the samba.spec in the > packaging folder I always get this error: > > > > Compiling ../lib/talloc/talloc.c > > ../lib/talloc/talloc.c:50:21: replace.h: No such file or directory > > Looks like a "-I../lib/replace" (or equivalent) is missing somewhere. > > > ../lib/talloc/talloc.c: In function `_talloc_realloc': > > ../lib/talloc/talloc.c:987: error: `bool' undeclared (first use in > this function) > > ../lib/talloc/talloc.c:987: error: (Each undeclared identifier is > reported only once > > ../lib/talloc/talloc.c:987: error: for each function it appears in.) > > ../lib/talloc/talloc.c:987: error: syntax error before "malloced" > > ../lib/talloc/talloc.c:1035: error: `malloced' undeclared (first use > in this function) > > ../lib/talloc/talloc.c:1035: error: `true' undeclared (first use in > this function) > > ../lib/talloc/talloc.c:1486:1: warning: "va_copy" redefined > > This looks like HAVE_VA_COPY was not correctly defined. > > I think you should first figure out the replace.h issue before looking > at the HAVE_VA_COPY issue, though. > > > In file included from ../lib/talloc/talloc.h:30, > > from ../lib/talloc/talloc.c:51: > > /usr/lib/gcc/i386-redhat-linux/3.4.6/include/stdarg.h:54:1: warning: > this is the location of the previous definition > > The following command failed: > > ccache gcc -O2 -g -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -c > ../lib/talloc/talloc.c -o ../lib/talloc/talloc.o > > make: *** [../lib/talloc/talloc.o] Error 1 > > error: Bad exit status from /var/tmp/rpm-tmp.72692 (%build) > > -- > Michael Wood -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Windows 2008 terminal services with a samba PDC
Dear, My windows 2008 terminal server doesn't find the terminal license server when I add the windows server to the samba domain. The license server is installed on the same 2008 server as where the terminal services are installed on. When the windows server was still in a workgroup, then he found the TS license server. I'm using samba 3.2.14-40 and on the windows server 2008, the SP2 is installed. The windowsservers name is WIN2008 and I can ping to WIN2008 from the linux server, so the DNS is correct. Can anyone tell me what the problem can be, or what I can do to resolv this problem? -- Kind regards, Thomas Six Schaubroeck informatica Tel 0032 9 389 0526 DISCLAIMER http://www.schaubroeck.be/maildisclaimer.htm -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] compiling samba-3.4.x on RHEL4
hello when I try to compile samba-3.4.x on RHEL4 with the samba.spec in the packaging folder I always get this error: Compiling ../lib/talloc/talloc.c ../lib/talloc/talloc.c:50:21: replace.h: No such file or directory ../lib/talloc/talloc.c: In function `_talloc_realloc': ../lib/talloc/talloc.c:987: error: `bool' undeclared (first use in this function) ../lib/talloc/talloc.c:987: error: (Each undeclared identifier is reported only once ../lib/talloc/talloc.c:987: error: for each function it appears in.) ../lib/talloc/talloc.c:987: error: syntax error before "malloced" ../lib/talloc/talloc.c:1035: error: `malloced' undeclared (first use in this function) ../lib/talloc/talloc.c:1035: error: `true' undeclared (first use in this function) ../lib/talloc/talloc.c:1486:1: warning: "va_copy" redefined In file included from ../lib/talloc/talloc.h:30, from ../lib/talloc/talloc.c:51: /usr/lib/gcc/i386-redhat-linux/3.4.6/include/stdarg.h:54:1: warning: this is the location of the previous definition The following command failed: ccache gcc -O2 -g -march=i386 -mcpu=i686 -D_GNU_SOURCE -fPIC -c ../lib/talloc/talloc.c -o ../lib/talloc/talloc.o make: *** [../lib/talloc/talloc.o] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.72692 (%build) any ideas? kind regards werner -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Security context stack overflow on Debian5+LDAP
On Thu, Sep 10, 2009 at 09:57:39AM +0200, Lorenzo Milesi wrote: > Hi > > I'm setting up a Samba PDC, with auth over Zimbra's LDAP, with this howto: > http://wiki.zimbra.com/index.php?title=UNIX_and_Windows_Accounts_in_Zimbra_LDAP_and_Zimbra_Admin_UI_6.0 > > > System is a fully updated Debian 5. All packages from distro. Samba is > 3.2.5-4lenny6. > Now everything is almost ok, but I'm getting an error when trying to mount > the samba share: > [2009/09/10 09:44:07, 2] passdb/pdb_ldap.c:init_group_from_ldap(2344) > init_group_from_ldap: Entry found for group: 10001 > [2009/09/10 09:44:07, 0] smbd/sec_ctx.c:push_sec_ctx(210) > Security context stack overflow! > [2009/09/10 09:44:07, 0] lib/util.c:smb_panic(1663) > PANIC (pid 17363): Security context stack overflow! > [2009/09/10 09:44:07, 0] lib/util.c:log_stack_trace(1767) > BACKTRACE: 58 stack frames: > #0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x8201d24] > #1 /usr/sbin/smbd(smb_panic+0x80) [0x8201e81] > #2 /usr/sbin/smbd(push_sec_ctx+0x7b) [0x80ce8f1] > #3 /usr/sbin/smbd(become_root+0x17) [0x80c152a] > #4 /usr/sbin/smbd(lookup_sids+0x845) [0x81b841f] > #5 /usr/sbin/smbd(lookup_sid+0x12a) [0x81b8c20] ... Hmmm. 3.2.5-4lenny6, is that an up-to-date package? I'm pretty certain I have seen that ages ago and it was fixed. Is it possible for you to retry with 3.4.1? If not, the least we need is a debug level 10 log leading up to this, and if possible also a network trace of the LDAP traffic. Volker 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
[Samba] Security context stack overflow on Debian5+LDAP
Hi I'm setting up a Samba PDC, with auth over Zimbra's LDAP, with this howto: http://wiki.zimbra.com/index.php?title=UNIX_and_Windows_Accounts_in_Zimbra_LDAP_and_Zimbra_Admin_UI_6.0 System is a fully updated Debian 5. All packages from distro. Samba is 3.2.5-4lenny6. Now everything is almost ok, but I'm getting an error when trying to mount the samba share: [2009/09/10 09:44:07, 2] passdb/pdb_ldap.c:init_group_from_ldap(2344) init_group_from_ldap: Entry found for group: 10001 [2009/09/10 09:44:07, 0] smbd/sec_ctx.c:push_sec_ctx(210) Security context stack overflow! [2009/09/10 09:44:07, 0] lib/util.c:smb_panic(1663) PANIC (pid 17363): Security context stack overflow! [2009/09/10 09:44:07, 0] lib/util.c:log_stack_trace(1767) BACKTRACE: 58 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x2d) [0x8201d24] #1 /usr/sbin/smbd(smb_panic+0x80) [0x8201e81] #2 /usr/sbin/smbd(push_sec_ctx+0x7b) [0x80ce8f1] #3 /usr/sbin/smbd(become_root+0x17) [0x80c152a] #4 /usr/sbin/smbd(lookup_sids+0x845) [0x81b841f] #5 /usr/sbin/smbd(lookup_sid+0x12a) [0x81b8c20] #6 /usr/sbin/smbd(pdb_get_group_sid+0x169) [0x81b1d40] #7 /usr/sbin/smbd(pdb_get_group_rid+0x26) [0x84a9f64] #8 /usr/sbin/smbd(init_buffer_from_sam_v3+0xe5) [0x84a6e90] #9 /usr/sbin/smbd(pdb_copy_sam_account+0x3e) [0x84a8329] #10 /usr/sbin/smbd(pdb_getsampwsid+0x131) [0x81b4d28] #11 /usr/sbin/smbd [0x81b4e4d] #12 /usr/sbin/smbd [0x81b559a] #13 /usr/sbin/smbd(pdb_lookup_rids+0x3f) [0x81b39b4] #14 /usr/sbin/smbd(lookup_sids+0x882) [0x81b845c] #15 /usr/sbin/smbd(lookup_sid+0x12a) [0x81b8c20] #16 /usr/sbin/smbd(pdb_get_group_sid+0x169) [0x81b1d40] #17 /usr/sbin/smbd(pdb_get_group_rid+0x26) [0x84a9f64] #18 /usr/sbin/smbd(init_buffer_from_sam_v3+0xe5) [0x84a6e90] #19 /usr/sbin/smbd(pdb_copy_sam_account+0x3e) [0x84a8329] #20 /usr/sbin/smbd(pdb_getsampwsid+0x131) [0x81b4d28] #21 /usr/sbin/smbd [0x81b4e4d] #22 /usr/sbin/smbd [0x81b559a] #23 /usr/sbin/smbd(pdb_lookup_rids+0x3f) [0x81b39b4] #24 /usr/sbin/smbd(lookup_sids+0x882) [0x81b845c] #25 /usr/sbin/smbd(lookup_sid+0x12a) [0x81b8c20] #26 /usr/sbin/smbd(pdb_get_group_sid+0x169) [0x81b1d40] #27 /usr/sbin/smbd(pdb_get_group_rid+0x26) [0x84a9f64] #28 /usr/sbin/smbd(init_buffer_from_sam_v3+0xe5) [0x84a6e90] #29 /usr/sbin/smbd(pdb_copy_sam_account+0x3e) [0x84a8329] #30 /usr/sbin/smbd(pdb_getsampwsid+0x131) [0x81b4d28] #31 /usr/sbin/smbd [0x81b4e4d] #32 /usr/sbin/smbd [0x81b559a] #33 /usr/sbin/smbd(pdb_lookup_rids+0x3f) [0x81b39b4] #34 /usr/sbin/smbd(lookup_sids+0x882) [0x81b845c] #35 /usr/sbin/smbd(lookup_sid+0x12a) [0x81b8c20] #36 /usr/sbin/smbd(pdb_get_group_sid+0x169) [0x81b1d40] #37 /usr/sbin/smbd(pdb_get_group_rid+0x26) [0x84a9f64] #38 /usr/sbin/smbd(init_buffer_from_sam_v3+0xe5) [0x84a6e90] #39 /usr/sbin/smbd(pdb_copy_sam_account+0x3e) [0x84a8329] #40 /usr/sbin/smbd(pdb_getsampwsid+0x131) [0x81b4d28] #41 /usr/sbin/smbd [0x81b4e4d] #42 /usr/sbin/smbd [0x81b5130] #43 /usr/sbin/smbd(pdb_sid_to_id+0x29) [0x81b3823] #44 /usr/sbin/smbd [0x81b6bca] #45 /usr/sbin/smbd(sid_to_gid+0x109) [0x81b6ea4] #46 /usr/sbin/smbd(create_local_token+0x1ee) [0x82467b6] #47 /usr/sbin/smbd [0x824993d] #48 /usr/sbin/smbd [0x8102427] #49 /usr/sbin/smbd(ntlmssp_update+0x297) [0x8101c16] #50 /usr/sbin/smbd(auth_ntlmssp_update+0x48) [0x82495e1] #51 /usr/sbin/smbd [0x843a57c] #52 /usr/sbin/smbd(reply_sesssetup_and_X+0x1c4) [0x843a9bd] #53 /usr/sbin/smbd [0x80de096] #54 /usr/sbin/smbd(smbd_process+0x429) [0x80dfbe1] #55 /usr/sbin/smbd(main+0xfa2) [0x80a747f] #56 /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b03455] #57 /usr/sbin/smbd [0x80a4511] [2009/09/10 09:44:07, 0] lib/util.c:smb_panic(1668) smb_panic(): calling panic action [/usr/share/samba/panic-action 17363] [2009/09/10 09:44:07, 0] lib/util.c:smb_panic(1676) smb_panic(): action returned status 0 [2009/09/10 09:44:07, 0] lib/fault.c:dump_core(201) dumping core in /var/log/samba/cores/smbd I did several searches but with no luck... Does anyone have an idea on how can I solve this? thanks -- Lorenzo Milesi - lorenzo.mil...@yetopen.it YetOpen S.r.l. - http://www.yetopen.it/ Via Previati 72 - 23900 Lecco - ITALY - Tel 0341 220 205 - Fax 178 607 8199 GPG/PGP Key-Id: 0xE704E230 - http://keyserver.linux.it D.Lgs. 196/2003 Si avverte che tutte le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario. Nel caso in cui questo messaggio Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo, a non inoltrarlo a terzi e ad avvertirci non appena possibile. Grazie. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
