#influxdb

I love InfluxDB and Telegraf!!!!

so awesome

So uh, I can't really start influxdb as a service. I can see the process running, but then it disappears and quickly comes back. I think it repeatedly tries to load files?

Reeckz: checked syslog for messages?

Seems like Influx is having issues reading a symlink?

Line in question: influxd[15578]: run: open server: open service: open /etc/letsencrypt/live/monit.ams.rem.uz/fullchain.pem: permission denied

I checked permissions and influx has access.

Seems pretty obvious that some component in that path does not...

check each directory on the way to both the symlink and its target

(as the user running influxdb)

Thank you blahdeblah !

I just copied it into /etc/influxdb

That works, I guess; as long as you're not expecting it to update regularly or something

Once every 90 days.

Of course; in that case, I strongly recommend against just copying the file

Why is that?

Because then you have to recopy the file every time you renew your letsencrypt certificate instead of just restarting influxdb

Although, depending on how letsencrypt manages permissions, that may be necessary anyway

It's the same user that runs certbot

But if it were me, I'd at least try to find out whether it's possible to keep only one local copy of the key

Yeah, I can't figure this out.

nathanielc: i found my problem (not sure if it is an architectural one). i can only create batch tasks in kapacitor for collectd data, stream is not working. For future reference https://paste.krebsco.de/EqCqx3kY is what is working for me

I've recently upgraded to telegraf 1.2.0 and I'm seeing these errors in my telegraf log: E! ERROR in input [inputs.exec]: Errors encountered: [metric parsing error, reason: [buffer too short], buffer: [], index: [0]]

I've verified that the metric line is correct by trying to inject it directly using the influx cli command

I think it might be related to the changes regarding newline that has been done not so long ago

is it possible to increase debug level to figure out exactly where/why the parse fails?

I figured out what the issue is. If a program run by inputs.exec with data format "influx" outputs no lines, this error will show up

what should a line protocol script output if it has no lines to output (e.g. because the monitoring service is not installed)

?