Hi Salman,

Thanks for your question.

In order to better understand what is going on here could I please ask you to 
provide some more details about the deployment you are using:


*         What version of Clearwater are you using?

*         What topology are you using? What nodes make up your deployment?

On your homer node it would be useful if you could retrieve and send me the 
homer and monit logs, to do this try starting homer again and then download the 
most recent log files contained in /var/log/homer and /var/log/clearwater-monit.

On startup homer should read its configuration file and generate a 
local_settings.py file to mandate what handlers to install. One possibility is 
that this local_settings.py file was never generated. To verify this could you 
please run the command "sudo 
/usr/share/clearwater/infrastructure/scripts/homer" and let me know what the 
output is. You might find that after running this script you are able to start 
the homer process without any errors.

Thanks,

Andrew

From: Clearwater [mailto:[email protected]] On 
Behalf Of Muhammad Shaikh (Salman)
Sent: Monday, April 10, 2017 11:17 PM
To: [email protected]
Subject: [Project Clearwater] Clearwater IMS homers failed to start..

I have net setup running and after the installation of homer it is failed to 
start with error message:

[homer]ubuntu@homer:~$ sudo service homer start
:0: UserWarning: You do not have a working installation of the service_identity 
module: 'No module named service_identity'.  Please install it from 
<https://pypi.python.org/pypi/service_identity> and make sure all of its 
dependencies are satisfied.  Without the service_identity module, Twisted can 
perform only rudimentary TLS client hostname verification.  Many valid 
certificate/hostname mappings may be rejected.
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File 
"/usr/share/clearwater/crest/env/lib/python2.7/site-packages/crest-0.1-py2.7.egg/metaswitch/crest/main.py",
 line 218, in <module>
    standalone()
  File 
"/usr/share/clearwater/crest/env/lib/python2.7/site-packages/crest-0.1-py2.7.egg/metaswitch/crest/main.py",
 line 128, in standalone
    application = create_application()
  File 
"/usr/share/clearwater/crest/env/lib/python2.7/site-packages/crest-0.1-py2.7.egg/metaswitch/crest/main.py",
 line 98, in create_application
    application = cyclone.web.Application(api.get_routes(), **app_settings)
  File 
"/usr/share/clearwater/crest/env/lib/python2.7/site-packages/crest-0.1-py2.7.egg/metaswitch/crest/api/__init__.py",
 line 68, in get_routes
    return sum([load_module(m).ROUTES for m in settings.INSTALLED_HANDLERS], 
[]) + ROUTES
  File 
"/usr/share/clearwater/crest/env/lib/python2.7/site-packages/crest-0.1-py2.7.egg/metaswitch/crest/api/__init__.py",
 line 62, in load_module
    fromlist=["ROUTES"])
ImportError: No module named homestead

I am using Python 2.7.6 and have already installed and updated the 
service_identity modue of python through easy_install and now I get the message 
that it is already up to date:

easy_install service_identity
Searching for service-identity
Best match: service-identity 16.0.0
Processing service_identity-16.0.0-py2.7.egg
service-identity 16.0.0 is already the active version in easy-install.pth

Using /usr/local/lib/python2.7/dist-packages/service_identity-16.0.0-py2.7.egg
Processing dependencies for service-identity
Finished processing dependencies for service-identity

----------------------------------------------------------
Salman Shaikh
NFV Open Lab Architect
Huawei R&D USA
FutureWei Technologies, Inc
Email: [email protected]<mailto:[email protected]>
Mobile: +1 (408) 421-6210
----------------------------------------------------------

_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

Reply via email to