H,
I am trying to enable webook for GitHub with flux as mentioned in this link https://toolkit.fluxcd.io/guides/webhook-receivers/. GitHub fails to push the event and gets 400 error code. This is on gcp cluster.
Any pointers to debug this of great help.
On the cluster, I cross-checked controllers are all up and running
-Prashanth
Looks like the issue with some setting in the GitRepository names. Now i see the following error when the Push event i sent
{"level":"info","ts":"2021-02-22T05:56:23.346Z","logger":"receiver-server","msg":"handling request","digest":"cfc7a9a5cd337d1c0f58d5d790eb1f988c3c91ed1201a1b692cf8b479abc62a2"}
{"level":"info","ts":"2021-02-22T05:56:23.347Z","logger":"receiver-server","msg":"handling GitHub event: push","receiver":"github-receiver"}
{"level":"info","ts":"2021-02-22T05:56:23.347Z","logger":"receiver-server","msg":"found matching receiver","receiver":"github-receiver"}
{"level":"info","ts":"2021-02-22T05:56:23.354Z","logger":"receiver-server","msg":"resource annotated","receiver":"github-receiver","resource":"gitrepoinfo"}
{"level":"info","ts":"2021-02-22T05:56:23.580Z","logger":"event-server","msg":"Discarding event, no alerts found for the involved object","object":"flux-system/gitrepoinfo","kind":"GitRepository"}
{"level":"info","ts":"2021-02-22T05:56:24.321Z","logger":"event-server","msg":"Discarding event, no alerts found for the involved object","object":"flux-system/podinfo","kind":"Kustomization"}
I added Alert and Provider configuration, then to see the error. Even though events are getting pushed, flux is not picking up changes from repo.
Any pointers would be of great help.
-Prashanth
Related
I have an API that I host using Lambda (nodejs), with API-gateway. I'm using serverless to deploy.
Generally things have been fine, but while I was working on a specific function today, I started to receive HTTP 500 errors when hitting the endpoint. However, while there were still API-Gateway access logs for the end point, there were no Cloudwatch logs for the lambda functions getting hit. I was able to verify that the Authorizer was getting hit successfully, and not returning any issue (if it was, it would have been a 401). After using CLI tools to invoke the function from the command line, the 500 error went away and I was able to successfully hit the endpoints again.
Has anyone ever ran into this before? If I'm missing a debug step, I would really like to know. It was really concerning that my API could be generating 500 errors with no paper trail to help me understand what was happening.
You can check your role and permissions ,this link could help you https://aws.amazon.com/premiumsupport/knowledge-center/api-gateway-lambda-stage-variable-500/
Also you can debug further with X-ray : https://docs.aws.amazon.com/lambda/latest/dg/services-xray.html
I can't seem to find much information on this one. I have a requirement to include the error message body in the email alert that is sent out when the GCP alert policy is triggered.
Now I can see from the documentation page that certain variables can be added relating to the policy itself but does anyone know of any easy way to parse the log contents failure payload and pass it? This may be a failure of understanding on my part.
What I have tried is to setup a cloud function that raises an error with a specific message whenever the http request is made. I have setup a policy on the logs for this function that trigger for the error severity. This works fine but what I can't do is parse the error message in the email alert body. Does anyone know of a good work around for this or am I missing something?
I have a state machine with multiple steps.
I want to send notification whenever a step run successfully or give error.
One solution is to add a SNS step after each step so whenever a step is successful then next step will run which is to send notification but what if a step fails then How can I send email ?
Is there any solution to this problem ?
I know we can set cloud watch rules but it send notification when a complete state machine fails but here I want to get notifications at lower level i.e. at every step of state machine.
Thanks for your question.
In the AWS Step Functions Console, there's a sample project called Callback pattern example which should illustrate what you're trying to achieve:
Step Functions offers error catching functionality which allows you to transition to a specific state based on the error thrown. For more information see this helpful documentation on error handling: Error Handling in Step Functions - AWS Step Functions
We are using twilio for sending messages but as Twilio(Text Messaging) integration was shutting down we deployed the integration using cloud run by following steps from https://github.com/GoogleCloudPlatform/dialogflow-integrations/tree/master/twilio#readme
After deployment messages were sending successfully but now suddenly we are getting errors in twilio like
Some messages are sending successfully and for some messages we are getting error.can anybody help me in this.thanks in advance
According to Twillio docs there might be some possible causes for Unreachable destination handset
1.The destination handset you are trying to reach is switched off or otherwise unavailable.
2.The device you are trying to reach does not have sufficient signal
3.The device cannot receive SMS (for example, the phone number belongs to a landline)
4.There is an issue with the mobile carrier
Possible Solutions
The first step to troubleshooting this issue is to attempt to replicate the problems.
Attempt to send another test message to this user via a REST API request, or through the API Explorer in the Twilio Console.
We have 2 React Native app are using AWS Cognito for authentication. We use library react-native-aws-cognito-js in our code. The apps are working fine until these 2 days. Apps are experiencing intermittent "Internal Server Error".
How can I find more information about this error? Any tool can help us pinpoint the cause?
Update
From CloudTrail, each API call has an event "CreateNetworkInterface". Many of such API calls have error code "Client.NetworkInterfaceLimitExceeded". What is the cause and solution to this?
According to this AWS Doc (in Chinese), CloudWatch will not write to log when error is due to insufficient IP/ENI. That explains the increase in error number but no logs in CloudWatch.
Upate 2
We have found a scheduled Lambda job which may exhausted IP addresses. We stopped the batch job. But still can't have too many user login to server due to "Client.NetworkInterfaceLimitExceeded" error. I realized that there are many "CreateNetworkInterface" event and few "DeleteNetworkInterface" event. How can I "clean up / reset" all network interface in VPC?
Short answer: Cloud Trail.
Long answer with a suggestion
Assuming your application code is fine, most likely the cause of your 500 error is based on Cognito's initial limitations (e.g., number of calls per user): https://docs.aws.amazon.com/cognito/latest/developerguide/limits.html.
AWS suggests to use Cloud Trail, for logging Api calls.
However I would suggest, to prove the limitations first, add some logs around the api call yourself, and in development you could call your app/api with a high number of calls; and most likely you will see the 500 error due to the limitations.
You could do the following in the terminal:
for i in `seq 1 1000`; do curl --cookie SecureCookie=TokenValueFromAWS http://localhost:desirablePort/SecuredPath; done