Chris,
for some reason your astlinux box can not reach server for detecting local IP
address (getip.krisk.org). Check your internet connection, default route, try
ping getip.krisk.org
--- On Mon, 9/22/08, Chris Abnett <[EMAIL PROTECTED]> wrote:
From: Chris Abnett <[EMAIL PROTECTED]>
Subject: RE: [Astlinux-users] Periodic Inadyn?
To: [EMAIL PROTECTED], "'AstLinux Users Mailing List'"
<[email protected]>
Date: Monday, September 22, 2008, 2:41 PM
Here ya go:
babyasterisk ~ # ps|grep inadyn
2464 -1 500 S inadyn
babyasterisk ~ # grep -i inadyn /var/log/messages
Sep 21 04:17:19 babyasterisk user.info INADYN[2464]: INADYN:
Started 'INADYN version 1.96' - dynamic DNS updater.
Sep 21 04:17:19 babyasterisk user.warn INADYN[2464]: I:INADYN:
IP address for alias 'cadillackid.com' needs update to '65.60.224.51'
Sep 21 04:17:20 babyasterisk user.warn INADYN[2464]: I:INADYN:
Alias 'cadillackid.com' to IP '65.60.224.51' updated successful.
Sep 21 23:09:08 babyasterisk user.warn INADYN[2464]: W: DYNDNS:
Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Sep 21 23:09:08 babyasterisk user.warn INADYN[2464]:
W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 562)
Sep 21 23:11:09 babyasterisk user.warn INADYN[2464]: W: DYNDNS:
Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Sep 21 23:11:09 babyasterisk user.warn INADYN[2464]:
W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 563)
Sep 21 23:16:18 babyasterisk user.warn INADYN[2464]: W: DYNDNS:
Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Sep 21 23:16:18 babyasterisk user.warn INADYN[2464]:
W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 564)
Sep 21 23:21:27 babyasterisk user.warn INADYN[2464]: W: DYNDNS:
Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Sep 21 23:21:27 babyasterisk user.warn INADYN[2464]:
W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 565)
Sep 21 23:23:36 babyasterisk user.warn INADYN[2464]: W: DYNDNS:
Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Sep 21 23:23:36 babyasterisk user.warn INADYN[2464]:
W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 566)
Sep 21 23:28:45 babyasterisk user.warn INADYN[2464]: W: DYNDNS:
Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Sep 21 23:28:45 babyasterisk user.warn INADYN[2464]:
W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 567)
Sep 21 23:33:54 babyasterisk user.warn INADYN[2464]: W: DYNDNS:
Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Sep 21 23:33:54 babyasterisk user.warn INADYN[2464]:
W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 568)
Sep 21 23:39:03 babyasterisk user.warn INADYN[2464]: W: DYNDNS:
Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Sep 21 23:39:03 babyasterisk user.warn INADYN[2464]:
W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 569)
Sep 21 23:41:06 babyasterisk user.warn INADYN[2464]: W: DYNDNS:
Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Sep 21 23:41:06 babyasterisk user.warn INADYN[2464]:
W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 570)
Sep 21 23:46:15 babyasterisk user.warn INADYN[2464]: W: DYNDNS:
Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
Sep 21 23:46:15 babyasterisk user.warn INADYN[2464]:
W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs. (it 571)
babyasterisk ~ #
From: Dominko Vrljic
[mailto:[EMAIL PROTECTED]
Sent: Monday, September 22, 2008 10:01 AM
To: 'AstLinux Users Mailing List'
Subject: Re: [Astlinux-users] Periodic Inadyn?
Christopher,
please send output of these commands:
ps |grep inadyn
grep -i inadyn /var/log/messages
--- On Mon, 9/22/08, Chris Abnett <[EMAIL PROTECTED]>
wrote:
From: Chris Abnett
<[EMAIL PROTECTED]>
Subject: Periodic Inadyn?
To: [EMAIL PROTECTED], "'AstLinux Users Mailing List'"
<[email protected]>
Date: Monday, September 22, 2008, 12:30 PM
Ok I have Inadyn running to keep my dyndns custom address up to dayte which
it does very well.. EXCEPT if I reboot the cable modem and don't reboot the
astlinux machine... what happens is I end up with a new IP (sometimes, not
always) and consequently InaDyn never sees the change unless I reboot
astlinux, so this disrupts any inbound traffic to my FQDN from the
outside... is there a way to make InaDyn run anytime the Astlinux Machine
has changed IP's?
-Christopher
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL
PROTECTED]
