Open Nfinished opened 3 years ago
can you share your eseye.log
and provide date/time when this error append ?
2020-12-31 08:26:31
Point me to the eseye.log
?
/var/www/seat/storage/logs
together with its friends š
Odd, no log for December 31. No eseye logs at all, just laravel
You should have one with the upper message which is tied to a 4xx or 5xx response from ESI. If none exist, then, you have directory permission issue.
My experience with planet-related exceptions is that the user probably has an outdated legacy PI setup somewhere. Check which character it relates to (job information in horizon will show you that somewhere) and ask them to remove it in game, this solved all the issues I had with this error. It's likely they're not using planets anyway if they have this error, so that should solve the errors appearing in your instance. SeAT could of course also still support the legacy outdated planets but... eh.
To support things, we need valid response from esi. And here, it seems something make it crash š
If you set log level to debug and requeue the failed job, you should get the response body in eseye log together with response status
@Nfinished Also note that if you are using a docker installation, the eseye log will only be present in the seat-worker
container
Ah that'd be it, I was looking in seat-web. Will share logs soon.
Sharing because the error text suggests it's not on CCP's side. All packages up to date.
Seat\Eveapi\Jobs\PlanetaryInteraction\Character\Planets