We use proprietary and third party´s cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
Ask Your Question

Nacho's profile - activity

2018-01-12 08:30:37 +0100 received badge  Famous Question (source)
2017-12-14 20:52:49 +0100 received badge  Famous Question (source)
2017-10-25 08:59:17 +0100 received badge  Notable Question (source)
2017-10-19 10:25:09 +0100 received badge  Popular Question (source)
2017-10-19 09:32:28 +0100 commented answer Fiware Lab : How to use the whole disk space at instance Context Broker

Thanks Fernando, jicarretero sent the link to a question at SOF. Anyway image "orion-psb-image-R5.4" avaliable at FiwareLab has a known bug since 3 years ago. Maybe would better replace the instance with the bug by another one with the bug solved to avoid this problem to new users of fiwarelab?

2017-10-19 08:25:06 +0100 commented answer FIWARE : Idm Keyrock under SSL error AH01990: PRNG still contains insufficient entropy!

I have deployed an instance of WIRECLOUD at FiwareLab. I have configured Apache under SSL with certificates signed by a CA and eveything works OK!!! No entrophy errors. Wirecloud and KeyRock have the same versions of Apache/2.4.7 and Python 2.7.6. This can be helpful to find a solution for KeyRock?

2017-10-19 08:14:04 +0100 received badge  Editor (source)
2017-10-19 07:15:11 +0100 commented answer FIWARE : Idm Keyrock under SSL error AH01990: PRNG still contains insufficient entropy!

I have deployed a new instance of IDM-keyrock at FiwareLab, I have configured Apache under SSL with certificates signed by a CA and I get again the Entrophy Error. So the instance avaliable at FiwareLab of the GE focused on Security does not work under secure protocol. It seems to be like a joke ;-(

2017-10-18 08:45:40 +0100 commented answer FIWARE : Idm Keyrock under SSL error AH01990: PRNG still contains insufficient entropy!

Dear Fiware, already I am waiting any help about this issue. Many thanks

2017-10-18 08:22:04 +0100 received badge  Notable Question (source)
2017-10-18 08:22:04 +0100 received badge  Famous Question (source)
2017-10-17 14:18:09 +0100 received badge  Popular Question (source)
2017-10-17 09:23:55 +0100 received badge  Notable Question (source)
2017-10-17 07:16:38 +0100 received badge  Enthusiast
2017-10-16 17:23:43 +0100 commented answer FIWARE : Idm Keyrock under SSL error AH01990: PRNG still contains insufficient entropy!

I have tested some proposals and they does not work. Is it possible get a running instance of idm-keyrock configured with apache web server and ssl? Best regards

2017-10-11 13:42:38 +0100 received badge  Popular Question (source)
2017-10-11 13:29:40 +0100 asked a question FIWARE : Idm Keyrock under SSL error AH01990: PRNG still contains insufficient entropy!

Dear Fiware,

I have deployed at Fiware Lab one instance of the idm-keyrock based on image "keyrock-R5.3.0". The IDM works under protocol http and default port 8000 with no problems.

I have installed Apache Web Server to setup with SSL certificates signed by a CA and the website works 1 or 2 times and then I get at the error file of apache the messages appears below

AH01990: PRNG still contains insufficient entropy!

extern "Python": function Cryptographyrandbytes() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0.

Any tip or help to solve this problem is wellcome

Many thanks in advance for your support!

Best Regards

Nacho

2017-10-09 12:55:19 +0100 asked a question Fiware Lab : How to use the whole disk space at instance Context Broker

I have deployed at Fiware Lab an instance of the Context Broker.

The instance has assigned 40GB but when I execute the command

"df -h"

I see the following

/dev/vda1 4,8GB

tmpfs 1,9 GB

Where are the other GBs?

How to use the whole disk space?

Best Regards

2017-09-08 08:39:12 +0100 asked a question Error at Cygnus when receives a Notification from "Orion context Broker" : 'fiware-servicepath' header value does not match the number of notified context responses

I have created a Subscription at Orion Context Broker in order to send the data to Cygnus for persist the data in mongodb. When Orion receives and new event value send the notification to Cygnus and I get the following log info at console.

time=2017-08-31T10:10:56.130Z | lvl=INFO | corr=ad9caef6-8e34-11e7-885a-fa163e0d608a | trans=c08becae-0e14-4859-940c-32558dfec7f3 | srv=default | subsrv=/cygnusservicepath | comp=cygnusagent | op=getEvents | msg=com.telefonica.iot.cygnus.handlers.NGSIRestHandler[286] : [NGSIRestHandler] Starting internal transaction (c08becae-0e14-4859-940c-32558dfec7f3) time=2017-08-31T10:10:56.141Z | lvl=INFO | corr=ad9caef6-8e34-11e7-885a-fa163e0d608a | trans=c08becae-0e14-4859-940c-32558dfec7f3 | srv=default | subsrv=/cygnusservicepath | comp=cygnusagent | op=getEvents | msg=com.telefonica.iot.cygnus.handlers.NGSIRestHandler[304] : [NGSIRestHandler] Received data ({"subscriptionId":"xxxxxxxxx","data":[{"id":"id1","type":"type1,....) time=2017-08-31T10:10:56.239Z | lvl=WARN | corr=ad9caef6-8e34-11e7-885a-fa163e0d608a | trans=c08becae-0e14-4859-940c-32558dfec7f3 | srv=default | subsrv=/cygnusservicepath | comp=cygnusagent | op=getEvents | msg=com.telefonica.iot.cygnus.handlers.NGSIRestHandler[324] : [NGSIRestHandler] Bad HTTP notification ('fiware-servicepath' header value does not match the number of notified context responses time=2017-08-31T10:10:56.240Z | lvl=WARN | corr=ad9caef6-8e34-11e7-885a-fa163e0d608a | trans=c08becae-0e14-4859-940c-32558dfec7f3 | srv=default | subsrv=/cygnusservicepath | comp=cygnusagent | op=doPost | msg=org.apache.flume.source.http.HTTPSource$FlumeHTTPServlet[186] : Received bad request from client. org.apache.flume.source.http.HTTPBadRequestException: 'fiware-servicepath' header value does not match the number of notified context responses at com.telefonica.iot.cygnus.handlers.NGSIRestHandler.getEvents(NGSIRestHandler.java:327) at org.apache.flume.source.http.HTTPSource$FlumeHTTPServlet.doPost(HTTPSource.java:184) at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) at javax.servlet.http.HttpServlet.service(HttpServlet.java:814) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:945) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

The header is sent from Orion Context Broker to Cygnus, show what can I do to solve the problem?

Maybe something is not properly configured?

cat /usr/cygnus/conf/agent_mongo.conf cygnusagent.sources = http-source cygnusagent.sinks = mongo-sink cygnusagent.channels = mongo-channel

cygnusagent.sources.http-source.channels = mongo-channel cygnusagent.sources.http-source.type = org.apache.flume.source.http.HTTPSource cygnusagent.sources.http-source.port = 5050 cygnusagent.sources.http-source.handler = com.telefonica.iot.cygnus.handlers.NGSIRestHandler cygnusagent.sources.http-source.handler.notificationtarget = /notify cygnusagent.sources.http-source.handler.defaultservice = default cygnusagent.sources.http-source.handler.defaultservicepath = /cygnusservicepath cygnusagent.sources.http-source.handler.eventsttl = 10 cygnusagent.sources.http-source.interceptors = ts gi cygnusagent.sources.http-source.interceptors.ts.type = timestamp cygnusagent.sources.http-source.interceptors.gi.type = com.telefonica.iot.cygnus.interceptors.NGSIGroupingInterceptor$Builder cygnusagent ... (more)