- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-25-2015 04:08 PM
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><?xml version="1.0" encoding="UTF-8"?>
<DescribeImagesResponse xmlns="http://ec2.amazonaws.com/doc/2013-08-15/">
<requestId>ec2ef18d-f9dc-4a22-aa0e-3d0b
My instance is dev10218
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-29-2015 09:38 AM
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).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-25-2015 04:51 PM
Hi Kenny,
It looks like your two instances are on two different version of ServiceNow.
One suggestion is to upgrade both to Fuji Patch 4 and run your test again.
Jack
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-26-2015 07:58 AM
Actually, the instance I mentioned has a newer patch version than the one that works properly. I am, however, getting an update today. So, we'll see how that goes first. It should be done by 9:30 a.m. your time.
Thanks for the info.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-26-2015 10:15 AM
My instance has been upgraded. I am still receiving the same errors when executing AWS discovery. (dev10218)
Can you please take a look at this?
Thanks!
From: Kenny Wimberly
Sent: Friday, June 26, 2015 10:58 AM
To: 'servicenow-pub@phx1.jivehosted.com'
Subject: RE: Help - Amazon (AWS) Discovery Issue k-h5sw
Actually, the instance I mentioned has a newer patch version than the one that works properly. I am, however, getting an update today. So, we'll see how that goes first. It should be done by 9:30 a.m. your time.
Thanks for the info.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-26-2015 10:26 AM
Hi Kenny,
Unfortunately I'm not very familiar with the Discovery product and don't have much to add at this point.
Would you like me to move this question out to the regular developer community to see if someone there can help? That area gets more community visibility.
Jack