-
Notifications
You must be signed in to change notification settings - Fork 63
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
audit_info lookupUser with empty content leads to parse error #164
Comments
@estein9825 If you've the failed environment handy, can you share log of |
Unfortunately that particular environment was restored and we have not tried to increase our relay server components since then. It might be that it is no longer an issue with the relay patch that I implemented for paralus/relay#43. But I'm not sure. I will keep an eye out and try to grab that info if it happens again. |
We are not able to see audit-logs in paralus dashbaord. Logs from relay-tail logs from /audit-logs/audit.log {"level":"info","ts":"2023-05-08T08:38:17.389Z","msg":"audit","xid":"chcb9uf9lqnjlm35tipg","method":"GET","url":"/apis/install.istio.io/v1alpha1","query":"timeout=32s","serverName":"13de4669-a1f3-4e05-bf63-66a4629afdf6.user.paralus.slvr-corp-corpdemo1.awsdns.internal.das","user":"a=a0d2e395-bb80-4960-88b0-1dc1477593f3/o=0a2699fc-2bec-4b4c-90e2-5bf6c5a28aca/p=1f7bf0a2-ff4a-46f2-a282-1d4bd84bc81a/u=admin-64paralus-46local/is=false/es=false/st=ws/su=false/rn=false/","remoteAddr":"10.188.212.37","statusCode":200,"written":472,"duration":0.001689512} |
@divyanjali1 What error or message your are getting on dashboard or from get audit API? If the error message is not related to parse error (as per title of this issue), then it would be better if you open separate issue for it. |
@akshay196 I don't see any logs in dashboard at all and the only logs I see regarding audit-logs are one I have posted above Can you help me with the specific location for checking the logs ? |
@divyanjali1 your issue seems to be different from the current one, I recommend to create a new issue and track the conversations there. It may be confusing to have conversations around two different issues here. |
We are working on #264 for increasing number of relay servers in Paralus. We will address this bug as a part of this. |
Expected vs actual behavior
Somehow the auditing of a user lookup lead to blank info, which caused the following panic exception:
Steps to reproduce the bug
(optional) If you have ideas on why the bug happens or how it can be solved, please provide it here
Dropping the relay server down to 1, turning fluent-bit off, and restoring the database before bringing up paralus again seemed to have gotten it to work.
The text was updated successfully, but these errors were encountered: