Fail to timeout?

[daknob]

Just ran a copy of this project with a changed sites.json file. All sites are valid and can be DNS resolved. I have 33 websites in the list, but one of them (no idea which) causes the script to stay forever at 32/33. It keeps repeating itself forever. Socket timeout works on other websites.

[benjaminp]

What site is causing problems?

On Sun, Jan 18, 2015, at 22:03, DaKnOb wrote:

Just ran a copy of this project with a changed sites.json file. All sites are valid and can be DNS resolved. I have 33 websites in the list, but one of them (no idea which) causes the script to stay forever at 32/33. It keeps repeating itself forever. Socket timeout works on other websites.

---

Reply to this email directly or view it on GitHub: https://github.com/gutworth/httpswatch/issues/15

[daknob]

I'd be glad to provide the URL of the website but I added all 33 websites to the JSON and then ran the script, which means I have no way of knowing this, unless I remove the sites one-by-one and see which one was it. Any way to print the site each thread processes in the progress that's printed every second for debugging purposes? If not, I'll have to remove the sites one-by-one. Thanks

[daknob]

The domain is www.tuc.gr which seems to be causing the trouble. It is resolvable, with port 443 open but if you send anything via telnet it simply doesn't reply. Guess we should add more than socket timeout?

[benjaminp]

I get EOF occurred in violation of protocol (_ssl.c:600). Maybe you have an old version of openssl, which is hanging?

[daknob]

It's OpenSSL 1.0.1e w/ debian security patches.. Maybe that's it..

[daknob]

Neither OpenSSL v1.0.1j nor OpenSSL v1.0.1k seem to fix the problem..