In some exceptionally rare cases, you may experience issues caused by the fact that the FastNetMon daemon is not running.
Usually, you notice such issues by following the error from fcli or from our API daemon:
sudo fcli show log 2024/09/17 15:14:31 Cannot connect to FastNetMon API localhost:50052: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:50052: connect: connection refused" 2024/09/17 15:14:31 Please check that daemon is running: sudo systemctl status fastnetmon and restart it if needed: sudo systemctl restart fastnetmon
Such an error may be temporary, meaning it disappears after 10-20 seconds, and you simply need to retry your command. In this case, it means that very likely you triggered FastNetMon daemon restart by using a command which internally restarts the FastNetMon daemon, and then it needs 10-60 seconds to load properly:
sudo fcli commit
If this error persists longer than 60 seconds, you should check if everything is OK with the daemon.
The first step we recommend taking is to check the daemon status:
sudo systemctl status fastnetmon
Correctly running FastNetMon daemon appears as follows:
You need to pay attention to the fields "Active" and the date and time stamps right after it, which indicate the time when the daemon was started. If it few hours ago, then it's OK and the daemon is running correctly. In some cases, FastNetMon daemon may be in a crash loop, and it has status "active (running)", but the time when it started may be a few seconds ago. In this case, we recommend checking the guide about debugging segmentation faults in FastNetMon.
You can also manually check that the FastNetMon process is in memory:
ps aux | grep fastnetmon
And the correct output appears as follows:
If you've confirmed that the daemon is not running, the next step is to check the last entries in the FastNetMon log file:
tail -n 1000 /var/log/fastnetmon/fastnetmon.log
The most common reason for FastNetMon unavailability is an issue with MongoDB accessibility, and we recommend using this guide to find out reasons.
If FastNetMon is running but you still see an error that the API is not available, we recommend checking that FastNetMon listens on this port:
sudo netstat -lnpt |grep 50052 tcp6 0 0 127.0.0.1:50052 :::* LISTEN 3307319/fastnetmon
And if it does not, we recommend checking the FastNetMon log file for possible reasons. In addition to this, we recommend checking the firewall configuration to ensure that it allows local connections to port 50052 via TCP protocol.
If none of these instructions work, please reach out to our support.