This is normal when there is a problem communication with the server.
It will probably fix itself with time.
Lonnie
On Mar 6, 2011, at 2:01 PM, John Novack wrote:
> Any clue what this means?
>
> Mar 6 14:00:30 NCTM user.warn INADYN[1641]: INADYN:IP: Error 0x68 in recv()
> Mar 6 14:00:30 NCTM
Any clue what this means?
Mar 6 14:00:30 NCTM user.warn INADYN[1641]: INADYN:IP: Error 0x68 in recv()
Mar 6 14:00:30 NCTM user.warn INADYN[1641]: W: DYNDNS: Error
'RC_IP_RECV_ERROR' (0x15) when talking to IP server
Mar 6 14:00:30 NCTM user.warn INADYN[1641]: W:'RC_IP_RECV_ERROR' (0x15)
updating th
Lonnie Abelbeck wrote:
> John,
>
> The latest AstLinux uses inadyn 1.96.2 that we have patched to fix issues and
> add features. Unfortunately inadyn has not been officially supported for
> some time. Though it still works well.
>
In the link I posted, there was mention of 1.97 as well.
W
John,
The latest AstLinux uses inadyn 1.96.2 that we have patched to fix issues and
add features. Unfortunately inadyn has not been officially supported for some
time. Though it still works well.
In older AstLinux (pre 0.7.0 ?), the site "getip.krisk.org" was used to
determine the public IP
with further investigation, it seems the source of the problem is dyndns
and their checkip servers. the secondary problem is inadyn, which, once
it fails on a specific server, continues to hit that ip rather than
trying one of the others.
Dyndns needs to fix their checkip servers to resolve thi
Michael Keuter wrote:
> On Sat, 18 Dec 2010 07:59:05 -0600, Darrick Hartman
> wrote:
>
>> John,
>>
>> I believe this has been mentioned before. You can manually mount the
>> runnix partion. Also, current versions of AstLinux include the
>> dosfslabel command which will allow you to label
I'm pretty sure there were several changes and fixes related to InaDyn
since that release.
Darrick
On 12/18/2010 08:17 AM, John Novack wrote:
> I probably will not attempt this remotely, as this chap is some 6 hours away
> IF his unit has a removable CF card, I may simply mail him another newer
I probably will not attempt this remotely, as this chap is some 6 hours away
IF his unit has a removable CF card, I may simply mail him another newer one
I have several of these out and working, so am hesitant to mess with
working units!
I may give it a try on a test bed here though, some day whe
On Sat, 18 Dec 2010 07:59:05 -0600, Darrick Hartman
wrote:
> John,
>
> I believe this has been mentioned before. You can manually mount the
> runnix partion. Also, current versions of AstLinux include the
> dosfslabel command which will allow you to label the RUNNIX partition.
>
> mount -t v
John,
I believe this has been mentioned before. You can manually mount the
runnix partion. Also, current versions of AstLinux include the
dosfslabel command which will allow you to label the RUNNIX partition.
mount -t vfat /dev/hda1 /oldroot/cdrom
Then either manually place the new .run file
I have an AstLinux 0.5 install that has been receiving error messages
and failing to update the address.
A reboot ( after 250 days ) seemed to fix it, but then this morning the
error reappears.
Any INADYN expert have a suggestion?
Given this is a 0.5 install, remote upgrade is not possible due t
11 matches
Mail list logo
