Banda Ancha EU

Comunidad de usuarios
de fibra, móvil y ADSL

hosting en interdominios
47 lecturas y 0 respuestas
  • Cerrado

    [Editado 2/04/06 16:04]

    Analisis sobre los cuelgues del comrend 536+

    Tengo el comtrend desde hace más de un año y hasta la fecha me había ido bien.

    Sin embargo sin aparente motivo hace un par de meses tuvo varios cuelgues. Digo sin aparente motivo porque no hubo ningún cambio ni en el software ni en las condiciones de operación. Tras los cuelgues decidí abrirle unas vias de ventilación y eso parece que resolvió el problema hasta ayer. En las ultimas 24 horas se ha colgado varias veces.

    Para ver lo que le sucede al router instalé un demonio de syslog en un equipo de la LAN y lo deje corriendo por si se reproducían los cuelgues. Ese mismo equipo corre emule las 24 horas. Ahora mismo hay un mes entero de logs del router en el syslog, hasta hoy no figuraba ningun error en el log.

    Esto es lo que ha sucedido esta noche:

    Emule pierde la conexión a las 4:01:08, los posteriores reintentos no funcionan, parece que se ha caido el link.

    02/04/2006 3:25:51: El nuevo [ID]entificador de Cliente es 1685851966
    02/04/2006 3:25:52: Recibidos 2 nuevos servidores
    02/04/2006 4:01:08: Conexión perdida con DonkeyServer No1 (62.241.53.2:4242)
    02/04/2006 4:01:08: Conectando a DonkeyServer No1 (62.241.53.2:4242)...
    02/04/2006 4:01:29: DonkeyServer No1 (62.241.53.2:4242) parece caído
    02/04/2006 4:01:29: Conectando a DonkeyServer No2 (62.241.53.16:4242)...
    02/04/2006 4:01:50: DonkeyServer No2 (62.241.53.16:4242) parece caído
    02/04/2006 4:01:50: Conectando a Byte Devils (64.34.165.203:5306)...
    02/04/2006 4:02:11: Error fatal al intentar la conexión. La conexión a Internet podría estar desactivada

    Este es el log del router a esa misma hora.

    2006-04-02 03:33:00 User.Alert 192.168.1.1 kernel: Intrusion -> IN=ppp_8_35_1 OUT= MAC= SRC=62.14.50.33 DST=62.15.124.100 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=59194 DF PROTO=TCP SPT=4040 DPT=445 WINDOW=65535 RES=0x00 SYN URGP=0
    2006-04-02 03:37:41 User.Alert 192.168.1.1 kernel: Intrusion -> IN=ppp_8_35_1 OUT= MAC= SRC=62.14.198.214 DST=62.15.124.100 LEN=48 TOS=0x00 PREC=0x00 TTL=124 ID=3094 PROTO=TCP SPT=17609 DPT=445 WINDOW=64240 RES=0x00 SYN URGP=0
    2006-04-02 03:49:01 User.Alert 192.168.1.1 kernel: Intrusion -> IN=ppp_8_35_1 OUT= MAC= SRC=62.15.119.111 DST=62.15.124.100 LEN=48 TOS=0x00 PREC=0x00 TTL=124 ID=6261 PROTO=TCP SPT=6244 DPT=139 WINDOW=64240 RES=0x00 SYN URGP=0
    2006-04-02 03:57:02 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 03:57:02 User.Warning 192.168.1.1 kernel: Call Trace: [] [] [] [] [] [] []
    2006-04-02 04:01:52 Syslog.Emerg 192.168.1.1 BCM96345 started: BusyBox v1.00 (2005.09.27-01:38+0000)
    2006-04-02 04:01:52 User.Debug 192.168.1.1 syslog: klogd &

    A las 4:01 hay un reinicio automatico del router, despues de un error de kernel. A las 4:02 ha conectado:

    2006-04-02 04:02:32 Daemon.Critical 192.168.1.1 pppd[407]: Received valid IP address from server. Connection UP.
    2006-04-02 04:02:32 User.Debug 192.168.1.1 syslog: route add default gw 212.106.217.204 2>/dev/null

    Y el emule también:

    02/04/2006 4:02:42: Conexión establecida con: DonkeyServer No1
    02/04/2006 4:02:42: El nuevo [ID]entificador de Cliente es 1685851966

    A las 4:31 emule vuelve a perder la conexión.

    02/04/2006 4:31:27: Conexión perdida con DonkeyServer No1 (62.241.53.2:4242)
    02/04/2006 4:31:27: Conectando a DonkeyServer No1 (62.241.53.2:4242)...
    02/04/2006 4:31:48: DonkeyServer No1 (62.241.53.2:4242) parece caído

    Efectivamente se ve que el router tiene problemas con la conexión. Por lo que veo, da la sensación de que ha perdido el link:

    2006-04-02 04:31:17 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 04:31:17 User.Warning 192.168.1.1 kernel: Call Trace: [] [] [] [] [] [] []
    2006-04-02 04:31:17 User.Critical 192.168.1.1 kernel: ADSL link down
    2006-04-02 04:31:17 User.Warning 192.168.1.1 kernel: Saving OEM data from 0xA0FF74C4
    2006-04-02 04:31:17 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 04:31:17 User.Warning 192.168.1.1 kernel: Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []
    2006-04-02 04:31:17 User.Warning 192.168.1.1 kernel: AdslCoreHwReset: AdslOemDataAddr = 0xA0FF74C4
    2006-04-02 04:31:17 User.Warning 192.168.1.1 kernel: Restoring OEM data from 0xA0FF74C4
    2006-04-02 04:31:17 User.Critical 192.168.1.1 kernel: ADSL link up, interleaved, us=320, ds=1024
    2006-04-02 04:33:20 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 04:33:20 User.Warning 192.168.1.1 kernel: Call Trace: [] [] [] [] [] [] []
    2006-04-02 04:33:20 User.Warning 192.168.1.1 kernel: Saving OEM data from 0xA0FF74C4
    2006-04-02 04:33:20 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 04:33:20 User.Warning 192.168.1.1 kernel: Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []
    2006-04-02 04:33:20 User.Warning 192.168.1.1 kernel: AdslCoreHwReset: AdslOemDataAddr = 0xA0FF74C4
    2006-04-02 04:33:20 User.Warning 192.168.1.1 kernel: Restoring OEM data from 0xA0FF74C4
    2006-04-02 04:33:20 User.Critical 192.168.1.1 kernel: ADSL link down
    2006-04-02 04:33:20 Daemon.Critical 192.168.1.1 pppd[407]: Clear IP addresses. Connection DOWN.
    2006-04-02 04:33:20 Daemon.Critical 192.168.1.1 pppd[407]: Clear IP addresses. PPP connection DOWN.
    2006-04-02 04:36:08 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 04:36:08 User.Warning 192.168.1.1 kernel: Call Trace: [] [] [] [] [] [] []
    2006-04-02 04:36:08 User.Warning 192.168.1.1 dnsprobe[472]: dns query failed
    2006-04-02 04:36:08 User.Warning 192.168.1.1 kernel: Saving OEM data from 0xA0FF74C4
    2006-04-02 04:36:08 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 04:36:08 User.Warning 192.168.1.1 kernel: Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []
    2006-04-02 04:36:08 User.Warning 192.168.1.1 kernel: AdslCoreHwReset: AdslOemDataAddr = 0xA0FF74C4
    2006-04-02 04:36:08 User.Warning 192.168.1.1 kernel: Restoring OEM data from 0xA0FF74C4
    2006-04-02 04:40:02 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!

    Esto se repite hasta las 7:51 donde hay un nuevo reinicio, tres horas y 20 miuntos despues del error de kernel.

    2006-04-02 07:51:46 Syslog.Emerg 192.168.1.1 BCM96345 started: BusyBox v1.00 (2005.09.27-01:38+0000)
    2006-04-02 07:51:46 User.Debug 192.168.1.1 syslog: klogd &
    2006-04-02 07:51:46 User.Notice 192.168.1.1 kernel: klogd started: BusyBox v1.00 (2005.09.27-01:38+0000)
    2006-04-02 07:51:46 User.Debug 192.168.1.1 syslog: ddnsd /var/ddnsd.cfg /var/ddnsd.cache &
    2006-04-02 07:51:46 User.Debug 192.168.1.1 syslog: sntp -s time.nist.gov -s time.cachenetworks.com -t "Brussels, Copenhagen, Madrid, Paris" &

    Nueva conexión ppp:

    2006-04-02 07:52:29 Daemon.Critical 192.168.1.1 pppd[407]: PPP LCP UP.
    2006-04-02 07:52:29 Daemon.Critical 192.168.1.1 pppd[407]: Received valid IP address from server. Connection UP.
    2006-04-02 07:52:29 User.Debug 192.168.1.1 syslog: route add default gw 212.106.217.204 2>/dev/null

    Y emule conecta:

    02/04/2006 7:52:44: Conexión establecida con: DonkeyServer No1
    02/04/2006 7:52:44: El nuevo [ID]entificador de Cliente es 2306674494
    02/04/2006 7:52:46: Recibidos 1 nuevos servidores

    A las 8:24 emule vuelve a perder la conexión:

    02/04/2006 8:24:29: Conexión perdida con DonkeyServer No1 (62.241.53.2:4242)
    02/04/2006 8:24:30: Conectando a DonkeyServer No1 (62.241.53.2:4242)...
    02/04/2006 8:24:51: DonkeyServer No1 (62.241.53.2:4242) parece caído

    El motivo es exactamente el mismo que el anterior. Un problema con el link de ADSL.

    2006-04-02 08:24:49 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 08:24:49 User.Warning 192.168.1.1 kernel: Call Trace: [] [] [] [] [] [] []
    2006-04-02 08:24:49 User.Critical 192.168.1.1 kernel: ADSL link down
    2006-04-02 08:24:49 User.Warning 192.168.1.1 kernel: Saving OEM data from 0xA0FF74C4
    2006-04-02 08:24:49 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 08:24:49 User.Warning 192.168.1.1 kernel: Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []
    2006-04-02 08:24:49 User.Warning 192.168.1.1 kernel: AdslCoreHwReset: AdslOemDataAddr = 0xA0FF74C4
    2006-04-02 08:24:49 User.Warning 192.168.1.1 kernel: Restoring OEM data from 0xA0FF74C4
    2006-04-02 08:24:49 User.Critical 192.168.1.1 kernel: ADSL link up, interleaved, us=320, ds=1024
    2006-04-02 08:26:46 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 08:26:46 User.Warning 192.168.1.1 kernel: Call Trace: [] [] [] [] [] [] []
    2006-04-02 08:26:46 User.Warning 192.168.1.1 kernel: Saving OEM data from 0xA0FF74C4
    2006-04-02 08:26:46 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 08:26:46 User.Warning 192.168.1.1 kernel: Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []
    2006-04-02 08:26:46 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 08:26:46 User.Warning 192.168.1.1 kernel: Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []
    2006-04-02 08:26:46 Daemon.Critical 192.168.1.1 pppd[407]: Clear IP addresses. Connection DOWN.
    2006-04-02 08:26:46 Daemon.Critical 192.168.1.1 pppd[407]: Clear IP addresses. PPP connection DOWN.
    2006-04-02 08:26:46 User.Warning 192.168.1.1 kernel: AdslCoreHwReset: AdslOemDataAddr = 0xA0FF74C4
    2006-04-02 08:26:46 User.Warning 192.168.1.1 kernel: Restoring OEM data from 0xA0FF74C4
    2006-04-02 08:26:46 User.Critical 192.168.1.1 kernel: ADSL link down
    2006-04-02 08:29:31 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 08:29:31 User.Warning 192.168.1.1 kernel: Call Trace: [] [] [] [] [] [] []
    2006-04-02 08:29:31 User.Warning 192.168.1.1 kernel: Saving OEM data from 0xA0FF74C4
    2006-04-02 08:29:31 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 08:29:31 User.Warning 192.168.1.1 kernel: [truncated] Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [
    2006-04-02 08:29:31 User.Warning 192.168.1.1 kernel: AdslCoreHwReset: AdslOemDataAddr = 0xA0FF74C4
    2006-04-02 08:29:31 User.Warning 192.168.1.1 kernel: Restoring OEM data from 0xA0FF74C4
    2006-04-02 08:29:31 User.Warning 192.168.1.1 dnsprobe[472]: dns query failed
    2006-04-02 08:33:26 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 08:33:26 User.Warning 192.168.1.1 kernel: Call Trace: [] [] [] [] [] [] []
    2006-04-02 08:33:26 User.Warning 192.168.1.1 kernel: Saving OEM data from 0xA0FF74C4
    2006-04-02 08:33:26 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!

    Hay un punto curioso. El router pierde el link (adsl link down), lo recupera (adsl link up) al siguiente segundo pero dos minutos más tarde lo vuelve a perder y borra las ips. En ese momento entra el en periodo de autismo.

    Ahora son las 10:42, el router tiene encendido el led rojo de error y no contesta al ping ni responde por web, voy a esperar a ver si se reinicia por si mismo.

    Bien, veo que finalmente se ha reiniciado:

    2006-04-02 13:51:57 User.Warning 192.168.1.1 kernel: Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []
    2006-04-02 13:51:57 User.Error 192.168.1.1 kernel: bad: scheduling while atomic!
    2006-04-02 13:51:57 User.Warning 192.168.1.1 kernel: [truncated] Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [
    2006-04-02 13:55:17 Syslog.Emerg 192.168.1.1 BCM96345 started: BusyBox v1.00 (2005.09.27-01:38+0000)
    2006-04-02 13:55:17 User.Debug 192.168.1.1 syslog: klogd &
    2006-04-02 13:55:17 User.Notice 192.168.1.1 kernel: klogd started: BusyBox v1.00 (2005.09.27-01:38+0000)
    2006-04-02 13:55:17 User.Warning 192.168.1.1 kernel: Linux version 2.6.8.1 (jyang@jyang.linux.comtrend.com) (gcc version 3.4.2) #1 Tue Sep 27 09:32:14 CST 2005
    2006-04-02 13:55:17 User.Warning 192.168.1.1 kernel: Total Flash size: 4096K with 67 sectors
    2006-04-02 13:55:17 User.Warning 192.168.1.1 kernel: Scratch pad is not used for this flash part.

    y efectivamente emule vuelve a funcionar:

    02/04/2006 13:56:09: Conectado a DonkeyServer No1 (62.241.53.2:4242), enviando petición de login
    02/04/2006 13:56:10: Precaución DonkeyServer No1 (62.241.53.2:4242) - This server is full.
    02/04/2006 13:56:10: DonkeyServer No1 (62.241.53.2:4242) parece estar lleno
    02/04/2006 13:56:10: Conectando a DonkeyServer No2 (62.241.53.16:4242)...
    02/04/2006 13:56:10: Conectado a DonkeyServer No2 (62.241.53.16:4242), enviando petición de login
    02/04/2006 13:56:10: Conexión establecida con: DonkeyServer No2
    02/04/2006 13:56:11: El nuevo [ID]entificador de Cliente es 1782386494

    Como conclusión, en mi caso el router no se cuelga. Sigue operativo, continúa enviando logs y es capaz de reiniciarse solo. No veo que haya un timeout claro, los periodos entre los errores y los inicios son muy dispares.

    Es muy posible que el problema venga de la conexión ADSL. Puede suceder que una caida del link haga que el router se vuelva inestable. En cualquier caso, esto no debería suceder, el router debería recuperarse de un fallo de ADSL en mucho menos tiempo y sin necesidad de reiniciar.

    Voy a traducir esto a inglis y se lo mando a los de comtrend para que rellenen un poco su papelera de reciclaje ;)

    Estos son los datos importantes del router:

    Software Version: A101-302JAZ-C01_R05.A2pB017l.d15h
    Bootloader (CFE) Version: 1.0.37-5.17
    Wireless Driver Version: 3.91.41.0

    Mode: G.DMT
    Type: Interleave
    Line Coding: Trellis On
    Status: No Defect
    Link Power State: L0

    Downstream Upstream
    SNR Margin (dB): 31.9 28.0
    Attenuation (dB): 20.0 9.0
    Output Power (dBm): 5.8 9.3
    Attainable Rate (Kbps): 7840 1120
    Rate (Kbps): 1024 320
    K (number of bytes in DMT frame): 33 11
    R (number of check bytes in RS code word): 16 16
    S (RS code word size in DMT frame): 4 16
    D (interleaver depth): 16 4
    Delay (msec): 16 16

    Super Frames: 115504 115502
    Super Frame Errors: 0 0
    RS Words: 1963584 490883
    RS Correctable Errors: 0 0
    RS Uncorrectable Errors: 0 N/A

    HEC Errors: 0 0
    OCD Errors: 0 0
    LCD Errors: 0 0
    Total Cells: 4743222 0
    Data Cells: 222720 0
    Bit Errors: 0 0

    Total ES: 0 0
    Total SES: 0 0
    Total UAS: 16 0

    Un ultimo apunte. Esto de aqui es una perdida de conexión producida cuando quitas el cable de ADSL:

    2006-04-02 15:56:47 User.Critical 192.168.1.1 kernel: ADSL link down
    2006-04-02 15:56:49 Daemon.Critical 192.168.1.1 pppd[407]: Clear IP addresses. Connection DOWN.
    2006-04-02 15:56:49 Daemon.Critical 192.168.1.1 pppd[407]: Clear IP addresses. PPP connection DOWN.
    2006-04-02 15:56:59 User.Warning 192.168.1.1 dnsprobe[472]: dns query failed
    2006-04-02 15:57:01 User.Warning 192.168.1.1 dnsprobe[472]: dns query failed
    2006-04-02 15:57:03 User.Warning 192.168.1.1 dnsprobe[472]: dns query failed
    2006-04-02 15:57:03 User.Notice 192.168.1.1 dnsprobe[472]: Primary DNS server Is Down... Switching To Secondary DNS server
    2006-04-02 15:57:26 User.Critical 192.168.1.1 kernel: ADSL G.994 training
    2006-04-02 15:57:35 User.Warning 192.168.1.1 dnsprobe[472]: dns query failed
    2006-04-02 15:57:37 User.Warning 192.168.1.1 dnsprobe[472]: dns query failed
    2006-04-02 15:57:39 User.Warning 192.168.1.1 dnsprobe[472]: dns query failed
    2006-04-02 15:57:51 User.Critical 192.168.1.1 kernel: ADSL G.992 channel analysis
    2006-04-02 15:57:56 User.Critical 192.168.1.1 kernel: ADSL link up, interleaved, us=320, ds=1024

    No aparece el "kernel: bad: scheduling while atomic!" de las perdidas de conexion que lo cuelgan.

    Este tema es antiguo y puede contener información obsoleta. Abre un nuevo tema para publicar tu mensaje.
    1