thr3ads.net - samba - [Samba] samba PANIC [Nov 2011]

If this information is useful, please help other people find it:
Share via:

skull

2011-Nov-25 14:42 UTC

[Samba] samba PANIC

Hello folks.

We've got a wierd Problem at a customer server.
The Server was running fine until tomorrow morning...

My problem is that i have no idea where to begin my search for a solution.
The Server is used as a Primary Domain Controller and worked just fine.

here you see what cat /var/log/message | grep smbd is trying to tell me:

First i have a lot of lines like this:
Nov 20 04:04:12 dc smbd[18091]: [2011/11/20 04:04:12.761519,  0] 
printing/print_cups.c:108(cups_connect)
Nov 20 04:04:12 dc smbd[18091]:   Unable to connect to CUPS server 
localhost:631 - Connection refused
..Thats normal because cups is not running.


This one looks more suspicious, it seems that the machine can't properly 
connect to the domain. But the system was running fine anyway... (regarding 
the machine and the network/domain itself)

Nov 20 11:14:34 dc smbd[19184]: [2011/11/20 11:14:34.524218,  0] 
rpc_server/srv_netlog_nt.c:714(_netr_ServerAuthenticate3)
Nov 20 11:14:34 dc smbd[19184]:   _netr_ServerAuthenticate3: 
netlogon_creds_server_check failed. Rejecting auth request from client 
WKST21 machine account WKST21$
Nov 20 11:15:02 dc smbd[19184]: [2011/11/20 11:15:02.680302,  0] 
lib/util_sock.c:474(read_fd_with_timeout)
Nov 20 11:15:02 dc smbd[19184]: [2011/11/20 11:15:02.680450,  0] 
lib/util_sock.c:1441(get_peer_addr_internal)
Nov 20 11:15:02 dc smbd[19184]:   getpeername failed. Error was Transport 
endpoint is not connected
Nov 20 11:15:02 dc smbd[19184]:   read_fd_with_timeout: client 0.0.0.0 read 
error = Connection reset by peer.
Nov 20 11:15:06 dc smbd[19188]: [2011/11/20 11:15:06.924877,  0] 
smbd/nttrans.c:2271(call_nt_transact_ioctl)
Nov 20 11:15:06 dc smbd[19188]:   call_nt_transact_ioctl(0x1401c4): 
Currently not implemented.
Nov 20 11:17:54 dc smbd[19208]: [2011/11/20 11:17:54.824653,  0] 
printing/print_cups.c:108(cups_connect)
So i don't really worry about that.

The cups errors went on until there was a new line after the cups errors:
Nov 20 16:11:30 dc smbd[21347]:   Unable to connect to CUPS server 
localhost:631 - Connection refused
Nov 20 16:11:30 dc smbd[21346]: [2011/11/20 16:11:30.467905,  0] 
printing/print_cups.c:468(cups_async_callback)
Nov 20 16:11:30 dc smbd[21346]:   failed to retrieve printer list: 
NT_STATUS_UNSUCCESSFUL
note the NT_STATUS_UNSUCCESSFUL error....>From then the cups error is always followed by the NT_STATUS_UNSUCCESSFUL but samba worked fine anyway.

