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

fix: [#2032] local status cmd reports status correctly #2079

Merged
merged 1 commit into from
Sep 2, 2024

Conversation

jacderida
Copy link
Contributor

Description

In a service-based network, a node was determined to be running by searching for a process whose path matched the path where the service binary is installed. This works because those are unique paths. However, it did not work for a local network, because each process uses a binary at the same path.

For a status refresh, we now distinguish between a service-based network and a local network. For the local network, we determine if a node is running simply by connecting to its RPC service.

Related Issue

Fixes #2035

Type of Change

Please mark the types of changes made in this pull request.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Other (please describe):

In a service-based network, a node was determined to be running by searching for a process whose
path matched the path where the service binary is installed. This works because those are unique
paths. However, it did not work for a local network, because each process uses a binary at the same
path.

For a status refresh, we now distinguish between a service-based network and a local network. For
the local network, we determine if a node is running simply by connecting to its RPC service.
@jacderida jacderida force-pushed the fix-node_man-local_status branch from 1119a1d to a9c6d88 Compare August 31, 2024 21:19
@joshuef joshuef added this pull request to the merge queue Sep 1, 2024
Merged via the queue into maidsafe:main with commit e5e554a Sep 2, 2024
40 checks passed
@loziniak
Copy link
Contributor

This still does not work for me:

https://forum.autonomi.community/t/update-15-august-2024/40225/34

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

Successfully merging this pull request may close these issues.

[safenode-manager] nodes are misreported as "STOPPED"
3 participants