Like lots of people my apps are affected by timeouts from connect(), fql and other apis.
It started on Wednesday 16, 08:00 UTC+00.
It is still unresolved.
Any official comment on this problem ?
http://developers.facebook.com/bugs/182705755149358
2011/11/17 13:38 UTC+01
IsFan
The operation has timed out
2011/11/17 13:05 UTC+01
Fql
The operation has timed out
2011/11/17 12:33 UTC+01
IsFan
The operation has timed out
2011/11/17 07:33 UTC+01
IsVerified
The operation has timed out
...
2011/11/16 21:59 UTC+01
CloseSession
The operation has timed out
...
The facebook officials responded to the facebook thread that they fixed the problem, and it is gone.
Related
I am using dataverse to extract data from CRM into Power BI Power Query. For the past few weeks, there hasn't been any issues with establishing a connection and getting the data. However, just earlier this week, I have been unable to retrieve any sort of data; instead, I encounter the following error -
DataSource.Error: Microsoft SQL: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The wait operation timed out.)
Details:
DataSourceKind=CommonDataService
DataSourcePath=organization CRM web portal here
Message=A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 - The wait operation timed out.)
ErrorCode=-2146232060
Number=258
Class=20
As far as I know, there has not been any changes to my user privileges, or any changes to our servers. Furthermore, by using my personal mobile hotspot, I was able to successfully retrieve all the data from CRM. However, when I swapped back to my office's WiFi, the error occurred again. Is there any way to troubleshoot or check what is the cause of the problem (which is likely my office's WiFi/Network)?
The error Throttling failure: Maximum SigV2 SMTP sending rate exceeded. suddenly started to appear in our .NET application though there were no exceeding any quota (14 mails per second or 50000 per day) in our AWS Sending Statistics.
I can see many similar issues about Throttling – Maximum sending rate exceeded on StackOverflow but I'm confused about SigV2 in my error message.
Searching in other resources like this one gave me the idea that this issue started to happen recently from about October 20, 2020, and there is no exact answer to why this happened. The only solution I can see is to migrate from using SigV2 signing process to the new method.
The question is: Why this happened and can this issue be solved without changes in the application code?
This is not a service quota issue. The issue you are facing is due to excessive authentication requests from your side. This issue will not occur if you renew your SMTP credentials in the SES console to use Sigv4 credentials.
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-credentials.html
As you can see your daily rate exceeded
But you can open a case and increase your maximum rate
Having OTRS queues to run escalations are fine. The thing is, that the tickets stay escalated if the solution time is exceeded.
The thing is sometimes it is a client responsibility to deliver something to close the ticket.
In this case the client gets a response.
How can I reset the escalation time to the time the ticket is replied and the pending is set to a specific date?
So the escalation time will occur e.g. 1 day after the pending date.
Just check https://www.znuny.com/add-ons/znuny4otrs-repository and follow the instructions. After this the package is available the package manager
try the free add-on Znuny4OTRS-EscalationSuspend. Then you can configure states where escalations are suspended. E.g. a state like 'pending customer feedback'
we run a website that obtains location data through the Google Place API. We have 150k daily searches available, which we haven´t met yet as the website has been live for few weeks only. We have suddenly received a 502 error. A notification in the Console says: “The server encountered a temporary error and could not complete your request.”. Is this a temporary error? Is there any suggestions on what we can do? The website hasn’t been available for 40 minutes.
When you receive 5xx status or UNKNOWN_ERROR in the response, you should implement a retrying logic. Google has a following recommendation in their web services documentation:
In rare cases something may go wrong serving your request; you may receive a 4XX or 5XX HTTP response code, or the TCP connection may simply fail somewhere between your client and Google's server. Often it is worthwhile re-trying the request as the followup request may succeed when the original failed. However, it is important not to simply loop repeatedly making requests to Google's servers. This looping behavior can overload the network between your client and Google causing problems for many parties.
A better approach is to retry with increasing delays between attempts. Usually the delay is increased by a multiplicative factor with each attempt, an approach known as Exponential Backoff.
https://developers.google.com/maps/documentation/directions/web-service-best-practices#exponential-backoff
However, if retrying logic with Exponential Backoff doesn't help and the error persists for a long time you should file a bug in Google issue tracker
I hope this addresses your doubt!
UPDATE
There was an issue on Google side yesterday (November 6, 2017), you can refer to the following bug that explains the issue:
https://issuetracker.google.com/issues/68938173
Where can I go look to find the source of a connection reset error? Here are the details:
I have a Clojure applet that uses clj-http.client.
I need to track down what is sending the following error
Feb 14, 2013 5:16:04 PM
org.apache.http.impl.client.DefaultRequestDirector execute
INFO: I/O exception (java.net.SocketException)
caught when processing request: Connection reset
Feb 14, 2013 5:16:04 PM
org.apache.http.impl.client.DefaultRequestDirector execute
INFO: Retrying request
We have looked through the server's IIS logs, and cannot find any error indicating a connection reset. We've also looked at the server's Event Logs, and cannot find an error that matches the error I'm getting in the client. As a matter of fact, the IIS logs look OK. I can see my address verification "GET" requests right in the log.
It's just a guess, though I often get that error message when the web server is configured to respond to the wrong host name. If it is serving for www.example.com/my/service and I open a connection to 1.2.3.4/my/service then it hangs up with "connection reset".