Hello,
There is an issue with the installation configuration. I set multiple .json files in /etc/sensu/conf.d but uciwa read /etc/sensu folder and can’t start. If i put my uchiwa.json in conf.d and modify the init script of uchiwa this doesn’t work anymore.
Is there a fix ?
thank you
Hi,
Uchiwa is configured to use the /etc/sensu/uchiwa.json file. If you move your configuration to this location, does Uchiwa properly start? If not, please provide us more information such as error logs and the exact configuration used so we can help you troubleshoot.
Thanks
···
On Friday, December 5, 2014 7:56:26 AM UTC-5, Doe John wrote:
Hello,
There is an issue with the installation configuration. I set multiple .json files in /etc/sensu/conf.d but uciwa read /etc/sensu folder and can’t start. If i put my uchiwa.json in conf.d and modify the init script of uchiwa this doesn’t work anymore.
Is there a fix ?
thank you
Hello,
Thank you for you answer.
I installed the last version of Sensu/Uchiwa on Debian Wheezy.
I create separate json configuration files and put them in /etc/sensu/conf.d (e.g : redis.json, client.json, api.json)
When you install uchiwa (apt-get install uchiwa) it put directly the file in /etc/sensu/ so i moved it in conf.d like the others.
When i start uchiwa nothing happens, there is no logs ofr uchiwa, no uchiwa running process. The workaround i find is to modify the /etc/init.d/uchiwa to point to my exact location
So the multiple choice configuration doesn't works with uchiwa.json, if you put the file in conf.d the deamon doesn't starts
Thank you for your help
Regards,
johnnyb
···
On 12/06/2014 07:41 PM, Simon Plourde wrote:
Hi,
Uchiwa is configured to use the /etc/sensu/uchiwa.json file. If you move your configuration to this location, does Uchiwa properly start? If not, please provide us more information such as error logs and the exact configuration used so we can help you troubleshoot.
Thanks
On Friday, December 5, 2014 7:56:26 AM UTC-5, Doe John wrote:
Hello,
There is an issue with the installation configuration. I set
multiple .json files in /etc/sensu/conf.d but uciwa read
/etc/sensu folder and can't start. If i put my uchiwa.json in
conf.d and modify the init script of uchiwa this doesn't work anymore.
Is there a fix ?
thank you
Hello,
The issue persists with Uchiwa
All my file conf are in conf.d
I have this output log : “Output”:“Error: could not read config file /etc/sensu/uchiwa.json.”}
There is no uchiwa.json in /etc/sensu/ i renamed it with .old
Uchiwa does’t look at conf.d directory
Is there a fix ?
Thank you
···
Le vendredi 5 décembre 2014 13:56:26 UTC+1, Doe John a écrit :
Hello,
There is an issue with the installation configuration. I set multiple .json files in /etc/sensu/conf.d but uciwa read /etc/sensu folder and can’t start. If i put my uchiwa.json in conf.d and modify the init script of uchiwa this doesn’t work anymore.
Is there a fix ?
thank you
Hi,
Uchiwa will indeed look for the /etc/sensu/uchiwa.json file unless you modify the init script. This is an expected behavior since it’s an independent third party tool and the conf.d folder is used to specify the connection information used by the sensu components (rabbitmq, redis, etc.)
Regards,
···
On Saturday, December 27, 2014 12:14:44 PM UTC-5, Doe John wrote:
Hello,
The issue persists with Uchiwa
All my file conf are in conf.d
I have this output log : “Output”:“Error: could not read config file /etc/sensu/uchiwa.json.”}
There is no uchiwa.json in /etc/sensu/ i renamed it with .old
Uchiwa does’t look at conf.d directory
Is there a fix ?
Thank you
Le vendredi 5 décembre 2014 13:56:26 UTC+1, Doe John a écrit :
Hello,
There is an issue with the installation configuration. I set multiple .json files in /etc/sensu/conf.d but uciwa read /etc/sensu folder and can’t start. If i put my uchiwa.json in conf.d and modify the init script of uchiwa this doesn’t work anymore.
Is there a fix ?
thank you
Hello Simon
Thank you for your reply
I think it will be very usefull if someone write this in the documentation.
In this tutorial they use conf.d without init script modification, it’s weird…
i know now that uchiwa.json need to stay in /etc/sensu directory
regards
···
Le mardi 30 décembre 2014 23:06:11 UTC+1, Simon Plourde a écrit :
Hi,
Uchiwa will indeed look for the /etc/sensu/uchiwa.json file unless you modify the init script. This is an expected behavior since it’s an independent third party tool and the conf.d folder is used to specify the connection information used by the sensu components (rabbitmq, redis, etc.)
Regards,
On Saturday, December 27, 2014 12:14:44 PM UTC-5, Doe John wrote:
Hello,
The issue persists with Uchiwa
All my file conf are in conf.d
I have this output log : “Output”:“Error: could not read config file /etc/sensu/uchiwa.json.”}
There is no uchiwa.json in /etc/sensu/ i renamed it with .old
Uchiwa does’t look at conf.d directory
Is there a fix ?
Thank you
Le vendredi 5 décembre 2014 13:56:26 UTC+1, Doe John a écrit :
Hello,
There is an issue with the installation configuration. I set multiple .json files in /etc/sensu/conf.d but uciwa read /etc/sensu folder and can’t start. If i put my uchiwa.json in conf.d and modify the init script of uchiwa this doesn’t work anymore.
Is there a fix ?
thank you
Hi John,
Yes, the Digital Ocean tutorial has an error with the path, it was reported on the comments section but never corrected.
The documentation for the Uchiwa packages is located here: http://sensuapp.org/docs/latest/dashboards_uchiwa
Regards,
···
On Tuesday, December 30, 2014 5:16:21 PM UTC-5, Doe John wrote:
Hello Simon
Thank you for your reply
I think it will be very usefull if someone write this in the documentation.
In this tutorial they use conf.d without init script modification, it’s weird…
https://www.digitalocean.com/community/tutorials/how-to-configure-sensu-monitoring-rabbitmq-and-redis-on-ubuntu-14-04
i know now that uchiwa.json need to stay in /etc/sensu directory
regards
Le mardi 30 décembre 2014 23:06:11 UTC+1, Simon Plourde a écrit :
Hi,
Uchiwa will indeed look for the /etc/sensu/uchiwa.json file unless you modify the init script. This is an expected behavior since it’s an independent third party tool and the conf.d folder is used to specify the connection information used by the sensu components (rabbitmq, redis, etc.)
Regards,
On Saturday, December 27, 2014 12:14:44 PM UTC-5, Doe John wrote:
Hello,
The issue persists with Uchiwa
All my file conf are in conf.d
I have this output log : “Output”:“Error: could not read config file /etc/sensu/uchiwa.json.”}
There is no uchiwa.json in /etc/sensu/ i renamed it with .old
Uchiwa does’t look at conf.d directory
Is there a fix ?
Thank you
Le vendredi 5 décembre 2014 13:56:26 UTC+1, Doe John a écrit :
Hello,
There is an issue with the installation configuration. I set multiple .json files in /etc/sensu/conf.d but uciwa read /etc/sensu folder and can’t start. If i put my uchiwa.json in conf.d and modify the init script of uchiwa this doesn’t work anymore.
Is there a fix ?
thank you