Loading ...
Sorry, an error occurred while loading the content.

5699RE: Placefinder zero results on all requests?

Expand Messages
  • stephen718@ymail.com
    Nov 1, 2013

      Sure.


      1. Querying from a Java based application running on an Amazon EC2 instance.  Though I also tried it from the example PHP script running off the Amazon EC2 instance, and from a CentOS VM I run on my development laptop, got the exact same response: <?xml version="1.0" encoding="UTF-8"?><bossresponse responsecode="200"><placefinder start="0" count="0" request="gflags=R&amp;location=51.03808%2B-114.03401"></placefinder></bossresponse>


      2. Sure, though I'm getting a 200 response on all requests, as well as and the above XML so I don't think it's a network issue. I'll put the traceroute from my development box at the end of this.


      3. Placefinder is the only thing we use, so I don't know if other queries would be the same.


      Is it possible it's an issue with our individual application key/credentials so we're getting different results on our account vs. what you are getting?  Is there another set of test credentials I could use to try?


      Traceroute:


      [root@JASON geo]# traceroute yboss.yahooapis.com

      traceroute to yboss.yahooapis.com (98.136.188.39), 30 hops max, 60 byte packets

       1  router.asus.com (10.1.1.1)  0.512 ms  0.384 ms  0.486 ms

       2  * * *

       3  rc3so-tge0-0-0-7-28.cg.shawcable.net (64.59.131.213)  10.911 ms  11.672 ms  12.578 ms

       4  66.163.70.214 (66.163.70.214)  35.511 ms 66.163.70.242 (66.163.70.242)  35.454 ms rc5wt-tge0-4-0-1.wa.shawcable.net (66.163.70.190)  34.812 ms

       5  six.yahoo.com (206.81.80.98)  35.611 ms  35.525 ms  35.463 ms

       6  ae-7.pat2.gqb.yahoo.com (216.115.101.109)  40.342 ms  38.349 ms  38.897 ms

       7  ae-0.msr1.gq1.yahoo.com (66.196.67.1)  38.820 ms ae-1.msr2.gq1.yahoo.com (66.196.67.3)  36.325 ms ae-0.msr2.gq1.yahoo.com (66.196.67.23)  36.393 ms

       8  xe-9-0-0.clr1-a-gdc.gq1.yahoo.com (98.137.31.137)  38.893 ms xe-3-0-0.clr1-a-gdc.gq1.yahoo.com (98.137.31.131)  40.024 ms xe-4-0-0.clr1-a-gdc.gq1.yahoo.com (68.180.253.129)  38.828 ms

       9  et-17-1.fab8-1-gdc.gq1.yahoo.com (98.137.31.192)  39.324 ms et-17-1.fab4-1-gdc.gq1.yahoo.com (98.137.31.176)  39.443 ms  39.259 ms

      10  po-16.bas2-10-prd.gq1.yahoo.com (98.137.252.39)  39.163 ms po-15.bas1-10-prd.gq1.yahoo.com (98.137.252.19)  40.573 ms po-11.bas1-10-prd.gq1.yahoo.com (98.137.252.11)  39.030 ms

      11  * * *

      12  * * *

      13  * * *

      14  * * *

      15  * * *

      16  * * *

      17  * * *

      18  * * *

      19  * * *

      20  * * *

      21  * * *

      22  * * *

      23  * * *

      24  * * *

      25  * * *

      26  * * *

      27  * * *

      28  * * *

      29  * * *

      30  * * *



      ---In ysearchboss@yahoogroups.com, <rhampole@...> wrote:

      Can you provide some more context here since I tried running the same query tens of times and it worked every time for me. 

      1. Where are you querying from? 
      2. Can you provide a trace route if possible? 
      3. Are you having this problem for other queries? 
      We also run sample queries for our Status dashboard (http://developer.yahoo.com/apistatus/) and have not seen any issues there. 

      Thanks,
      BOSS Team


    • Show all 13 messages in this topic