spurious 'WARNING: cannot connect to checkip.dyndns.org:80' errors

Bug #60159 reported by Cristóbal M. Palmer
2
Affects Status Importance Assigned to Milestone
ddclient (Debian)
Invalid
Undecided
Unassigned
ddclient (Ubuntu)
Fix Released
Undecided
Marco Rodrigues

Bug Description

Binary package hint: ddclient

logcheck shows errors like this:

Sep 12 18:00:07 localhost ddclient[4619]: WARNING: cannot connect to checkip.dyndns.org:80 socket: IO::Socket::INET: connect: No route to host

But ddclient updates just fine.

see the upstream bug:

201295 ddclient cannot connect to checkip.dyndns.org:80 error

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=201295

Revision history for this message
Cristóbal M. Palmer (cristobalpalmer) wrote :

A (slightly scrubbed) copy of my /etc/ddclient.conf:

# Configuration file for ddclient generated by debconf
#
# /etc/ddclient.conf

pid=/var/run/ddclient.pid
protocol=dyndns2
#use=if, if=dyndns
use=web, web=dyndns
server=members.dyndns.org
login=somelogin
password='somepasswd'
some.domain.net,other.domain.net

Changed in ddclient:
status: Unknown → Unconfirmed
Revision history for this message
Marco Rodrigues (gothicx) wrote :

Isn't this fixed on feisty or gutsy ?

Revision history for this message
Marco Rodrigues (gothicx) wrote :

I think this is already fixed. If someone still have the same problem, please set the bug as "Confirmed". Thanks!

Changed in ddclient:
status: New → Confirmed
assignee: nobody → gothicx
status: Confirmed → Fix Released
status: New → Invalid
Revision history for this message
Miguel Branco (mpbbranco) wrote :

Started yesterday completely out of the blue (no upgrade, no reboot, no nothing) around 17:44 GMT May 22 according to daemon log.

ddclient is (or was) working fine, actually effectuated an ip update just last sunday smoothly.

Obs: message is "bad hostname checkip.dyndns.org" i/o "no route to host". Changed to checkip.dyndns.com to no avail. Of course both IPs are getting pinged fine.

Changed in ddclient (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Miguel Branco (mpbbranco) wrote :

Well, the message is still appearing over the weekend in a very random way.

Since it came out of the blue and I had some mysterious ipv6-related dns-resolution lag issues lately, maybe it is not related to the package itself.

Will turn back to fixed if no news.

Revision history for this message
Marco Rodrigues (gothicx) wrote :

So, I'm turning it back to 'Fix Released'.

Changed in ddclient (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.