Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exit code #99

Closed
modem7 opened this issue Feb 12, 2020 · 1 comment
Closed

Exit code #99

modem7 opened this issue Feb 12, 2020 · 1 comment
Labels
question Question how to use ddclient

Comments

@modem7
Copy link

modem7 commented Feb 12, 2020

Hey guys,

The way I have my network setup is mostly in Docker.

I have a Pihole with a dnscrypt upstream.

If DDClient starts up before anything else (which is likely, with it being such a light application), I can experience issues such as "WARNING: cannot connect to checkip.dyndns.com:80 socket: IO::Socket::INET: Bad hostname 'checkip.dyndns.com'"

If when the application saw this error, if we could get some form of exit code which either 1. indicates it to try again x number of times or 2. allowed it to mark the container/application as unhealthy, this would make sure these errors were either really errors, or more likely, an issue with when it initially checked dyndns.

Hope it makes sense!

Thanks

@modem7 modem7 changed the title Exit code =1 Exit code Feb 12, 2020
@wimpunk
Copy link
Contributor

wimpunk commented May 29, 2020

Sorry but it doesn't make sense. When ddclient can't update it has to keep running trying to update another time. Ddclient isn't made for monitoring the health of your network.

@wimpunk wimpunk closed this as completed May 29, 2020
@SuperSandro2000 SuperSandro2000 added the question Question how to use ddclient label May 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Question how to use ddclient
Projects
None yet
Development

No branches or pull requests

3 participants