Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-6765

FIWARE.Request.Lab.Spain.FIWARE Lab Assistance - Cannot communicate out of the Cloud

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-LAB-HELP
    • Labels:
      None

      Description

      Hi,

      I am developing FIWARE POI Data Provider and its Global instance.
      It seems that I cannot communicate out from my servers in the FIWARE Lab.

      A PHP http_get() gets a timeout from a request that works well from my
      browser. The problem started last week.

      BR
      Ari Okkonen


      Ari Okkonen
      Adminotech

      Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
      Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-lab-help

      [Created via e-mail received from: Ari Okkonen ADT <ari.okkonen@adminotech.com>]

        Activity

        Hide
        danieles Daniele Santoro added a comment -

        Dear I've forwarded your request to the Spain2 region support.

        Best,
        Daniele

        Show
        danieles Daniele Santoro added a comment - Dear I've forwarded your request to the Spain2 region support. Best, Daniele
        Hide
        ariokkon Ari Okkonen added a comment -

        The instances in Spain2 having the communication problem (http_get() of PHP not working) are:

        • Name: global_poi_instance, ID: 8e1f90cf-aff6-4d6e-a7ca-2fde8f763bf6
        • Name: arispoitest, ID: a8b1d0d8-bac1-456e-82f9-2179ec912d4f
        Show
        ariokkon Ari Okkonen added a comment - The instances in Spain2 having the communication problem (http_get() of PHP not working) are: Name: global_poi_instance, ID: 8e1f90cf-aff6-4d6e-a7ca-2fde8f763bf6 Name: arispoitest, ID: a8b1d0d8-bac1-456e-82f9-2179ec912d4f
        Hide
        jicg José Ignacio Carretero Guarde added a comment -

        The issue has been emailed:

        • Time sent: 14/Jun/16 8:48 AM
        • To: *ari.okkonen@cie.fi *
        • with subject: *(HELP-6765) [Fiware-lab-help] FIWARE Lab Assistance - Cannot communicate out of the Cloud *

        Could you please ellaborate a little bit more on this. There is NO connectivity problems in any of your instances. We haven't seen any problem with the network either. Will you please explain what is the query or anything that could help us debugging the problem?

        Regards,
        José Ignacio.

        Show
        jicg José Ignacio Carretero Guarde added a comment - The issue has been emailed: Time sent: 14/Jun/16 8:48 AM To: *ari.okkonen@cie.fi * with subject: *( HELP-6765 ) [Fiware-lab-help] FIWARE Lab Assistance - Cannot communicate out of the Cloud * Could you please ellaborate a little bit more on this. There is NO connectivity problems in any of your instances. We haven't seen any problem with the network either. Will you please explain what is the query or anything that could help us debugging the problem? Regards, José Ignacio.
        Hide
        ariokkon Ari Okkonen added a comment - - edited

        To reduce the problem I created the following PHP program and ran it in `Spain2.arispoitest`:

        <?php // test_http_get.php 2016-06-14 ariokkon
        if ($_SERVER['REQUEST_METHOD'] == 'GET' )
        {
          $url_out = 'http://www.example.org/';
          error_log('http_get(' . $url_out . ')');
          $output_msg = http_get($url_out);
          error_log('Response: "' . $output_msg . '"');
          echo('<http><head><title>test_http_get</title></head>');
          echo('<body>'. $output_msg . '</body></html>');
        }
        ?>
        

        Related excerpt from the `/var/log/apache2/error.log`:

        [Tue Jun 14 08:49:33.823372 2016] [:error] [pid 1257] [client 193.209.92.202:49259] http_get(http://www.example.org/)
        [Tue Jun 14 08:49:38.868960 2016] [:error] [pid 1257] [client 193.209.92.202:49259] PHP Warning:  http_get(): Timeout was reached; Resolving timed out after 3513 milliseconds (http://www.example.org/) in /var/www/html/poi_dp/test_http_get.php on line 13
        [Tue Jun 14 08:49:38.869175 2016] [:error] [pid 1257] [client 193.209.92.202:49259] Response: ""
        

        And the resulting response:

        <http><head><title>test_http_get</title></head><body></body></html>
        
        • Nothing in the body. So. The http_get() goes to timeout without getting anything from a well established URL.

        The PHP version:

        PHP 5.5.9-1ubuntu4.17 (cli) (built: May 19 2016 19:05:57)
        Copyright (c) 1997-2014 The PHP Group
        Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies
            with Zend OPcache v7.0.3, Copyright (c) 1999-2014, by Zend Technologies
        

        The Apache version:

        Server Version: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.17 OpenSSL/1.0.1f
        
        Show
        ariokkon Ari Okkonen added a comment - - edited To reduce the problem I created the following PHP program and ran it in `Spain2.arispoitest`: <?php // test_http_get.php 2016-06-14 ariokkon if ($_SERVER['REQUEST_METHOD'] == 'GET' ) { $url_out = 'http: //www.example.org/'; error_log('http_get(' . $url_out . ')'); $output_msg = http_get($url_out); error_log('Response: "' . $output_msg . '" '); echo('<http><head><title>test_http_get</title></head>'); echo('<body>'. $output_msg . '</body></html>'); } ?> Related excerpt from the `/var/log/apache2/error.log`: [Tue Jun 14 08:49:33.823372 2016] [:error] [pid 1257] [client 193.209.92.202:49259] http_get(http: //www.example.org/) [Tue Jun 14 08:49:38.868960 2016] [:error] [pid 1257] [client 193.209.92.202:49259] PHP Warning: http_get(): Timeout was reached; Resolving timed out after 3513 milliseconds (http: //www.example.org/) in / var /www/html/poi_dp/test_http_get.php on line 13 [Tue Jun 14 08:49:38.869175 2016] [:error] [pid 1257] [client 193.209.92.202:49259] Response: "" And the resulting response: <http><head><title>test_http_get</title></head><body></body></html> Nothing in the body. So. The http_get() goes to timeout without getting anything from a well established URL. The PHP version: PHP 5.5.9-1ubuntu4.17 (cli) (built: May 19 2016 19:05:57) Copyright (c) 1997-2014 The PHP Group Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies with Zend OPcache v7.0.3, Copyright (c) 1999-2014, by Zend Technologies The Apache version: Server Version: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.17 OpenSSL/1.0.1f
        Hide
        ariokkon Ari Okkonen added a comment - - edited

        Other, possibly related information:

        ubuntu@arispoitest:~$ route -n
        Kernel IP routing table
        Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
        0.0.0.0         192.168.192.1   0.0.0.0         UG    0      0        0 eth0
        192.168.192.0   0.0.0.0         255.255.192.0   U     0      0        0 eth0
        
        ubuntu@arispoitest:~$ cat /etc/network/interfaces
        auto lo
        iface lo inet loopback
         auto eth0
         iface eth0  inet dhcp
        
        ubuntu@arispoitest:~$ ifconfig -a
        eth0      Link encap:Ethernet  HWaddr fa:16:3e:e0:2f:f1
                  inet addr:192.168.224.245  Bcast:192.168.255.255  Mask:255.255.192.0
                  inet6 addr: fe80::f816:3eff:fee0:2ff1/64 Scope:Link
                  UP BROADCAST RUNNING MULTICAST  MTU:1400  Metric:1
                  RX packets:7484 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:1422 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:1000
                  RX bytes:398151 (398.1 KB)  TX bytes:236005 (236.0 KB)
        
        lo        Link encap:Local Loopback
                  inet addr:127.0.0.1  Mask:255.0.0.0
                  inet6 addr: ::1/128 Scope:Host
                  UP LOOPBACK RUNNING  MTU:65536  Metric:1
                  RX packets:850 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:850 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:0
                  RX bytes:279073 (279.0 KB)  TX bytes:279073 (279.0 KB)
        
        ubuntu@arispoitest:~$
        
        Show
        ariokkon Ari Okkonen added a comment - - edited Other, possibly related information: ubuntu@arispoitest:~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.192.1 0.0.0.0 UG 0 0 0 eth0 192.168.192.0 0.0.0.0 255.255.192.0 U 0 0 0 eth0 ubuntu@arispoitest:~$ cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp ubuntu@arispoitest:~$ ifconfig -a eth0 Link encap:Ethernet HWaddr fa:16:3e:e0:2f:f1 inet addr:192.168.224.245 Bcast:192.168.255.255 Mask:255.255.192.0 inet6 addr: fe80::f816:3eff:fee0:2ff1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1400 Metric:1 RX packets:7484 errors:0 dropped:0 overruns:0 frame:0 TX packets:1422 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:398151 (398.1 KB) TX bytes:236005 (236.0 KB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:850 errors:0 dropped:0 overruns:0 frame:0 TX packets:850 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:279073 (279.0 KB) TX bytes:279073 (279.0 KB) ubuntu@arispoitest:~$
        Hide
        jicg José Ignacio Carretero Guarde added a comment -

        I guess it is a matter with DNS resolution of www.example.org — If you edit /etc/resolv.conf and change the DNS order, then you'll be able to solve that concrete name faster.

        It should be like this (/etc/resolv.conf)

        1. Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
        2. DO NOT EDIT THIS FILE BY HAND – YOUR CHANGES WILL BE OVERWRITTEN
          nameserver 8.8.8.8
          nameserver 8.8.4.4
          search openstacklocal

        ----- You could even add these lines to your /etc/rc.local in order to keep the changes between reboots:
        cat << EOT | sudo tee /etc/resolv.conf
        nameserver 8.8.8.8
        nameserver 8.8.4.4
        search openstacklocal
        EOT

        Regards,
        José Ignacio.

        Show
        jicg José Ignacio Carretero Guarde added a comment - I guess it is a matter with DNS resolution of www.example.org — If you edit /etc/resolv.conf and change the DNS order, then you'll be able to solve that concrete name faster. It should be like this (/etc/resolv.conf) Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) DO NOT EDIT THIS FILE BY HAND – YOUR CHANGES WILL BE OVERWRITTEN nameserver 8.8.8.8 nameserver 8.8.4.4 search openstacklocal ----- You could even add these lines to your /etc/rc.local in order to keep the changes between reboots: cat << EOT | sudo tee /etc/resolv.conf nameserver 8.8.8.8 nameserver 8.8.4.4 search openstacklocal EOT Regards, José Ignacio.
        Hide
        ariokkon Ari Okkonen added a comment -

        Thank you. Works better after those changes. Can be closed.

        Show
        ariokkon Ari Okkonen added a comment - Thank you. Works better after those changes. Can be closed.

          People

          • Assignee:
            jicg José Ignacio Carretero Guarde
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: