On Tue, Jan 10, 2012 at 6:26 PM, Chris Buechler <[email protected]> wrote: >> Okay, I think I found out what's going on: >> >> /etc/crontab contains >> 1 1 * * * root /usr/bin/nice -n20 >> /etc/rc.dyndns.update >> >> which means that the script only gets called at 01:01 AM each day. >> >> Is there any particular reason why this rather long interval was chosen? > > It runs immediately after every IP change, and once a day to check if > it needs to do an update (if one hasn't been done in 25 days (IIRC, > somewhere around that) it'll update). No need for anything else.
Are you sure about this? I have seen DHCP fail for a while, finally succeeding - and dyndns did NOT update. Here's a quick system log for the latest occurrence of the problem (I had rebooted the box a hour earlier to see if that would bring the connection back, so the IP was currently listed as 0.0.0.0 in the UI): May 31 00:19:04 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 3 May 31 00:19:07 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 5 May 31 00:19:12 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 10 May 31 00:19:22 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 12 May 31 00:19:34 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 7 May 31 00:19:41 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 19 May 31 00:20:00 dhclient[33083]: No DHCPOFFERS received. May 31 00:20:00 dhclient[33083]: No working leases in persistent database - sleeping. May 31 00:20:00 dhclient: FAIL May 31 00:20:01 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 2 May 31 00:20:03 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 2 May 31 00:20:05 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 2 May 31 00:20:07 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 5 May 31 00:20:12 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 5 May 31 00:20:17 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 12 May 31 00:20:29 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 15 May 31 00:20:44 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 18 May 31 00:21:02 dhclient[33083]: No DHCPOFFERS received. May 31 00:21:02 dhclient[33083]: No working leases in persistent database - sleeping. May 31 00:21:02 dhclient: FAIL May 31 00:21:03 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 1 May 31 00:21:04 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 1 May 31 00:21:05 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 1 May 31 00:21:06 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 1 May 31 00:21:07 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 1 May 31 00:21:08 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 1 May 31 00:21:09 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 2 May 31 00:21:11 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 4 May 31 00:21:15 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 10 May 31 00:21:25 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 12 May 31 00:21:37 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 15 May 31 00:21:52 dhclient[33083]: DHCPDISCOVER on em1_vlan1001 to 255.255.255.255 port 67 interval 12 May 31 00:21:54 dhclient[33083]: DHCPOFFER from x.x.x.x May 31 00:21:54 dhclient: ARPSEND May 31 00:21:56 dhclient: ARPCHECK May 31 00:21:56 dhclient[33083]: DHCPREQUEST on em1_vlan1001 to 255.255.255.255 port 67 May 31 00:21:56 dhclient[33083]: DHCPACK from x.x.x.x May 31 00:21:56 dhclient: BOUND May 31 00:21:56 dhclient: Starting add_new_address() May 31 00:21:57 dhclient: ifconfig em1_vlan1001 inet y.y.y.y netmask 255.255.255.192 broadcast z.z.z.z May 31 00:21:57 dhclient: New IP Address (em1_vlan1001): y.y.y.y May 31 00:21:57 dhclient: New Subnet Mask (em1_vlan1001): 255.255.255.192 May 31 00:21:57 dhclient: New Broadcast Address (em1_vlan1001): z.z.z.z May 31 00:21:57 dhclient: New Routers (em1_vlan1001): x.x.x.x May 31 00:21:57 dhclient: Adding new routes to interface: em1_vlan1001 May 31 00:21:57 dhclient: /sbin/route add default x.x.x.x May 31 00:21:57 dhclient: Creating resolv.conf May 31 00:21:57 dhclient[33083]: bound to y.y.y.y -- renewal in 1300 seconds. May 31 00:25:33 dnsmasq[41037]: read /etc/hosts - 11 addresses May 31 00:25:33 dnsmasq[41037]: read /etc/hosts - 11 addresses The address it finally got was not the same as was stored in the dyndns cache ... and the dyndns status page showed the IP in red (meaning it was not up to date) ... yet 30 minutes later it had still not updated. Regards, -Jeppe _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
