Skip to content

GitLab

Closed
Created by Justin Albstmeijer@jalbstmeijer

Back end cronjob does not seem to handle errors very well

using ispconfig r373

Back end cronjob does not seem to handle errors very well.

Two examples:

creating a database with a non valid name:

07.07.2008-17:22 - DEBUG - Raised TableHook for table: 'web_database' 07.07.2008-17:22 - DEBUG - Call function 'process' in module 'database_module' raised by TableHook 'web_database'. 07.07.2008-17:22 - DEBUG - Raised event: 'database_insert' 07.07.2008-17:22 - DEBUG - Call function 'db_insert' in plugin 'mysql_clientdb_plugin' raised by event 'database_insert'. 07.07.2008-17:22 - ERROR - Unable to connect to the databaseYou have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '1234' at line 1 07.07.2008-17:22 - DEBUG - Deleting sys_datalog ID 118

-- Should the request be deleted from the queue if it is not processed correctly? -- -- Adding the actual sql commands used would be usefull in the debug output ---

deleting a non existing database:

07.07.2008-17:28 - DEBUG - Raised TableHook for table: 'web_database' 07.07.2008-17:28 - DEBUG - Call function 'process' in module 'database_module' raised by TableHook 'web_database'. 07.07.2008-17:28 - DEBUG - Raised event: 'database_delete' 07.07.2008-17:28 - DEBUG - Call function 'db_delete' in plugin 'mysql_clientdb_plugin' raised by event 'database_delete'. 07.07.2008-17:28 - DEBUG - Dropping mysql user: 1234 07.07.2008-17:28 - DEBUG - Dropping mysql database: 1234 07.07.2008-17:28 - DEBUG - Deleting sys_datalog ID 119

-- deleting the previous not created database, does not seem to trigger any error. ---