On Thu, May 31, 2012 at 1:12 AM, Chris Buechler <c...@pfsense.org> wrote:
> On Thu, May 31, 2012 at 3:44 AM, Jeppe Øland <jol...@gmail.com> wrote:
>> On Tue, Jan 10, 2012 at 6:26 PM, Chris Buechler <c...@pfsense.org> 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?
>>
>
> Yes. We'd have thousands of people screaming if that wasn't the case,
> and I've never seen that not work. /etc/rc.newwanip runs when any IP
> changes, which does the update. It's not shown there in your log. When
> it runs it logs, not sure how much you snipped out.
There is nothing in the log before that.
It starts with this:
May 30 23:58:14 firewall syslogd: kernel boot file is /boot/kernel/kernel
May 30 23:58:19 firewall dhclient: PREINIT
May 30 23:58:19 firewall dhclient[13858]: DHCPDISCOVER on em1_vlan1001
to 255.255.255.255 port 67 interval 1
May 30 23:58:20 firewall dhclient[13858]: DHCPDISCOVER on em1_vlan1001
to 255.255.255.255 port 67 interval 1
May 30 23:58:21 firewall dhclient[13858]: DHCPDISCOVER on em1_vlan1001
to 255.255.255.255 port 67 interval 2
May 30 23:58:23 firewall dhclient[13858]: DHCPDISCOVER on em1_vlan1001
to 255.255.255.255 port 67 interval 4
May 30 23:58:27 firewall dhclient[13858]: DHCPDISCOVER on em1_vlan1001
to 255.255.255.255 port 67 interval 7
May 30 23:58:34 firewall dhclient[13858]: DHCPDISCOVER on em1_vlan1001
to 255.255.255.255 port 67 interval 8
May 30 23:58:42 firewall dhclient[13858]: DHCPDISCOVER on em1_vlan1001
to 255.255.255.255 port 67 interval 20
May 30 23:59:02 firewall dhclient[13858]: DHCPDISCOVER on em1_vlan1001
to 255.255.255.255 port 67 interval 18
May 30 23:59:20 firewall dhclient[13858]: No DHCPOFFERS received.
May 30 23:59:20 firewall dhclient[13858]: No working leases in
persistent database - sleeping.
May 30 23:59:20 firewall dhclient: FAIL
May 30 23:59:21 firewall dhclient[33083]: DHCPDISCOVER on em1_vlan1001
to 255.255.255.255 port 67 interval 1
May 30 23:59:22 firewall dhclient[33083]: DHCPDISCOVER on em1_vlan1001
to 255.255.255.255 port 67 interval 1
May 30 23:59:23 firewall dhclient[33083]: DHCPDISCOVER on em1_vlan1001
to 255.255.255.255 port 67 interval 1
May 30 23:59:24 firewall dhclient[33083]: DHCPDISCOVER on em1_vlan1001
to 255.255.255.255 port 67 interval 2
It goes on like that until the DHCP server came back about half an hour later...
But as I said, at boot time, the DHCP server was not responding so
even if the script had run at boot, it probably wouldn't have done
anything (given the lack of an address - or 0.0.0.0 if that's what it
would see).
I did not snip anything after the first line I pasted.
After waiting for a short while, I manually ran the script and that updated it.
Log in continuation of the previous one:
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
May 31 00:29:22 sshd[63791]: Accepted keyboard-interactive/pam for
root from 10.10.10.10 port 2329 ssh2
May 31 00:29:22 sshlockout[287]: sshlockout/webConfigurator v3.0
starting up
******* HERE I MANUALLY RAN THE UPDATE SCRIPT.
May 31 00:30:54 php: : DynDns: updatedns() starting
May 31 00:30:54 php: : DynDns debug information: y.y.y.y extracted
from local system.
May 31 00:30:54 php: : DynDns: Current WAN IP: y.y.y.y Cached IP:
oy.oy.oy.oy
May 31 00:30:54 php: : DynDns debug information: DynDns: cacheIP !=
wan_ip. Updating. Cached IP: oy.oy.oy.oy WAN IP: y.y.y.y
May 31 00:30:54 php: : DynDns: DynDns _update() starting.
May 31 00:30:54 php: : DynDns: DynDns _checkStatus() starting.
May 31 00:30:54 php: : DynDns: Current Service: dyndns
May 31 00:30:54 php: : DynDns debug information: y.y.y.y extracted
from local system.
May 31 00:30:54 php: : phpDynDNS: updating cache file
/conf/dyndns_wandyndns'mydomain'.cache: y.y.y.y
May 31 00:30:54 php: : phpDynDNS: (Success) IP Address Changed
Successfully! (199.188.194.135)
******* DHCP RENEWAL. SAME IP GIVEN OUT. SHOULD THE SCRIPT HAVE RUN NOW?
May 31 00:40:31 dnsmasq[41037]: read /etc/hosts - 11 addresses
May 31 00:43:41 dhclient[33083]: DHCPREQUEST on em1_vlan1001 to x.x.x.x
port 67
May 31 00:43:41 dhclient[33083]: DHCPACK from x.x.x.x
May 31 00:43:41 dhclient: RENEW
May 31 00:43:41 dhclient: Creating resolv.conf
May 31 00:43:41 dhclient[33083]: bound to y.y.y.y -- renewal in 1300
seconds.
******* CRONJOB DAILY SCRIPT RUN.
May 31 01:01:02 php: : DynDns: updatedns() starting
May 31 01:01:02 php: : DynDns debug information: y.y.y.y extracted
from local system.
May 31 01:01:02 php: : DynDns: Current WAN IP: y.y.y.y Cached IP:
y.y.y.y
May 31 01:01:02 php: : phpDynDNS: No change in my IP address and/or
25 days has not passed. Not updating dynamic DNS entry.
******* DHCP RENEWAL. SAME IP GIVEN OUT. SHOULD THE SCRIPT HAVE RUN NOW?
May 31 01:05:28 dhclient[33083]: DHCPREQUEST on em1_vlan1001 to x.x.x.x
port 67
May 31 01:05:29 dhclient[33083]: DHCPACK from x.x.x.x
May 31 01:05:29 dhclient: RENEW
May 31 01:05:29 dhclient: Creating resolv.conf
May 31 01:05:29 dhclient[33083]: bound to x.x.x.x -- renewal in 1300
seconds.
> It's possible if you're running some arbitrary snapshot it was broken
> at that particular point in time, it does work on every stable release
> for sure.
From dashboard:
2.0.1-RELEASE (amd64)
built on Tue Dec 13 14:25:00 EST 2011
FreeBSD 8.1-RELEASE-p6
You are on the latest version.
I agree it obviously works for the majority of users, but some of us
aren't so lucky...
Regards,
-Jeppe
_______________________________________________
List mailing list
List@lists.pfsense.org
http://lists.pfsense.org/mailman/listinfo/list
