Strange Reboot?

Discussion in 'Tomato Firmware' started by udippel, Jan 27, 2009.

  1. udippel

    udippel Addicted to LI Member

    I found my Tomato having rebooted; but there had been no power outage or so.
    It wouldn't bug me, were there not some strange things:

    Log says:
    Jan 1 08:00:36 router dnsmasq[140]: using nameserver
    Jan 1 08:00:36 router dnsmasq[140]: read /etc/hosts - 0 addresses
    Jan 1 08:00:36 router dnsmasq[140]: read /etc/hosts.dnsmasq - 4 addresses
    Jan 27 16:12:03 router ntpc[204]: Time Updated: Tue, 27 Jan 2009 16:12:03 +0800 [+1233043882s]
    Jan 27 16:12:23 router cron.err crond[104]: time disparity of 20550732 minutes detected
    Jan 27 16:12:27 router dnsmasq[140]: DHCPREQUEST(br0) 00:21:5d:4b:76:88
    Jan 27 16:12:27 router dnsmasq[140]: DHCPACK(br0)
    Jan 27 17:00:01 router root: -- MARK --
    Jan 27 17:38:04 router ntpc[2989]: Time Updated: Tue, 27 Jan 2009 17:38:04 +0800 [+3s]
    Jan 27 18:00:02 router root: -- MARK --
    Jan 27 19:00:01 router root: -- MARK --
    Where are the hourly marks of in between Jan 1 and Jan 27? It says it rebooted around that time (Jan 27 16:12:03) and received a new DDNS at Tue Jan 27 16:12:09 2009.

    The Device list contains a device that had not connected over the last 24 hours, 00:11:f5:22:24:40, as far as I know. It connected last several weeks ago.

    Could someone with more insight please explain what was going on?

  2. Mastec

    Mastec Network Guru Member

    I may be wrong on this but I think thats normal, the router just hasn't received the correct date from the NTP server after reboot. When my routers reboot they show Dec. 31 then the current date as soon as everything is loaded.

    Someone correct me if I am wrong, I like to learn as well.
  3. Low-WRT

    Low-WRT LI Guru Member

    You're right. It just takes several seconds/minutes to update the time.

    udippel, if you're using internal logging, you will lose all logging after a reboot...don't know why that mac connected, unless it really did connect...hopefully it's yours:biggrin:
  4. fyellin

    fyellin LI Guru Member


    Might I guess that you're GMT+8 (China, Taiwan, Singapore, . . .) or at least that you've got your router set to GMT+8? Those first three items are "Jan 1, 1970 00:00GMT". time zero in Unix-land.
  5. udippel

    udippel Addicted to LI Member

    Yes, true. Ah, I never thought it was Unix time and the router started on 1 Jan 1970! The 'beauty' of a cheap box, I guess, that it doesn't have a battery and a real-time chip.

    Now I still wonder why it would have received that strange DHCP-request, 19 seconds after it rebooted. It is a suburban area, and there are not more than a few houses around.

    Lastly, how could I find out (as well for the future), why it crashed at all, after more than 20 days of update. Or does it reboot regularly on its own? There is nothing under scheduler.


  6. fyellin

    fyellin LI Guru Member

    The device that is asking for a DHCP address is certainly one that has seen your network before. Your subnet, 192.168.116.* is somewhat unusual, and yet this device is directly asking for an IP address that it already knows about. A random device seeing your network for the first time would have the device doing a DHCPDISCOVER and the router responding with a DHCPOFFER.

    Why did it reboot? Who knows. There isn't really any good way of finding out, since Tomato wipes out its memory and file system when it reboots. If this only happens once, then maybe you had a brief power failure. If it continues, you can get Tomato to write its logs to a remote system.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice