Ol�, bom dia a todos! Isso mesmo gente, j� � a segunda vez na semana!
Meu servidor de dados rodando Red Hat 8.0 com o Samba 2.2.8a, PostgreSQL, Sshd e Postfix TRAVOU completamente hoje! O expediente aqui acaba as 17:30, hoje cheguei no trampo e n�o consegui me logar no mesmo, liguei o monitor e o rel�gio apontava 17:14 (do dia anterior)! N�o respondia ping, teclado n�o funcionava, ssh nem pensar... segunda vez j�!!! ========================= As mensagens do 'messages' pouco antes do travamento: Aug 14 15:21:08 MAQ_100 smbd[23261]: [2003/08/14 15:21:08, 0] smbd/oplock.c:oplock_break(869) Aug 14 15:21:08 MAQ_100 smbd[23261]: oplock_break: client failure in oplock break in file GPS/GPS01010.TEL Aug 14 15:22:22 MAQ_100 smbd[24251]: [2003/08/14 15:22:22, 0] lib/util_sock.c:read_data(436) Aug 14 15:22:22 MAQ_100 smbd[24251]: read_data: read failure for 4. Error = Connection reset by peer Aug 14 15:22:36 MAQ_100 smbd[23261]: [2003/08/14 15:22:36, 0] lib/util_sock.c:read_data(436) Aug 14 15:22:36 MAQ_100 smbd[23261]: read_data: read failure for 4. Error = Connection reset by peer Aug 14 15:24:57 MAQ_100 smbd[24083]: [2003/08/14 15:24:57, 0] lib/util_sock.c:read_data(436) Aug 14 15:24:57 MAQ_100 smbd[24083]: read_data: read failure for 4. Error = Connection reset by peer Aug 14 15:32:12 MAQ_100 smbd[24637]: [2003/08/14 15:32:12, 0] lib/util_sock.c:read_data(436) Aug 14 15:32:12 MAQ_100 smbd[24637]: read_data: read failure for 4. Error = Connection reset by peer Aug 14 15:33:58 MAQ_100 smbd[19718]: [2003/08/14 15:33:58, 0] lib/util_sock.c:read_data(436) Aug 14 15:33:58 MAQ_100 smbd[19718]: read_data: read failure for 4. Error = Connection reset by peer Aug 14 15:38:49 MAQ_100 smbd[24400]: [2003/08/14 15:38:49, 0] lib/util_sock.c:read_data(436) Aug 14 15:38:49 MAQ_100 smbd[24400]: read_data: read failure for 4. Error = Connection reset by peer Aug 14 15:45:51 MAQ_100 smbd[24178]: [2003/08/14 15:45:51, 0] lib/util_sock.c:read_data(436) Aug 14 15:45:51 MAQ_100 smbd[24178]: read_data: read failure for 4. Error = No route to host Aug 14 15:55:31 MAQ_100 smbd[24876]: [2003/08/14 15:55:31, 0] lib/util_sock.c:read_socket_with_timeout(300) Aug 14 15:55:31 MAQ_100 smbd[24876]: read_socket_with_timeout: timeout read. read error = Connection reset by peer. Aug 14 15:55:31 MAQ_100 smbd[24876]: [2003/08/14 15:55:31, 0] smbd/oplock.c:oplock_break(794) Aug 14 15:55:31 MAQ_100 smbd[24876]: oplock_break: receive_smb error (Connection reset by peer) Aug 14 15:55:31 MAQ_100 smbd[24876]: oplock_break failed for file PROSOFT.CNF/00340CTB.LIB (dev = 804, inode = 3703818, file_id = 388). Aug 14 15:55:31 MAQ_100 smbd[24876]: [2003/08/14 15:55:31, 0] smbd/oplock.c:oplock_break(879) Aug 14 15:55:31 MAQ_100 smbd[24876]: oplock_break: client failure in break - shutting down this smbd. Aug 14 15:56:03 MAQ_100 smbd[25024]: [2003/08/14 15:56:03, 0] smbd/oplock.c:request_oplock_break(1011) Aug 14 15:56:04 MAQ_100 smbd[25024]: request_oplock_break: no response received to oplock break request to pid 24876 on port 33346 for dev = 804, inode = 3703818, file_id = 388 Aug 14 16:11:41 MAQ_100 smbd[21472]: [2003/08/14 16:11:41, 0] lib/util_sock.c:read_data(436) Aug 14 16:11:42 MAQ_100 smbd[21472]: read_data: read failure for 4. Error = Connection reset by peer Aug 14 16:39:32 MAQ_100 smbd[25301]: [2003/08/14 16:39:32, 0] lib/util_sock.c:read_data(436) Aug 14 16:39:32 MAQ_100 smbd[25301]: read_data: read failure for 4. Error = Connection reset by peer Aug 14 16:59:41 MAQ_100 smbd[24722]: [2003/08/14 16:59:40, 0] lib/util_sock.c:read_data(436) Aug 14 16:59:41 MAQ_100 smbd[24722]: read_data: read failure for 4. Error = Connection reset by peer Aug 14 17:09:22 MAQ_100 smbd[25823]: [2003/08/14 17:09:22, 0] lib/util_sock.c:read_data(436) Aug 14 17:09:22 MAQ_100 smbd[25823]: read_data: read failure for 4. Error = Connection reset by peer Aug 15 07:35:24 MAQ_100 syslogd 1.4.1: restart. Ago 15 07:35:24 MAQ_100 syslog: arranque do syslogd succeed ========================= Os log's do PostgreSQl: [...] ERROR: 'ksqo' is not a valid option name ERROR: parser: parse error at or near "0" at character 1 ERROR: 'ksqo' is not a valid option name ERROR: parser: parse error at or near "0" at character 1 LOG: database system was interrupted at 2003-08-14 17:09:21 BRT LOG: checkpoint record is at 0/1B95E4C0 LOG: redo record is at 0/1B95E4C0; undo record is at 0/0; shutdown FALSE LOG: next transaction id: 3907339; next oid: 297594 LOG: database system was not properly shut down; automatic recovery in progress LOG: ReadRecord: record with zero length at 0/1B95E500 LOG: redo is not required LOG: database system is ready ========================= Log's do Samba +- nesse hor�rio (maq_302): [2003/08/13 10:17:52, 0] smbd/oplock.c:request_oplock_break(1011) request_oplock_break: no response received to oplock break request to pid 12489 on port 33150 for dev = 804, inode = 180248, file_id = 348[2003/08/14 08:28:27, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = Connection reset by peer [2003/08/14 09:48:52, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = Connection reset by peer [2003/08/14 14:35:19, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = Connection reset by peer [2003/08/14 15:24:57, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = Connection reset by peer [2003/08/14 15:32:12, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = Connection reset by peer [2003/08/14 16:59:40, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = Connection reset by peer [2003/08/14 17:09:22, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = Connection reset by peer ========================= De outra m�quina, que nem chegou at� esse hor�rio (maq_705): [2003/08/07 08:39:36, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = Connection reset by peer [2003/08/11 11:25:37, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = Connection reset by peer [2003/08/14 16:39:32, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = Connection reset by peer ========================= Gente, por favor... Algu�m sabe de algo que possa estar ocorrendo? Meu servidor � um DELL Power Edge 1600 SC Muito obrigado! Abra�os, Tiago Cruz Org. King de Contab. S/C Ltda. Linux User # 282636 http://www.linuxrapido.linuxdicas.com.br/ Mandrake Linux i18n Team --------------------------------------------------------------------------- Esta lista � patrocinada pela Conectiva S.A. Visite http://www.conectiva.com.br Arquivo: http://bazar2.conectiva.com.br/mailman/listinfo/linux-br Regras de utiliza��o da lista: http://linux-br.conectiva.com.br FAQ: http://www.zago.eti.br/menu.html
