Hello Fernando, I gladly report issue(s) to somewhere official place where they can be easily followed. Though I'm bit worried to use stackoverflow as communication channel because my questions are FI-WARE project related and I'm not certain if all my issues are ok to be asked in public forum. If you use some internal error database I can provided defect description to there. Only open issue at the moment is that snapshot creation is not working for me, José reported that port issue is fixed and I also confirmed that. Best regards, Sami On 01.04.2014 12:47, FERNANDO LOPEZ AGUILAR wrote: > Dear Sami, > > Due to we would like to keep the information of the questions registered > in some place. I would like that you can put the question in stackoverflow > and we could trace the different question and answer like a FAQ? > > > El 31/03/14 09:34, "Sami" <sami.jylkka at cyberlightning.com> escribió: > >> Hi José, >> thanks, ssh connection works again and I'm able to launch jetty server. >> Still I'm not able to access jetty server with web browser. >> >> VM IP is 130.206.80.182. When I connect to VM with SSH and do following >> in VM's terminal I get jetty server response correctly. >> "telnet 130.206.80.182 8080" >> "get /geoserver/web/" >> >> However when I type to web browser >> "http://130.206.80.182:8080/geoserver" I get only connection timeout. I >> wonder if there is still some wrong definition or missing security >> definition in VM..? Are you able to open >> http://130.206.80.182:8080/geoserver url succesfully? Jetty server is >> currently running >> >> I tried also snapshot creation, creation starts but I can't see created >> snapshot anywhere. When snapshot creation is started i see snaphost name >> in the "snapshots" -section, but in some stage it disappears from there..? >> >> Best regards, >> Sami >> >> >> >> On 27.03.2014 17:33, José Ignacio Carretero Guarde wrote: >>> Hi, I think your VM should be running again, and I home you can do your >>> snapshot now. >>> >>> BR, >>> José Ignacio. >>> >>> El 27/03/14 11:48, Sami escribió: >>>> Hello, >>>> and sorry to bother you again but my problems still are active :( >>>> >>>> Yesterday (wednesday) I suddenly wasn't able to anymore access to >>>> testbed via ssh connection, though it did work on tuesday. Server >>>> which I'm trying to connect seems to be there, at least based on >>>> testbed UI info, but it just gives this message when I try SSH: "ssh: >>>> connect to host 130.206.80.182 port 22: No route to host" >>>> I noticed that Instance powerstate is PAUSED, does this somehow affect >>>> that I'm not able to access server with ssh? >>>> >>>> Regarding previous problem not able to connect running web server in >>>> VM. I confirmed that our company firewall doesn't restrict anyhow >>>> outgoing ports, so problem is caused by some other reason. But for >>>> some reason Josê was able to connect there. I'd appreciate help in >>>> this matter. >>>> >>>> Last problem is that I'm not able to create snapshot of the created >>>> VM. I really want to create that after I have created and configured >>>> server correctly so that I'm able to use snapshot if new similar >>>> server needs to be created. >>>> >>>> Thank you for the support you've already provided! >>>> >>>> Best regards, >>>> Sami >>>> >>>> >>>> On 25.03.2014 10:45, José Ignacio Carretero Guarde wrote: >>>>> Yes, the point of using the mobile phone is "being out" of my >>>>> company's >>>>> network. The IP and the network where the mobile phone is connected is >>>>> an unprivileged network, so the packets sent by this IP are not >>>>> privileged, they are unknown to the testbed, they are not firewalled >>>>> by >>>>> my company's firewall... But if I used the wifi in my company, the >>>>> tests >>>>> would be as biased as the test in my computer. >>>>> >>>>> That's what I mean when I say: "From my mobile phone" >>>>> >>>>> Ask your network administrator if these acceses are firewalled. >>>>> >>>>> Best regards, >>>>> José Ignacio. >>>>> >>>>> El 25/03/14 09:38, Sami escribió: >>>>>> Thanks, >>>>>> this is really weird. I'm not getting any response with my computer >>>>>> nor my own mobile phone. I tried telnet with my computer similarly as >>>>>> you did, but I get connection timout. >>>>>> My personal mobile phone is in 4G network and it is not anyhow >>>>>> connected to our company network. But I'm not able to access to jetty >>>>>> server either with it. I tried accessing web servier via phone's web >>>>>> browser and also using separate telnet app, no luck. How on earth >>>>>> your >>>>>> connection to server works, this is bizarre.. >>>>>> >>>>>> Best regards, >>>>>> Sami >>>>>> >>>>>> On 25.03.2014 10:22, José Ignacio Carretero Guarde wrote: >>>>>>> Well, I can access without problems --- Even from my mobile phone I >>>>>>> get >>>>>>> a 404 :) -- This means the server is listening and the port is >>>>>>> allowed. >>>>>>> >>>>>>> One common problem is the Company disallowing ports different to >>>>>>> 80, 443 >>>>>>> and sometimes 22: >>>>>>> >>>>>>> Regards, >>>>>>> José Ignacio. >>>>>>> >>>>>>> Look at this.... >>>>>>> >>>>>>> jicg at corporario:~$ telnet 130.206.80.182 8008 >>>>>>> Trying 130.206.80.182... >>>>>>> Connected to 130.206.80.182. >>>>>>> Escape character is '^]'. >>>>>>> GET / >>>>>>> <HTML> >>>>>>> <HEAD> >>>>>>> <TITLE>Error 404 - Not Found</TITLE> >>>>>>> <BODY> >>>>>>> <H2>Error 404 - Not Found.</H2> >>>>>>> No context on this server matched or handled this >>>>>>> request.<BR>Contexts >>>>>>> known to this server are: <ul><li><a >>>>>>> >>>>>>> href="/geoserver">/geoserver ---> org.mortbay.jetty.plugin. >>>>>>> Jetty6PluginWebAppContext at 7038dd52{/geoserver,/git/geoserver/src/web/ >>>>>>> app/src/main/webapp}</a></li> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> <!-- Padding for IE --> >>>>>>> <!-- Padding for IE --> >>>>>>> <!-- Padding for IE --> >>>>>>> <!-- Padding for IE --> >>>>>>> <!-- Padding for IE --> >>>>>>> <!-- Padding for IE --> >>>>>>> <!-- Padding for IE --> >>>>>>> <!-- Padding for IE --> >>>>>>> <!-- Padding for IE --> >>>>>>> <!-- Padding for IE --> >>>>>>> </BODY> >>>>>>> </HTML> >>>>>>> Connection closed by foreign host. >>>>>>> >>>>>>> >>>>>>> >>>>>>> El 25/03/14 09:16, Sami escribió: >>>>>>>> Hello Jóse and thank you for the support which you have already >>>>>>>> provided. >>>>>>>> I'm still facing problems when I setup VM software. Perhaps >>>>>>>> problem is >>>>>>>> just caused by wrong server configuration. >>>>>>>> >>>>>>>> What I have done is that I start jetty server in VM, i've tried >>>>>>>> multiple different ports but no luck when trying to access to them >>>>>>>> outside. As you explained below ports from 1 to 8080 are open and I >>>>>>>> think that therefore there should be some response when jetty is >>>>>>>> running specific port. I tried ports 8080 and 8008 with Jetty which >>>>>>>> should be open and accessible, but still accessing doesn't work. >>>>>>>> Are >>>>>>>> you able to point out if there is some clear problem in my security >>>>>>>> settings? VM is running at 130.206.80.182, jetty server currently >>>>>>>> at >>>>>>>> 130.206.80.182:8008 >>>>>>>> >>>>>>>> I also tried to do snapshot if the created VM but I can't see >>>>>>>> snapshot >>>>>>>> anywhere. Should I have more discspace for storing snapshost or is >>>>>>>> there some trick which I should know in order to succesfully >>>>>>>> create VM >>>>>>>> snapshot? >>>>>>>> >>>>>>>> Best regards, >>>>>>>> Sami >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On 24.03.2014 13:15, José Ignacio Carretero Guarde wrote: >>>>>>>>> So, I must assume that the web portal messages mislead the users. >>>>>>>>> I'll >>>>>>>>> report this to developers to see if they can change the message. >>>>>>>>> >>>>>>>>> The explanation is: What you need is a public IP in order access >>>>>>>>> your VM >>>>>>>>> from the internet, but this instance of Openstack is >>>>>>>>> configurated do >>>>>>>>> automatically deliver a public IP, which means that your VMs >>>>>>>>> will be >>>>>>>>> accesible from the internet. -- Anyway, this will change in the >>>>>>>>> future >>>>>>>>> and you'll need to assign a floating IP. >>>>>>>>> >>>>>>>>> I don't know if there was any connectivity issue with your VMs, I >>>>>>>>> didn't >>>>>>>>> look into the testbed last weekend :), and I only tested today, I >>>>>>>>> didn't >>>>>>>>> change anything. Anyway, I'm glad you can finally access the VM. >>>>>>>>> >>>>>>>>> Best regards, >>>>>>>>> José Ignacio. >>>>>>>>> >>>>>>>>> El 24/03/14 11:53, Sami escribió: >>>>>>>>>> Hi Jóse, >>>>>>>>>> and thanks for the clarification, you explained PING issue very >>>>>>>>>> well. >>>>>>>>>> >>>>>>>>>> I don't understand why SSH connection works now, after I received >>>>>>>>>> your >>>>>>>>>> email I tried it also again and it really worked! This is >>>>>>>>>> mystery to >>>>>>>>>> me, I have not changed anything from anywhere, but for some >>>>>>>>>> reason >>>>>>>>>> SSH >>>>>>>>>> connection is now successfully established compared to last >>>>>>>>>> Saturday >>>>>>>>>> when it always failed. Could it be so that I tried last Saturday >>>>>>>>>> ssh >>>>>>>>>> too early after MV was created, so that server was actually >>>>>>>>>> still in >>>>>>>>>> initiation process and it wasn't completely started.. well, I'm >>>>>>>>>> happy >>>>>>>>>> that connection works now and I'm able to proceed with VM setup. >>>>>>>>>> >>>>>>>>>> regarding 2 public IP. When I create new VM, testbed gives this >>>>>>>>>> information to me: >>>>>>>>>> " >>>>>>>>>> To access the instance: >>>>>>>>>> >>>>>>>>>> You need to include a security group with port 22 opened to >>>>>>>>>> access >>>>>>>>>> via SSH. >>>>>>>>>> >>>>>>>>>> You need to assign a floating IP to access from a external >>>>>>>>>> network. >>>>>>>>>> >>>>>>>>>> " >>>>>>>>>> I understood "You need to assign a floating IP to access from a >>>>>>>>>> external network." -sentence so that I need to assign floating IP >>>>>>>>>> from >>>>>>>>>> Security section if I want to access to server instance at all. I >>>>>>>>>> think I'm accessing from external network to server instance. >>>>>>>>>> Based on your comment I have now removed floating IP from the >>>>>>>>>> instance >>>>>>>>>> and SSH connection seems to work, so floating IP wasn't needed at >>>>>>>>>> all. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Best regards, >>>>>>>>>> Sami >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 24.03.2014 11:43, José Ignacio Carretero Guarde wrote: >>>>>>>>>>> Hi Sami, >>>>>>>>>>> >>>>>>>>>>> About problem 1, I've removed the xlarge flavor. It shouldn't >>>>>>>>>>> never >>>>>>>>>>> had >>>>>>>>>>> to have been there. Sorry. >>>>>>>>>>> >>>>>>>>>>> About your 2nd problem I can't understand where's the problem. >>>>>>>>>>> --- >>>>>>>>>>> You've opened the ssh connection for your VM and it works. The >>>>>>>>>>> question >>>>>>>>>>> is: Why do you need two public IPs for you VM? I've sshd your >>>>>>>>>>> 130.206.80.182 without problem (from my mobile-phone's 3G >>>>>>>>>>> Connection, >>>>>>>>>>> not from any privileged network). >>>>>>>>>>> >>>>>>>>>>> I'd like to comment that "sending ping to instance" is not >>>>>>>>>>> allowed in >>>>>>>>>>> your security groups --- So it means it is working well. These >>>>>>>>>>> are >>>>>>>>>>> your >>>>>>>>>>> security groups: >>>>>>>>>>> >>>>>>>>>>> tcp 0.0.0.0/0 1 8080 -- TCP from port 1 to port 8080 (which >>>>>>>>>>> includes >>>>>>>>>>> ports 22, 80 , 23, 3306, 5432, etc.) >>>>>>>>>>> tcp 0.0.0.0/0 1 22 -- TCP from port 1 to port 22. >>>>>>>>>>> tcp 0.0.0.0/0 23 80 -- TCP from port 23 to port 80 >>>>>>>>>>> udp 0.0.0.0/0 1 22 -- UDP from port 1 to port 22 (No >>>>>>>>>>> NTP, no >>>>>>>>>>> many >>>>>>>>>>> other interesting services) >>>>>>>>>>> >>>>>>>>>>> As you can see, there are no ICMP rules at all, which basically >>>>>>>>>>> means no >>>>>>>>>>> PING at all. >>>>>>>>>>> >>>>>>>>>>> I hope my explanation could help you. >>>>>>>>>>> >>>>>>>>>>> Best regards, >>>>>>>>>>> José Ignacio. >>>>>>>>>>> >>>>>>>>>>> El 22/03/14 11:11, Sami escribió: >>>>>>>>>>>> Hi José, >>>>>>>>>>>> I'm trying to launch new instance and I've faced some problems: >>>>>>>>>>>> >>>>>>>>>>>> 1st problem which I noticed that always when I select >>>>>>>>>>>> "m1.xlarge" >>>>>>>>>>>> as a >>>>>>>>>>>> flavor, status in the created instance will be "ERROR". But >>>>>>>>>>>> when I >>>>>>>>>>>> create instance with "m1.large" flavor, instance is created. >>>>>>>>>>>> Why I >>>>>>>>>>>> can't select m1.xlarge as a flavor? >>>>>>>>>>>> >>>>>>>>>>>> 2nd problem is that even thoug testbed Instance GUI identifies >>>>>>>>>>>> that >>>>>>>>>>>> instance is succesfully build and it is on running state, I am >>>>>>>>>>>> not >>>>>>>>>>>> able to access to that instance anyhow. I've defined security >>>>>>>>>>>> group >>>>>>>>>>>> and key as guidance says, still connecting with SSH fails. even >>>>>>>>>>>> sending ping to instance doesn't respond anything >>>>>>>>>>>> >>>>>>>>>>>> due second problem my task to create new VM is halt >>>>>>>>>>>> >>>>>>>>>>>> Thanks in advance! >>>>>>>>>>>> >>>>>>>>>>>> br, >>>>>>>>>>>> Sami >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> ________________________________ >>>>>>>>>>> >>>>>>>>>>> Este mensaje se dirige exclusivamente a su destinatario. Puede >>>>>>>>>>> consultar nuestra política de envío y recepción de correo >>>>>>>>>>> electrónico >>>>>>>>>>> en el enlace situado más abajo. >>>>>>>>>>> This message is intended exclusively for its addressee. We only >>>>>>>>>>> send >>>>>>>>>>> and receive email on the basis of the terms set out at: >>>>>>>>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx >>>>>>>>>> -- >>>>>>>>>> Sami Jylkkä >>>>>>>>>> Software Designer >>>>>>>>>> Cyberlightning Ltd. >>>>>>>>>> >>>>>>>>>> Go towww.cybersli.de and enrich your presentations! >>>>>>>>>> >>>>>>>>>> www.cyberlightning.com >>>>>>>>>> >>>>>>>>>> This e-mail and all attached material are confidential and may >>>>>>>>>> contain legally privileged information. If you are not the >>>>>>>>>> intended >>>>>>>>>> recipient, please contact the sender and delete the e-mail from >>>>>>>>>> your >>>>>>>>>> system without producing, distributing or retaining copies >>>>>>>>>> thereof. >>>>>>>>> >>>>>>>>> ________________________________ >>>>>>>>> >>>>>>>>> Este mensaje se dirige exclusivamente a su destinatario. Puede >>>>>>>>> consultar nuestra política de envío y recepción de correo >>>>>>>>> electrónico >>>>>>>>> en el enlace situado más abajo. >>>>>>>>> This message is intended exclusively for its addressee. We only >>>>>>>>> send >>>>>>>>> and receive email on the basis of the terms set out at: >>>>>>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx >>>>>>> >>>>>>> ________________________________ >>>>>>> >>>>>>> Este mensaje se dirige exclusivamente a su destinatario. Puede >>>>>>> consultar nuestra política de envío y recepción de correo >>>>>>> electrónico >>>>>>> en el enlace situado más abajo. >>>>>>> This message is intended exclusively for its addressee. We only send >>>>>>> and receive email on the basis of the terms set out at: >>>>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx >>>>> >>>>> ________________________________ >>>>> >>>>> Este mensaje se dirige exclusivamente a su destinatario. Puede >>>>> consultar nuestra política de envío y recepción de correo electrónico >>>>> en el enlace situado más abajo. >>>>> This message is intended exclusively for its addressee. We only send >>>>> and receive email on the basis of the terms set out at: >>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx >>> >>> ________________________________ >>> >>> Este mensaje se dirige exclusivamente a su destinatario. Puede >>> consultar nuestra política de envío y recepción de correo electrónico >>> en el enlace situado más abajo. >>> This message is intended exclusively for its addressee. We only send >>> and receive email on the basis of the terms set out at: >>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx >> -- >> Sami Jylkkä >> Software Designer >> Cyberlightning Ltd. >> >> Go to www.cybersli.de and enrich your presentations! >> >> www.cyberlightning.com >> >> This e-mail and all attached material are confidential and may contain >> legally privileged information. If you are not the intended recipient, >> please contact the sender and delete the e-mail from your system without >> producing, distributing or retaining copies thereof. >> >> _______________________________________________ >> Fiware-testbed-help mailing list >> Fiware-testbed-help at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-testbed-help > > ________________________________ > > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. > This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: > http://www.tid.es/ES/PAGINAS/disclaimer.aspx -- Sami Jylkkä Software Designer Cyberlightning Ltd. Go to www.cybersli.de and enrich your presentations! www.cyberlightning.com This e-mail and all attached material are confidential and may contain legally privileged information. If you are not the intended recipient, please contact the sender and delete the e-mail from your system without producing, distributing or retaining copies thereof.
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy