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

config: clarify host/port for bitcoind config #176

Open
raweber42 opened this issue Nov 16, 2023 · 8 comments
Open

config: clarify host/port for bitcoind config #176

raweber42 opened this issue Nov 16, 2023 · 8 comments

Comments

@raweber42
Copy link

Running the frcli audit command fails somehow arbitrarily. For some start/end times it works fine, for some it doesn't and returns a 401 error.

I can audit reports for any time of the year (months, quarter of, half of and full year).

Running frcli audit --loop-category --start_time 1672527600 --end_time 1680299999 for the first quarter of 2023 works just fine. But frcli audit --loop-category --start_time 1680300000 --end_time 1688162399 for the second quarter fails with the error:
[frcli] rpc error: code = Unknown desc = status code: 401, response: ""

Running it without --loop-category has the same behavior.

But running just frcli audit works just fine.

See above. We are running faraday in Kubernetes.

Standalone.

CLI

We build our own image, currently we are using 0.2.11-alpha

Runs on a kubernetes cluster.

Runs on a kubernetes cluster.

I can't find a faraday.log file, where do I get it?

@mrfelton
Copy link
Contributor

Did you ever get past this? We are experiencing something similar

@guggero
Copy link
Member

guggero commented Jan 12, 2024

I asked the user for more information over another comms channel but never got more details. My suspicion is that the bitcoind configuration parameters were wrong (the 401 very likely comes from the attempt to connect to bitcoind from Faraday directly).

@mrfelton
Copy link
Contributor

I'm able to connect to bitdcoind manually from the same container that faraday is running on, using the same connection details that faraday is using

@guggero
Copy link
Member

guggero commented Jan 12, 2024

Then it would be useful to get more logs from faraday...

@mrfelton
Copy link
Contributor

mrfelton commented Jan 12, 2024

I think the issue may indeed be related to the bitcoind connection. Looks like a possible issue with how we are injecting secrets for the bitcoind connection string, so continuing to investigate that side of things atm.

@mrfelton
Copy link
Contributor

mrfelton commented Jan 12, 2024

Confirmed - the problem was related to the bitcoin connection. In our cases, two issues. Missing the port from the hostname, and an incorrectly injected secret passed as the password. Thanks.

@guggero
Copy link
Member

guggero commented Jan 12, 2024

Okay, thank you for confirming. We could probably update the flag/config description a bit better, at least for the host/port part. Renaming the issue to make it more clear what needs to be done.

@guggero guggero changed the title Cannot audit for certain times of the year - returns 401 config: clarify host/port for bitcoind config Jan 12, 2024
@mrfelton
Copy link
Contributor

Part of the trouble debugging is that the issue only seems to manifest if you try to do an audit of a time period that contains channel closes. I assume those are the only cases where it actually attempts to connect to bitcoind. Perhaps doing a connect on startup would enable detection of connection issues much sooner and require a lot less debugging to investigate.

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

No branches or pull requests

3 participants