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

haproxy 3.1.0 fails to fully start #395

Open
drboone opened this issue Dec 7, 2024 · 3 comments
Open

haproxy 3.1.0 fails to fully start #395

drboone opened this issue Dec 7, 2024 · 3 comments
Assignees

Comments

@drboone
Copy link

drboone commented Dec 7, 2024

Our haproxy guest got updated to haproxy-3.1.0 this morning. After an extended period of searching, I realized that none of the listen ports were actually in use. Some fiddling with truss -f seems to show that the master process starts its first worker, which never really makes any progress, and there's just no further truss output. There's a message "Failed to load worker".

Falling back to 3.0.6 has us back on the air for now.

Platform 20241017T041739Z.

Apologies for the crappy bug report.

@jperkin jperkin self-assigned this Dec 9, 2024
@jperkin
Copy link
Collaborator

jperkin commented Dec 9, 2024

Are you able to share any non-sensitive parts of your config? At least with a basic proxy setup 3.1.0 works ok for me, so I wonder if this is due to specific features.

@drboone
Copy link
Author

drboone commented Dec 12, 2024

Interesting. Unfortunately my test install is also my production install so I don't have a good way to generate a minimum test case right now.

I think the secrets are all out of the attached full config. I should extract a promise not to laugh... :)
haproxy.cfg.txt

Sorry I missed your question for so long.

github-actions bot pushed a commit that referenced this issue Jan 5, 2025
### Changes in 0.4.25 (2023-08-21)

1. Fix `getQuote.yahoo()` for API changes. Thanks to Ethan B. Smith for the
    report and patch! Also add error message for users in GDPR countries, since
    we cannot automatically consent to GDPR and the request fails without
    consent.
    [#392](joshuaulrich/quantmod#392)
    [#393](joshuaulrich/quantmod#393)
    [#395](joshuaulrich/quantmod#395)

1. Fix `getQuote.yahoo()` when the user only requested metrics that do not have
    have a value for 'regularMarketTime'. Set the value to NA in these cases
    so the output remains the same regardless of whether the endpoint returns
    a 'regularMarketTime' or not. Thanks to @mehdiMBH for the report!
    [#255](joshuaulrich/quantmod#255)

1. Add fields to `getQuote.yahoo()` that are returned when no fields are
    explicitly requested. Thanks to @Courvoisier13 for the report!
    [#335](joshuaulrich/quantmod#335)

1. Add intraday endpoint to `getSymbols.yahoo()`. Thanks to @kapsner for the
    report and patch! Also allow suppressing the warning if more than 7 days
    of data are requested (@eddelbuettel).
    [#351](joshuaulrich/quantmod#351)
    [#381](joshuaulrich/quantmod#381)
    [#399](joshuaulrich/quantmod#399)

1. Add warning if `getSymbols()` is called with tickers that are reserved words
    because accessing them requires back-quotes (e.g. ``NA``).
    [#401](joshuaulrich/quantmod#401)

1. Fix `allReturns()` when 'subset' is specified. Thanks to @Panagis1980 for
    the report!
    [#402](joshuaulrich/quantmod#402)

### Changes in 0.4.24 (2023-07-17)

1. Fix `getSymbols.oanda()` URL. Thanks to @macray76 for the report.
    [#387](joshuaulrich/quantmod#387)

### Changes in 0.4.23 (2023-06-14)

1. Fix `getQuote.yahoo()` error. Thanks to Ethan B. Smith for the report and
    patch!
    [#382](joshuaulrich/quantmod#382)
    [#383](joshuaulrich/quantmod#383)

1. Add `name` argument to `add_TA()`. Thanks to @SamoPP for the suggestion!
    [#377](joshuaulrich/quantmod#377)
    [#205](joshuaulrich/quantmod#205)
@jperkin
Copy link
Collaborator

jperkin commented Jan 27, 2025

Stupid stupid GitHub autoclose.

@jperkin jperkin reopened this Jan 27, 2025
jperkin pushed a commit that referenced this issue Jan 28, 2025
Pkgsrc changes:
 * Remove now-upstream-integrated patch.
 * Checksum changes.

Upstream changes:

NSD version 4.11.0 had a serious bug in which applying updates to
zones (and other modifications that require a reload, such as adding
and deleting zones), could stop entirely after reception of a broken
or corrupted update via zone transfer. We believe that this broken
state would appear as one of the NSD processes consuming 100% CPU.
Version 4.11.1 has this corrected as well as some other smaller
non-critical bugs.

We strongly advise to not run NSD version 4.11.0, and if you have
it deployed already, upgrade to 4.11.1 at the earliest possible
opportunity.

4.11.1
================
BUG FIXES:
        - Fix #415: Fix out of tree builds. Thanks Florian Obser (@fobser).
        - Fix #414: XoT interoperability with BIND and Knot
        - Fix #421: old-main can quit before the reload process received
          from old-main that it is done on the reload_listener pipe.
          Thanks Otto Retter.
        - Fix whitespace in comment.
        - Fix #424: Stalled updates after corrupt transfer.

4.11.0
================
FEATURES:
        - Support reloading configuration on SIGHUP.
        - Fix #383: log timestamps in ISO8601 format with timezone.
          This adds the option `log-time-iso: yes` that logs in ISO8601
          format.
        - Updated cookie secrets management.
          The default cookie secret file location can be set at compile time
          with the --with-cookiesecretsfile=path option to configure. The
          default location is changed to {dbdir}/cookiesecrets.txt. The
          previous default location will be checked at startup when there is
          no cookie secrets file at the new default location.
          A staging cookie can now also be configured in the configuration
          file and secrets configured in the configuration file now take
          precedence over those read from file.
          All DNS related setting in the configuration file will be reevaluated
          and effectuated after nsd-control reconfig.
        - Merge #398: RFC 9660 The DNS Zone Version (ZONEVERSION) Option
        - Merge #406: ohttp and tls-supported-groups SvcParam suppor
        - Merge #408: NINFO, RKEY, RESINFO, WALLET, CLA and TA RR types
        - Merge #409: Writing of NSAP-PTR, GPOS and HIP RR types
        - Merge #407: Better balanced verbosity levels for logging.

BUG FIXES:
        - Fix title underline and declaration after statement warnings.
        - Add cross platform freebsd, openbsd and netbsd to github ci.
        - Update simdzone to include fix for netbsd double bswap declarations,
          and also semantic checks for DS and ZONEMD. And CFLAGS has -march
          prepended to fix detection.
        - Merge #376: Point the user towards tcpdump for logging individual
          queries.
        - Track $INCLUDEs in zone files.
        - Fix ci to update macos-12 to the macos-15 runner image.
        - Merge #390: Apply non-xfr tasks before xfr tasks.
          This fixes an issue where non-xfr tasks are lost when they are
          batch processed together with non-xfr tasks.
          This merge also changes that notifies are passed on from the serve
          processes to the xfrd directly instead of via main. This was
          necessary to allow applying the non-xfr tasks without forking a
          backup-main for the sole purpose of forwarding notifies.
        - Merge #391: Update copyright lines (in version output).
        - Fix #392: Inconsistent documentation about control-interface.
        - Merge #395: Explain the zonefile example better.
        - Merge #394: Fix the path to use doc/manual/.
        - Fix analyzer issue in do_print_cookie_secrets to check for failure.
        - Merge #404: Introducing Sphinx substitution in code blocks.
          As well as other fixes with Sphinx build.
        - Update Copyright lines in help output
        - Merge #395: Explain zonefile example better
        - Merge #394: Fix doc path (fixes "Edit on GitHub" button in the docs)
        - Fix Makefile for parallel build failure around bison rule.
        - Fix #405: Fix typo in documentation.
        - Treat a mismatch in RRset TTLs as a warning.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants