Lots of error on the remote log server...

[hsafe]

Hi,
Anyone has any idea why am receiving so many below message on the remote server logger from artillery STD-IN?
2017-11-04T11:05:53.490394+03:30 Received URL Error, Reason: [Errno socket error] [Errno 110] Connection timed `
The two servers are on the same VLAN and both are monitored on the Zenoss monitoring server with no unavailability notifications....

[obnosis]

Hamid, This socket error means: Received URL Error: Reason [Errno socket error] [Error 110] Connection Timeout: 1) General socket debug Techniques: https://stackoverflow.com/questions/12145536/how-can-i-debug-what-is-causing-a-connection-refused-or-a-connection-time-out Hints: Do a manual telnet to that port/server? Verify listening on correct port on target machine? 2) Can you do a traceback? https://docs.python.org/2/library/traceback.html Hint: Traceback will indicate exactly what and why you are getting this timeout? Wicked good traceback snippets: https://stackoverflow.com/questions/3702675/how-to-print-the-full-traceback-without-halting-the-program 3) Torque kernel Timeout Values: https://www.cyberciti.biz/faq/enable-tcp-syn-cookie-protection/ Verify that SYN Cookie Protection is NOT turned on in /etc/synctl.conf: net.ipv4.tcp_syncookies = 0 down voteaccepted If you have chosen a random, but valid, IP address and port, socket.connect() will attempt to make a connection to that endpoint. By default, if no explicit timeout is set for the socket, it will block while doing so and eventually timeout, raising exception socket.error: [Errno 110] Connection timed out. The default timeout on most machines is 120 seconds. Perhaps you are not waiting long enough for socket.connect() to return (or timeout)? Breaking out of the script will also cause 110 error. You can try reducing the timeout in the script like this: import socket s = socket.socket() s.settimeout(5) # 5 secondstry: s.connect(('123.123.123.123', 12345)) # "random" IP address and portexcept socket.error, exc: print "Caught exception socket.error : %s" % exc Note that if a timeout is explicitly set for the socket, the exception will be socket.timeout which is derived from socket.error and will therefore be caught by the above except clause. Timeout values are kernel defined. Effectively the number of attempts to get a response to the SYN packet displayed/set here: cat /proc/sys/net/ipv4/tcp_syn_retries. The retires are usually sent using an exponential backoff algorithm which increases the interval between retries, e.g. 3 , 7 , 15, 31 secs. Where a Linux system has tcp_syn_retries set to 5 which works out to be approx 120 seconds Reference: https://github.com/BinaryDefense/artillery (503) 754-4452 (623) 238-8447 IT Clowns Limited, INC is a 501(3)c Non-Profit it-clowns.com

…

On Sat, Nov 4, 2017 at 2:02 AM, Hamid Safe ***@***.***> wrote: Hi, Anyone has any idea why am receiving so many below message on the remote server logger from artillery STD-IN? 2017-11-04T11:05:53.490394+03:30 Received URL Error, Reason: [Errno socket error] [Errno 110] Connection timed ` The two servers are on the same VLAN and both are monitored on the Zenoss monitoring server with no unavailability notifications.... — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#78>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABPyKVBcoM3mQjjYw5IBwWrhno2jTgaWks5szCgZgaJpZM4QR8Oj> .