Miguel Carrillo added a comment - 29/Oct/14 5:33 PM Thanks ,Pedro. Something to add to the ticket http://130.206.126.4:8080 < http://130.206.126.4:8080/AuthoringTool/Main.html > ... is ugly Please use DNS entries El 29/10/2014 17:23, Pedro Alves escribió: Hi, I'm unable to access the CEP GE Proton Development Web UI launching instance from cep blueprint template.Instance id: 24c57801-6045-4dc6-9883-b39317fed472, region: Spain. Steps: -clone "cep" blueprint template from catalog: https://cloud.lab.fi-ware.org/#nova/blueprints/catalog/ -update tier so the keypair is added to the instance -launch cloned blueprint template -associate floating IP to instance -try the Web UI url using the public ip: http://130.206.126.4:8080/AuthoringTool/Main.html -check if instance security group as rule to open port 80: ok Result: the proton web UI web page is not accessible. Expected result: web page with CEP GE Proton Development Web UI. I connected to the instance via SSH and was able to collect some logs (tomcat, chef client), see attachment. From the logs I can see the tomcat is unable to start due to an undefined port(WARNING: [SetPropertiesRule] {Server} Setting property 'port' to '' did not find a matching property.). Probably this is related to an undefined port in tomcat /var/lib/tomcat6/conf/server.xml in line (<Server port="" shutdown="SHUTDOWN"> , port is not defined). This file is managed by chef, if I set the port chef resets the file and unsets the port. Responsible: OneSource Description: Unable to access CEP GE Proton Development Web UI when launching instance from blueprint template named "cep" Tested GE(s): CEP Environment: FIWARE Lab Instance: private instance Regards, – Pedro Alves pgalves@onesource.pt< pgalves@onesource.pt > http://onesource.pt < http://onesource.pt/ >

Fabiana Fournier added a comment - 05/Nov/14 9:37 AM Thank you. I open the following bug to investigate the initialization issue of a CEP instance that is created from a template http://jira.fi-ware.org/browse/DATA-39