1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

dnsmasq appears topero be crashing and restarting Tomato pr

Discussion in 'Tomato Firmware' started by kallsop, Jan 27, 2010.

  1. kallsop

    kallsop Addicted to LI Member

    Here is the 1.27 log.

    Code:
    Jan 26 22:19:43 tomato daemon.info dnsmasq[6625]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP no-scripts no-TFTP
    Jan 26 22:19:43 tomato daemon.info dnsmasq-dhcp[6625]: DHCP, IP range 192.168.0.100 -- 192.168.0.149, lease time 1d
    Jan 26 22:19:43 tomato daemon.info dnsmasq[6625]: reading /etc/resolv.dnsmasq
    Jan 26 22:19:43 tomato daemon.info dnsmasq[6625]: using nameserver 208.67.220.220#53
    Jan 26 22:19:43 tomato daemon.info dnsmasq[6625]: using nameserver 208.67.222.222#53
    Jan 26 22:19:43 tomato daemon.info dnsmasq[6625]: read /etc/hosts - 0 addresses
    Jan 26 22:19:43 tomato daemon.info dnsmasq[6625]: read /etc/hosts.dnsmasq - 14 addresses
    Jan 26 22:22:24 tomato daemon.info dnsmasq-dhcp[6625]: DHCPREQUEST(br0) 192.168.0.109 00:1d:92:00:00:00 
    Jan 26 22:22:24 tomato daemon.info dnsmasq-dhcp[6625]: DHCPACK(br0) 192.168.0.109 00:1d:92:00:00:00 atom
    Jan 26 22:24:04 tomato daemon.info dnsmasq-dhcp[6625]: DHCPINFORM(br0) 192.168.0.105 00:22:fa:00:00:00 
    Jan 26 22:24:04 tomato daemon.info dnsmasq-dhcp[6625]: DHCPACK(br0) 192.168.0.105 00:22:fa:00:00:00 Acer
    Jan 26 22:29:45 tomato daemon.info dnsmasq[6625]: exiting on receipt of SIGTERM
    Jan 26 22:29:45 tomato daemon.info dnsmasq[6969]: started, version 2.51 cachesize 150
    Jan 26 22:29:45 tomato daemon.info dnsmasq[6969]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP no-scripts no-TFTP
    Jan 26 22:29:45 tomato daemon.info dnsmasq-dhcp[6969]: DHCP, IP range 192.168.0.100 -- 192.168.0.149, lease time 1d
    Jan 26 22:29:45 tomato daemon.info dnsmasq[6969]: reading /etc/resolv.dnsmasq
    Jan 26 22:29:45 tomato daemon.info dnsmasq[6969]: using nameserver 208.67.220.220#53
    Jan 26 22:29:45 tomato daemon.info dnsmasq[6969]: using nameserver 208.67.222.222#53
    Jan 26 22:29:45 tomato daemon.info dnsmasq[6969]: read /etc/hosts - 0 addresses
    Jan 26 22:29:45 tomato daemon.info dnsmasq[6969]: read /etc/hosts.dnsmasq - 14 addresses
    Jan 26 22:39:49 tomato daemon.info dnsmasq[6969]: exiting on receipt of SIGTERM
    Jan 26 22:39:49 tomato daemon.info dnsmasq[7348]: started, version 2.51 cachesize 150
    Jan 26 22:39:49 tomato daemon.info dnsmasq[7348]: compile time options: no-IPv6 GNU-getopt no-RTC no-DBus no-I18N DHCP no-scripts no-TFTP
    Jan 26 22:39:49 tomato daemon.info dnsmasq-dhcp[7348]: DHCP, IP range 192.168.0.100 -- 192.168.0.149, lease time 1d
    Jan 26 22:39:49 tomato daemon.info dnsmasq[7348]: reading /etc/resolv.dnsmasq
    Jan 26 22:39:49 tomato daemon.info dnsmasq[7348]: using nameserver 208.67.220.220#53
    Jan 26 22:39:49 tomato daemon.info dnsmasq[7348]: using nameserver 208.67.222.222#53
    Jan 26 22:39:49 tomato daemon.info dnsmasq[7348]: read /etc/hosts - 0 addresses
    Jan 26 22:39:49 tomato daemon.info dnsmasq[7348]: read /etc/hosts.dnsmasq - 14 addresses
    
    dnsmasq appears to be crashing and restarting. Ideas? QoS is disabled. The router is configured to use OpenDNS.
     
  2. Toastman

    Toastman Super Moderator Staff Member Member

    Usually when the router runs out of memory it starts to shut down processes. DNSmasq is one of the first to go. You should look for something that is causing large numbers of connections, or anything else that might cause the router to use up memory. Usual cause is a connection storm caused by P2P/Bit Torrent DNA/DHT etc. or even a trojan on one of your PC's trying to phone home, a mail bomb virus sending thousands of emails etc. This can happen so quickly that there is no trace in the logs and you have to be lucky to actually see it happen.
     
  3. kallsop

    kallsop Addicted to LI Member


    If you are replying to my router reboots, thanks. Since flashing to 1.28 beta, it hasn't crashed once and that was about 8 days ago. The usage of networked PC's hasn't changed, so whatever the problem was, it likely wasn't due to network traffic.
     
  4. Toastman

    Toastman Super Moderator Staff Member Member

    That's very interesting and useful - thanks!
     

Share This Page