And here is where it went bonkers:
======================
Nov 25 07:28:53 dc smbd[1261]: [2011/11/25 07:28:53.344761,  0] 
rpc_server/srv_netlog_nt.c:714(_netr_ServerAuthenticate3)
Nov 25 07:28:53 dc smbd[1261]:   _netr_ServerAuthenticate3: 
netlogon_creds_server_check failed. Rejecting auth request from client 
WKST21 machine account WKST21$
Nov 25 07:29:23 dc smbd[1265]: [2011/11/25 07:29:23.457344,  0] 
lib/util_sock.c:1441(get_peer_addr_internal)
Nov 25 07:29:23 dc smbd[1265]:   getpeername failed. Error was Transport 
endpoint is not connected
Nov 25 07:29:23 dc smbd[1265]: [2011/11/25 07:29:23.469821,  0] 
lib/util_sock.c:680(write_data)
Nov 25 07:29:23 dc smbd[1265]: [2011/11/25 07:29:23.469877,  0] 
lib/util_sock.c:1441(get_peer_addr_internal)
Nov 25 07:29:23 dc smbd[1265]:   getpeername failed. Error was Transport 
endpoint is not connected
Nov 25 07:29:23 dc smbd[1265]:   write_data: write failure in writing to 
client 0.0.0.0. Error Connection reset by peer
Nov 25 07:29:23 dc smbd[1265]: [2011/11/25 07:29:23.486266,  0] 
smbd/process.c:79(srv_send_smb)
Nov 25 07:29:23 dc smbd[1265]:   Error writing 4 bytes to client. -1. 
(Transport endpoint is not connected)
Nov 25 07:29:23 dc smbd[1261]: [2011/11/25 07:29:23.618947,  0] 
lib/util_sock.c:474(read_fd_with_timeout)
Nov 25 07:29:23 dc smbd[1261]: [2011/11/25 07:29:23.619014,  0] 
lib/util_sock.c:1441(get_peer_addr_internal)
Nov 25 07:29:23 dc smbd[1261]:   getpeername failed. Error was Transport 
endpoint is not connected
Nov 25 07:29:23 dc smbd[1261]:   read_fd_with_timeout: client 0.0.0.0 read 
error = Connection reset by peer.
Nov 25 07:30:16 dc smbd[1276]: [2011/11/25 07:30:16.679122,  0] 
lib/util_sock.c:680(write_data)
Nov 25 07:30:16 dc smbd[1276]: [2011/11/25 07:30:16.699813,  0] 
lib/util_sock.c:1441(get_peer_addr_internal)
Nov 25 07:30:16 dc smbd[1276]:   getpeername failed. Error was Transport 
endpoint is not connected
Nov 25 07:30:16 dc smbd[1276]:   write_data: write failure in writing to 
client 0.0.0.0. Error Connection reset by peer
Nov 25 07:30:16 dc smbd[1276]: [2011/11/25 07:30:16.699925,  0] 
smbd/process.c:79(srv_send_smb)
Nov 25 07:30:16 dc smbd[1276]:   Error writing 4 bytes to client. -1. 
(Transport endpoint is not connected)
Nov 25 07:31:07 dc smbd[1283]: [2011/11/25 07:31:07.193249,  0] 
lib/util_sock.c:1441(get_peer_addr_internal)
Nov 25 07:31:07 dc smbd[1283]:   getpeername failed. Error was Transport 
endpoint is not connected
Nov 25 07:31:07 dc smbd[1283]: [2011/11/25 07:31:07.193914,  0] 
lib/util_sock.c:680(write_data)
Nov 25 07:31:07 dc smbd[1283]: [2011/11/25 07:31:07.193967,  0] 
lib/util_sock.c:1441(get_peer_addr_internal)
Nov 25 07:31:07 dc smbd[1283]:   getpeername failed. Error was Transport 
endpoint is not connected
Nov 25 07:31:07 dc smbd[1283]:   write_data: write failure in writing to 
client 0.0.0.0. Error Connection reset by peer
Nov 25 07:31:07 dc smbd[1283]: [2011/11/25 07:31:07.194056,  0] 
smbd/process.c:79(srv_send_smb)
Nov 25 07:31:07 dc smbd[1283]:   Error writing 4 bytes to client. -1. 
(Transport endpoint is not connected)
Nov 25 07:31:23 dc smbd[1285]: [2011/11/25 07:31:23.386030,  0] 
rpc_server/srv_netlog_nt.c:714(_netr_ServerAuthenticate3)
Nov 25 07:31:23 dc smbd[1285]:   _netr_ServerAuthenticate3: 
netlogon_creds_server_check failed. Rejecting auth request from client 
WKST34 machine account WKST34$
Nov 25 07:31:54 dc smbd[1285]: [2011/11/25 07:31:54.988624,  0] 
smbd/nttrans.c:2296(call_nt_transact_ioctl)
Nov 25 07:31:54 dc smbd[1285]:   call_nt_transact_ioctl(0x1401c4): Currently 
not implemented.
Nov 25 07:32:17 dc smbd[1290]: [2011/11/25 07:32:17.620808,  0] 
lib/util_sock.c:474(read_fd_with_timeout)
Nov 25 07:32:17 dc smbd[1290]: [2011/11/25 07:32:17.620914,  0] 
lib/util_sock.c:1441(get_peer_addr_internal)
Nov 25 07:32:17 dc smbd[1290]:   getpeername failed. Error was Transport 
endpoint is not connected
Nov 25 07:32:17 dc smbd[1290]:   read_fd_with_timeout: client 0.0.0.0 read 
error = Connection reset by peer.
Nov 25 07:32:47 dc smbd[1292]: [2011/11/25 07:32:47.619491,  0] 
lib/util_sock.c:474(read_fd_with_timeout)
Nov 25 07:32:47 dc smbd[1292]: [2011/11/25 07:32:47.619593,  0] 
lib/util_sock.c:1441(get_peer_addr_internal)
Nov 25 07:32:47 dc smbd[1292]:   getpeername failed. Error was Transport 
endpoint is not connected
Nov 25 07:32:47 dc smbd[1292]:   read_fd_with_timeout: client 0.0.0.0 read 
error = Connection reset by peer.
Nov 25 07:32:54 dc smbd[1294]: [2011/11/25 07:32:54.643053,  0] 
smbd/nttrans.c:2296(call_nt_transact_ioctl)
Nov 25 07:32:54 dc smbd[1294]:   call_nt_transact_ioctl(0x1401c4): Currently 
not implemented.
Nov 25 07:34:56 dc smbd[1297]: [2011/11/25 07:34:56.772439,  0] 
locking/locking.c:804(share_mode_lock_destructor)
Nov 25 07:34:56 dc smbd[1297]:   store returned NT_STATUS_UNSUCCESSFUL
Nov 25 07:34:56 dc smbd[1297]: [2011/11/25 07:34:56.772544,  0] 
lib/util.c:1468(smb_panic)
Nov 25 07:34:56 dc smbd[1297]:   PANIC (pid 1297): could not store share 
mode entry: NT_STATUS_UNSUCCESSFUL
Nov 25 07:34:56 dc smbd[1297]: [2011/11/25 07:34:56.817234,  0] 
lib/util.c:1572(log_stack_trace)
Nov 25 07:34:56 dc smbd[1297]:   BACKTRACE: 21 stack frames:
Nov 25 07:34:56 dc smbd[1297]:    #0 smbd(log_stack_trace+0x2d) [0x71cb80]
Nov 25 07:34:56 dc smbd[1297]:    #1 smbd(smb_panic+0x7c) [0x71ccb2]
Nov 25 07:34:56 dc smbd[1297]:    #2 smbd [0x6a3fad]
Nov 25 07:34:56 dc smbd[1297]:    #3 smbd(_talloc_free+0x162) [0xaaff0f]
Nov 25 07:34:56 dc smbd[1297]:    #4 smbd [0x4b9708]
Nov 25 07:34:56 dc smbd[1297]:    #5 smbd(create_file_default+0x236) 
[0x4b9dd6]
Nov 25 07:34:56 dc smbd[1297]:    #6 smbd [0x4f9400]
Nov 25 07:34:56 dc smbd[1297]:    #7 smbd(smb_vfs_call_create_file+0xac) 
[0x4bfdaa]
Nov 25 07:34:56 dc smbd[1297]:    #8 smbd(reply_ntcreate_and_X+0x5ce) 
[0x47ea59]
Nov 25 07:34:56 dc smbd[1297]:    #9 smbd [0x4d1e26]
Nov 25 07:34:56 dc smbd[1297]:    #10 smbd [0x4d4eb1]
Nov 25 07:34:56 dc smbd[1297]:    #11 smbd [0x4d5777]
Nov 25 07:34:56 dc smbd[1297]:    #12 smbd(run_events+0x276) [0x72d5c1]
Nov 25 07:34:56 dc smbd[1297]:    #13 smbd(smbd_process+0xb40) [0x4d4641]
Nov 25 07:34:56 dc smbd[1297]:    #14 smbd [0xaae3bb]
Nov 25 07:34:56 dc smbd[1297]:    #15 smbd(run_events+0x276) [0x72d5c1]
Nov 25 07:34:56 dc smbd[1297]:    #16 smbd [0x72d876]
Nov 25 07:34:56 dc smbd[1297]:    #17 smbd(_tevent_loop_once+0x9d) 
[0x72ddbd]
Nov 25 07:34:56 dc smbd[1297]:    #18 smbd(main+0x1277) [0xaae085]
Nov 25 07:34:56 dc smbd[1297]:    #19 /lib/libc.so.6(__libc_start_main+0xdc) 
[0xff5dec]
Nov 25 07:34:56 dc smbd[1297]:    #20 smbd [0x450fa1]
Nov 25 07:34:56 dc smbd[1297]: [2011/11/25 07:34:56.892103,  0] 
lib/fault.c:326(dump_core)
Nov 25 07:34:56 dc smbd[1297]:   dumping core in /var/log/samba/cores/smbd
Nov 25 07:34:56 dc smbd[1297]:


Can someone give me a hint what could have happened?
We are using Samba version:
samba3-client-3.5.12-44.el5
samba3-3.5.12-44.el5
samba3-utils-3.5.12-44.el5

Any hint would be appreciated

greetings
mathew

fuzzy_4711

2011-Nov-25 14:54 UTC

head link

[Samba] samba PANIC

-------- Original - Text --------> Error was Transport endpoint is not connected 
http://lists.debian.org/debian-user-german/2006/02/msg02752.html

skull

2011-Nov-25 15:39 UTC

head link

[Samba] samba PANIC

thanks for the hint

but could that really the cause for the crash?

----- Original Message ----- 
From: "fuzzy_4711" <fuzzy_4711 at gmx.de>
To: <samba at lists.samba.org>
Sent: Friday, November 25, 2011 3:54 PM
Subject: Re: [Samba] samba PANIC

> 
> 
> -------- Original - Text --------
>> Error was Transport endpoint is not connected 
> 
> http://lists.debian.org/debian-user-german/2006/02/msg02752.html
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba

skull

2011-Nov-28 10:15 UTC

head link

[Samba] samba PANIC

We got another Crash today.

Still the same error message as last thursday.
Does no one have an idea where to begin my search?
Do you guys need more information?

greetings

here once again the error message from thursday:
Nov 25 07:40:08 dc smbd[1311]: [2011/11/25 07:40:08.237930,  0] 
locking/locking.c:804(share_mode_lock_destructor)
Nov 25 07:40:08 dc smbd[1311]:   store returned NT_STATUS_UNSUCCESSFUL
Nov 25 07:40:08 dc smbd[1311]: [2011/11/25 07:40:08.238030,  0] 
lib/util.c:1468(smb_panic)
Nov 25 07:40:08 dc smbd[1311]:   PANIC (pid 1311): could not store share 
mode entry: NT_STATUS_UNSUCCESSFUL
Nov 25 07:40:08 dc smbd[1311]: [2011/11/25 07:40:08.242848,  0] 
lib/util.c:1572(log_stack_trace)
Nov 25 07:40:08 dc smbd[1311]:   BACKTRACE: 21 stack frames:
Nov 25 07:40:08 dc smbd[1311]:    #0 smbd(log_stack_trace+0x2d) [0x71cb80]
Nov 25 07:40:08 dc smbd[1311]:    #1 smbd(smb_panic+0x7c) [0x71ccb2]
Nov 25 07:40:08 dc smbd[1311]:    #2 smbd [0x6a3fad]
Nov 25 07:40:08 dc smbd[1311]:    #3 smbd(_talloc_free+0x162) [0xaaff0f]
Nov 25 07:40:08 dc smbd[1311]:    #4 smbd [0x4b9708]
Nov 25 07:40:08 dc smbd[1311]:    #5 smbd(create_file_default+0x236) 
[0x4b9dd6]
Nov 25 07:40:08 dc smbd[1311]:    #6 smbd [0x4f9400]
Nov 25 07:40:08 dc smbd[1311]:    #7 smbd(smb_vfs_call_create_file+0xac) 
[0x4bfdaa]
Nov 25 07:40:08 dc smbd[1311]:    #8 smbd(reply_ntcreate_and_X+0x5ce) 
[0x47ea59]
Nov 25 07:40:08 dc smbd[1311]:    #9 smbd [0x4d1e26]
Nov 25 07:40:09 dc smbd[1311]:    #10 smbd [0x4d4eb1]
Nov 25 07:40:09 dc smbd[1311]:    #11 smbd [0x4d5777]
Nov 25 07:40:09 dc smbd[1311]:    #12 smbd(run_events+0x276) [0x72d5c1]
Nov 25 07:40:09 dc smbd[1311]:    #13 smbd(smbd_process+0xb40) [0x4d4641]
Nov 25 07:40:09 dc smbd[1311]:    #14 smbd [0xaae3bb]
Nov 25 07:40:10 dc smbd[1311]:    #15 smbd(run_events+0x276) [0x72d5c1]
Nov 25 07:40:10 dc smbd[1311]:    #16 smbd [0x72d876]
Nov 25 07:40:10 dc smbd[1311]:    #17 smbd(_tevent_loop_once+0x9d) 
[0x72ddbd]
Nov 25 07:40:10 dc smbd[1311]:    #18 smbd(main+0x1277) [0xaae085]
Nov 25 07:40:10 dc smbd[1311]:    #19 /lib/libc.so.6(__libc_start_main+0xdc) 
[0xff5dec]
Nov 25 07:40:11 dc smbd[1311]:    #20 smbd [0x450fa1]
Nov 25 07:40:11 dc smbd[1311]: [2011/11/25 07:40:11.378394,  0] 
lib/fault.c:326(dump_core)
Nov 25 07:40:11 dc smbd[1311]:   dumping core in 
/var/log/samba/cores/smbd----- Original Message ----- 
From: "skull" <skull17 at gmx.ch>
To: <samba at lists.samba.org>
Sent: Friday, November 25, 2011 4:39 PM
Subject: Re: [Samba] samba PANIC

