I’ve been running influxdb 1.7.9 for some time and am intermittently seeing ‘connection reset by peer’ messages when sending line protocol data with python
for example:
Traceback (most recent call last):
File “./mdt_client_stats.py”, line 61, in
p=urllib2.urlopen(url+‘/write?db=lustre’,export_stats())
File “/usr/lib64/python2.7/urllib2.py”, line 154, in urlopen
return opener.open(url, data, timeout)
File “/usr/lib64/python2.7/urllib2.py”, line 431, in open
response = self._open(req, data)
File “/usr/lib64/python2.7/urllib2.py”, line 449, in _open
‘_open’, req)
File “/usr/lib64/python2.7/urllib2.py”, line 409, in _call_chain
result = func(*args)
File “/usr/lib64/python2.7/urllib2.py”, line 1258, in https_open
context=self._context, check_hostname=self._check_hostname)
File “/usr/lib64/python2.7/urllib2.py”, line 1214, in do_open
raise URLError(err)
urllib2.URLError: <urlopen error [Errno 104] Connection reset by peer>
Our server is using a wildcard commercial SSL cert, and validates OK. What I’m seeing in the influx server logs are the 401 response (as expected) but nothing else, whereas a successful write has the 401 followed by the authorized 204, ie
[root@glacier ~]# journalctl -f | grep <ip>
May 22 19:40:55 glacier influxd[6573]: [httpd] <ip> - - [22/May/2020:19:40:55 +0800] "POST /write?db=lustre HTTP/1.1" 401 55 "-" "Python-urllib/2.7" 191afc42-9c21-11ea-8eba-ecebb89a8104 69
May 22 19:40:57 glacier influxd[6573]: [httpd] <ip> - - [22/May/2020:19:40:57 +0800] "POST /write?db=lustre HTTP/1.1" 401 55 "-" "Python-urllib/2.7" 1a21e107-9c21-11ea-8ec9-ecebb89a8104 80
May 22 19:40:58 glacier influxd[6573]: [httpd] <ip> - - [22/May/2020:19:40:58 +0800] "POST /write?db=lustre HTTP/1.1" 401 55 "-" "Python-urllib/2.7" 1ae3c255-9c21-11ea-8ed4-ecebb89a8104 79
May 22 19:40:59 glacier influxd[6573]: [httpd] <ip> - - [22/May/2020:19:40:59 +0800] "POST /write?db=lustre HTTP/1.1" 401 55 "-" "Python-urllib/2.7" 1ba3d3c0-9c21-11ea-8ee5-ecebb89a8104 60
May 22 19:41:01 glacier influxd[6573]: [httpd] <ip> - - [22/May/2020:19:41:01 +0800] "POST /write?db=lustre HTTP/1.1" 401 55 "-" "Python-urllib/2.7" 1c782cd6-9c21-11ea-8efd-ecebb89a8104 80
May 22 19:41:01 glacier influxd[6573]: [httpd] <ip> - mdtscript [22/May/2020:19:41:01 +0800] "POST /write?db=lustre HTTP/1.1" 204 0 "-" "Python-urllib/2.7" 1c79ce47-9c21-11ea-8eff-ecebb89a8104 48526
May 22 19:41:03 glacier influxd[6573]: [httpd] <ip> - - [22/May/2020:19:41:03 +0800] "POST /write?db=lustre HTTP/1.1" 401 55 "-" "Python-urllib/2.7" 1df2da63-9c21-11ea-8f45-ecebb89a8104 71
(the above is from me repeatedly running the script on command line from client - it failed 6/7 times)
The script is pushing approximately 2300 points at a time, each with 3 tags and between 1 and 15 entries in the field_set - is this unreasonable? I’m not aware of seeing this when I’m sending fewer points (o 1-5) at a time.
Upgrading to influxdb-1.8.0-1.x86_64 doesn’t seem to have helped (from https://repos.influxdata.com/centos/\$releasever/\$basearch/stable)
Any suggestions?
Andrew
