-
Notifications
You must be signed in to change notification settings - Fork 458
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
Nethermind client should log when it auto-generates jwt-secret file #7747
Comments
When i ran the code, it seemed to silently do this, when it sees a |
@ssonthal |
Sure. Will work on this. |
so. To reproduce:
PS: it's easier to search the log by dumping it into a file using it could also be hard to keep track of when the logs get to the point of attempting sync, since you are redirecting the output to a file. then search the file. |
Hey @MarekM25 / @obasekiosa I could reproduce this issue locally. Here's a screenshot of the logs after:
As you can see the jwt-secret was auto-generated by the client but no warning logs appeared. |
Nice! So the expected log level should be info not warning. The default level of logs displayed by the client is info now that you know this and can reproduce it, you could attempt finding out what the issue is another place to check is the location of the code that logs the "Reading authentication secret..." line of the logs. good luck. |
Hey @obasekiosa , I must have done something wrong the prev time. I tried multiple time to reproduce that issue again. but it seems to be logging the msgs fine. Tried thrice after the first attempt. |
@ssonthal its being logged as a warning. (colored) in the mean time wanna try 7748 I'll close this as closed |
closing this. |
Is your feature request related to a problem? Please describe.
Right now the client only logs on start up when it doesn't see a keystore directory in the data directory and generates one.
It should log when it also generates a new jwt-secret file.
The text was updated successfully, but these errors were encountered: