That one did the trick, thanks!
EDK 4.4.0.0 with ESI support
-
- Someday Author
- Posts: 95
- Joined: Thu May 16, 2013 12:48
Re: EDK 4.4.0.0 with ESI support
ok i found, it was wrong permission on /cache/update folder ... thanks for your supportanchorhead wrote: ↑Thu May 10, 2018 16:02 Hello Salvoxia,
I tried with link to refresh description in upgrade section but always :
Fatal error: Call to a member function getAttribute() on null in /var/www/xxxx/update/CCPDB/xml.parser.php on line 118
But for this error i don't know :
Strict Standards: Static function statSummary::addKill() should not be abstract in /var/www/xxx/common/includes/class.statsummary.php on line 119
Strict Standards: Static function statSummary::delKill() should not be abstract in /var/www/xxx/common/includes/class.statsummary.php on line 125
Strict Standards: Static function statSummary::update() should not be abstract in /var/www/xxx/common/includes/class.statsummary.php on line 132
Re: EDK 4.4.0.0 with ESI support
Hi,
these are strictly spoken not errors but just notices, everything should still work. They are visible because of a wrong error reporting setting, the linked Fix #2 in this post should take care of that.
I'll look into cleaning it up, nevertheless.
Best Regards,
Salvoxia
these are strictly spoken not errors but just notices, everything should still work. They are visible because of a wrong error reporting setting, the linked Fix #2 in this post should take care of that.
I'll look into cleaning it up, nevertheless.
Best Regards,
Salvoxia
-
- Someday Author
- Posts: 95
- Joined: Thu May 16, 2013 12:48
Re: EDK 4.4.0.0 with ESI support
ok fine thanks youSalvoxia wrote: ↑Thu May 10, 2018 20:59 Hi,
these are strictly spoken not errors but just notices, everything should still work. They are visible because of a wrong error reporting setting, the linked Fix #2 in this post should take care of that.
I'll look into cleaning it up, nevertheless.
Best Regards,
Salvoxia
Re: EDK 4.4.0.0 with ESI support
Code: Select all
cron/cron_esi.php
2018/05/10 19:35:30 - ESI SSO Key: MyName (type: corp)
2018/05/10 19:35:30 - 0 kills were posted and 0 were skipped (1000 kills fetched)
2018/05/10 19:35:30 - Last kill ID: 498804
2018/05/10 19:35:30 - Stopped parsing after reaching maximum processing time of 55 seconds.
2018/05/10 19:35:30 - Spent 66.104444980621s talking to ESI
2018/05/10 19:35:30 - Time taken = 72.601155996323 seconds.
Suggestion: Add the date/time of the last kill plz


Re: EDK 4.4.0.0 with ESI support
It seams ignore npc only death isnt working.
I klicked it in sso tokens settings but still grabbed an npc kill.
I klicked it in sso tokens settings but still grabbed an npc kill.
Re: EDK 4.4.0.0 with ESI support
Also one small error showed up:
Code: Select all
http://my.site/index.php/admin_esisso/
Notice: Undefined variable: message in /killboardfolder/common/smarty/sysplugins/smarty_internal_data.php on line 291
Re: EDK 4.4.0.0 with ESI support
@celagon:
Hmm, I couldn't reproduce that.
Keep in mind that ESI fetch and zKBFetch have separate settings for ignoring NPC only kills.
If you already respected that, and it still didn't work correctly, could you please link such a kill?
Maybe the "NPC detection" has problems under certain circumstances..
@neffets:
Thanks for reporting. That's a minor "uncleanliness" in the template engine's code, and only visible due to wrong error reporting settings.
A hotfix for this can be found here.
Considering your corp's huge kill history, I'm really interested in whether ESIFetch worked through all right
And I'll take a look into reporting the last kill timestamp as well.
Best Regards,
Salvoxia
Hmm, I couldn't reproduce that.
Keep in mind that ESI fetch and zKBFetch have separate settings for ignoring NPC only kills.
If you already respected that, and it still didn't work correctly, could you please link such a kill?
Maybe the "NPC detection" has problems under certain circumstances..
@neffets:
Thanks for reporting. That's a minor "uncleanliness" in the template engine's code, and only visible due to wrong error reporting settings.
A hotfix for this can be found here.
Considering your corp's huge kill history, I'm really interested in whether ESIFetch worked through all right

And I'll take a look into reporting the last kill timestamp as well.
Best Regards,
Salvoxia
Re: EDK 4.4.0.0 with ESI support
awesome, i can't say thank you enough for the effort you put in this!
FYI:
Currently killboard is arround killid 10bil, so nearly 15% is done (max-killid as of today is near the 70bil)
I'm currently processing ~800kills/minute, while ~25 kills per 1000 fetched are getting posted.
so far its running really smooth, sometimes i get a "no result in last esi runs, skipping" message, but that only lasts a few minutes. And two times I had to change CHMOD on some cache-folders.
FYI:
Currently killboard is arround killid 10bil, so nearly 15% is done (max-killid as of today is near the 70bil)
I'm currently processing ~800kills/minute, while ~25 kills per 1000 fetched are getting posted.
so far its running really smooth, sometimes i get a "no result in last esi runs, skipping" message, but that only lasts a few minutes. And two times I had to change CHMOD on some cache-folders.
Re: EDK 4.4.0.0 with ESI support
Aand i run into a not parsable kill:
https://esi.tech.ccp.is/latest/killmail ... fa8cd6c65/
2018/05/11 18:09:19 - Error processing involved party. Kill-ID: 16522946, KillID = 16522946
https://esi.tech.ccp.is/latest/killmail ... fa8cd6c65/
2018/05/11 18:09:19 - Error processing involved party. Kill-ID: 16522946, KillID = 16522946