Did you manually start the InfluxDB process using something similar to the command below?
``` sudo influxd -config /etc/influxdb/influxdb.conf ``` If you ran the above command as root, it could have potentially modified the permissions on the files. Make sure that you only start the InfluxDB process via systemctl, and not manually running the `influxd` command. Thanks, Ross On Fri, Jul 29, 2016 at 1:04 PM, <[email protected]> wrote: > > Definitely looks like a permissions error ! > I am getting a similar message on the SSL certificate file now: > > ``` > run: open server: open service: open /etc/ssl/influxdb.pem: permission > denied > ``` > > But applying the same chown command on the file causes the service to run > again. > > > > I find this annoying and weird. > How do you suggest I go about finding out why the permissions were changed? > (I never changed them as root for sure!) > > Thanks, > Ali > > > On Friday, July 29, 2016 at 9:38:53 PM UTC+4, Ross McDonald wrote: > > Since it's a permissions issues, you'll need to `chown` the data > directory to restore access: > > > > > > ``` > > sudo chown -R influxdb:influxdb /var/lib/influxdb > > ``` > > > > > > You may also want to look into how or why the permissions were changed. > > > > > > Thanks, > > Ross > > > > > > On Fri, Jul 29, 2016 at 12:35 PM, <[email protected]> wrote: > > > > Yes, a lot of permission denied errors : (logged in as root BTW) > > > > > > > > [run] 2016/07/29 21:33:06 Go version go1.6.2, GOMAXPROCS set to 4 > > > > [run] 2016/07/29 21:33:07 Using configuration at: > /etc/influxdb/influxdb.conf > > > > run: create server: open /var/lib/influxdb/meta/meta.db: permission > denied > > > > [run] 2016/07/29 21:33:07 InfluxDB starting, version 0.13.0, branch > 0.13, commit e57fb88a051ee40fd9277094345fbd47bb4783ce > > > > [run] 2016/07/29 21:33:07 Go version go1.6.2, GOMAXPROCS set to 4 > > > > [run] 2016/07/29 21:33:07 Using configuration at: > /etc/influxdb/influxdb.conf > > > > run: create server: open /var/lib/influxdb/meta/meta.db: permission > denied > > > > [run] 2016/07/29 21:33:07 InfluxDB starting, version 0.13.0, branch > 0.13, commit e57fb88a051ee40fd9277094345fbd47bb4783ce > > > > [run] 2016/07/29 21:33:07 Go version go1.6.2, GOMAXPROCS set to 4 > > > > [run] 2016/07/29 21:33:07 Using configuration at: > /etc/influxdb/influxdb.conf > > > > run: create server: open /var/lib/influxdb/meta/meta.db: permission > denied > > > > [run] 2016/07/29 21:33:07 InfluxDB starting, version 0.13.0, branch > 0.13, commit e57fb88a051ee40fd9277094345fbd47bb4783ce > > > > [run] 2016/07/29 21:33:07 Go version go1.6.2, GOMAXPROCS set to 4 > > > > [run] 2016/07/29 21:33:07 Using configuration at: > /etc/influxdb/influxdb.conf > > > > run: create server: open /var/lib/influxdb/meta/meta.db: permission > denied > > > > [run] 2016/07/29 21:33:08 InfluxDB starting, version 0.13.0, branch > 0.13, commit e57fb88a051ee40fd9277094345fbd47bb4783ce > > > > [run] 2016/07/29 21:33:08 Go version go1.6.2, GOMAXPROCS set to 4 > > > > [run] 2016/07/29 21:33:08 Using configuration at: > /etc/influxdb/influxdb.conf > > > > > > > > > > > > > > > > > > > > > > > > > > On Friday, July 29, 2016 at 9:29:37 PM UTC+4, Ross McDonald wrote: > > > > With 0.13.0 on RHEL 7, the logs were still being redirected to the > `/var/log/influxdb` directory. Are there any relevant messages in the > `/var/log/influxdb/influxd.log` file? > > > > > > Thanks, > > Ross > > > > > > > > > > On Fri, Jul 29, 2016 at 12:25 PM, <[email protected]> wrote: > > > > > > I am running influxdb on a RHLE 7 machine. > > > > I installed a fresh 0.13.0 version of influxdb. > > > > After I created databases, users and retention policies, I was able to > write to the database from a remote client using the HTTP API successfully. > > > > > > > > However, when I enabled HTTPS in the config file, I tried restarting the > service but it failed, giving me errors similar to the following: > > > > > > > > > > > > > > > > ● influxdb.service - InfluxDB is an open-source, distributed, time > series database > > > > Loaded: loaded (/usr/lib/systemd/system/influxdb.service; disabled; > vendor preset: disabled) > > > > Active: failed (Result: start-limit) since Fri 2016-07-29 20:57:19 > GST; 1s ago > > > > Docs: https://docs.influxdata.com/influxdb/ > > > > Process: 53595 ExecStart=/bin/sh -c /usr/bin/influxd -config > /etc/influxdb/influxdb.conf ${INFLUXD_OPTS} >>${STDOUT} 2>>${STDERR} > (code=exited, status=1/FAILURE) > > > > Main PID: 53595 (code=exited, status=1/FAILURE) > > > > > > > > Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: Unit influxdb.service entered > failed state. > > > > Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: influxdb.service failed. > > > > Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: influxdb.service holdoff time > over, scheduling restart. > > > > Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: start request repeated too > quickly for influxdb.service > > > > Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: Failed to start InfluxDB is > an open-source, distributed, time series database. > > > > Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: Unit influxdb.service entered > failed state. > > > > Jul 29 20:57:19 hrc-cse-perf01 systemd[1]: influxdb.service failed. > > > > > > > > > > > > I managed to get it to start again by using the command influx (and > write to database using HTTPS this is why I doubt this is from HTTPS ) , > but it still causes the service to fail sometimes (when I change something > in the config file and try to restart service again.) > > > > > > > > Now, I can't get the service to work again. > > > > > > > > This problem has been bugging me for quite sometime now. > > > > Tried some usual obvious commands related to systems, but with no use: > > > > > > > > systemctl restart influxdb.service > > > > > > > > systemctl stop influxdb.service > > > > systemctl reset-faild influxdb.service > > > > then > > > > systemctl start influxdb.service > > > > > > > > and > > > > systemctl disable influxdb.service > > > > > > > > NOTHING CHANGES. > > > > > > > > > > > > This is the result of journalctl -xe in case it's of any use (although > looks similar to the first error): > > > > > > > > -- Subject: Unit influxdb.service has begun start-up > > > > -- Defined-By: systemd > > > > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > > > > -- > > > > -- Unit influxdb.service has begun starting up. > > > > Jul 29 21:16:56 hrc-cse-perf01 systemd[1]: influxdb.service: main > process exited, code=exited, status=1/FAILURE > > > > Jul 29 21:16:56 hrc-cse-perf01 systemd[1]: Unit influxdb.service entered > failed state. > > > > Jul 29 21:16:56 hrc-cse-perf01 systemd[1]: influxdb.service failed. > > > > Jul 29 21:16:57 hrc-cse-perf01 systemd[1]: influxdb.service holdoff time > over, scheduling restart. > > > > Jul 29 21:16:57 hrc-cse-perf01 systemd[1]: Cannot add dependency job for > unit firewalld.service, ignoring: Unit firewalld.service is ma > > > > Jul 29 21:16:57 hrc-cse-perf01 systemd[1]: start request repeated too > quickly for influxdb.service > > > > Jul 29 21:16:57 hrc-cse-perf01 systemd[1]: Failed to start InfluxDB is > an open-source, distributed, time series database. > > > > -- Subject: Unit influxdb.service has failed > > > > -- Defined-By: systemd > > > > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > > > > -- > > > > -- Unit influxdb.service has failed. > > > > > > > > -- > > > > -- The result is failed. > > > > > > > > -- > > > > Remember to include the InfluxDB version number with all issue reports > > > > --- > > > > You received this message because you are subscribed to the Google > Groups "InfluxDB" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > > > To post to this group, send email to [email protected]. > > > > Visit this group at https://groups.google.com/group/influxdb. > > > > To view this discussion on the web visit > https://groups.google.com/d/msgid/influxdb/712fa317-99aa-4281-b0b8-82cd6c18645a%40googlegroups.com > . > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > > > > > > > > > > -- > > > > Remember to include the InfluxDB version number with all issue reports > > > > --- > > > > You received this message because you are subscribed to the Google > Groups "InfluxDB" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > > > To post to this group, send email to [email protected]. > > > > Visit this group at https://groups.google.com/group/influxdb. > > > > To view this discussion on the web visit > https://groups.google.com/d/msgid/influxdb/8d9a03f7-7bf9-4081-a457-caccc9020daa%40googlegroups.com > . > > > > > > > > For more options, visit https://groups.google.com/d/optout. > > -- > Remember to include the InfluxDB version number with all issue reports > --- > You received this message because you are subscribed to the Google Groups > "InfluxDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/influxdb. > To view this discussion on the web visit > https://groups.google.com/d/msgid/influxdb/a0435328-c077-42a9-8d25-f531d5ada30c%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- Remember to include the InfluxDB version number with all issue reports --- You received this message because you are subscribed to the Google Groups "InfluxDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/CAD8sRLDpAao%2BVyA8Tgkep59C76-zfwBkDW0qspXqtRe58g50KA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
