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

nextdns status returns Error: unknown status: #940

Open
iptvcld opened this issue May 11, 2024 · 6 comments
Open

nextdns status returns Error: unknown status: #940

iptvcld opened this issue May 11, 2024 · 6 comments
Labels
🐞 bug Something isn't working

Comments

@iptvcld
Copy link

iptvcld commented May 11, 2024

Context
INFO: OS: ubuntu
INFO: GOARCH: amd64
INFO: GOOS: linux
INFO: NEXTDNS_BIN: /usr/bin/nextdns
INFO: INSTALL_RELEASE: 1.43.3

Hello; I have NextDNS installed on Ubuntu and when ever i run nextdns status in the CLI it first returns back Error: unknown status: and then if i run that same status command a couple more times then it returns running.

image

@iptvcld iptvcld added the 🐞 bug Something isn't working label May 11, 2024
@RPMozley
Copy link

As per forum post, here’s the other bug report that was fixed #674
Seems the fix put in the unknown status that you’re seeing.

@iptvcld
Copy link
Author

iptvcld commented May 11, 2024

As per forum post, here’s the other bug report that was fixed #674 Seems the fix put in the unknown status that you’re seeing.

Your right, seems like that’s where the error is originated from this code.
image

But I am not understanding why this is being caught for me. Is Ubuntu not the preferred distro for this CLI to work?

is freeBSD perhaps a better choice?

@RPMozley
Copy link

The CLI itself is perfectly fine doing it's job, it's just that running the status script sometimes times out waiting for the systemctl status to return a result.
If you just run the systemctl status nextdns command yourself and wait for it to give the result, it will most likely say it's running and active.

@iptvcld
Copy link
Author

iptvcld commented May 11, 2024

The CLI itself is perfectly fine doing it's job, it's just that running the status script sometimes times out waiting for the systemctl status to return a result. If you just run the systemctl status nextdns command yourself and wait for it to give the result, it will most likely say it's running and active.

Thanks for the explanation, maybe the cli can be updated to pause for a few seconds before out putting the result. But I am thinking to move over to freeBSD, would I have the same results there as well or because FreeBSD does not use systemd, I won’t see these delays with a false positive?

@iptvcld
Copy link
Author

iptvcld commented May 12, 2024

Something like this command will pull the status as well
systemctl status nextdns | awk '/Active:/ {gsub(/^.*\(|\).*$/, "", $0); print}'
This will return back: running or dead

@iptvcld
Copy link
Author

iptvcld commented May 14, 2024

Hoping there is a fix to this, I wanted to stay with Ubuntu or Debian but seems like alpine Linux may work better?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants