Mikk36 / eve-online-carebear-statistics

Automatically exported from code.google.com/p/eve-online-carebear-statistics
0 stars 1 forks source link

Could not fetch data #2

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Updated to the new version 23rd Dec 2011
2. Put in new CAK in config file
3. run cron job (load cron.php)

What is the expected output? What do you see instead?
Expected: Get journal rows and put in db. Actual: Error message saying 'Could 
not fetch data' and no data being imported. 

What version of the product are you using? On what operating system?
New version 23/11/11. Linux server

Please provide any additional information below.
I have checked the api key by going directly to the page ( 
https://api.eve-online.com/corp/WalletJournal.xml.aspx?keyID=myuserID&vcode=myAP
iKey&characterID=mycharID) and it works there, I can see all the data etc... 

Original issue reported on code.google.com by aska...@gmail.com on 26 Dec 2011 at 10:10

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
I updated the cron.php file to include a bit more detailed error message if 
cURL is used. Try it out and we'll see what's the issue.

Original comment by mik...@gmail.com on 29 Dec 2011 at 10:59

GoogleCodeExporter commented 8 years ago
With usecurl set to true I get this (with new cron.php file). 
----------------
<br />
Warning:  curl_errno(): 7 is not a valid cURL handle resource in 
/home/avalon/public_html/carebear/cron.php on line 254<br />
<br />
Warning:  curl_error(): 7 is not a valid cURL handle resource in 
/home/avalon/public_html/carebear/cron.php on line 254<br />
<br />
Warning:  curl_errno(): 7 is not a valid cURL handle resource in 
/home/avalon/public_html/carebear/cron.php on line 255<br />
<br />
Warning:  curl_error(): 7 is not a valid cURL handle resource in 
/home/avalon/public_html/carebear/cron.php on line 255<br />
Could not fetch data, error no : ""
---------------

With usecurl set false I get this: 
----------------
<br />
Warning:  
file_get_contents(https://api.eveonline.com/corp/CorporationSheet.xml.aspx?keyID
=apiid&vCode=privatecode&characterID=toonid) [<a 
href='function.file-get-contents'>function.file-get-contents</a>]: failed to 
open stream: Connection timed out in /home/avalon/public_html/carebear/cron.php 
on line 75<br />
Could not fetch data
----------------
Obviously changed api info. However I think I have found the issue. In the 
corporationsheet link it is wrong, it is & when it should only be &. I don't 
see any differences however from the old cron.php file but my php is crap and 
so don't know how to fix this and if it is indeed the issue. 

Original comment by aska...@gmail.com on 30 Dec 2011 at 12:20

GoogleCodeExporter commented 8 years ago
My bad, had a bit bad order of code. Could you try it again now?
Should display the error correctly.

Original comment by mik...@gmail.com on 30 Dec 2011 at 12:54

GoogleCodeExporter commented 8 years ago
However, looking at your file_get_contents response, it would seem that 
something is blocking outgoing requests to the CCP API server.

Original comment by mik...@gmail.com on 30 Dec 2011 at 1:03

GoogleCodeExporter commented 8 years ago
Updated cron.php and got the below error messages with usecurl true and false: 
-----------------------------
Could not fetch data, error no 7: "couldn't connect to host"
-----------------------------
<br />
Warning:  
file_get_contents(https://api.eveonline.com/corp/CorporationSheet.xml.aspx?keyID
=mykeyid&vCode=myvcode&characterID=mycharid) [<a 
href='function.file-get-contents'>function.file-get-contents</a>]: failed to 
open stream: Connection timed out in /home/avalon/public_html/carebear/cron.php 
on line 75<br />
Could not fetch data
---------------------------------

Still have the error where that url doesn't work due to the amp; after the & 
causing an authentication failure on the ccp api server. 

I have a killboard and EVEBB forums running on the same server, both of which 
can access the api server fine, so shouldn't be a firewall or something. 

