On Wednesday 15 July 2009 23:09:58 Catalin Muresan wrote: > 2009/7/15 Doru IACOB <[email protected]>: > mai repede e invers, pica conexiunea, pica ntp si dupa aia ai mesajul > WATCHDOG: Internal: transmit timed out, asa ca investigheaza de la > conexiune. > Mai e ceva ciudat in log, nu e ordonat dupa timp.
Probabil o ia ceasul razna tocmai pentru ca nu se poate sincroniza si log-eaza ora aiurea. Imi imaginez ca log-urile sunt in ordinea corecta doar ca timestamp-ul e incorect. > > > Jun 30 00:10:55 FW ntpdate[7950]: adjust time server 172.x.x.x offset > > 0.047648 sec > > Jun 30 00:20:59 FW ntpdate[7997]: no server suitable for synchronization > > found > > Jun 30 00:30:59 FW ntpdate[8093]: no server suitable for synchronization > > found > > Jun 30 00:40:59 FW ntpdate[8196]: no server suitable for synchronization > > found > > Jun 30 00:50:59 FW ntpdate[8243]: no server suitable for synchronization > > found > > Jun 30 01:00:59 FW ntpdate[8349]: no server suitable for synchronization > > found > > Jun 30 00:08:23 FW kernel: NETDEV WATCHDOG: Internal: transmit timed out > > Jun 30 00:08:23 FW kernel: sky2 Internal: tx timeout > > Jun 30 00:08:23 FW kernel: sky2 Internal: disabling interface > > Jun 30 00:08:23 FW kernel: sky2 Internal: enabling interface > > Jun 30 00:08:23 FW kernel: sky2 Internal: ram buffer 48K > > Jun 30 00:08:26 FW kernel: sky2 Internal: Link is up at 1000 Mbps, full > > duplex, flow control rx > > Jun 30 01:10:55 FW ntpdate[8429]: adjust time server 172.x.x.x offset > > 0.404657 sec Mihai _______________________________________________ RLUG mailing list [email protected] http://lists.lug.ro/mailman/listinfo/rlug
