Amazon (AWS) Discovery Issue

[Kenny Wimberly]

When trying to discover my AWS info, one one instance, I don't have any issues. On another instance, I get the following errors in my system log. I do not get all of the EC2 images as a result. I have the EXACT same setup in one instance and it works fine. It does not work in my current instance. This is an excerpt from one of the errors:

FAILED TRYING TO EXECUTE ON CONNECTION 27: INSERT INTO ecc_queue0002 (`payload`, `topic`, `queue`, `sys_id`, `sys_updated_on`, `state`, `sys_created_on`, `agent`, `sys_created_by`, `processed`, `source`, `response_to`, `sequence`, `sys_updated_by`, `name`, `agent_correlator`, `sys_mod_count`) VALUES(?, 'RESTProbe', 'input', '570046320f3446002b8d0dbce1050ebd', '2015-06-25 22:39:05', 'ready', '2015-06-25 22:39:05', 'mid.server.NODE_AGENT', 'admin', NULL, 'https://ec2.ap-northeast-1.amazonaws.com', 'ff0ff1320f3446002b8d0dbce1050eb1', '14e2cdfdb720000001', 'admin', 'get', '430ffdfe0ff046002b8d0dbce1050e81', 0)

Syntax Error or Access Rule Violation detected by database (The size of BLOB/TEXT data inserted in one transaction is greater than 10% of redo log size. Increase the redo log size using innodb_log_file_size.)

Placeholders follow:

0 (2483072):<?xml version="1.0" encoding="UTF-8"?><results probe_time="3623"><result><output>&lt;?xml version="1.0" encoding="UTF-8"?&gt;

&lt;DescribeImagesResponse xmlns="http://ec2.amazonaws.com/doc/2013-08-15/"&gt;

&lt;requestId&gt;ec2ef18d-f9dc-4a22-aa0e-3d0b

My instance is dev10218

[Kenny Wimberly]

This is not an issue that the community can resolve. It has to do with a setting on the back end DB. I guess my only option would be to wipe and start over.

[jnguy1]

Hey Kenny,

Were you able to get this sorted out?

Thanks.
Jack

[Kenny Wimberly]

I released the instance and provisioned another one today. We'll see if discovery works on this one. I'll keep you posted. If you don't hear anything from me, it is sorted out. However, I wanted to report it just in case there is a similar issue on a prod instance that can't be reprovisioned.

Thanks.

[Kenny Wimberly · Accepted solution]

I have completed the AWS setup on my new instance after all plugins have been installed and verified. I am now able to do a discovery properly on the new instance without issue (13669).

[jnguy1]

Great - glad to hear you were able to get it to work