fiware

问题 I am configuring the FIWARE PEP-Proxy-steelskin without RPM, due it is installed in a Ubuntu machine. After the installation, no log appears in /var/log/pepProxy , and I am afraid this is because of the installation. Is there a way to create the log without RPM? 回答1: It is indeed. Steelskin does not log to a particular file, but to the standard output. That's why you are not seeing any log in /var/log. In order to get the log, just make a redirection of the standard output: nohup bin/pepProxy

问题 I am trying to install cygnus-ngsi, following this guide. While installing via Docker, I get the following error: INFO: Apache domain <http://apache.rediris.es/> INFO: URL MAVEN <http://apache.rediris.es/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz> INFO: URL FLUME <http://apache.rediris.es/flume/1.4.0/apache-flume-1.4.0-bin.tar.gz> INFO: Download and install Maven and Flume... curl: (7) couldn't connect to host It seems to be that the mirror http://apache.rediris.es is down. Is

问题 Working on setting Cygnus as a sink to CKAN, and I get this error, what part of Cygnus setup is responsible for this( subscription, configuration ...) cygnus_1 | time=2018-10-01T12:40:04.517Z | lvl=DEBUG | corr=1ea858dc-c577- 11e8-b0fd-0242ac140003 | trans=5c553916-f5e6-4bbc-b98a-bcaba61a306c | srv=waste4think | subsrv=/room/test | comp=cygnus-ngsi | op=getEvents | msg=com.telefonica.iot.cygnus.handlers.NGSIRestHandler[320] : [NGSIRestHandler] Parsed NotifyContextRequest:{" subscriptionId":

问题 I'm trying to make a GET request to a Context Broker instance from a browser. I've enabled CORS on the CB using the -corsOrigin __ALL flag when starting the app, and I can see that this has worked by making a request in POSTMAN and seeing this header in the response: access-control-allow-origin →* . I need to specify the Fiware-Service header in my GET request in order to get the correct entities, which I believe is making the request not simple, triggering an OPTIONS HTTP request. Inspecting

问题 I'm trying to send measurements using IoT Agent UL2.0. First, I created a device as follows: POST /iot/devices HTTP/1.1 Host: localhost:4061 Fiware-Service: Empresa1 Fiware-ServicePath: /empresa1 Content-Type: application/json Cache-Control: no-cache { "devices": [ { "device_id": "A6", "entity_name": "A6", "entity_type": "E6", "attributes": [ { "object_id": "a", "name": "aaa", "type": "text" }, { "object_id": "b", "name": "bbb", "type": "text" }, { "object_id": "c", "name": "ccc", "type":

问题 I want to use Apache flume Elastic search native sink in cygnus. How can I configure cygnus to use this native sink? Do I put the native jar file in Apache flume lib and configure the agent as the folowing: # Name the components on this agent a1.sources = r1 a1.sinks = k1 a1.channels = c1 # Describe/configure the source a1.sources.r1.type = netcat a1.sources.r1.bind = localhost a1.sources.r1.port = 44444 # Describe the sink a1.sinks.k1.type = logger # Use a channel which buffers events in

问题 We are trying to install Orion Context Broker in a CentOS-7 virtual machine as recommended in this link: https://fiware-orion.readthedocs.io/en/master/admin/install/index.html When we run the step "yum install contextBroker", an HTTPS 404 error is obtained (please, see instalation log). Apparently, the repositories are not available. We can access to the URL https://nexus.lab.fiware.org/service/rest/repository/browse/el/7/x86_64/release/ from the virtual machine (see curl output) and our

问题 I try to send a subscription to my Orion Context Broker instance. I'm sending this JSON: { "duration": "P1M", "reference": "http://130.206.127.23:1026/ngsi10/notifyContext", "notifyConditions": [ { "condValues": [ "PT10s" ], "type": "ONTIMEINTERVAL" } ], "entities": [ { "id": "1.0", "type": "Capsule", "isPattern": "false" } ], "attributes": [ "temperature" ] } And I receive the next message: <subscribeContextResponse> <subscribeError> <errorCode> <code>400</code> <reasonPhrase>Bad Request<

问题 I installed fiware cygnus using RPM on my centOS 7 but I can't start it as service. I got the following error: [root@localhost cygnus]# sudo service cygnus start Starting cygnus (via systemctl): Job for cygnus.service failed. See 'systemctl status cygnus.service' and 'journalctl -xn' for details. [ÉCHOUÉ] [root@localhost cygnus]# systemctl status cygnus.service -l cygnus.service - SYSV: cygnus Loaded: loaded (/etc/rc.d/init.d/cygnus) Active: failed (Result: exit-code) since ven. 2015-07-31 19

问题 We are customizing a Wirecloud installation to provide our own branding, text and header links. We have created a subtheme to the 'defaulttheme' and are overlaying our own template, images and sccs files to accomplish our customization. We have managed to change the header image, landing page and a few other bits, but are hampered by the following: The generated HTML provides no clues as to which template it originated from (we think?) Documentation here: https://wirecloud.readthedocs.io/en