> thanks for the hint
>
> but could that really the cause for the crash?
>
> ----- Original Message ----- 
> From: "fuzzy_4711" <fuzzy_4711 at gmx.de>
> To: <samba at lists.samba.org>
> Sent: Friday, November 25, 2011 3:54 PM
> Subject: Re: [Samba] samba PANIC
>
>
>>
>>
>> -------- Original - Text --------
>>> Error was Transport endpoint is not connected
>>
>> http://lists.debian.org/debian-user-german/2006/02/msg02752.html
>> -- 
>> 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

Volker Lendecke

2011-Nov-28 10:19 UTC

head link

[Samba] samba PANIC

On Mon, Nov 28, 2011 at 11:15:52AM +0100, skull wrote:> We got another Crash today.
> 
> Still the same error message as last thursday.
> Does no one have an idea where to begin my search?
> Do you guys need more information?
Exact Samba version, your smb.conf and a debug level 10 log
of smbd leading to that crash would tremendously help.

With best regards,

Volker Lendecke

-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 G?ttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG G?ttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt at sernet.de

skull

2011-Nov-28 12:37 UTC

head link

[Samba] samba PANIC

due tu the fact that the server is in a productive environment i am not able 
to restart the samba service.
is there a way do raise the loglevel without restarting samba?

