[CentOS-pt-br] Compartilhamento morrendo :(

Wilson Paolini wilson.paolini em gmail.com
Terça Julho 17 16:46:46 EDT 2012


Cara, o meu syslog ta assim:

Jul 17 09:56:21 wilson-pc dhclient: DHCPREQUEST of 172.22.13.30 on eth0 to
172.22.13.222 port 67
Jul 17 09:56:21 wilson-pc dhclient: DHCPACK of 172.22.13.30 from
172.22.13.222
Jul 17 09:56:21 wilson-pc dhclient: bound to 172.22.13.30 -- renewal in
3374 seconds.

A última linha não tem no seu syslog, parece que não ta fixando ip. Tenta
colocar ip fixo para testar, ai já da para saber se é problema de dhcp.

2012/7/17 Nilson Pena <nilson em radiologia.odo.br>

> Caiu agora por volta das 16:50
>
> Segue o var/log/messages da hora aproximada:
> e dmesg depois
>
> Jul 17 16:41:57 tubarao dhcpd: DHCPACK on 192.168.50.100 to
> 2c:27:d7:14:5a:34 via eth1
> Jul 17 16:42:16 tubarao dhclient[4018]: DHCPREQUEST on eth1 to
> 255.255.255.255 port 67 (xid=0x638c93ae)
> Jul 17 16:42:16 tubarao dhcpd: DHCPREQUEST for 192.168.50.100 from
> 2c:27:d7:14:5a:34 via eth1
> Jul 17 16:42:16 tubarao dhcpd: DHCPACK on 192.168.50.100 to
> 2c:27:d7:14:5a:34 via eth1
> Jul 17 16:42:28 tubarao dhclient[4018]: DHCPREQUEST on eth1 to
> 255.255.255.255 port 67 (xid=0x638c93ae)
> Jul 17 16:42:28 tubarao dhcpd: DHCPREQUEST for 192.168.50.100 from
> 2c:27:d7:14:5a:34 via eth1
> Jul 17 16:42:28 tubarao dhcpd: DHCPACK on 192.168.50.100 to
> 2c:27:d7:14:5a:34 via eth1
> Jul 17 16:42:48 tubarao dhclient[4018]: DHCPREQUEST on eth1 to
> 255.255.255.255 port 67 (xid=0x638c93ae)
> Jul 17 16:42:48 tubarao dhcpd: DHCPREQUEST for 192.168.50.100 from
> 2c:27:d7:14:5a:34 via eth1
> Jul 17 16:42:48 tubarao dhcpd: DHCPACK on 192.168.50.100 to
> 2c:27:d7:14:5a:34 via eth1
> Jul 17 16:42:50 tubarao NET[2501]: /sbin/dhclient-script : updated
> /etc/resolv.conf
> Jul 17 16:42:50 tubarao dhclient[4018]: DHCPDISCOVER on eth1 to
> 255.255.255.255 port 67 interval 7 (xid=0x168516f6)
> Jul 17 16:42:50 tubarao dhcpd: DHCPDISCOVER from 2c:27:d7:14:5a:34 via eth1
> Jul 17 16:42:50 tubarao dhcpd: DHCPOFFER on 192.168.50.100 to
> 2c:27:d7:14:5a:34 via eth1
> Jul 17 16:42:50 tubarao dhclient[4018]: DHCPOFFER from 192.168.50.100
> Jul 17 16:42:50 tubarao dhclient[4018]: DHCPREQUEST on eth1 to
> 255.255.255.255 port 67 (xid=0x168516f6)
> Jul 17 16:42:50 tubarao dhcpd: DHCPREQUEST for 192.168.50.100
> (192.168.50.100) from 2c:27:d7:14:5a:34 via eth1
> Jul 17 16:42:50 tubarao dhcpd: DHCPACK on 192.168.50.100 to
> 2c:27:d7:14:5a:34 via eth1
> Jul 17 16:42:50 tubarao dhclient[4018]: DHCPACK from 192.168.50.100
> (xid=0x168516f6)
> Jul 17 16:42:51 tubarao ntpd[1697]: Deleting interface #39 eth1,
> 192.168.50.1#123, interface stats: received=0, sent=0, dropped=0,
> active_time=16542 secs
> Jul 17 16:42:52 tubarao NET[2547]: /sbin/dhclient-script : updated
> /etc/resolv.conf
> Jul 17 16:42:52 tubarao dhclient[4018]: bound to 192.168.50.100 -- renewal
> in 9132 seconds.
> Jul 17 16:42:53 tubarao ntpd[1697]: Listening on interface #41 eth1,
> 192.168.50.100#123 Enabled
> Jul 17 16:44:23 tubarao dhcpd: DHCPINFORM from 192.168.50.11 via eth1: not
> authoritative for subnet 192.168.50.0
> Jul 17 16:44:26 tubarao dhcpd: DHCPINFORM from 192.168.50.11 via eth1: not
> authoritative for subnet 192.168.50.0
> Jul 17 16:51:09 tubarao dhcpd: DHCPINFORM from 192.168.50.11 via eth1: not
> authoritative for subnet 192.168.50.0
> Jul 17 16:51:12 tubarao dhcpd: DHCPINFORM from 192.168.50.11 via eth1: not
> authoritative for subnet 192.168.50.0
> Jul 17 17:07:18 tubarao smbd[2322]: [2012/07/17 17:07:18.513933,  0]
> lib/util_sock.c:474(read_fd_with_timeout)
> Jul 17 17:07:18 tubarao smbd[2322]: [2012/07/17 17:07:18.514220,  0]
> lib/util_sock.c:1441(get_peer_addr_internal)
> Jul 17 17:07:18 tubarao smbd[2322]:   getpeername failed. Error was Ponto
> final de transporte não está conectado
> Jul 17 17:07:18 tubarao smbd[2322]:   read_fd_with_timeout: client 0.0.0.0
> read error = Tempo esgotado para conexão.
>
>
> Finalzinho do DMESG
>
> nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
> ip_tables: (C) 2000-2006 Netfilter Core Team
> nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
> usb 4-2: USB disconnect, address 4
> usb 4-2: new low speed USB device using ohci_hcd and address 5
> usb 4-2: New USB device found, idVendor=1c4f, idProduct=0003
> usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> usb 4-2: Product: Usb Mouse
> usb 4-2: Manufacturer: SIGMACHIP
> usb 4-2: configuration #1 chosen from 1 choice
> input: SIGMACHIP Usb Mouse as
> /devices/pci0000:00/0000:00:12.0/usb4/4-2/4-2:1.0/input/input6
> generic-usb 0003:1C4F:0003.0004: input,hidraw0: USB HID v1.10 Mouse
> [SIGMACHIP Usb Mouse] on usb-0000:00:12.0-2/input0
> ip_tables: (C) 2000-2006 Netfilter Core Team
> nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
> lo: Disabled Privacy Extensions
> tg3 0000:03:00.0: irq 30 for MSI/MSI-X
> ADDRCONF(NETDEV_UP): eth0: link is not ready
> tg3 0000:03:00.0: eth0: Link is up at 100 Mbps, full duplex
> tg3 0000:03:00.0: eth0: Flow control is on for TX and on for RX
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> ADDRCONF(NETDEV_UP): eth1: link is not ready
> e1000e: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
> e1000e 0000:02:00.0: eth1: 10/100 speed: disabling TSO
> ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
> eth0: no IPv6 routers present
> eth1: no IPv6 routers present
> lo: Disabled Privacy Extensions
> tg3 0000:03:00.0: irq 30 for MSI/MSI-X
> ADDRCONF(NETDEV_UP): eth0: link is not ready
> tg3 0000:03:00.0: eth0: Link is up at 100 Mbps, full duplex
> tg3 0000:03:00.0: eth0: Flow control is on for TX and on for RX
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> ADDRCONF(NETDEV_UP): eth1: link is not ready
> e1000e: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
> e1000e 0000:02:00.0: eth1: 10/100 speed: disabling TSO
> ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
> eth0: no IPv6 routers present
> eth1: no IPv6 routers present
> lo: Disabled Privacy Extensions
> tg3 0000:03:00.0: irq 30 for MSI/MSI-X
> ADDRCONF(NETDEV_UP): eth0: link is not ready
> tg3 0000:03:00.0: eth0: Link is up at 100 Mbps, full duplex
> tg3 0000:03:00.0: eth0: Flow control is on for TX and on for RX
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> ADDRCONF(NETDEV_UP): eth1: link is not ready
> e1000e: eth1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
> e1000e 0000:02:00.0: eth1: 10/100 speed: disabling TSO
> ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
> eth0: no IPv6 routers present
> eth1: no IPv6 routers present
>
>
>
>
>
>
>
> 2012/7/17 Thiago Coutinho <root em thiagoc.net>
>
>> 2012/7/17 Nilson Pena <nilson em radiologia.odo.br>:
>> > Estou com um servidor CENTOS que do nada a rede cai.
>> > Se eu der um service network restart, tudo volta ao normal por um
>> tempo, mas
>> > depois cai de novo.
>> > Alguma ideia do que seja? Algum arquivo de log que me indique o que
>> possa
>> > estar acontecendo?
>>
>> Verifique o comando dmesg e o arquivo /var/log/messages.
>>
>> --
>> thiagoc
>>
>> "O povo não deveria temer o governo. O governo é quem deveria temer o
>> povo."
>> V de Vingança
>> _______________________________________________
>> CentOS-pt-br mailing list
>> CentOS-pt-br em centos.org
>> http://lists.centos.org/mailman/listinfo/centos-pt-br
>>
>
>
> _______________________________________________
> CentOS-pt-br mailing list
> CentOS-pt-br em centos.org
> http://lists.centos.org/mailman/listinfo/centos-pt-br
>
>
-------------- Próxima Parte ----------
Um anexo em HTML foi limpo...
URL: http://lists.centos.org/pipermail/centos-pt-br/attachments/20120717/32ae4112/attachment.html 


Mais detalhes sobre a lista de discussão CentOS-pt-br