Ubuntu
ddclient package

ddclient spawns several competing daemons

Bug #152875 reported by Frederic Wenzel
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ddclient (Debian)
Fix Released
Unknown
ddclient (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: ddclient

I am running Ubuntu Feisty.

I have a DSL line that gets disconnected every 24 hours, then upon a reconnect gets a new IP address.

When I set both of the following settings in /etc/default/ddclient to true...
----
# Set to "true" if ddclient should be run every time a new ppp connection is
# established. This might be useful, if you are using dial-on-demand
run_ipup="true"

# Set to "true" if ddclient should run in daemon mode
run_daemon="true"
----

...then ddclient will over time spawn several, competing ddclient daemon processes (when I noticed the issue I had 3 of them) that will almost constantly execute update requests on the dyndns server. This got me temporarily banned from dyndns.org, until I set run_ipup to false and kept the run_daemon option as true, which will work fine.

My ddclient is configured to get its IP address from the interface ppp0.

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

I'll confirm with upstream about this bug.

Changed in ddclient:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Marco Rodrigues (gothicx) wrote :

You should not combine those two options, because running on ip_up means ddclient will be run once when you get connected, but when you run it as a daemon, it will continue running.

Changed in ddclient:
status: Triaged → Invalid
status: Invalid → Confirmed
Revision history for this message
Frederic Wenzel (freeed) wrote :

Yup, exactly, that's what I found out the hard way too ;)

My suggestion would be either effectively keeping these two options from running together (for example by checking for a running instance before spawning another one?) or at least adding a sentence to the config file so people are aware that these two options exclude each other.

Thanks!

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

This bug was reported upstream at https://sourceforge.net/tracker/index.php?func=detail&aid=2619554&group_id=116817&atid=676128

Alessio Treglia (quadrispro)
Changed in ddclient (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Ezra Reeves (ezrareeves) wrote :

According to the upstream bug report Debian is upstream.

Ezra Reeves (ezrareeves)
Changed in ddclient (Ubuntu):
assignee: nobody → Ezra Reeves (ezrareeves)
status: Triaged → In Progress
Revision history for this message
Ezra Reeves (ezrareeves) wrote :

The DD is adding the patch but I don't know if it will be in time for Lucid freeze.

Changed in ddclient (Ubuntu):
assignee: Ezra Reeves (ezrareeves) → nobody
Revision history for this message
Benjamin Drung (bdrung) wrote :

Thanks, uploaded

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ddclient - 3.8.0-9ubuntu2

---------------
ddclient (3.8.0-9ubuntu2) lucid; urgency=low

  * Fixed PPP and daemon mode incompatibility (LP: #152875);
    Debian bug #462207.
 -- Ezra Reeves <email address hidden> Wed, 24 Mar 2010 13:08:48 -0400

Changed in ddclient (Ubuntu):
status: In Progress → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in ddclient (Debian):
status: Unknown → New
Bug Watch Updater (bug-watch-updater)
Changed in ddclient (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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