Hello is it possible to get some feedback on this. On 11 Jun 2015 21:02, <dave.watson at trendalyze.com> wrote: > Please see the issue below > > > > On 09/06/2015 11:34, dave.watson at trendalyze.com wrote: > > he followings are the steps need to be executed in the cluster:. > Step 3: generating and installing the master node's certificate > > The platform requires a certificate for the master node, signed by a valid > CA, is installed in order to be shown as an authentication proof. Thus, > this certificate must be created by generating a Certificate Signing > Request (CSR); do it once in the master node: > > $ openssl req -newkey rsa:2048 -new -keyout newkey.pem -out newreq.pem > > The above command will prompt for certain information; the most important > information regarding the Cosmos platform is the name of the server > (whichever hostname was chosen for the cosmos master node) where the > certificate is going to be installed, and that the challenge password must > be empty. Althought the PEM pass phrase must be empty (otherwise, the httpd > server will not be automatically started), it has to be filled in this step > and removed later by performing: > > $ openssl rsa -in newkey.pem -out newkey.pem > > Reached this point, you may choose among two options for signing the > certificate: > > - Use a valid CA in the Internet. The content of the generated SCR ( > newreq.pem file) must be used within the CA in order to retrieve the > final certificate, which will be typically called certnew.cer. The way > each CA manages the CSR varies from one to another. > - Self-signing the certificate. In this case, you have to perform this > command: > > $ openssl req -new -x509 -key newkey.pem -out certnew.cer > > In any case, once the certificate (certnew.cer), key (newkey.pem) and CSR > (newreq.pem) have been got, rename the files according to this (do it in > all the machines): > > $ cp newkey.pem [COSMOS_TMP_PATH]/puppet/modules/cosmos/files/environments//certs/_key.pem > $ cp cernew.cer [COSMOS_TMP_PATH]/puppet/modules/cosmos/files/environments//certs/_cer.pem > $ cp newreq.pem [COSMOS_TMP_PATH]/puppet/modules/cosmos/files/environments//certs/_req.pem > > *Followings are my execution in TrendalyzeC1 Server, * > I am creating a newkey.pem file along with PEM Pass Pharse as a empty. > > [root at trendalyzeC1 certs]# *openssl req -newkey rsa:2048 -new -keyout > newkey.pem -out newreq.pem* > Generating a 2048 bit RSA private key > > ......................................................................................................+++ > ..................................+++ > writing new private key to 'newkey.pem' > Enter PEM pass phrase: > 140563222914888:error:28069065:lib(40):UI_set_result:result too > small:ui_lib.c:869:You must type in 4 to 1024 characters > 140563222914888:error:0906406D:PEM routines:PEM_def_callback:problems > getting password:pem_lib.c:111: > 140563222914888:error:0907E06F:PEM routines:DO_PK8PKEY:read > key:pem_pk8.c:130: > [root at trendalyzeC1 certs]# ls > newkey.pem > > [root at trendalyzeC1 certs]# *openssl rsa -in newkey.pem -out newkey.pem* > *unable to load Private Key* > 140336722401096:error:0906D06C:PEM routines:PEM_read_bio:no start > line:pem_lib.c:703:Expecting: ANY PRIVATE KEY > [root at trendalyzeC1 certs]# ls > newkey.pem > [root at trendalyzeC1 certs]# *openssl req -new -x509 -key newkey.pem -out > certnew.cer* > *unable to load Private Key* > 140142761813832:error:0906D06C:PEM routines:PEM_read_bio:no start > line:pem_lib.c:703:Expecting: ANY PRIVATE KEY > > > > On 30/04/2015 12:44, FRANCISCO ROMERO BUENO wrote: > > Hi Dave, > Regarding this and the other question you did yesterday, the deployed > cluster at FIWARE LAB runs MRv1 and not MRv2/YARN, so you will not find a > Zooekeeper server nor Application Master and so on. > We are working on a new MRv2 cluster for FIWARE LAB (specifically, HDP > 2.0.6 distribution) that I hope is available in the next weeks. > Regards, > Francisco > De: "dave.watson at trendalyze.com" <dave.watson at trendalyze.com> > Fecha: miércoles, 29 de abril de 2015, 11:42 > Para: Francisco Romero Bueno <francisco.romerobueno at telefonica.com> > CC: FERMIN GALAN MARQUEZ <fermin.galanmarquez at telefonica.com>, SERGIO > GARCIA GOMEZ <sergio.garciagomez at telefonica.com>, Dave Watson < > watson.dave at gmail.com> > Asunto: ZK port for the cosmos lab > Would like to know the zookeeper port of cosmos server as well. .the > default port# 2181 is not there. > > [dave.watson at cosmosmaster-gi hadoop]$ netstat -tulnp | grep 8020 > (No info could be read for "-p": geteuid()=775 but you should be root.) > tcp 0 0 192.168.189.1:8020 0.0.0.0:* > LISTEN - > [dave.watson at cosmosmaster-gi hadoop]$ netstat -tulnp | grep 2181 > (No info could be read for "-p": geteuid()=775 but you should be root.) > [dave.watson at cosmosmaster-gi hadoop]$ > > > > On 27/04/2015 11:47, FRANCISCO ROMERO BUENO wrote: > > Hi Dave, > Please try with temp994433 (temporal password), then change it by using > the passwd command. > Anyway, http://cosmos.lab.fi-ware.org/cosmos-gui/ is just a URL for > creating the Cosmos account, not for login. > Regards, > Francisco > De: "dave.watson at trendalyze.com" <dave.watson at trendalyze.com> > Fecha: lunes, 27 de abril de 2015, 11:11 > Para: Francisco Romero Bueno <francisco.romerobueno at telefonica.com> > CC: "fiware-lab-help at lists.fi-ware.org" <fiware-lab-help at lists.fi-ware.org>, > FERMIN GALAN MARQUEZ <fermin.galanmarquez at telefonica.com>, SERGIO GARCIA > GOMEZ <sergio.garciagomez at telefonica.com>, Dave Watson < > watson.dave at gmail.com> > Asunto: Re: Create Cosmos Lab Account - Portal is not available? > Thank you. Please can you advise how to do a password reset? I can not > seem to get in with the prior and current passwords used for the FIWARE Lab > account. > > root at trendalyze2:~# ssh dave.watson at cosmos.lab.fiware.org > dave.watson at cosmos.lab.fiware.org's password: > Permission denied, please try again. > dave.watson at cosmos.lab.fiware.org's password: > Permission denied, please try again. > dave.watson at cosmos.lab.fiware.org's password: > Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). > root at trendalyze2:~# > > Also be advised the Cosmos GUI http://cosmos.lab.fi-ware.org/cosmos-gui/ > does not permit login so am not sure if I can reset the password there. > > > > > > On 27/04/2015 08:05, FRANCISCO ROMERO BUENO wrote: > > Hi Dave, > I’ve looking at the logs and no recent activity related to your user was > registered. So I think the service was effectively temporarily down. > Anyway, your user is already registered in Cosmos, at least from February > 7th: > > # cat /etc/passwd | grep watson > > dave.watson:x:775:775::/home/dave.watson:/bin/bash > > # hadoop fs -ls /user | grep watson > > drwxr-xr-x - dave.watson dave.watson 0 > 2015-02-07 18:56 /user/dave.watson > The users are the local Unix user and the HDFS user, respectively. > Regards, > Francisco > De: "dave.watson at trendalyze.com" <dave.watson at trendalyze.com> > Fecha: sábado, 25 de abril de 2015, 12:07 > Para: "fiware-lab-help at lists.fi-ware.org" < > fiware-lab-help at lists.fi-ware.org>, Francisco Romero Bueno < > francisco.romerobueno at telefonica.com>, Francisco Romero Bueno < > francisco.romerobueno at telefonica.com>, FERMIN GALAN MARQUEZ < > fermin.galanmarquez at telefonica.com>, SERGIO GARCIA GOMEZ < > sergio.garciagomez at telefonica.com> > CC: Dave Watson <watson.dave at gmail.com> > Asunto: Create Cosmos Lab Account - Portal is not available? > Following instructions in Step 1 of > > http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/BigData_Analysis_-_Quick_Start_for_Programmers#Step_1._Create_a_Cosmos_account > > But the Cosmos portal is not working > http://cosmos.lab.fi-ware.org/cosmos-gui/ > > Try to login to Cosmos portal using FIWARE Lab username/password (from > community account) but it doesn't repond when hit Logon button > The alternative link times out > http://cosmos.lab.fi-ware.org:9990/cosmos-gui/ > > > ------------------------------ > > 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 > > > ------------------------------ > > 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 > > > ------------------------------ > > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20150625/efc20674/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy