Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "Merge #3108 Cleanup project, update builds, fixes" #3113

Merged
merged 1 commit into from
Jul 14, 2020

Conversation

HebaruSan
Copy link
Member

Problem

The Inflator refuses to start. Mods haven't been updated in over 24 hours.

650 [1] DEBUG CKAN.NetKAN.Processors.QueueHandler (null) - Initializing SQS queue handler
681 [1] DEBUG CKAN.NetKAN.Processors.Inflator (null) - Initializing inflator
861 [1] INFO CKAN.KSPManager (null) - Loading KSP instances from registry
881 [1] INFO CKAN.NetKAN.Processors.Inflator (null) - Using main CKAN meta-cache at /home/netkan/.local/share/CKAN/downloads
1302 [1] DEBUG CKAN.NetKAN.Processors.QueueHandler (null) - Looking up URL for queue Inbound.fifo
32828 [1] FATAL CKAN.NetKAN.Program (null) - Unable to get IAM security credentials from EC2 Instance Metadata Service.
32830 [1] FATAL CKAN.NetKAN.Program (null) -   at Amazon.Runtime.DefaultInstanceProfileAWSCredentials.FetchCredentials () [0x00013] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.DefaultInstanceProfileAWSCredentials.GetCredentials () [0x0001b] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.CredentialsRetriever.PreInvoke (Amazon.Runtime.IExecutionContext executionContext) [0x00030] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.CredentialsRetriever.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x00000] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.PipelineHandler.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x0000e] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.RetryHandler.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x00050] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.PipelineHandler.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x0000e] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.CallbackHandler.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x00007] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.PipelineHandler.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x0000e] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.EndpointResolver.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x00007] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.PipelineHandler.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x0000e] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.SQS.Internal.ProcessRequestHandler.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x00007] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.PipelineHandler.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x0000e] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.Marshaller.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x00006] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.PipelineHandler.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x0000e] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.CallbackHandler.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x00007] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.PipelineHandler.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x0000e] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.ErrorCallbackHandler.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x00012] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.PipelineHandler.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x0000e] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.MetricsHandler.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x0002b] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.Internal.RuntimePipeline.InvokeSync (Amazon.Runtime.IExecutionContext executionContext) [0x00006] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.Runtime.AmazonServiceClient.Invoke[TResponse] (Amazon.Runtime.AmazonWebServiceRequest request, Amazon.Runtime.Internal.InvokeOptionsBase options) [0x0007d] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at Amazon.SQS.AmazonSQSClient.GetQueueUrl (Amazon.SQS.Model.GetQueueUrlRequest request) [0x0001c] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at CKAN.NetKAN.Processors.QueueHandler.getQueueUrl (System.String name) [0x00022] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at CKAN.NetKAN.Processors.QueueHandler..ctor (System.String inputQueueName, System.String outputQueueName, System.String cacheDir, System.Boolean overwriteCache, System.String githubToken, System.Boolean prerelease) [0x0005e] in <7bf78a1a90b146f1b4841c36916192cf>:0 
  at CKAN.NetKAN.Program.Run (CKAN.NetKAN.CmdLineOptions options) [0x0014b] in <7bf78a1a90b146f1b4841c36916192cf>:0 

Cause

The relevant part of the error is, "Unable to get IAM security credentials from EC2 Instance Metadata Service." I don't know what that means, but it happens when we access AWS to try to get our input queue name. This started when we merged #3108, which updated the reference for AWSSDK.

Changes

The changes from #3108 are now reverted. This will allow us to get the Inflator running again while we figure out what went wrong and how to fix it.

Fixes #3112 (probably).

This reverts commit 5912af2, reversing
changes made to 7c6310b.
@HebaruSan HebaruSan added Bug Something is not working as intended Pull request Build Issues affecting the build system Netkan Issues affecting the netkan data labels Jul 13, 2020
Copy link
Member

@DasSkelett DasSkelett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, let's take the safe way., since we don't know for 100% whether the SDK update is the cause, or maybe the CommandLineParser changes or something else.

@HebaruSan
Copy link
Member Author

Yeah, I'd prefer to zero in on the exact cause and fix just that, because there's a lot here that looks useful, but I don't have a working testbed in which to perform that kind of investigation; I get a failing dev-bot regardless of what I compile...

@HebaruSan HebaruSan merged commit b22eaed into KSP-CKAN:master Jul 14, 2020
@HebaruSan HebaruSan deleted the revert/build-updates branch July 14, 2020 00:02
@HebaruSan
Copy link
Member Author

Whew, it's running again. 😌
http://status.ksp-ckan.space/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is not working as intended Build Issues affecting the build system Netkan Issues affecting the netkan data
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] netkan.exe no longer able to successfully use IAM
2 participants