Thread: [Ddclient-support] Log file

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hello. I just installed ddclient on a Debian server and I want to know
if there a option to have a log file to check the daemon.

Thank and best regards.

-- 
Josu Lazkano

Hello. I just installed ddclient on a Debian server and I want to know
if there a option to have a log file to check the daemon.

Thank and best regards.

-- 
Josu Lazkano

Thanks for the reply, I want to check if the service is log in well on
the dyndns server.

Something on /var/log/ddclient.log

Best regards.

2011/5/20 wimpunk <wi...@us...>:
> On Fri, 2011-05-20 at 10:21 +0200, Josu Lazkano wrote:
>> Hello. I just installed ddclient on a Debian server and I want to know
>> if there a option to have a log file to check the daemon.
>>
>> Thank and best regards.
>>
>
> What do you mean with a log file to check the daemon?  What part do you
> want to check?
>
> regards,
>
> wimpunk.
>
>
>

-- 
Josu Lazkano

By default ddclient can log to syslog.  You can add a filter to syslog
to log to your preferred named.  Check your syslog documentation.

wimpunk.

On Fri, May 20, 2011 at 7:56 PM, Josu Lazkano <jos...@gm...> wrote:
> Thanks for the reply, I want to check if the service is log in well on
> the dyndns server.
>
> Something on /var/log/ddclient.log
>
> Best regards.
>
> 2011/5/20 wimpunk <wi...@us...>:
>> On Fri, 2011-05-20 at 10:21 +0200, Josu Lazkano wrote:
>>> Hello. I just installed ddclient on a Debian server and I want to know
>>> if there a option to have a log file to check the daemon.
>>>
>>> Thank and best regards.
>>>
>>
>> What do you mean with a log file to check the daemon?  What part do you
>> want to check?
>>
>> regards,
>>
>> wimpunk.
>>
>>
>>
>
>
>
> --
> Josu Lazkano
>
> ------------------------------------------------------------------------------
> What Every C/C++ and Fortran developer Should Know!
> Read this article and learn how Intel has extended the reach of its
> next-generation tools to help Windows* and Linux* C/C++ and Fortran
> developers boost performance applications - including clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> Ddclient-support mailing list
> Ddc...@li...
> https://lists.sourceforge.net/lists/listinfo/ddclient-support
>

2011/5/20 Torsten Landschoff <t.l...@gm...>:
> On Fri, 2011-05-20 at 10:21 +0200, Josu Lazkano wrote:
>> Hello. I just installed ddclient on a Debian server and I want to know
>> if there a option to have a log file to check the daemon.
>
> There is the -syslog option (enabled by default on Debian) which uses
> the system log daemon to log information. The result is usually found
> in /var/log/daemon.log:
>
> root@pluto:/home/torsten# grep ddclient /var/log/daemon.log
> May 17 04:18:53 pluto ddclient[697]: SUCCESS:  updating XXXXXX.dyndns.org: good: IP address set to 123.28.190.18
> May 18 04:07:55 pluto ddclient[697]: SUCCESS:  updating XXXXXX.dyndns.org: good: IP address set to 123.18.50.23
> May 19 04:09:11 pluto ddclient[697]: SUCCESS:  updating XXXXXX.dyndns.org: good: IP address set to 123.18.80.46
>
> Good luck!
>
> Torsten
>
>
>

Thanks again, I check the /car/log/daemon.log and it is there!!!

May 19 20:10:27 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 19 20:16:07 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 19 20:21:10 htpc ddclient[1726]: SUCCESS:  updating
subdomain.domain.com: good: IP address set to 188.77.225.4
May 20 01:57:08 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 20 02:02:48 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 20 02:08:28 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 20 02:14:08 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 20 02:19:48 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 20 02:24:50 htpc ddclient[1726]: SUCCESS:  updating
subdomain.domain.com: good: IP address set to 188.77.252.109
May 20 03:10:32 htpc ddclient[1726]: WARNING:  cannot connect to
checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
'checkip.dyndns.org'
May 20 03:15:33 htpc ddclient[1726]: SUCCESS:  updating
subdomain.domain.com: good: IP address set to 188.77.237.45

I am getting some warnings, I will change the ipcheck page, any alternative?

Is possible to add a log file on the config to output all data to and
specific file?

Thanks for your help.

Kind regards.

-- 
Josu Lazkano

On Fri, May 20, 2011 at 9:10 PM, Josu Lazkano <jos...@gm...> wrote:
> 2011/5/20 Torsten Landschoff <t.l...@gm...>:
>> On Fri, 2011-05-20 at 10:21 +0200, Josu Lazkano wrote:
>>> Hello. I just installed ddclient on a Debian server and I want to know
>>> if there a option to have a log file to check the daemon.
>>
>> There is the -syslog option (enabled by default on Debian) which uses
>> the system log daemon to log information. The result is usually found
>> in /var/log/daemon.log:
>>
>> root@pluto:/home/torsten# grep ddclient /var/log/daemon.log
>> May 17 04:18:53 pluto ddclient[697]: SUCCESS:  updating XXXXXX.dyndns.org: good: IP address set to 123.28.190.18
>> May 18 04:07:55 pluto ddclient[697]: SUCCESS:  updating XXXXXX.dyndns.org: good: IP address set to 123.18.50.23
>> May 19 04:09:11 pluto ddclient[697]: SUCCESS:  updating XXXXXX.dyndns.org: good: IP address set to 123.18.80.46
>>
>> Good luck!
>>
>> Torsten
>>
>>
>>
>
> Thanks again, I check the /car/log/daemon.log and it is there!!!
>
> May 19 20:10:27 htpc ddclient[1726]: WARNING:  cannot connect to
> checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
> 'checkip.dyndns.org'
> May 19 20:16:07 htpc ddclient[1726]: WARNING:  cannot connect to
> checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
> 'checkip.dyndns.org'
> May 19 20:21:10 htpc ddclient[1726]: SUCCESS:  updating

I've tried some others but most have give errors to.  Btw, how fast do
you run ddclient?  There is a rate limit for the service so there is a
possibility you get blocked by there service.
In my experience the best thing you can do is getting your IP from your router.

Regards,

wim.

Hi Josu,

Josu Lazkano schrieb am Fri, May 20, 2011 at 09:10:36PM +0200:

> May 19 20:10:27 htpc ddclient[1726]: WARNING:  cannot connect to
> checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname
> 'checkip.dyndns.org'

The IO::Socket::INET library tries to resolve the host
name 'checkip.dyndns.org' into an IP address and that fails.
Probably, you are starting ddclient early in the boot process
before you have name resolution up and running.

Make sure that while booting, you start the various services
in a good order, and don't start anything before the required
prerequisites are working.  In particular, first start up your
interfaces - dial-in, probably? - then start up the DNS resolver
(which may be automatic, some PPP and some DHCP client programs
automatically create the file /etc/resolv.conf when receiving the
necessary information from the peer) and only start ddclient when
you are sure that DNS resolution is working properly, in particular
that /etc/resolv.conf is in place and contains working name
server adresses of your Internet service provider.

How to achieve that in detail is outside the scope of this list,
ask the supplier of your PPP, DHCP or booting system - whatever
you happen to be using - for support if you fail to fix that yourself.

Yours,
  Ingo

-- 
Ingo Schwarze <isc...@as...> | Software Engineer
Astaro GmbH & Co. KG | www.astaro.com | 76227 Karlsruhe | Germany