Re: Placa de red
2009/8/26 andres descalzo <adescalz.debian@ymail.com>:
> El 26/08/2009 20:57, Felix Perez escribió:
>>
>> 2009/8/26 andres descalzo<adescalz.debian@ymail.com>:
>>
>>>
>>> El 25/08/2009 23:35, Victor Padro escribió:
>>>
>>>>
>>>> 2009/8/25 andres descalzo<adescalz.debian@ymail.com>:
>>>>
>>>>
>>>>>
>>>>> El 25/08/2009 23:30, Victor Padro escribió:
>>>>>
>>>>>
>>>>>>
>>>>>> 2009/8/25 andres descalzo<adescalz.debian@ymail.com>:
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>
>>> Se que estos son muchos datos, a veces no los comprendo todos. El
>>> problema
>>> es que el server que queda muerto, lo mas raro que pude encontrar en el
>>> syslog es lo siguiente:
>>>
>>> server = NombreDeMiServidor
>>>
>>> Aug 26 09:22:13 server mc: *** info
>>> Aug 26 09:22:13 server mc: /dev/gpmctl: No such file or directory
>>> Aug 26 09:22:13 server mc: *** info
>>> Aug 26 09:22:13 server mc: /dev/gpmctl: No such file or directory
>>> Aug 26 09:22:13 server mc: *** err
>>> Aug 26 09:22:13 server mc: Oh, oh, it's an error! possibly I die!
>>> Aug 26 09:26:15 server mc: *** info
>>> Aug 26 09:26:15 server mc: /dev/gpmctl: No such file or directory
>>> Aug 26 09:26:15 server mc: *** info
>>> Aug 26 09:26:15 server mc: /dev/gpmctl: No such file or directory
>>> Aug 26 09:26:15 server mc: *** err
>>> Aug 26 09:26:15 server mc: Oh, oh, it's an error! possibly I die!
>>> Aug 26 09:29:56 server init: tty4 main process (4267) killed by TERM
>>> signal
>>> Aug 26 09:29:56 server init: tty5 main process (4268) killed by TERM
>>> signal
>>> Aug 26 09:29:56 server init: tty2 main process (4272) killed by TERM
>>> signal
>>> Aug 26 09:29:56 server init: tty3 main process (4274) killed by TERM
>>> signal
>>> Aug 26 09:29:56 server init: tty6 main process (4275) killed by TERM
>>> signal
>>> Aug 26 09:29:56 server init: tty1 main process (5721) killed by TERM
>>> signal
>>> Aug 26 09:29:56 server console-kit-daemon[4683]: WARNING: Unable to
>>> activate
>>> console: No such device or address
>>> Aug 26 09:30:00 server mysqld[4468]: 090826 9:30:00 [Note]
>>> /usr/sbin/mysqld: Normal shutdown
>>> Aug 26 09:30:00 server mysqld[4468]:
>>> Aug 26 09:30:00 server mysqld[4468]: 090826 9:30:00 [Note] Slave I/O
>>> thread
>>> killed while reading event
>>> Aug 26 09:30:00 server mysqld[4468]: 090826 9:30:00 [Note] Slave I/O
>>> thread
>>> exiting, read up to log 'mysql-bin.1914360', position 300
>>> Aug 26 09:30:00 server mysqld[4468]: 090826 9:30:00 [Note] Error reading
>>> relay log event: slave SQL thread was killed
>>> Aug 26 09:30:00 server mysqld[4468]: 090826 9:30:00 [Note]
>>> /usr/sbin/mysqld: Shutdown complete
>>> Aug 26 09:30:00 server mysqld[4468]:
>>> Aug 26 09:30:00 server mysqld_safe[8751]: ended
>>> Aug 26 09:30:01 server /USR/SBIN/CRON[8785]: (root) CMD ([ -x
>>> /usr/sbin/update-motd ]&& /usr/sbin/update-motd 2>/dev/null)
>>> Aug 26 09:30:02 server exiting on signal 15
>>>
>>> ----------------------
>>>
>>>
>>> Esta es la salida de lspci y lshw:
>>>
>>> root@server:~# lspci
>>> 00:00.0 Host bridge: Intel Corporation 3200/3210 Chipset DRAM Controller
>>> 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
>>> Controller #4 (rev 02)
>>> 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
>>> Controller #5 (rev 02)
>>> 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
>>> Controller #6 (rev 02)
>>> 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI
>>> Controller #2 (rev 02)
>>> 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
>>> Port
>>> 1 (rev 02)
>>> 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
>>> Port
>>> 5 (rev 02)
>>> 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
>>> Controller #1 (rev 02)
>>> 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
>>> Controller #2 (rev 02)
>>> 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
>>> Controller #3 (rev 02)
>>> 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI
>>> Controller #1 (rev 02)
>>> 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
>>> 00:1f.0 ISA bridge: Intel Corporation 82801IR (ICH9R) LPC Interface
>>> Controller (rev 02)
>>> 00:1f.2 RAID bus controller: Intel Corporation 82801 SATA RAID Controller
>>> (rev 02)
>>> 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller
>>> (rev
>>> 02)
>>> 02:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G200e
>>> [Pilot]
>>> ServerEngines (SEP1) (rev 02)
>>> 03:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169
>>> Gigabit Ethernet (rev 10)
>>> 03:02.0 Ethernet controller: Intel Corporation 82541GI Gigabit Ethernet
>>> Controller (rev 05)
>>> root@server:~#
>>>
>>> root@server:~#lshw
>>>
>>> ....
>>> *-pci
>>> description: Host bridge
>>> product: 3200/3210 Chipset DRAM Controller
>>> vendor: Intel Corporation
>>> physical id: 100
>>> bus info: pci@0000:00:00.0
>>> version: 00
>>> width: 32 bits
>>> clock: 33MHz
>>> ...
>>>
>>> *-pci:2
>>> description: PCI bridge
>>> product: 82801 PCI Bridge
>>> vendor: Intel Corporation
>>> physical id: 1e
>>> bus info: pci@0000:00:1e.0
>>> version: 92
>>> width: 32 bits
>>> clock: 33MHz
>>> capabilities: pci bus_master cap_list
>>> *-network:0
>>> description: Ethernet interface
>>> product: RTL-8169 Gigabit Ethernet
>>> vendor: Realtek Semiconductor Co., Ltd.
>>> physical id: 1
>>> bus info: pci@0000:03:01.0
>>> logical name: eth1
>>> version: 10
>>> serial: 00:13:f7:8a:50:19
>>> size: 10MB/s
>>> capacity: 1GB/s
>>> width: 32 bits
>>> clock: 66MHz
>>> capabilities: pm bus_master cap_list ethernet physical tp
>>> mii
>>> 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
>>> configuration: autonegotiation=off broadcast=yes
>>> driver=r8169
>>> driverversion=2.3LK-NAPI duplex=half ip=192.168.10.152 latency=64
>>> link=yes
>>> max$
>>> *-network:1 DISABLED
>>> description: Ethernet interface
>>> product: 82541GI Gigabit Ethernet Controller
>>> vendor: Intel Corporation
>>> physical id: 2
>>> bus info: pci@0000:03:02.0
>>> logical name: eth0
>>> version: 05
>>> serial: 00:15:17:9c:c7:65
>>> capacity: 1GB/s
>>> width: 32 bits
>>> clock: 66MHz
>>> capabilities: pm pcix bus_master cap_list ethernet
>>> physical
>>> tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
>>> configuration: autonegotiation=off broadcast=yes
>>> driver=e1000
>>> driverversion=7.3.20-k3-NAPI firmware=N/A latency=32 link=no mingnt=255
>>> module$
>>>
>>> ....
>>>
>>
>> Insisto creo, que tienes un problema con la calidad de la señal de
>> datos lo que hace que se muera la tarjeta de red, incluso podría
>> quemarse la tarjeta de red y/o puertos de comunicaciones.
>>
>> Descarta eso primero.
>>
>>
>>
>
> Felix, si, yo tambien pienso lo mismo, pero de la parte técnica me dicen que
> tiene esta conectado a un hub que alimenta a otros servidores también, y que
> al haber pasado ya dos veces sobre este server , tendría que ser un problema
> del mismo server, pero no se como detectarlo.
>
> Desde ya gracias.
Eso no indica nada, solo indica que los otros equipos aún no han
tenido fallas, debes verificar entre el punto conectado al server y la
conección al hub. Si tienes una contraparte técnica deben responderte
con fundamentos técnicos. Con mayor razón si el problema lo han
tenido dos veces sobre el mismo server.
Ese mismo problema lo tuve con un equipo que funcionaba con
terminales tontos y habitualmente se quemaba una tarjeta serial del
server y era especificamente un terminal y el cable de datos que
llegaba a este, solucionamos el problema electrico y no falló nunca
más.
Otra cosa que puedes hacer es poner un hub pequeño entra el el punto
de conexión y el servidor y en este caso el hub te serviria como una
especie de filtro. Si se quema el hub ya sabes a quien echarle la
culpa.
Por ahora no se me ocurre más.
Suerte.
--
usuario linux #274354
normas de la lista: http://wiki.debian.org/NormasLista
Reply to: