EDK 4.4.0.0 with ESI support

[neffets]

hey

max_process: 10
zkb_negoffset: 2
latest_timestamp: 2011-07-04 19:00:00


with these settings processing the cron.php for zkb takes between 15 and 25 seconds if no kill is parsed. I fear with setting this up too much, i would exeed my php-script-execution-time of 60s

[Salvoxia]

Hi,

I sent you a PM about that.

Best Regards,
Salvoxia

[neffets]

Thank you for working this out so fast! Awesome support!

[Salvoxia]

Hi all,

as it turned out, that problem was actually not related with ESI, but an inherent problem with zKBFetch.
The issue was added to the list of known issues in the first post, along with a hotfix.

A big thanks to neffets for great cooperation to debug this problem

Best Regards,
Salvoxia

[Bas]

Hello, Salvoxia!

Thanks for release.
At this moment I've few errors in logs, some of them only warnings, but anyway
First of all, current server configuration:

Graphics
GD is available.
FreeType support is enabled
Cache directory is writeable
Connectivity
allow_url_fopen is available.
Socket Connect is available.
OpenSSL module is installed.
HTTPS wrapper is installed.
cURL with SSL support is available.
Server
PHP version: 7.2.5
MYSQL version: 5.6
API Caching
Current API caching folder is set to /opt/www/kb/cache/esi
API Caching folder exists.
API Caching folder is writable.
Successfully connected to ESI API
SQL Caching
Current SQL caching folder is set to /opt/www/kb/cache/SQL
SQL Caching folder exists.
SQL Caching folder is writable.
Object Caching
Current Object caching folder is set to /opt/www/kb/cache/store
Object Caching folder exists.
Object Caching folder is writable.

Page: SSO Keys
I pressed "Fetch Killls", all is ok, but I've the following notices:

Notice: No suitable handler for query found. "select" in /opt/www/kb/common/includes/class.dbcachedquery.php on line 263

Notice: Undefined variable: on_load in /opt/www/kb/common/smarty/sysplugins/smarty_internal_data.php on line 291
style="height: 100%">

I using atxedk Theme v1.4. I updated it.

And finally:

Unknown solar system ID: 32000062, KillID = 70257174
Unknown solar system ID: 32000062, KillID = 70257183

Some compatibility notices from PHP log:

PHP 2018-05-29 19:07:08 8192: The each() function is deprecated. This message will be suppressed on further calls in /opt/www/kb/common/smarty/sysplugins/smarty_internal_compilebase.php on line 52
PHP 2018-05-29 19:28:31 2: Use of undefined constant KB_PROFILE - assumed 'KB_PROFILE' (this will throw an Error in a future version of PHP) in /opt/www/kb/common/includes/class.page.php on line 183

[Salvoxia]

Hi,

for the notices, please see here: http://www.evekb.org/forum/viewtopic.ph ... 062#p50446

The unknown solar systems are abyssal deadspace. Right now, EDK cannot post these kills, because it does not know the solar systems. The ESI endpoint for solar systems can not yet handle abyssal deadspace, and I'm still waiting for the current SDE conversion.
So v 4.4.1.0 incoming

I'll take a look at the compatibility warnings, haven't worked yet with PHP 7.2.

Best Regards,
Salvoxia

[Bas]

smarty notices - fixed
style notice - fixed
unknown solar systems - clear for me, will wait
compatibility warnings - clear

No suitable handler for query found

didn't find

[Salvoxia]

Hi,

if you like to help me hunt that one down, could you please do the following:
Open common/includes/class.dbcachedquery.php and replace the this line of code

Code: Select all

trigger_error('No suitable handler for query found. "'.$ta[0].'"',E_USER_NOTICE);

with this one

Code: Select all

trigger_error('No suitable handler for query found. "'.$ta[0].'", SQL: '.$sql,E_USER_NOTICE);

That should add the SQL query causing this notice. If I know that, I can find out why that method was called (even though it shouldn't for select statements).

Best Regards,
Salvoxia

[Bas]

Great! Fetcher works without any errors/warnings/notices.
Thank you!

[Dism0]

cant wait for 4.4.1 to come out so i can make fun of my corps abyss losses.