[openstack-dev] [masakari] problems starting up masakari instance monitoring in devstack @ master

Rikimaru Honjo honjo.rikimaru at po.ntt-tx.co.jp
Thu Dec 7 05:24:44 UTC 2017


Hello Greg,

I forgot to tell you.

Please use process_list.yaml instead of proc.list.sample.

On 2017/12/07 14:03, Rikimaru Honjo wrote:
> Hello Greg,
> 
> Please use masakarimonitors.conf instead of hostmonitor.conf and processmonitor.conf.
> You can generate it by "tox -egenconfig".
> 
> hostmonitor.conf and processmonitor.conf are used for monitors implemented by shell script.
> masakarimonitors.conf is a configuration file for monitors implemented by python that you installed.
> 
> And, we are preparing setting guides.
> Please see it if you are good.
> 
> masakari:
> https://review.openstack.org/#/c/489570/
> 
> masakari-monitors:
> https://review.openstack.org/#/c/489095/
> 
> Best regards,
> 
> On 2017/12/06 22:48, Waines, Greg wrote:
>> I am just getting started working with masakari.
>> I am working on master.
>>
>> I have setup Masakari in Devstack (see details at end of email) ... which starts up masakari-engine and masakari-api processes.
>>
>> I have git cloned the masakari-monitors and started them up (roughly) following the instructions at https://github.com/openstack/masakari-monitors .
>> Specifically:
>> # install & startup monitors
>> cd
>> git clone https://github.com/openstack/masakari-monitors.git
>> cd masakari-monitors
>> sudo python setup.py install
>> cd
>> sudo mkdir /etc/masakarimonitors
>> sudo cp ~/masakari-monitors/etc/masakarimonitors/hostmonitor.conf.sample /etc/masakarimonitors/hostmonitor.conf
>> sudo cp ~/masakari-monitors/etc/masakarimonitors/processmonitor.conf.sample /etc/masakarimonitors/processmonitor.conf
>> sudo cp ~/masakari-monitors/etc/masakarimonitors/proc.list.sample /etc/masakarimonitors/proc.list
>> cd ~/masakari-monitors/masakarimonitors/cmd
>> sudo masakari-processmonitor.sh /etc/masakarimonitors/processmonitor.conf /etc/masakarimonitors/proc.list &
>> sudo masakari-hostmonitor.sh /etc/masakarimonitors/hostmonitor.conf &
>> sudo /usr/bin/python ./instancemonitor.py &
>>
>> However the instancemonitor.py starts and exits ... and does not appear to start any process(es) ... with no error messages and no log file.
>>
>> Is this the correct way to startup masakari instance monitoring ?
>>
>> Greg.
>>
>>
>>
>>
>> My Masakari setup in Devstack
>>
>> sudo useradd -s /bin/bash -d /opt/stack -m stack
>> echo "stack ALL=(ALL) NOPASSWD: ALL" | sudo tee /etc/sudoers.d/stack
>> sudo su - stack
>>
>> git clone https://github.com/openstack-dev/devstack
>> cd devstack
>>
>>                                                  local.conf file:
>> [[local|localrc]]
>> ADMIN_PASSWORD=admin
>> DATABASE_PASSWORD=admin
>> RABBIT_PASSWORD=admin
>> SERVICE_PASSWORD=admin
>> # setup Neutron services
>> disable_service n-net
>> enable_service q-svc
>> enable_service q-agt
>> enable_service q-dhcp
>> enable_service q-l3
>> enable_service q-meta
>> # ceilometer
>> enable_plugin ceilometer https://git.openstack.org/openstack/ceilometer
>> enable_plugin aodh https://git.openstack.org/openstack/aodh
>> # heat
>> enable_plugin heat https://git.openstack.org/openstack/heat
>> # vitrage
>> enable_plugin vitrage https://git.openstack.org/openstack/vitrage
>> enable_plugin vitrage-dashboard https://git.openstack.org/openstack/vitrage-dashboard
>> # masakari
>> enable_plugin masakari git://git.openstack.org/openstack/masakari
>>
>>
>> ./stack.sh
>>
>>
>>
>>
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> 

-- 
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
Rikimaru Honjo
E-mail:honjo.rikimaru at po.ntt-tx.co.jp




More information about the OpenStack-dev mailing list