I am trying to read data from IBM MQ using ibmmq node module. The lambda function works fine with serverless-offline plugin with the below changes in my local environment.
Downgrading python version to 2.x
Installing windows build tools, node-gyp, Windows8.0 SDK, visual studio 2015
But the same lambda when deployed in AWS throws the below error
module initialization error: Error
at Error (native)
at bindings (/var/task/node_modules/ibmmq/node_modules/bindings/bindings.js:76:44)
at Object. (/var/task/node_modules/ibmmq/node_modules/ref/lib/ref.js:5:47)
at Module._compile (module.js:570:32)
I have added windows-build-tools to my dependencies. Any ideas on how to make this work
Related
I'm running a terraform plan through AWS Codebuild. terraform init works consistently but terraform plan intermittently throws this error:
Error: rpc error: code = Canceled desc = context canceled
terraform version: 0.12.31
aws provider version: ~> 3.55.0
The intention here was to change Python lambda runtimes from 3.6 to 3.9. In this regard, I upgraded terraform from 0.12.21 to 0.12.31 and aws provider version from ~>2 to ~> 3.55.0 (aws provider version 3.55.0 is the first version that supports python 3.9 runtime)
I've seen that others have had similar issues and what seemed to have worked for them is trying a different version of the provider. I wanted to keep these versions of terraform and aws provider because if I upgrade it further here, it would have consequences elsewhere in our pipeline. Does anyone have any ideas on how I can move forward?
I've finally solved it. I increased the Compute resources allocated to Codebuild by following this page: https://docs.aws.amazon.com/codebuild/latest/userguide/change-project-cli.html
All my builds are running through successfully now. So it looks like it was just the resource constraint all along.
I am experiencing a problem installing the PowerShell module on the Windows 2019 server. The server is a cloud server hosted on an AWS Ec2 instance. I have followed all the online resources to debug the issue, and I have enabled the tls12 on the server. But still, I am facing a problem with installing any of the modules.
Getting the PackageManagement error as well as the source warning.
WARNING: Source Location 'https://www.powershellgallery.com/api/v2/package/PackageManagement/1.4.7' is not valid.
PackageManagement\Install-Package : Package 'PackageManagement' failed to download. Here is the screenshot of the error from PowerShell session
I am trying to restore NuGet packages from the Azure Artifacts feed with the task "Nuget restore" which is giving an error -
2020-03-17T06:16:01.923910Z Resolved from tool cache: 4.1.0
2020-03-17T06:16:01.939365Z Using version: 4.1.0
2020-03-17T06:16:01.924520Z Found tool in cache: NuGet 4.1.0 x64
2020-03-17T06:16:02.080668Z [command]C:\Windows\system32\chcp.com 65001
2020-03-17T06:16:02.007116Z Active code page: 65001
2020-03-17T06:16:02.012223Z Detected NuGet version 4.1.0.2450 / 4.1.0
2020-03-17T06:16:02.081611Z SYSTEMVSSCONNECTION exists true
2020-03-17T06:16:04.157611Z ##[error]Error: Error: read ECONNRESET
2020-03-17T06:16:04.190260Z ##[error]Packages failed to restore
Details -
Server - Azure DevOps server 2019
Azure DevOps build pipeline
Azure Artifacts Feed - offline
Agent Version 2.144.2
What I noticed
my "Nuget Restore" task is working well when my build machine is in the same LAN with azure DevOps server and giving an error with the different LAN's build machine.
I googled but did not find anything. some pages showing this error is because of the proxy, some page is showing version issue of NuGet.
Not getting what exactly the issue is. Can someone help with this?
Sonarqube error in VSTS Build when version 4 of sonar extension is used.
Error -
[SQ] API GET. '/api/server/version' failed, error was:
{"code":"UNABLE_TO_GET_ISSUER_CERT_LOCALLY"} .
SonarQube extension version 3 build runs successfully.
We are using Sonarqube version 7.1
I also faced same error:
[error][SQ] API GET '/api/server/version' failed, error was: {"code":"UNABLE_TO_GET_ISSUER_CERT_LOCALLY"
To fix this issue:
First I installed Java 17 to devOps build agent machine https://www.oracle.com/java/technologies/javase/jdk17-archive-downloads.html
Java SE Development Kit 17.0.5 Windows x64 Installer.
Installed path: C:\Program Files\Java\jdk-17.0.5
Then add two devOps build pipeline variables:
NODE_EXTRA_CA_CERTS and SONAR_SCANNER_OPTS
SONAR_SCANNER_OPTS:
Copy your cacerts and replace existing one.
path: “…\Java\jdk 17.0.5\lib\security\cacerts”
Then add both paths in devOps SONAR_SCANNER_OPTS variable:
-Djavax.net.ssl.trustStore="C:\program files\Java\jdk 17.0.5\lib\security\cacerts"
-Djavax.net.ssl.keyStore="C:\program files\Java\jdk 17.0.5\lib\security\cacerts"
NODE_EXTRA_CA_CERTS:
copy your cert *.PEM file and replace it the existing one in devops build agent path: C:\devOps_Agent\sonarchain.pem
After this step SonarQube prepare starting to work.
I am trying to learn to use the AWS SDK for Ruby, and I started by running the sample programs on S3. But the S3 example gives me this error:
/var/lib/gems/1.9.1/gems/aws-sdk-1.8.0/lib/aws/core/client.rb:318:in 'return_or_raise':AWS::Core::Client::NetworkError (AWS::Core::Client::NetworkError)
from /var/lib/gems/1.9.1/gems/aws-sdk-1.8.0/lib/aws/core/client.rb:419:in 'client_request'
from (eval):3:in 'put_object'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.8.0/lib/aws/s3/s3_object.rb:1655:in 'write_with_put_object'
from /var/lib/gems/1.9.1/gems/aws-sdk-1.8.0/lib/aws/s3/s3_object.rb:600:in 'write'
from s3/upload_file.rb:31:in 'main'
I have already checked using s3cmd and it is working fine.
I am using Ruby 1.9.1 and AWS SDK version is 1.8.0.