Timeline for Avoid a faulty server behind load balancer
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 2, 2015 at 13:04 | comment | added | Segers-Ian | So as follow up, you did not entirely answer the question but you were correct on that Twitter could not have been the culprit itself. After lots of troubleshooting with the admins from the Server Park that hots our hardware we discovered that a former employee had requested a firewall block (by the Hosting company itself) on all low port numbers for outgoing traffic. After we removed it everything went to normal. | |
| Oct 2, 2015 at 13:02 | vote | accept | Segers-Ian | ||
| Sep 25, 2015 at 9:02 | comment | added | Segers-Ian | I have been screening all the log files multiple times for finding concentrations of limit exceeding and we programmed very defensively to not hit the limits since Twitter API provides a good mechanism to get the status quo on our API limit status. Of course we can always have leak, but we didn't scale recently with users and changes in a solution that worked well for a long time. So it can never be excluded that, that is the issue, but I am very confident :s. But Appreciate the feedback. | |
| Sep 25, 2015 at 8:45 | history | answered | Craig Watson | CC BY-SA 3.0 |