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

[net_monitor]: Failed to connect socket. #8600

Open
2 of 3 tasks
cjmodi306 opened this issue Aug 23, 2024 · 0 comments
Open
2 of 3 tasks

[net_monitor]: Failed to connect socket. #8600

cjmodi306 opened this issue Aug 23, 2024 · 0 comments
Labels
type:bug Software flaws or errors.

Comments

@cjmodi306
Copy link

cjmodi306 commented Aug 23, 2024

Checklist

  • I've read the contribution guidelines.
  • I've searched other issues and no duplicate issues were found.
  • I'm convinced that this is not my fault but a bug.

Description

The system_monitor package of Autoware fails to read the network usage. Following is the error message that it returns:

[ERROR] [1724405216.453723643] [net_monitor]: Failed to connect socket. No such file or directory

As I looked further into the code of traffic_reader, which is one of the dependencies of system_monitor, I realized that the socket_path "/tmp/traffic_reader" does not exist. Hence, it cannot connect to it.

Has anyone else faced this issue? Any possible solution to this? Thanks.

Expected behavior

The package should be able to connect to the socket and read network usage.

Actual behavior

[ERROR] [1724405224.453356494] [net_monitor]: Failed to connect socket. No such file or directory

Steps to reproduce

ros2 launch system_monitor system_monitor.launch.xml

Versions

  • OS: Kubuntu 22.04
  • ROS 2: Humble

Possible causes

No response

Additional context

No response

@idorobotics idorobotics added the type:bug Software flaws or errors. label Aug 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Software flaws or errors.
Projects
None yet
Development

No branches or pull requests

2 participants