Re: [Samba] Linux 2.6.31, samba server no longer working
I increased the log level and got something out of log.smbd. It claiming that the user "millerti" doesn't exist. Some googling suggested that samba is now using a new user database backend. Using smbpasswd, I added the missing user with the right password, and voila, I am able to connect now. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Linux 2.6.31, samba server no longer working
This is stand-alone. It should be very simple, with just password authentication. I'm not seeing any permission denied in log files. At least not smbd.log, and I can't seem to find anything in the system log. On Sat, Oct 17, 2009 at 12:39 AM, Robert LeBlanc wrote: > I wonder if this is similar to what I was seeing with 3.4.2 today. Are you > bound to AD or is it stand alone? I kept seeing a permission denied message > in the log files when trying to access the Kerberos keytab file. I coughed > it up to backporting 3.4.2 to Debian Lenny and there was a problem with > using krb5 1.6 instead of 1.7. I didn't feel like backporting Kerberos too > to test that threory, I need to get these machines up, so I just installed > my patched version of 3.2.5. > > Robert LeBlanc > Life Sciences & Undergraduate Education Computer Support > Brigham Young University > > > On Fri, Oct 16, 2009 at 7:35 PM, Timothy Normand Miller > wrote: >> >> Sorry. Not the kernel. Samba 3.3.7 worked (with a bug fix I had >> added). It's version 3.4.2 that doesn't work. I've checked the >> config files. I can't figure out why it doesn't work. I just get >> connection refused. >> >> On Fri, Oct 16, 2009 at 12:26 PM, Timothy Normand Miller >> wrote: >> > Hi, >> > >> > Since upgrading to Linux 2.6.31, smb shares on my linux box are no >> > longer mountable by other computers. As far as the client is >> > concerned, it looks like authentication is failing. But when I look >> > in /var/log/samba, I find absolutely nothing about any attempted or >> > failed connections. Both smbd and nmbd are still running, so they >> > didn't crash. I just can't find anything to help me diagnose the >> > problem. >> > >> > Can anyone give me some suggestions about where to start looking for >> > the cause of the trouble? >> > >> > Thanks! >> > >> > -- >> > Timothy Normand Miller >> > http://www.cse.ohio-state.edu/~millerti >> > Open Graphics Project >> > >> >> >> >> -- >> Timothy Normand Miller >> http://www.cse.ohio-state.edu/~millerti >> Open Graphics Project >> -- >> To unsubscribe from this list go to the following URL and read the >> instructions: https://lists.samba.org/mailman/options/samba > > -- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Open Graphics Project -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Linux 2.6.31, samba server no longer working
Sorry. Not the kernel. Samba 3.3.7 worked (with a bug fix I had added). It's version 3.4.2 that doesn't work. I've checked the config files. I can't figure out why it doesn't work. I just get connection refused. On Fri, Oct 16, 2009 at 12:26 PM, Timothy Normand Miller wrote: > Hi, > > Since upgrading to Linux 2.6.31, smb shares on my linux box are no > longer mountable by other computers. As far as the client is > concerned, it looks like authentication is failing. But when I look > in /var/log/samba, I find absolutely nothing about any attempted or > failed connections. Both smbd and nmbd are still running, so they > didn't crash. I just can't find anything to help me diagnose the > problem. > > Can anyone give me some suggestions about where to start looking for > the cause of the trouble? > > Thanks! > > -- > Timothy Normand Miller > http://www.cse.ohio-state.edu/~millerti > Open Graphics Project > -- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Open Graphics Project -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Linux 2.6.31, samba server no longer working
Hi, Since upgrading to Linux 2.6.31, smb shares on my linux box are no longer mountable by other computers. As far as the client is concerned, it looks like authentication is failing. But when I look in /var/log/samba, I find absolutely nothing about any attempted or failed connections. Both smbd and nmbd are still running, so they didn't crash. I just can't find anything to help me diagnose the problem. Can anyone give me some suggestions about where to start looking for the cause of the trouble? Thanks! -- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Open Graphics Project -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] HELP: Samba server crashing on me
On Mon, Sep 7, 2009 at 11:47 AM, Michael Wood wrote: > 2009/9/7 Timothy Normand Miller : >> I'm glad I could help. Should we try to figure out why it happened in >> the first place? Like what changed in my environment that caused it >> to go through this code path now and never before? > > Do you suddenly have any Macs using Bonjour or something? :) Just a > guess, and that still wouldn't explain why you're the first person to > notice. > > mDNS is Multicast DNS which is used by Bonjour/zeroconf/avahi. The machine that usually mounts the SMB share is a Mac. I installed Snow Leopard two days after it came out, but I only started having problems with samba yesterday. -- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Open Graphics Project -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] HELP: Samba server crashing on me
I'm glad I could help. Should we try to figure out why it happened in
the first place? Like what changed in my environment that caused it
to go through this code path now and never before?
On Mon, Sep 7, 2009 at 6:17 AM, Volker
Lendecke wrote:
> On Mon, Sep 07, 2009 at 01:05:31AM -0400, Timothy Normand Miller wrote:
>> Well, the solution was as simple as this:
>>
>> bool dns_register_smbd_reply(struct dns_reg_state *dns_state,
>> fd_set *lfds, struct timeval *timeout)
>> {
>> int mdnsd_conn_fd = -1;
>>
>> + if (!dns_state) return false;
>> if (dns_state->srv_ref == NULL) {
>> return false;
>> }
>
> Thanks a lot! Will be in 3.3.8.
>
> Volker
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkqk3bAACgkQbsgDfmnSbrYtFACcDg4py8Uk6hj0iftSSDaWYkZ7
> KWQAn1nlU8wo5D+SmmcVezqZ3bKhYgsX
> =G1Rg
> -END PGP SIGNATURE-
>
>
--
Timothy Normand Miller
http://www.cse.ohio-state.edu/~millerti
Open Graphics Project
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] HELP: Samba server crashing on me
Well, the solution was as simple as this:
bool dns_register_smbd_reply(struct dns_reg_state *dns_state,
fd_set *lfds, struct timeval *timeout)
{
int mdnsd_conn_fd = -1;
+if (!dns_state) return false;
if (dns_state->srv_ref == NULL) {
return false;
}
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] HELP: Samba server crashing on me
> > Please file a bug report on https://bugzilla.samba.org - attach all the > info you presented on this list, and also the output of "testparm -s". > > Suggest you also include the output of "smbd -b" and of "uname -a". Sure thing. > > What is your platform? Did you compile Samba yourself or is this from a > recognized packaged source? Both. I'm using Gentoo. > > Would like to understand why you have this problem and noone else has > reported this problem. Me too. :) -- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Open Graphics Project -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] HELP: Samba server crashing on me
I'm stymied by the fact that no matter what I set the CFLAGS to in the
environment, the compile is optimizing out symbols, but here's what
I'm finding in the source:
static bool open_sockets_smbd(bool is_daemon, bool interactive, const
char *smb_ports)
{
...
struct dns_reg_state * dns_reg = NULL;
... nothing that modifies dns_reg ...
/* process pending nDNS responses */
if (dns_register_smbd_reply(dns_reg, &r_fds, &idle_timeout)) {
--num;
}
...
}
Then the function dns_register_smbd_reply blindly rereferences the
first argument:
bool dns_register_smbd_reply(struct dns_reg_state *dns_state,
fd_set *lfds, struct timeval *timeout)
{
int mdnsd_conn_fd = -1;
if (dns_state->srv_ref == NULL) {
return false;
}
...
}
So, can anyone tell me what I might do to avoid this sequence of
events? It didn't happen before. I don't know what's causing it to
happen now.
On Sun, Sep 6, 2009 at 11:26 PM, Timothy Normand
Miller wrote:
> This is where smbd is getting signal 11 (see the ***):
>
> /* Processes reply from mDNS daemon. Returns true if a reply was received */
> bool dns_register_smbd_reply(struct dns_reg_state *dns_state,
> fd_set *lfds, struct timeval *timeout)
> {
> int mdnsd_conn_fd = -1;
>
> if (dns_state->srv_ref == NULL) { // *** RIGHT HERE AT LINE 171 ***
> return false;
> }
>
> mdnsd_conn_fd = DNSServiceRefSockFD(dns_state->srv_ref);
>
> /* Process reply from daemon. Handles any errors. */
> if ((mdnsd_conn_fd != -1) && (FD_ISSET(mdnsd_conn_fd,lfds)) ) {
> DNSServiceErrorType err;
>
> err = DNSServiceProcessResult(dns_state->srv_ref);
> if (err != kDNSServiceErr_NoError) {
> DEBUG(3, ("failed to process mDNS result (err
> %d), re-trying\n",
> err));
> schedule_dns_register_smbd_retry(dns_state, timeout);
> }
>
> return true;
> }
>
> return false;
> }
>
>
> It appears that dns_state is null, which is evident from the stack trace:
>
> #6 dns_register_smbd_reply (dns_state=0x0, lfds=0x7fffbf342960,
> timeout=0x7fffbf342af0) at smbd/dnsregister.c:171
>
> That's called from here in server.c, in main():
>
> if (dns_register_smbd_reply(dns_reg, &r_fds, &idle_timeout)) {
> --num;
> }
>
> Unfortunately, I can't debug further since dns_reg is optimized out by -O2.
>
--
Timothy Normand Miller
http://www.cse.ohio-state.edu/~millerti
Open Graphics Project
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] HELP: Samba server crashing on me
This is where smbd is getting signal 11 (see the ***):
/* Processes reply from mDNS daemon. Returns true if a reply was received */
bool dns_register_smbd_reply(struct dns_reg_state *dns_state,
fd_set *lfds, struct timeval *timeout)
{
int mdnsd_conn_fd = -1;
if (dns_state->srv_ref == NULL) { // *** RIGHT HERE AT LINE 171 ***
return false;
}
mdnsd_conn_fd = DNSServiceRefSockFD(dns_state->srv_ref);
/* Process reply from daemon. Handles any errors. */
if ((mdnsd_conn_fd != -1) && (FD_ISSET(mdnsd_conn_fd,lfds)) ) {
DNSServiceErrorType err;
err = DNSServiceProcessResult(dns_state->srv_ref);
if (err != kDNSServiceErr_NoError) {
DEBUG(3, ("failed to process mDNS result (err
%d), re-trying\n",
err));
schedule_dns_register_smbd_retry(dns_state, timeout);
}
return true;
}
return false;
}
It appears that dns_state is null, which is evident from the stack trace:
#6 dns_register_smbd_reply (dns_state=0x0, lfds=0x7fffbf342960,
timeout=0x7fffbf342af0) at smbd/dnsregister.c:171
That's called from here in server.c, in main():
if (dns_register_smbd_reply(dns_reg, &r_fds, &idle_timeout)) {
--num;
}
Unfortunately, I can't debug further since dns_reg is optimized out by -O2.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] HELP: Samba server crashing on me
On Sun, Sep 6, 2009 at 11:17 PM, John H Terpstra - Samba Team wrote: > On 09/06/2009 10:12 PM, Timothy Normand Miller wrote: >> On Sun, Sep 6, 2009 at 10:54 PM, Jobst Schmalenbach >> wrote: >>> >>> This is ONLY a guess: >>> >>> * signal 11 means invalid memory reference, so I would check your RAM >>> and even your harddisks, it could be a page fault. >>> (find some other ram, put them in and run it for a while). >> >> This problem is new and 100% reproducable. I've tried rebooting, >> which should fix any intermittent problem. Also the RAM is from >> Crucial, and I'm not doing any overclocking of any kind. Everything >> else is 100% stable, except for samba, which crashes. >> >> Turns out that it doesn't crash until a client tries to connect. >> >>> >>> * may, just maybe your problems from earlier "Unable to connect to CUPS >>> server" >>> have had too many pointer allocations/references that the next one in the >>> chain crashed the server, fix this and check again. >> >> That's the first thing I fixed. Didn't help. Any other ideas? >> >> Apparently, the crash is here: >> >>>> #6 dns_register_smbd_reply (dns_state=0x0, lfds=0x74963ed0, >>>> timeout=0x74964060) at smbd/dnsregister.c:171 >> >> I'm going to pull the source and see what's there. > > Did you by any chance update glibc before this problem started to occur? A few weeks ago. I'm pretty sure I've rebooted once since then, so I don't think that's the problem. > > Samba is a user-space application. If your whole system crashed this > suggests a symptomatic problem with either the hardware (memory or > motherboard) or else corrupt binaries (either kernel or system libraries). No. Only smbd is crashing. Everything else is fine. > > - John T. > >>> >>> this is what I would do first. >>> Jobst >>> >>> >>> >>> On Sun, Sep 06, 2009 at 10:44:01PM -0400, Timothy Normand Miller >>> (theo...@gmail.com) wrote: >>>> For no reason that I can discover, my smb server has started crashing >>>> on me. I'm really hoping someone help me out with this. This is the >>>> relevant portion of the log: >>>> >>>> [2009/09/06 22:24:44, 0] smbd/server.c:main(1274) >>>> smbd version 3.3.7 started. >>>> Copyright Andrew Tridgell and the Samba Team 1992-2009 >>>> [2009/09/06 22:24:44, 0] printing/print_cups.c:cups_connect(103) >>>> Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No >>>> such file or directory >>>> [2009/09/06 22:24:44, 0] printing/print_cups.c:cups_connect(103) >>>> Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No >>>> such file or directory >>>> [2009/09/06 22:26:09, 0] smbd/server.c:main(1274) >>>> smbd version 3.3.7 started. >>>> Copyright Andrew Tridgell and the Samba Team 1992-2009 >>>> [2009/09/06 22:26:09, 0] printing/print_cups.c:cups_connect(103) >>>> Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No >>>> such file or directory >>>> [2009/09/06 22:26:09, 0] printing/print_cups.c:cups_connect(103) >>>> Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No >>>> such file or directory >>>> [2009/09/06 22:26:43, 0] lib/fault.c:fault_report(40) >>>> === >>>> [2009/09/06 22:26:43, 0] lib/fault.c:fault_report(41) >>>> INTERNAL ERROR: Signal 11 in pid 16066 (3.3.7) >>>> Please read the Trouble-Shooting section of the Samba3-HOWTO >>>> [2009/09/06 22:26:43, 0] lib/fault.c:fault_report(43) >>>> >>>> From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf >>>> [2009/09/06 22:26:43, 0] lib/fault.c:fault_report(44) >>>> === >>>> [2009/09/06 22:26:43, 0] lib/util.c:smb_panic(1673) >>>> PANIC (pid 16066): internal error >>>> [2009/09/06 22:26:43, 0] lib/util.c:log_stack_trace(1777) >>>> BACKTRACE: 8 stack frames: >>>> #0 /usr/sbin/smbd(log_stack_trace+0x1c) [0x7f4fdfff6b10] >>>> #1 /usr/sbin/smbd(smb_panic+0x5b) [0x7f4fdfff6c1d] >>>> #2 /usr/sbin/smbd [0x7f4fdffe3e71] >>>> #3 /lib/libpthread.so.0 [0x7f4fde09bef0] >>>> #4 /
Re: [Samba] HELP: Samba server crashing on me
On Sun, Sep 6, 2009 at 10:54 PM, Jobst Schmalenbach wrote: > > This is ONLY a guess: > > * signal 11 means invalid memory reference, so I would check your RAM > and even your harddisks, it could be a page fault. > (find some other ram, put them in and run it for a while). This problem is new and 100% reproducable. I've tried rebooting, which should fix any intermittent problem. Also the RAM is from Crucial, and I'm not doing any overclocking of any kind. Everything else is 100% stable, except for samba, which crashes. Turns out that it doesn't crash until a client tries to connect. > > * may, just maybe your problems from earlier "Unable to connect to CUPS > server" > have had too many pointer allocations/references that the next one in the > chain crashed the server, fix this and check again. That's the first thing I fixed. Didn't help. Any other ideas? Apparently, the crash is here: >> #6 dns_register_smbd_reply (dns_state=0x0, lfds=0x74963ed0, >> timeout=0x74964060) at smbd/dnsregister.c:171 I'm going to pull the source and see what's there. > > this is what I would do first. > Jobst > > > > On Sun, Sep 06, 2009 at 10:44:01PM -0400, Timothy Normand Miller > (theo...@gmail.com) wrote: >> For no reason that I can discover, my smb server has started crashing >> on me. I'm really hoping someone help me out with this. This is the >> relevant portion of the log: >> >> [2009/09/06 22:24:44, 0] smbd/server.c:main(1274) >> smbd version 3.3.7 started. >> Copyright Andrew Tridgell and the Samba Team 1992-2009 >> [2009/09/06 22:24:44, 0] printing/print_cups.c:cups_connect(103) >> Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No >> such file or directory >> [2009/09/06 22:24:44, 0] printing/print_cups.c:cups_connect(103) >> Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No >> such file or directory >> [2009/09/06 22:26:09, 0] smbd/server.c:main(1274) >> smbd version 3.3.7 started. >> Copyright Andrew Tridgell and the Samba Team 1992-2009 >> [2009/09/06 22:26:09, 0] printing/print_cups.c:cups_connect(103) >> Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No >> such file or directory >> [2009/09/06 22:26:09, 0] printing/print_cups.c:cups_connect(103) >> Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No >> such file or directory >> [2009/09/06 22:26:43, 0] lib/fault.c:fault_report(40) >> === >> [2009/09/06 22:26:43, 0] lib/fault.c:fault_report(41) >> INTERNAL ERROR: Signal 11 in pid 16066 (3.3.7) >> Please read the Trouble-Shooting section of the Samba3-HOWTO >> [2009/09/06 22:26:43, 0] lib/fault.c:fault_report(43) >> >> From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf >> [2009/09/06 22:26:43, 0] lib/fault.c:fault_report(44) >> === >> [2009/09/06 22:26:43, 0] lib/util.c:smb_panic(1673) >> PANIC (pid 16066): internal error >> [2009/09/06 22:26:43, 0] lib/util.c:log_stack_trace(1777) >> BACKTRACE: 8 stack frames: >> #0 /usr/sbin/smbd(log_stack_trace+0x1c) [0x7f4fdfff6b10] >> #1 /usr/sbin/smbd(smb_panic+0x5b) [0x7f4fdfff6c1d] >> #2 /usr/sbin/smbd [0x7f4fdffe3e71] >> #3 /lib/libpthread.so.0 [0x7f4fde09bef0] >> #4 /usr/sbin/smbd(dns_register_smbd_reply+0x1c) [0x7f4fdfe59e3b] >> #5 /usr/sbin/smbd(main+0x16e8) [0x7f4fe01f05cc] >> #6 /lib/libc.so.6(__libc_start_main+0xe6) [0x7f4fdca49a26] >> #7 /usr/sbin/smbd [0x7f4fdfde1339] >> [2009/09/06 22:26:43, 0] lib/fault.c:dump_core(231) >> dumping core in /var/log/samba/cores/smbd >> >> I don't get much out of gdb: >> >> #0 0x7f4fdca5d645 in raise (sig=) at >> ../nptl/sysdeps/unix/sysv/linux/raise.c:64 >> 64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. >> in ../nptl/sysdeps/unix/sysv/linux/raise.c >> (gdb) where >> #0 0x7f4fdca5d645 in raise (sig=) at >> ../nptl/sysdeps/unix/sysv/linux/raise.c:64 >> #1 0x7f4fdca5eb63 in abort () at abort.c:88 >> #2 0x7f4fdffe38db in dump_core () at lib/fault.c:242 >> #3 0x7f4fdfff6d3b in smb_panic (why=) at >> lib/util.c:1689 >> #4 0x7f4fdffe3e71 in sig_fault (sig=11) at lib/fault.c:46 >> #5 >> #6 dns_register_smbd_reply (dns_state=0x0, lfds=0x74963ed0, >> timeout=0x74964060) at smbd/dnsregister.c:171 >> #7 0x7f4fe01f05cc in main (argc=, >> argv=) at smbd/server.c:6
[Samba] HELP: Samba server crashing on me
For no reason that I can discover, my smb server has started crashing on me. I'm really hoping someone help me out with this. This is the relevant portion of the log: [2009/09/06 22:24:44, 0] smbd/server.c:main(1274) smbd version 3.3.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2009 [2009/09/06 22:24:44, 0] printing/print_cups.c:cups_connect(103) Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No such file or directory [2009/09/06 22:24:44, 0] printing/print_cups.c:cups_connect(103) Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No such file or directory [2009/09/06 22:26:09, 0] smbd/server.c:main(1274) smbd version 3.3.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2009 [2009/09/06 22:26:09, 0] printing/print_cups.c:cups_connect(103) Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No such file or directory [2009/09/06 22:26:09, 0] printing/print_cups.c:cups_connect(103) Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No such file or directory [2009/09/06 22:26:43, 0] lib/fault.c:fault_report(40) === [2009/09/06 22:26:43, 0] lib/fault.c:fault_report(41) INTERNAL ERROR: Signal 11 in pid 16066 (3.3.7) Please read the Trouble-Shooting section of the Samba3-HOWTO [2009/09/06 22:26:43, 0] lib/fault.c:fault_report(43) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2009/09/06 22:26:43, 0] lib/fault.c:fault_report(44) === [2009/09/06 22:26:43, 0] lib/util.c:smb_panic(1673) PANIC (pid 16066): internal error [2009/09/06 22:26:43, 0] lib/util.c:log_stack_trace(1777) BACKTRACE: 8 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x1c) [0x7f4fdfff6b10] #1 /usr/sbin/smbd(smb_panic+0x5b) [0x7f4fdfff6c1d] #2 /usr/sbin/smbd [0x7f4fdffe3e71] #3 /lib/libpthread.so.0 [0x7f4fde09bef0] #4 /usr/sbin/smbd(dns_register_smbd_reply+0x1c) [0x7f4fdfe59e3b] #5 /usr/sbin/smbd(main+0x16e8) [0x7f4fe01f05cc] #6 /lib/libc.so.6(__libc_start_main+0xe6) [0x7f4fdca49a26] #7 /usr/sbin/smbd [0x7f4fdfde1339] [2009/09/06 22:26:43, 0] lib/fault.c:dump_core(231) dumping core in /var/log/samba/cores/smbd I don't get much out of gdb: #0 0x7f4fdca5d645 in raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. in ../nptl/sysdeps/unix/sysv/linux/raise.c (gdb) where #0 0x7f4fdca5d645 in raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x7f4fdca5eb63 in abort () at abort.c:88 #2 0x7f4fdffe38db in dump_core () at lib/fault.c:242 #3 0x7f4fdfff6d3b in smb_panic (why=) at lib/util.c:1689 #4 0x7f4fdffe3e71 in sig_fault (sig=11) at lib/fault.c:46 #5 #6 dns_register_smbd_reply (dns_state=0x0, lfds=0x74963ed0, timeout=0x74964060) at smbd/dnsregister.c:171 #7 0x7f4fe01f05cc in main (argc=, argv=) at smbd/server.c:689 Other things: - I did try stopping and restarting the service - I ran testparm, and it says my config is fine -- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Open Graphics Project -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] CIFS slow on gigabit, doesn't support sockopt=TCP_NODELAY ?
Hi, everyone. I originally sent this to the cifs-vfs mailing list, but upon reading the descriptions of the lists, I think that might have been the wrong place to ask. My apologies for the repeat. I hope I got the right place this time. :) I've noticed that the cifs client for Linux is slow over gigabit ethernet. It seems to max out at about 10 megs/sec, while the drives can go a lot faster. Also, if I mount the same network share from a Mac, it's a lot faster. When _sharing_ via samba, one can set the TCP_NODELAY option (among others), which fixes the problem. But with the cifs client, I find that there appears to be no way to set the option. When mounting manually, you can use "-o sockopt=TCP_NODELAY", and you can also put that into /etc/fstab. Either way, the option appears to be ignored. I filed this bug with Gentoo: http://bugs.gentoo.org/265183 Am I doing this wrong? Is there a work-around? Or plans to fix it? Thanks! -- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Open Graphics Project -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
