PHP Fatal error: Uncaught You have an error in your SQL syntax

[OUengineer]

Hi, 
 

log file from our server is full with this error. 
We couldn't find the solution related to this problem. 

We are using prestashop 1.6.1.11

 

[19-Apr-2017 13:03:22 Europe/Bucharest] PHP Fatal error:  Uncaught You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LIMIT 1' at line 4<br /><br /><pre>

            SELECT m.*

            FROM `ps_module` m

            JOIN `ps_module_shop` ms ON (m.`id_module` = ms.`id_module` AND ms.`id_shop` = 1)

            WHERE m.`id_module` = LIMIT 1</pre>

  thrown in /****/classes/db/Db.php on line 791

 

 

 

 

The 791 line in Db.php is this: 
 

 

If someone have some information to fix this would be awesome.
Thank you  

[Knowband Plugins]

There is no such query by default in PrestaShop v1.6.1.11 . This query must be executed from some of the third party modules on your store. Can you please let us know if one of your installed modules is executing this query to fetch some data?

[OUengineer]

Thank you for your advice. 

I don't find any related module in our prestashop BUT I saw our logs on prestashop backoffice and when this error start to record on server logs we have this :

 

Message: Add RequestSql

Object type: RequestSql  

Object id: 1 

 

From what I remember, but I am not sure, on that date and hour I tried to put a new cron job in module "cronjob". 
That job is already removed from cron job. Was "active" for few days. 

Could be this related with cron job ? 

Thank you 

[OUengineer]

After some searching about this "RequestSQL" I have found in AdminTools/RequestSQL. Someone put a request there. 
I have deleted and hope this fix the problem. 

Thank you Knowband. 

[Atomico]

Hi i have the same problem, but i have no cronjob e no query in requestSQL.. any other idea?

[OUengineer]

Hi i have the same problem, but i have no cronjob e no query in requestSQL.. any other idea?

I have put debug false and now I don't received this error anymore in my log file