Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
Sender Email:
-
HD-Chapter:Data
-
HD-Enabler:Cosmos
Description
Hello,
I'm sending this email because I've been having some issues with Cygnus within my Orion instance in Fi-Cloud.
I was trying to make Cygnus persist Orion's data onto my COSMOS HDFS space within the COSMOS global instance. I was having trouble with cygnus config file. I wasn't getting results on COSMOS's HDFS, by seeing the appropriate file beeing created within the hadoop file system, so I was trying diferent things with the config file /usr/cygnus/conf/cygnus.conf .
Then I saw that I was running Cygnus on version 0.5 and decided to update it to the latest version 0.8 by using the command "yum install cygnus" on my Orion instance, as instructed on ssh access.By doing this Cygnus stopped working and no 'service cygnus' is running anymore.. The cygnus folder, /usr/cygnus, is gone and removal of cygnus with 'yum remove cygnus' fails. Trying to reinstall does nothing as it is already installed.
I didn't stop the cygnus service before installing the newest version. Don't know if that was inapropriate.
More, I've been having issues starting new VMs on my Fi-Cloud latelly, to which I have already posted a support email. Because of that I don't want to even restart Orion's instance on the fear that it too stops working because of this issues with Fi-Cloud.
If it is of any help, you can reach Orion's intance at 130.206.117.94 or at 192.168.207.254 of the node-int-net-01 network of Fi-Cloud.
The end goal is simply to have Cygnus persist Orion's readings on my HDFS user space of COSMOS.
If you need more information, please let me know, I will answer right away,
Thank you,
Arthur
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-tech-help
[Created via e-mail received from: Arthur Vieira <arthurmvieira@hotmail.com>]
Hi Arthur,
this is a well-known issue, there was a bug in the RPM used to install
Cygnus < 0.8.0 that avoids it is updated in a correct way. This was
corrected lately, so if you upgrade for instance from 0.8.0 to 0.8.2 there
is no problem at all.
The steps needed to upgrade from 0.5 to 0.8.2 (the latest stable release)
are:
$ (sudo) yum clean all # just to clean the yum cache
$ (sudo) yum list cygnus # this will show you 0.8.2 is available
$ (sudo) sudo rpm -e -vv --allmatches --nodeps --noscripts --notriggers
cygnus # this is needed if you have installed a version < 0.8.0
$ (sudo) yum install cygnus # this installs 0.8.2
You have all the details in this stackoverflow.com question:
http://stackoverflow.com/questions/31310111/oauth2-in-cygnus
Regards,
Francisco
El 18/8/15 17:00, "Manuel Escriche (JIRA)" <jira-help-desk@fi-ware.org>
________________________________
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