I found an old way to to it in an oreilly openbook but im not sure if this 
still works
http://oreilly.com/openbook/samba/book/ch09_01.html
9.1.1.2 Activating and deactivating logging

# Increase the logging level by 1
kill -SIGUSR1 1234

# Decrease the logging level by 1
kill -SIGUSR2 1234


----- Original Message ----- 
From: "Volker Lendecke" <Volker.Lendecke at SerNet.DE>
To: "skull" <skull17 at gmx.ch>
Cc: <samba at lists.samba.org>
Sent: Monday, November 28, 2011 11:19 AM
Subject: Re: [Samba] samba PANIC

> On Mon, Nov 28, 2011 at 11:15:52AM +0100, skull wrote:
>> We got another Crash today.
>>
>> Still the same error message as last thursday.
>> Does no one have an idea where to begin my search?
>> Do you guys need more information?
>
> Exact Samba version, your smb.conf and a debug level 10 log
> of smbd leading to that crash would tremendously help.
>
> With best regards,
>
> Volker Lendecke
>
> -- 
> SerNet GmbH, Bahnhofsallee 1b, 37081 G?ttingen
> phone: +49-551-370000-0, fax: +49-551-370000-9
> AG G?ttingen, HRB 2816, GF: Dr. Johannes Loxen
> http://www.sernet.de, mailto:kontakt at sernet.de

skull

2011-Nov-28 15:01 UTC

head link

[Samba] samba PANIC

thanks.
its a redhat system so a "service smb reload" does the trick.
i'll raise the loglevel and provide more information later.
----- Original Message ----- 
From: "Dermot" <paikkos at googlemail.com>
To: "skull" <skull17 at gmx.ch>
Sent: Monday, November 28, 2011 1:56 PM
Subject: Re: [Samba] samba PANIC

> On 28 November 2011 12:37, skull <skull17 at gmx.ch> wrote:
>> due tu the fact that the server is in a productive environment i am not
>> able
>> to restart the samba service.
>> is there a way do raise the loglevel without restarting samba?
>>
>> I found an old way to to it in an oreilly openbook but im not sure if 
>> this
>> still works
>> http://oreilly.com/openbook/samba/book/ch09_01.html
>> 9.1.1.2 Activating and deactivating logging
>>
>> # Increase the logging level by 1
>> kill -SIGUSR1 1234
>>
>> # Decrease the logging level by 1
>> kill -SIGUSR2 1234
>
>
> You should be able to reload your configuration without restarting the
> service. You can either edit you config file and change the debug
> level or change the command line that runs you smbd to include with
> the -d flag at a level you want.
>
> The way you reload you config is dependent on you distribution,
> perhaps '/etc/init,d/samba reload' or kill -HUP `pgrepsmbd` but
you'd
> want to test this on a non-production server first.
> HTH,
> Dermot

Reasonably Related Threads

Search for more maybe matching threads

samba - Nov 2011 - samba PANIC

[Samba] samba PANIC

[Samba] samba PANIC

[Samba] samba PANIC

[Samba] samba PANIC

[Samba] samba PANIC

[Samba] samba PANIC

[Samba] samba PANIC

Reasonably Related Threads