[SOLVED] DynDNS timeout

[weust]

Fitch and I already spoke about this on IRC. The Duck DNS entry (the only one I've tested so far) doesn't seem to work because of something. He knows the details.
Anyway, I just logged in on my OPNsense VM and saw this crash report.
Perhaps it will help?

Crash report begins.  Anonymous machine information:

amd64
10.1-RELEASE-p6
FreeBSD 10.1-RELEASE-p6 #0 5aa5ada(master): Thu Feb 26 16:26:03 CET 2015     root@sensey64:/usr/obj/usr/src/sys/SMP

Crash report details:

PHP Errors:
[09-Mar-2015 15:42:40 Europe/Amsterdam] PHP Fatal error:  Uncaught exception 'Exception' with message 'Timeout (120) executing :filter sync' in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Backend.php:84
Stack trace:
#0 /usr/local/etc/inc/util.inc(158): OPNsense\Core\Backend->sendEvent('filter sync')
#1 /usr/local/etc/inc/util.inc(1643): send_event('filter sync')
#2 /usr/local/etc/inc/config.lib.inc(534): carp_sync_client()
#3 /usr/local/www/services_dyndns_edit.php(163): write_config()
#4 {main}
  thrown in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Backend.php on line 84
[09-Mar-2015 15:44:33 Europe/Amsterdam] PHP Fatal error:  Uncaught exception 'Exception' with message 'Timeout (120) executing :filter sync' in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Backend.php:84
Stack trace:
#0 /usr/local/etc/inc/util.inc(158): OPNsense\Core\Backend->sendEvent('filter sync')
#1 /usr/local/etc/inc/util.inc(1643): send_event('filter sync')
#2 /usr/local/etc/inc/config.lib.inc(534): carp_sync_client()
#3 /usr/local/www/services_dyndns_edit.php(163): write_config()
#4 {main}
  thrown in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Backend.php on line 84

[franco]

The two are probably unrelated. Maybe I did something wrong while pushing the changes to the GitHub repository. Can test this morning.

[franco]

I did not get that timeout error and Duck DNS works as expected... Did you enter your hostname correctly?

http://i.imgur.com/UOqmHD1.png

[weust]

I had first only the host name as the entry, but later the FQDN as per the description below that field.
I Wil do another check.

[franco]

Maybe we can split off ".duckdns.org" in case it was added. But then again, if people put in a typo it may not work again, yadda, yadda....

[weust]

True, true. But perhaps taking the approach on how Duck DNS want us to do things would be nice.
What I mean is, you look at that site and do things the way they tell you how to set it up.
Though I am not 100% sure they have only one way of doing things.
But they do show a separate token and the hostname, so basically what you have now as far as field name goes (Hostname) that should be enough. No need for the domain as well.

[franco]

It would be nice to redesign the GUI to adapt to the service's terminology, but that is even more work than maintaining the update glue underneath that could use a serious facelift and testing. So this is back to normal now for you?

[weust]

What do you mean by normal?

[franco]

OPNsense refreshing Duck DNS IP as expected?

[weust]

I disabled the entry the evening before yesterday because of the crash report it gave.
Will check it again tonight.

[weust]

Duck DNS works now for me.

Important is to only use the hostname, and not the FQDN.
That will trigger an error:

opnsense: /services_dyndns_edit.php: phpDynDNS: (Unknown Response)

After I set it to just the hostname it updated fine, but does generate some logging.
Minor fine tuning no doubt:

Mar 13 20:45:55 opnsense: /services_dyndns_edit.php: phpDynDNS: (Success) IP Address Updated Successfully!
Mar 13 20:45:55 opnsense: /services_dyndns_edit.php: phpDynDNS: updating cache file /conf/dyndns_wanduckdns'machinename'0.cache: xxx.xxx.xxx.xxx
Mar 13 20:45:54 opnsense: /services_dyndns_edit.php: phpDynDNS: (ERROR!) No Password Provided.

The xxx's being my IP address obviously and machinename the hostname.

Seems something is left behind that want the password to be there, but not sure if that would mean a complete rewrite. If that is the case, it's safe to ignore that error message.

[franco]

Thanks, I fixed both issues: FDQN is now usable as well and the password error is gone.

https://github.com/opnsense/core/commit/01d78e2a685be51d9c4beb03204d95510c5a8d97

[weust]

Excellent