Original comment by aska...@gmail.com on 30 Dec 2011 at 8:58

GoogleCodeExporter commented 8 years ago
"Couldn't connect to host" is anything but related to you thinking it's the & 
issue. & is automatically translated when the error message is being printed 
for the user. If you want, you can echo out the url before it shuts down, but I 
assure, that's not the problem here.

Your real problem is that the PHP script can not get a connection to the 
api.eveonline.com.

Original comment by mik...@gmail.com on 30 Dec 2011 at 12:05

GoogleCodeExporter commented 8 years ago
ok then fair enough. 

I used to use the old version but with your updated on 23rd Dec decided it was 
time to update to the new CAK. The old version worked fine and could access the 
api server, and so can the currently working killboard and evebb forums on the 
same server. Any ideas?

Original comment by aska...@gmail.com on 30 Dec 2011 at 12:40

GoogleCodeExporter commented 8 years ago
Not many, I still think it's something in your server configuration that must 
be not letting the script access the site. The script itself is a direct mirror 
from my own server, where it's working fine.
Even more, the script has received very little modification over from what you 
propably had before.
The API URL only received two edits, both in one commit: 
http://code.google.com/p/eve-online-carebear-statistics/source/diff?path=/cron.p
hp&format=side&r=a2eccab6e57ed7dc00a4e1e55db62ef0785fa7fb&old_path=/cron.php&old
=255aff137d6f926617d00085d15486d3b0b98c86

Original comment by mik...@gmail.com on 30 Dec 2011 at 9:29

GoogleCodeExporter commented 8 years ago
If the request got through and it contained malformed information, you would 
see an error in the cron.log file, for example:
2011-12-30 11:30:06 Error 901: Web site database temporarily disabled.
2011-12-30 21:32:54 Error 203: Authentication failure.

Original comment by mik...@gmail.com on 30 Dec 2011 at 9:34

GoogleCodeExporter commented 8 years ago
Any news?

Original comment by mik...@gmail.com on 6 Jan 2012 at 1:42

GoogleCodeExporter commented 8 years ago
CCP have said it is not them blocking anything their end. My host says they are 
not blocking anything on their firewalls etc... however I am trying to get more 
info as if its not CCP, and my killboard works why else wouldn't this be 
working. I tried a clean install on a different account on same server, doesn't 
work either, so I think it is safe to say it is not your software but most 
likely my host blocking this script, which just seems plan weird, esp as a 
clean install in a new place also did not work. 

Waiting for them to get back to me still.... Otherwise any other ideas? I don't 
have shell access (or whatever it is) so I can't see if it can connect directly 
to the api.server, but like I said, killboard works fine... 

Let me know if you have any other ideas, even if its just to help troubleshoot 
it and dtermine where the connection is getting blocked. 

Original comment by aska...@gmail.com on 6 Jan 2012 at 1:51

GoogleCodeExporter commented 8 years ago
Finally got a reply from server host and says they can access it fine, and it 
now appears to work. I have a feeling it was the server host messing something 
up and fixing it without admitting it was them lol. 

Anyway, working again now, thanks! 

What are the chances of getting it to display Incursion info better? :)

Original comment by aska...@gmail.com on 9 Jan 2012 at 9:36

GoogleCodeExporter commented 8 years ago
Sigh. It appears it worked for 3 days and then stopped again. Has your working 
copy worked all the time? Just wondering if it is the eve api server being 
funky. It hasn't been able to connect from 4th Jan till now (and still won't). 
Thanks

Original comment by aska...@gmail.com on 13 Jan 2012 at 9:24

GoogleCodeExporter commented 8 years ago
Hosting company got back to me, they were blocking all outgoing https traffic 
:/ 

All working now anyway lol

Original comment by aska...@gmail.com on 16 Jan 2012 at 11:10

GoogleCodeExporter commented 8 years ago

Original comment by mik...@gmail.com on 25 Jan 2012 at 11:08