Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Component/s: FINODEX
-
Labels:None
Description
Hi Carlos,
I did an example of connection between context broker and cosmos via Cygnus.
Here my config.
In cosmos.doc you can find my guide.
I hope that it will useful for you.
Regards,
Pasquale
Inviato da Samsung Mobile.
<div>-------- Messaggio originale --------</div><div>Da: stefano de panfilis <stefano.depanfilis@eng.it> </div><div>Data:14/09/2015 00:44 (GMT+01:00) </div><div>A: Carlos Corrales <carlos@secmotic.com> </div><div>Cc: FRANCISCO ROMERO BUENO <francisco.romerobueno@telefonica.com>, jose@secmotic.com, fiware-finodex-coaching@lists.fi-ware.org </div><div>Oggetto: Re: [Fiware-finodex-coaching] Problems with COSMOS persistance </div><div>
</div>dear carlos,
in fact, as an sme working in finodex you did correctly.
it will be your fiware coach (pasquale vitale in cc) that if not able to solve himself the issue, and i guess this time he will not, he will turn the ticket to the ge owner (francisco romero as indicated by juanjo).
ciao,
stefano
2015-09-13 16:36 GMT+02:00 Carlos Corrales <carlos@secmotic.com>:
Hi Juanjo,
Thanks for you feedback, we sent it today because we wanted you to answer it tomorrow morning .
As you can see, a ticket has been created in Jira (https://jira.fiware.org/browse/HELC-1025). I used the fiware-finodex-coaching list, because we are a FINODEX project and they told us to do so. Should we create another ticket in the fiware-tech-help list also?
Best regards
2015-09-13 16:30 GMT+02:00 Juanjo Hierro <juanjose.hierro@telefonica.com>:
Hi,
I copy Francisco (Paco) Romero who should be able to provide some help on this. I guess he won't be able to work on the matter until tomorrow since support is not granted out of office working hours.
Nevertheless, I believe that it is rather important that you open an issue so that a ticket on our help-desk system is created and then follow-up of support is feasible.
You may create a ticket in our helpdesk simply by sending an email to either fiware-lab-help (if it happens to be an issue which is mostly related to FIWARE Lab or the global COSMOS instance setup on the FIWARE Lab) or fiware-tech-help (if it happens to be an issue mostly related with the technology, i.e., with COSMOS in general and not the particular instance of COSMOS running on the FIWARE Lab).
Best regards,
– Juanjo
______________________________________________________
Coordinator and Chief Architect, FIWARE platform
CTO Industrial IoT, Telefónica
email: juanjose.hierro@telefonica.com
twitter: @JuanjoHierro
You can follow FIWARE at:
website: http://www.fiware.org
twitter: @FIWARE
facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
linkedIn: http://www.linkedin.com/groups/FIWARE-4239932
On 13/09/15 15:20, Carlos Corrales wrote:
Hi everyone,
I'm Carlos Corrales, part of the development team at SAPIN (FINODEX012). We have been working hard in the application and now that it's finished and we are doing tests with final users, we are improving our code. A couple of months ago we were able to write data to our HDFS in the COSMOS Fiware machine (cosmos.lab.fi-ware.org) with our user (idelgado). As we are not using Cosmos for production right now (it will be used in the future), we left it aside. Now that we are checking that everything works as expected, we can see that our Cygnus connector is not able to write properly in HDFS. We haven't changed anything in the configuration, but we receive the following error when trying to write (flume.log file)
time=2015-09-13T15:11:36.744CEST | lvl=INFO | trans=1442149853-658-0000000000 | function=persist | comp=Cygnus | msg=es.tid.fiware.fiwareconnectors.cygnus.sinks.OrionHDFSSink[367] : [hdfs-sink] Persisting data at OrionHDFSSink. HDFS file (idelgado_SAPINnull), Data (
{"recvTime":"2015-09-13T15:11:00.413","age":"25", "age_md":[],"exercisetype":"Light", "exercisetype_md":[],"hr":"36", "hr_md":[],"id_session":"1234", "id_session_md":[]})
time=2015-09-13T15:11:36.803CEST | lvl=ERROR | trans=1442149853-658-0000000000 | function=process | comp=Cygnus | msg=es.tid.fiware.fiwareconnectors.cygnus.sinks.OrionSink[140] : Persistence error (The unknownt/idelgado_SAPINnull directory could not be created in HDFS. HttpFS response: 401 Unauthorized)
time=2015-09-13T15:11:36.804CEST | lvl=INFO | trans=1442149853-658-0000000000 | function=process | comp=Cygnus | msg=es.tid.fiware.fiwareconnectors.cygnus.sinks.OrionSink[150] : An event was put again in the channel (id=1444248959, ttl=0)
time=2015-09-13T15:11:36.804CEST | lvl=INFO | trans=1442149853-658-0000000000 | function=process | comp=Cygnus | msg=es.tid.fiware.fiwareconnectors.cygnus.sinks.OrionSink[175] : Finishing transaction (1442149853-658-0000000000)
As you can see, the error is 401 Unauthorized. However, we can access the Cosmos machine using SSH, and the user/password in the cygnus.conf file. We also checked that the IP address of the Cosmos machine hasn't changed.
Could you please help us? We don't know what else to check...
Best regards
–
Carlos Corrales
Cofounder Secmotic Innovation S.L.
http://www.secmotic.com
_______________________________________________
Fiware-finodex-coaching mailing list
Fiware-finodex-coaching@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-finodex-coaching-new
Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.
The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.
Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
–
Carlos Corrales
Cofounder Secmotic Innovation S.L.
http://www.secmotic.com
_______________________________________________
Fiware-finodex-coaching mailing list
Fiware-finodex-coaching@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-finodex-coaching-new
–
Stefano De Panfilis
Chief Innovation Officer
Engineering Ingegneria Informatica S.p.A.
via Riccardo Morandi 32
00148 Roma
Italy
tel (direct): +39-06-8759-4253
tel (secr.): +39-068307-4513
fax: +39-068307-4200
cell: +39-335-7542-567
skype: depa01
twitter: @depa01
_______________________________________________
Fiware-finodex-coaching mailing list
Fiware-finodex-coaching@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-finodex-coaching-new
[Created via e-mail received from: Pasquale Vitale <pvitale@eng.it>]
Activity
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
6h 44m | 1 | Pasquale Vitale | 14/Sep/15 2:21 PM | |||||
|
2s | 1 | Pasquale Vitale | 14/Sep/15 2:21 PM | |||||
|
2s | 1 | Pasquale Vitale | 14/Sep/15 2:21 PM |