[samba] выключили DC - winbindd упал

[Mike Lykov]

Здравствуйте.

Наблюдаю такую картину:

стоит 
squid-2.5.STABLE5-alt1
samba-3.0.2a-alt4
и настроена ntlm-авторизация. с некоторыми пассами все работает.

В субботу же, пришли администраторы и выключили контроллер домена, с которого 
winbindd берет информацию, по каким-то своим причинам.

после чего я пришел в полнедельник, и обнаружил, что все плохо %)

Вот и вопрос - в чем бага? куда сообщить, что показать? проявляется ли это еше 
у кого? как обойти? как указать, что кроме основного контроллера, есть еще 
два резервных?

выглядело это так:
[2004/03/20 13:20:49, 0] lib/util_sock.c:write_socket_data(388)                               
  write_socket_data: write failure. Error = Connection reset by peer                          
[2004/03/20 13:20:49, 0] lib/util_sock.c:write_socket(413)                                    
  write_socket: Error writing 494 bytes to socket 22: ERRNO = Connection reset 
by peer        
[2004/03/20 13:20:49, 0] libsmb/clientgen.c:cli_send_smb(155)                                 
  Error writing 494 bytes to client. -1 (Connection reset by peer)                            
[2004/03/20 13:20:49, 0] rpc_client/cli_pipe.c:rpc_api_pipe(424)                              
  cli_pipe: return critical error. Error was Write error: Connection reset by 
peer            
[2004/03/20 13:21:01, 0] rpc_client/cli_pipe.c:rpc_api_pipe(424)                              
  cli_pipe: return critical error. Error was Call timed out: server did not 
respond after 1000
[2004/03/20 13:22:12, 0] rpc_client/cli_pipe.c:rpc_api_pipe(424)                              
  cli_pipe: return critical error. Error was Call timed out: server did not 
respond after 1000
[2004/03/20 13:23:26, 0] rpc_client/cli_pipe.c:rpc_api_pipe(424)                              
  cli_pipe: return critical error. Error was Call timed out: server did not 
respond after 1000
[2004/03/20 13:24:08, 0] lib/util_sock.c:write_socket_data(388)                               
  write_socket_data: write failure. Error = Connection reset by peer                          
[2004/03/20 13:24:08, 0] lib/util_sock.c:write_socket(413)                                    
  write_socket: Error writing 138 bytes to socket 17: ERRNO = Connection reset 
by peer        
[2004/03/20 13:24:08, 0] libsmb/clientgen.c:cli_send_smb(155)                                 
  Error writing 138 bytes to client. -1 (Connection reset by peer)   
..... (много раз одно и то же)
..... тут перерыв на час и 20 мин почему-то
[2004/03/20 13:41:59, 0] rpc_client/cli_pipe.c:rpc_api_pipe(424)                              
  cli_pipe: return critical error. Error was Call timed out: server did not 
respond after 1000
[2004/03/20 14:44:23, 0] lib/util_sock.c:write_socket_data(388)                               
  write_socket_data: write failure. Error = Connection reset by peer                          
[2004/03/20 14:44:23, 0] lib/util_sock.c:write_socket(413)                                    
  write_socket: Error writing 486 bytes to socket 22: ERRNO = Connection reset 
by peer    
...... (много одинакового)
[2004/03/20 15:29:08, 0] libsmb/clientgen.c:cli_send_smb(155)                                 
  Error writing 45 bytes to client. -1 (Connection reset by peer)                             
[2004/03/20 15:29:08, 0] lib/fault.c:fault_report(36)                                         
  ===============================================================                             
[2004/03/20 15:29:08, 0] lib/fault.c:fault_report(37)                                         
  INTERNAL ERROR: Signal 11 in pid 17836 (3.0.2a-ALT/alt4)                                    
  Please read the appendix Bugs of the Samba HOWTO collection                                 
[2004/03/20 15:29:08, 0] lib/fault.c:fault_report(39)                                         
  ===============================================================    
[2004/03/20 15:29:08, 0] lib/util.c:smb_panic(1400)                                           
  PANIC: internal error                                                                       
[2004/03/20 15:29:08, 0] lib/util.c:smb_panic(1408)                                           
  BACKTRACE: 1 stack frames:                                                                  
   #0 /usr/sbin/winbindd(smb_panic+0xff) [0x80c27df]   

-- 
Mike