-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when running cron_esi.php #97
Comments
Hi, nice catch! Best Regards, |
Sorry for the Close/Open: I misclicked (yeah, I know, I need new fingers, maybe new brain as well...). |
Regarding the commit, nope, it doesn't solve the issue. Also forgot to mention that it also affects the "Fetch kills" button in the SSO Keys page of the admin panel. Now, I said the issue was with curl and IPv6 but I might be wrong... Digging a bit further, I find that curl_close is called too early: the handle is closed on line 424 in class_esisso.php, but accessed further on line 428 if there is no result.
Which is what led me to say it was an IPv6 related issue. I need to dig this further to find the core issue. |
Well, it might still be an IPv6 issue, since silly me didn't remember that cURL is used in different places. Your error was thrown when refreshing the access token, and there the IPv4 IP resolution setting is not present. |
Running cron_esi.php from crontab or through php-fpm (i.e. accessing cron/cron_esi.php from a web browser) fails with the following log:
I have PHP 7.1.22 and curl 7.61.1. I think I made an update on curl not so long ago, and this is when the issue arose.
It seems the problem is caused by IPv6: curl is looking for an AAAA record for esi.evetech.com, which does not exist.
The solution is to tell curl to use IPv4 and look fo an A record.
When I have time, I will try to add this settings to curl configuration. In the meantime, if someone wants to fix it, I'll be more than happy.
The text was updated successfully, but these errors were encountered: