Skip to content

darkcoind crashes when using non-standard ports #23

Closed

Description

@JanuaryLavender

To keep it short:

When you try to start a local masternode on a port different from [1]9999 darkcoind reports "CDarkSendPool::RegisterAsMasterNode() - Invalid port" in the debug log, but crashes right after.
When you try to start a remote masternode by running the "masternode start" command on your local darkcoind, the local darkcoind or darkcoin-qt show the same behavior. "CDarkSendPool::RegisterAsMasterNode() - Invalid port" is logged, but darkcoind crashes.

Activity

  1. jonathancross commented on Apr 16, 2016

    @jonathancross

    Has anyone confirmed if this is still an issue with dashd in 2016?

  2. added a commit that references this issue on Dec 28, 2016
  3. added a commit that references this issue on Feb 15, 2019
  4. added a commit that references this issue on Dec 4, 2019
  5. added a commit that references this issue on Jul 6, 2020
  6. added a commit that references this issue on Mar 29, 2021
  7. added a commit that references this issue on Oct 21, 2021
  8. added a commit that references this issue on Nov 18, 2021
  9. added a commit that references this issue on Jul 25, 2023
  10. added a commit that references this issue on May 24, 2024
  11. added a commit that references this issue on Nov 3, 2026
  12. added a commit that references this issue on Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions