Code Monkey home page Code Monkey logo

Comments (7)

crazy-max avatar crazy-max commented on May 30, 2024

Hum it seems the scheduler is stuck. Debug logs would help.

Can you also set SCHEDULE=*/10 * * * * and let me know if you still have the issue?

from ddns-route53.

benedikt-bartscher avatar benedikt-bartscher commented on May 30, 2024

I just retried with env LOG_LEVEL=debug but the output stays the same. How do i enable debug?
I can reproduce this problem on every firewall restart. I think setting the cronjob to 10min just reduces the chance of this error but does not solve it. A better way would be to just kill stuck jobs before every run. Or add a reasonable timeout.

from ddns-route53.

benedikt-bartscher avatar benedikt-bartscher commented on May 30, 2024

maybe we should expose these settings via env vars?:
https://aws.github.io/aws-sdk-go-v2/docs/configuring-sdk/retries-timeouts/

from ddns-route53.

benedikt-bartscher avatar benedikt-bartscher commented on May 30, 2024

i temporarily added os.Exit(1) after log.Warn().Msg("already running") to fix this

from ddns-route53.

crazy-max avatar crazy-max commented on May 30, 2024

I just retried with env LOG_LEVEL=debug but the output stays the same.

You should have some DBG logs such as:

ddns-route53    | Mon, 04 Jan 2021 19:15:55 EST INF Starting ddns-route53 version=2.2.0
ddns-route53    | Mon, 04 Jan 2021 19:15:55 EST INF Configuration loaded from file: /ddns-route53.yml
ddns-route53    | Mon, 04 Jan 2021 19:15:55 EST DBG No DDNSR53_* environment variables defined
ddns-route53    | Mon, 04 Jan 2021 19:15:55 EST DBG {
ddns-route53    |   "credentials": {
ddns-route53    |     "accessKeyID": "###########################",
ddns-route53    |     "secretAccessKey": "###########################"
ddns-route53    |   },
ddns-route53    |   "route53": {
ddns-route53    |     "hostedZoneID": "###########################",
ddns-route53    |     "recordsSet": [
ddns-route53    |       {
ddns-route53    |         "name": "#######.#######.",
ddns-route53    |         "type": "A",
ddns-route53    |         "ttl": 180
ddns-route53    |       }
ddns-route53    |     ]
ddns-route53    |   }
ddns-route53    | }

maybe we should expose these settings via env vars?:
https://aws.github.io/aws-sdk-go-v2/docs/configuring-sdk/retries-timeouts/

I'm not sure this is an issue when sending a request to AWS. Do you still repro?

from ddns-route53.

pkpfr avatar pkpfr commented on May 30, 2024

I also have the same issue. Added a log.Fatal() to fix it.

Aug 24 18:15:14 passkit ddns53[616]: Thu, 24 Aug 2023 18:15:14 BST INF WAN IPv6 has not changed for th1.passkit.com. record set
Aug 24 18:15:14 passkit ddns53[616]: Thu, 24 Aug 2023 18:15:14 BST INF No Route53 record set to update. Skipping...
Aug 24 18:15:14 passkit ddns53[616]: Thu, 24 Aug 2023 18:15:14 BST INF Next run in 29 seconds 998 milliseconds (2023-08-24 18:15:32 +0100 BST)
Aug 24 18:15:32 passkit ddns53[616]: Thu, 24 Aug 2023 18:15:32 BST INF Current WAN IPv4: 171.5.11.77
Aug 24 18:15:32 passkit ddns53[616]: Thu, 24 Aug 2023 18:15:32 BST INF Current WAN IPv6: 2403:6200:8876:cfdc:2ca:f78e:1649:e9dd
Aug 24 18:15:34 passkit ddns53[616]: Thu, 24 Aug 2023 18:15:34 BST INF WAN IPv4 has not changed for th1.passkit.com. record set
Aug 24 18:15:34 passkit ddns53[616]: Thu, 24 Aug 2023 18:15:34 BST INF WAN IPv6 has not changed for th1.passkit.com. record set
Aug 24 18:15:34 passkit ddns53[616]: Thu, 24 Aug 2023 18:15:34 BST INF No Route53 record set to update. Skipping...
Aug 24 18:15:34 passkit ddns53[616]: Thu, 24 Aug 2023 18:15:34 BST INF Next run in 29 seconds 999 milliseconds (2023-08-24 18:16:02 +0100 BST)
Aug 24 18:16:05 passkit ddns53[616]: Thu, 24 Aug 2023 18:16:05 BST INF Current WAN IPv4: 171.5.13.7
Aug 24 18:16:32 passkit ddns53[616]: Thu, 24 Aug 2023 18:16:32 BST WRN Already running
Aug 24 18:17:02 passkit ddns53[616]: Thu, 24 Aug 2023 18:17:02 BST WRN Already running
Aug 24 18:17:32 passkit ddns53[616]: Thu, 24 Aug 2023 18:17:32 BST WRN Already running
Aug 24 18:18:02 passkit ddns53[616]: Thu, 24 Aug 2023 18:18:02 BST WRN Already running
Aug 24 18:18:32 passkit ddns53[616]: Thu, 24 Aug 2023 18:18:32 BST WRN Already running
Aug 24 18:19:02 passkit ddns53[616]: Thu, 24 Aug 2023 18:19:02 BST WRN Already running

from ddns-route53.

crazy-max avatar crazy-max commented on May 30, 2024

#1064 should mitigate this issue. I will look at making backoff delay customizable if necessary.

Edit: added max backoff delay opt, see https://crazymax.dev/ddns-route53/usage/cli/#options

from ddns-route53.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.