Si activo las General Variables del Mysql, cuando creo el modulo veo el siguiente FAIL en las querys de MysQL, por si os dice algo
ORDER BY name ASC
138 Query SELECT COUNT(*) FROM tupdate
138 Query SELECT COUNT(*) FROM tupdate WHERE data_rollback LIKE '%"admin":1%'
138 Query SELECT id_grupo FROM tagente WHERE id_agente = 1 LIMIT 1
138 Query SELECT count(*) FROM tincidencia WHERE id_agent = 1 LIMIT 1
138 Query SELECT nombre FROM tagente WHERE id_agente = 1 LIMIT 1
138 Query SELECT * FROM `tagente` WHERE `id_agente` = 1 LIMIT 1
138 Query SELECT id_agente_modulo FROM tagente_modulo WHERE `nombre` = 'Host Alive' AND `id_agente` = 1 LIMIT 1
138 Query INSERT INTO `tagente_modulo` (`id_tipo_modulo`, `descripcion`, `max`, `min`, `snmp_oid`, `snmp_community`, `id_module_group`, `module_interval`, `module_ff_interval`, `ip_target`, `tcp_port`, `tcp_rcv`, `tcp_send`, `id_export`, `plugin_user`, `plugin_pass`, `plugin_parameter`, `id_plugin`, `post_process`, `prediction_module`, `max_timeout`, `max_retries`, `disabled`, `id_modulo`, `custom_id`, `history_data`, `min_warning`, `max_warning`, `str_warning`, `min_critical`, `max_critical`, `str_critical`, `custom_string_1`, `custom_string_2`, `custom_string_3`, `custom_integer_1`, `custom_integer_2`, `min_ff_event`, `min_ff_event_normal`, `min_ff_event_warning`, `min_ff_event_critical`, `each_ff`, `ff_timeout`, `unit`, `macros`, `quiet`, `critical_instructions`, `warning_instructions`, `unknown_instructions`, `critical_inverse`, `warning_inverse`, `cron_interval`, `id_category`, `disabled_types_event`, `module_macros`, `nombre`, `id_agente`) VALUES (6,'Check if host is alive using ICMP ping check.',0,0,'0','',2,300,0,'',NULL,'','',0,'','','',0,'0',NULL,0,0,0,2,'',1,0.000000,0.000000,'',0.000000,0.000000,'','','','',0,0,0,0,0,0,0,0,'','',0,'','','',0,0,'* * * * *',0,'{"going_unknown":1}','W10=','Host Alive',1)
138 Query INSERT INTO `tsesion` (`id_usuario`, `accion`, `ip_origen`, `descripcion`, `fecha`, `utimestamp`) VALUES ('admin','Agent management','172.20.3.111','Fail to try added module 'Host Alive' for agent pandora','2016-12-01 08:50:23',1480578623)
138 Query SELECT policy_linked FROM tagente_modulo WHERE id_agente_modulo = '' LIMIT 1
138 Query SELECT id_tipo, descripcion
FROM ttipo_modulo
WHERE categoria IN (3,4,5)
ORDER BY descripcion
2016-12-01 10:01:02 11666 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE FROM treport_content
WHERE id_agent != 0
AND id_agent NOT IN (SELECT id_agente FROM tagente)
AND `type` NOT IN ('SLA_services','custom_graph','sql_graph_vbar','sql_graph_hbar','sql_graph_pie','database_serialized','sql','inventory','inventory_changes','netflow_area','netflow_pie','netflow_data','netflow_statistics','netflow_summary')
2016-12-01 10:01:02 11666 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE FROM treport_content
WHERE `type` LIKE 'exception'
AND id_rc NOT IN (SELECT id_report_content FROM treport_content_item)
Si miro la tabla que se queja, la tsesion, veo los fails
root@localhost [pandora]> select * from tsesionG
*************************** 37. row ***************************
id_sesion: 37
id_usuario: admin
ip_origen: 172.20.3.111
accion: Agent management
descripcion: Fail to try added module 'Host Alive' for agent VIEW00
fecha: 2016-11-30 16:35:36
utimestamp: 1480520136
*************************** 38. row ***************************
id_sesion: 38
id_usuario: admin
ip_origen: 172.20.3.111
accion: Agent management
descripcion: Fail to try added module 'Host Alive' for agent VIEW00
fecha: 2016-11-30 16:40:40
utimestamp: 1480520440
*************************** 39. row ***************************
Los permisos en MySQL estan correctos, porque sino no podría entrar en Pandora ni poder generar agentes por lo que ya no se que más logs puedo extraer. Esto os dice algo máS?