-
Notifications
You must be signed in to change notification settings - Fork 1
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
[newcomer] geoip server intermittent failures #1
Comments
I was not able to replicate this issue. can you please mention some details. |
I think the thing to do is to create a Repy program that periodically polls the server, e.g. five times in a row, every hour of the day, for two weeks, and then see if the problem exists. I suggest you run this on a Seattle node. |
can this be done through cron? i think we can add this script to cron if possible |
Just write a Repy program. We can reuse that as an integration test later. |
I was not able to contact the servers with openconnection so i tried to write python script to connect and get response with them for around 100 times and each time i received success response. I think at present there is no issue and ticket can be closed. |
How come |
i did try to redo all the steps where i found that geoipservers only accepts connection on port 12679 which was later added into restrictions,test. After execution i tried to print openconnection instance and i got the following traceback :- abhishek@abhishek-VirtualBox:~/seattlelib_v2/RUNNABLE$ python repy.py restrictions.test poll_geoservers.r2py I think i can open connection successfully. |
when i try to run the script intermittently i receive below error:- Following is a full traceback, and a user traceback. Full debugging traceback: User traceback: I think somehow openconnection waits for some timeout may be like TCP FIN for graceful termination and then closes connection but if i run the code before graceful termination it gives error as mentioned in above trace. |
You should be able to work around this by using a different source port for the next connection. |
You are using 12345 as the destport in |
yes i am using 12345 as dest port. is that incorrect? |
Yep. From the issue description:
Use destport 12679. |
yes it connects on that but if i try to re-run program with same port it gives error as connection already exists.. |
Use a different source port for the next connection (see also our recent Skype conversation). |
Any updates from you, @asm582 ? |
tried to run sample code but i received the below exception:- User traceback: Exception (with class 'exception_hierarchy.TimeoutError'): Timed-out connecting to the remote host! |
Try with |
I have used the httpretrieve.r2py file that you mentioned and implemented the below code:- https://github.com/asm582/seattleissues/blob/master/poll_geoserver.r2py Due to TIME_WAIT state of TCP have made a call to sleep for 65 seconds for socket to terminate successfully. while polling the servers we see that geoipserver.poly.edu fails to give response intermittently. abhishek@abhishek-VirtualBox:~/seattlelib_v2/RUNNABLE$ python repy.py restrictions.test dylink.r2py poll_geoservers.r2py geoipserver.poly.edu geoipserver.poly.edu |
Using library geoip_client.repy, calls to geoip_record_by_addr() (and geoip_record_by_name()) get connection refused error intermittently:
111 Connection refused
The two geoip servers used are http://geoipserver.poly.edu:12679, http://geoipserver2.poly.edu:12679
However, sometimes they do respond to geoip requests.
The text was updated successfully, but these errors were encountered: