Problema Servidor Samba

1. Problema Servidor Samba

Duilio de Oliveira
duilio

(usa Suse)

Enviado em 28/04/2010 - 16:31h

Boa tarde a todos,

Estou tendo problemas com meu servidor Samba que é integrado com AD, de uns dias pra cá começou a aparecer essas mensagens no log:

Apr 28 15:15:22 cbemi-lnx-fs02 smbd[25582]: [2010/04/28 15:15:22, 0] smbd/service.c:make_connection_snum(740)
Apr 28 15:15:22 cbemi-lnx-fs02 smbd[25582]: create_connection_server_info failed: NT_STATUS_ACCESS_DENIED
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[27437]: [2010/04/28 15:15:23, 0] lib/util_sock.c:read_socket_with_timeout(939)
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[27437]: [2010/04/28 15:15:23, 0] lib/util_sock.c:get_peer_addr_internal(1676)
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[27437]: getpeername failed. Error was Ponto final de transporte não está conectado
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[27437]: read_socket_with_timeout: client 0.0.0.0 read error = Conexão fechada pela outra ponta.
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[27437]: [2010/04/28 15:15:23, 0] lib/util_sock.c:write_data(1136)
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[27437]: [2010/04/28 15:15:23, 0] lib/util_sock.c:get_peer_addr_internal(1676)
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[27437]: getpeername failed. Error was Ponto final de transporte não está conectado
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[27437]: write_data: write failure in writing to client 0.0.0.0. Error Pipe quebrado
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[27437]: [2010/04/28 15:15:23, 0] smbd/process.c:srv_send_smb(74)
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[27437]: Error writing 75 bytes to client. -1. (Ponto final de transporte não está conectado)
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[15804]: [2010/04/28 15:15:23, 0] lib/util_sock.c:read_socket_with_timeout(939)
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[15804]: [2010/04/28 15:15:23, 0] lib/util_sock.c:get_peer_addr_internal(1676)
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[15804]: getpeername failed. Error was Ponto final de transporte não está conectado
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[15804]: read_socket_with_timeout: client 0.0.0.0 read error = Conexão fechada pela outra ponta.
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[15804]: [2010/04/28 15:15:23, 0] lib/util_sock.c:write_data(1136)
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[15804]: [2010/04/28 15:15:23, 0] lib/util_sock.c:get_peer_addr_internal(1676)
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[15804]: getpeername failed. Error was Ponto final de transporte não está conectado
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[15804]: write_data: write failure in writing to client 0.0.0.0. Error Pipe quebrado
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[15804]: [2010/04/28 15:15:23, 0] smbd/process.c:srv_send_smb(74)
Apr 28 15:15:23 cbemi-lnx-fs02 smbd[15804]: Error writing 75 bytes to client. -1. (Ponto final de transporte não está conectado)
Apr 28 15:15:46 cbemi-lnx-fs02 smbd[25582]: [2010/04/28 15:15:46, 0] smbd/service.c:make_connection_snum(740)
Apr 28 15:15:46 cbemi-lnx-fs02 smbd[25582]: create_connection_server_info failed: NT_STATUS_ACCESS_DENIED
Apr 28 15:16:59 cbemi-lnx-fs02 smbd[25695]: [2010/04/28 15:16:59, 0] smbd/nttrans.c:call_nt_transact_ioctl(1989)
Apr 28 15:16:59 cbemi-lnx-fs02 smbd[25695]: call_nt_transact_ioctl(0x90060): Currently not implemented.
Apr 28 15:19:33 cbemi-lnx-fs02 smbd[25523]: [2010/04/28 15:19:33, 0] lib/util_sock.c:read_socket_with_timeout(939)
Apr 28 15:19:33 cbemi-lnx-fs02 smbd[25523]: [2010/04/28 15:19:33, 0] lib/util_sock.c:get_peer_addr_internal(1676)
Apr 28 15:19:33 cbemi-lnx-fs02 smbd[25523]: getpeername failed. Error was Ponto final de transporte não está conectado
Apr 28 15:19:33 cbemi-lnx-fs02 smbd[25523]: read_socket_with_timeout: client 0.0.0.0 read error = Conexão fechada pela outra ponta.
Apr 28 15:22:53 cbemi-lnx-fs02 smbd[26376]: [2010/04/28 15:22:53, 0] smbd/nttrans.c:call_nt_transact_ioctl(1989)
Apr 28 15:22:53 cbemi-lnx-fs02 smbd[26376]: call_nt_transact_ioctl(0x9005c): Currently not implemented.
Apr 28 15:24:01 cbemi-lnx-fs02 smbd[25514]: [2010/04/28 15:24:01, 0] smbd/nttrans.c:call_nt_transact_ioctl(1989)
Apr 28 15:24:01 cbemi-lnx-fs02 smbd[25514]: call_nt_transact_ioctl(0x90060): Currently not implemented.
Apr 28 15:26:22 cbemi-lnx-fs02 smbd[25582]: [2010/04/28 15:26:22, 0] smbd/nttrans.c:call_nt_transact_ioctl(1989)
Apr 28 15:26:22 cbemi-lnx-fs02 smbd[25582]: call_nt_transact_ioctl(0x90060): Currently not implemented.

Alguém teria alguma sugestão para contornar esse problema.

Desde já agradeço a atenção de todos


  


2. Re: Problema Servidor Samba

Raphael Monteiro
rmonteiraum

(usa CentOS)

Enviado em 18/01/2011 - 17:51h

Rapá, tô com o mesmo problema em um cliente.

Resolví dar um UP no tópico, pra ver se alguém que realmente saiba alguma coisa, possa postar alguma informação sobre o caso.

Abração


3. Re: Problema Servidor Samba

Gabriel Lopes
paleogoti

(usa Ubuntu)

Enviado em 27/11/2013 - 11:57h

To com problema semelhante. To tentando descobrir o motivo do meu servidor parar repentinamente, travando todos os meus switches, e só o q eu encontro no /var/log/messages é isso.
Nov 27 09:13:19 srvoracle smbd_audit: [2013/11/27 09:13:19, 0] smbd/nttrans.c:call_nt_transact_ioctl(2463)
Nov 27 09:13:19 srvoracle smbd_audit: call_nt_transact_ioctl(0x1401c4): Currently not implemented.







Patrocínio

Site hospedado pelo provedor RedeHost.
Linux banner
Linux banner
Linux banner

Destaques

Artigos

Dicas

Tópicos

Top 10 do mês

Scripts