Governance Log Showing "Failed Internal Error" for anyone else?

%3CLINGO-SUB%20id%3D%22lingo-sub-1120364%22%20slang%3D%22en-US%22%3EGovernance%20Log%20Showing%20%22Failed%20Internal%20Error%22%20for%20anyone%20else%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1120364%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%26nbsp%3B%3C%2FP%3E%3CP%3EParsing%20Cloud%20Discovery%20Logs%20was%20working%20up%20until%208%3A00%20AM%20Central%20this%20morning.%201%20out%20of%202%20log%20uploads%20were%20processed%20and%20hasn't%20worked%20since.%20My%20governance%20log%20shows%20%22Failed%20internal%20Error%22%20or%20pending%20for%20all%20cloud%20discovery%20logs.%20Connection%20is%20fine%20and%20changes%20haven't%20been%20made.%20Anyone%20else%20experiencing%20this%20issue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20345px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F166310i92E4FD0F59104917%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22Capture5.JPG%22%20title%3D%22Capture5.JPG%22%20%2F%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F166311i5669E9D31F985C2D%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22Capture4.JPG%22%20title%3D%22Capture4.JPG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1120364%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EFailed%20internal%20error%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Connector%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1156124%22%20slang%3D%22en-US%22%3ERe%3A%20Governance%20Log%20Showing%20%22Failed%20Internal%20Error%22%20for%20anyone%20else%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1156124%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F510396%22%20target%3D%22_blank%22%3E%40AL_IPSD%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHi%20AL_IPSD%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20validate%20the%20configured%20data%20source%20matches%20your%20firewall%2Fproxy.%20I%20would%20also%20recommend%20you%20restart%20the%20log%20collector%2Fdocker%20container%20to%20see%20if%20that%20resolves%20the%20issue.%20If%20all%20else%20fails%2C%20please%20open%20a%20support%20ticket%20to%20have%20this%20investigated%20further.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1158458%22%20slang%3D%22en-US%22%3ERe%3A%20Governance%20Log%20Showing%20%22Failed%20Internal%20Error%22%20for%20anyone%20else%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1158458%22%20slang%3D%22en-US%22%3E%3CP%3Ehi!%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F546565%22%20target%3D%22_blank%22%3E%40John_Lewis%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20had%20submitted%20a%20ticket%20via%20Azure.%20The%20issue%20ended%20up%20resolving%20itself%20later%20on%20in%20the%20day.%20I%20think%20there%20was%20just%20blip%20or%20something.%20All%20has%20been%20well%20since.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hello, 

Parsing Cloud Discovery Logs was working up until 8:00 AM Central this morning. 1 out of 2 log uploads were processed and hasn't worked since. My governance log shows "Failed internal Error" or pending for all cloud discovery logs. Connection is fine and changes haven't been made. Anyone else experiencing this issue?

 

Capture5.JPGCapture4.JPG

2 Replies

@AL_IPSD 

 

Hi AL_IPSD,

 

Please validate the configured data source matches your firewall/proxy. I would also recommend you restart the log collector/docker container to see if that resolves the issue. If all else fails, please open a support ticket to have this investigated further.

hi! @John_Lewis 

 

I had submitted a ticket via Azure. The issue ended up resolving itself later on in the day. I think there was just blip or something. All has been well since.

www.000webhost.com