tCollector cannot connect to OpenTSDB

50 views
Skip to first unread message

Frank Herrman

unread,
Nov 28, 2016, 4:45:13 PM11/28/16
to OpenTSDB
Hi,

I successfully installed and ran an OpenTSDB server with tCollector. I am now trying to set-up a second server which seems to be running fine. I can access OpenTSDB through telnet (also through localhost:4242 and ::1:4242), I can visit the web interface etc. So OpenTSDB seems to be running.

Still tCollector is not starting. I have set the 'verbose' option to see what is happening, and I notice it keeps trying to connect to OpenTSDB every minute:

2016-11-28 22:34:24,640 tcollector[28793] DEBUG: Connection to ('::1', 4242, 0, 0) was successful
2016-11-28 22:34:24,640 tcollector[28793] DEBUG: verifying our TSD connection is alive
2016-11-28 22:35:24,643 tcollector[28793] DEBUG: verifying our TSD connection is alive
2016-11-28 22:36:24,645 tcollector[28793] DEBUG: verifying our TSD connection is alive
(..)


When I execute ´version' through telnet manually it just returns the OpenTSDB issue, just like you would expect. Why is it tCollector can't seem to do the same?

Everything runs on the same server as you probably have guessed. Thanks!

Jonathan Creasy

unread,
Nov 28, 2016, 4:59:33 PM11/28/16
to Frank Herrman, OpenTSDB
That looks fine, it's just a heartbeat. Are you seeing any metrics?

Frank Herrman

unread,
Nov 29, 2016, 1:09:15 AM11/29/16
to OpenTSDB, f.he...@typify.nl
Ah ok, so no problem there then. Unfortunately, I don't see any metrics. In the tcollector/collectors/0/ folder I have one python script. This doesn't get executed at all. On the other server (which runs an older version of tCollector I must admit) shows 'Respawning myscript.py' every 15 seconds. I do not see that happen on the new server.

Op maandag 28 november 2016 22:59:33 UTC+1 schreef Jonathan Creasy:

Frank Herrman

unread,
Nov 29, 2016, 5:49:47 AM11/29/16
to OpenTSDB, f.he...@typify.nl
I found the issue myself..feel kinda stupid for not noticing, but after I went debugging through tcollector.py I found out it checked for access rights on the collectors:

if os.path.isfile(filename) and os.access(filename, os.X_OK):

My file did not have execute access. A simple chmod +x did the trick.

Thanks for your help.

Op dinsdag 29 november 2016 07:09:15 UTC+1 schreef Frank Herrman:
Reply all
Reply to author
Forward
0 new messages