Multiple SQL Errors

[LogicSequence]

Database error: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'and d.attributeID in (137,602)' at line 5
SQL: select itt_slot from kb3_item_types inner join kb3_dgmtypeattributes d where itt_id = d.value and d.typeID = and d.attributeID in (137,602);
ERROR [256] SQL error (You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'and d.attributeID in (137,602)' at line 5
Error on line 46 in file /COA/www/killboard/common/includes/class.dbnormalquery.php
PHP 5.4.16 (Linux), EDK 4.0.4 (Crucible)
File: /COA/www/killboard/common/includes/class.dbnormalquery.php, line: 46, function: trigger_error
File: /COA/www/killboard/common/includes/class.item.php, line: 152, class: DBNormalQuery, function: execute
File: /COA/www/killboard/common/includes/class.idfeed.php, line: 806, class: Item, function: getSlot
File: /COA/www/killboard/common/includes/class.idfeed.php, line: 556, class: IDFeed, function: processItem
File: /COA/www/killboard/common/includes/class.idfeed.php, line: 485, class: IDFeed, function: processKill
File: /COA/www/killboard/common/includes/class.idfeed.php, line: 138, class: IDFeed, function: processFeed
File: /COA/www/killboard/common/admin/admin_idfeedsyndication.php, line: 155, class: IDFeed, function: read
File: /COA/www/killboard/common/admin/admin_idfeedsyndication.php, line: 83, function: getIDFeed
File: /COA/www/killboard/common/index.php, line: 293, function: include
File: /COA/www/killboard/index.php, line: 27, function: include

I'm getting this error when fetching kills now as well, even after i applied the fix in the thread linked above. I don't know what to do, any ideas?

[Unknown_Terror]

Hi guys, I applied the fixes suggested and they work a charm as I was having the same issue as problem 1 of the OP. I'm still getting one error though.

ERROR [256] Invalid mail, invalid involved weapon
Error on line 624 in file /home1/madbags/public_html/ulv/common/includes/class.kill.php
PHP 5.2.17 (Linux), EDK 4.0.4 (Crucible)
File: /home1/madbags/public_html/ulv/common/includes/class.kill.php, line: 624, function: trigger_error
File: /home1/madbags/public_html/ulv/common/includes/class.kill.php, line: 1665, class: Kill, function: getRawMail
File: /home1/madbags/public_html/ulv/common/includes/class.kill.php, line: 1373, class: Kill, function: getHash
File: /home1/madbags/public_html/ulv/common/includes/class.idfeed.php, line: 559, class: Kill, function: add
File: /home1/madbags/public_html/ulv/common/includes/class.idfeed.php, line: 485, class: IDFeed, function: processKill
File: /home1/madbags/public_html/ulv/common/includes/class.idfeed.php, line: 138, class: IDFeed, function: processFeed
File: /home1/madbags/public_html/ulv/common/admin/admin_idfeedsyndication.php, line: 155, class: IDFeed, function: read
File: /home1/madbags/public_html/ulv/common/admin/admin_idfeedsyndication.php, line: 83, function: getIDFeed
File: /home1/madbags/public_html/ulv/common/index.php, line: 293, function: include
File: /home1/madbags/public_html/ulv/index.php, line: 27, function: include

It could take me forever to find the actual killmail causing the problem but I don't know if anyone has a solution to this?

Thanks

[Eowarebin]

Upgrading to the Inferno data dump, http://eve-id.net/forum/viewtopic.php?f=503&t=18752, fixes the first SQL syntax error.

Unable to get into that forum.

[Fuegor]

Upgrading to the Inferno data dump, http://eve-id.net/forum/viewtopic.php?f=503&t=18752, fixes the first SQL syntax error.

Unable to get into that forum.

The link has the old forum host inside. Just replace eve-id.net with evekb.org and it will work: viewtopic.php?f=503&t=18752

Btw: The linked thread is about an old database, the current rubicon 1.0.8 DB thread is here: http://www.evekb.org/forum/viewtopic.php?f=503&t=21640

[Eowarebin]

Very odd that you had the open-basedir issue on the KB. I have it running on a CentOS server with cpanel and have never had this issue before.