[Fiware-lab-federation-nodes] fiware.org SSL certificate & monitoring tools: 2 questions

Giorgio Robino giorgio.robino at cnit.it
Thu Oct 13 17:14:01 CEST 2016


Dear fiware-lab node-owners collegues

Two questions:

1. CERTIFICATE ISSUE
--------------------
Is the certificate renew issue solved ?

I'm asking because the monitoring tool script:

root at controller03:~# ./fiware-check-monitoring.sh

since monday report a "Could not get auth token" error:
.....
Check Monasca Agent credentials for 'monasca_user' role... curl: (60)  
SSL certificate problem: certificate has expired
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
No JSON object could be decoded
Could not get auth token
.....

and all monasca measurements give errors.


2. LOCAL NODE SANITY CHECK
--------------------------
A more general devops question/suggestion:
A part the monitoring script verification tools :),
how do you monit your openstack/fiware-lab environment sanity check?

Do you suggest any script more smart than check services status and  
grep errors on log files, with something like:

$ tail -f  
/var/log/{ceilometer,cinder,glance,keystone,mysql,neutron,nova,openvswitch,rabbitmq}/*.log /var/log/syslog | grep  
ERROR

?

Any help welcome!
Thanks
giorgio


-- 
--

tel. 010 353 2797




More information about the Fiware-lab-federation-nodes mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy