We have Azure Data Factory V2 pipeline, consuming data from on-prem SQL Server, Pipelines was running perfectly fine until 2 weeks. 2 weeks back it started running very slow (15min vs 2h:15min).
So today we tried to restart the machine which installed IR. After that pipeline started giving an error:
Unable to load DLL 'jvm.dll': The specified module could not be found.
We have verify everything mentioned in post.
Then we have reinstalled the Integration Runtime on the machine and now pipelines keep running without transferring data. All the pipelines lies in the queue. There is no activity we can see on IR Monitor. Pipelines are not sending any request to IR.
Sharing the answer as per the comment by the original poster:
Able to resolve the issue by reinstalling JRE and integration runtime.
Try a clean install. Uninstall the IR and the JRE, then install JRE, then IR.
Related
I tried to build an app using the GitLab pipeline and it failed with the following error
Execution failed for task ':react-native-reanimated:compileReleaseJavaWithJavac'.
But the app is built locally without any error. Can anyone have an idea why this happened?
I had a similar issue. Basically, your local machine and virtual machine on DevOps have different configurations. I solved it by updating the node and latest VM on azure DevOps. You can update your YAML file with the below code and change the node to the latest version available.
Please follow this solution: Android - `main` module field for "react-native-gesture-handler" lib that could not be resolved in Azure CI & its working fine in local machine
Please refer to the link from the Azure DevOps team for the latest mac os, Xcode, and node available. Cross-check with your local machine
https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md
I have a Spring Boot application with integration tests that are using testContainers.
Till recently, I used Docker Desktop and was able to easily run the test from within Intellij or from CLI.
Recently I changed my Windows machine to Rancher desktop.
Now when trying to run the integration tests gradle integrationTest I'm getting this error:
Caused by: java.lang.IllegalStateException: Previous attempts to find a Docker environment failed. Will not retry. Please see logs and check configuration
at org.testcontainers.dockerclient.DockerClientProviderStrategy.getFirstValidStrategy(DockerClientProviderStrategy.java:109)
at org.testcontainers.DockerClientFactory.getOrInitializeStrategy(DockerClientFactory.java:136)
at org.testcontainers.DockerClientFactory.client(DockerClientFactory.java:178)
at org.testcontainers.LazyDockerClient.getDockerClient(LazyDockerClient.java:14)
at org.testcontainers.LazyDockerClient.authConfig(LazyDockerClient.java:12)
at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:310)
Is there an additional configuration that is needed in Intellij or Rancher or Windows to make it work?
UPDATE Feb 2022: As reported here TestContainers works nicely with Rancher Desktop 1.0.1.
Based on the following two closed issues - first, second - in the testcontainers-java github, Testcontainers doesn't seem to support Rancher Desktop, at least officially.
I'm running rancher desktop version 1.0.0 on my windows mashine and could get testcontainers to work just by simple adding 'checks.disable=true' in .testcontainers.properties (located under C:\Users<your user>)
updating Rancher Desktop to version 1.0.1 fixed this issue for me
I got this error because my Rancher was using containerd. If you also use Rancher Desktop try to switch to dockerd under settings, but first back up the data you have just in case.
Runing the Build and Run Iot Edge Solution in Simulator stopped working suddenly, and the log builds the containers and stops at this message Network azure-iot-edge-dev is external, skipping Everything was working fine 5mins ago, tried rebooting, restarting docker, iotedgehubdev, but in vain. Do you know how can I get more logs and/or resolve this problem ?
This is a generic error that is thrown for a variety of reasons.
Possible causes can be:
Proxy blocking pulling images of edgeHub and edgeAgent
A problem in the deployment.template.json (or debug template), e.g. missing brackets
Ports of edgeHub that are in use
Docker configured for Windows containers when targeting Linux or visa-versa
The Build output or IoT hub output in Visual Studio usually gives a bit more information.
Do you know how can I get more logs and/or resolve this problem ?
Are you trying to debug/simulate it locally on windows 10 machine?
When you need to gather logs from an IoT Edge device, the most convenient way is to use the support-bundle command. By default, this command collects module, IoT Edge security manager and container engine logs, iotedge check JSON output, and other useful debug information. It compresses them into a single file for easy sharing. The support-bundle command is available in release 1.0.9 and later.
Run the support-bundle command with the --since flag to specify how long from the past you want to get logs. For example 6h will get logs since the last six hours, 6d since the last six days, 6m since the last six minutes and so on. Include the --help flag to see a complete list of options.
sudo iotedge support-bundle --since 6h
By default, the support-bundle command creates a zip file called support_bundle.zip in the directory where the command is called. Use the flag --output to specify a different path or file name for the output.
Incase if you are looking to debug the modules locally on VS2019, VS Code below documentations will be useful.
Use Visual Studio 2019 to develop and debug modules for Azure IoT Edge and
Use Visual Studio Code to develop and debug modules for Azure IoT Edge
Please share the complete logs if the above doesn't help.
I have this issue when trying to start a project from within Visual Studio when it's not running in administrator mode. I always forget and end up with this error. Same goes for if I run "iotedgehubdev.exe setup" from a command prompt. It only works when the command prompt is running in administrator mode.
I am trying to get a simple, single instance of RabbitMQ running via this RabbitMQ-chef recipe. Essentially, I have an Ubuntu machine, and I’d like Chef to take care of all the heavy lifting necessary to install, configure and get RabbitMQ running on it.
The documentation isn’t really written for beginners, but I went ahead and started by downloading the cookook:
knife cookbook site download rabbitmq
WARNING: No knife configuration file found
Downloading rabbitmq from the cookbooks site at version 4.1.2 to /Users/myuser/sandbox/chef/0.6.2/rabbitmq-4.1.2.tar.gz
Cookbook saved: /Users/myuser/sandbox/chef/0.6.2/rabbitmq-4.1.2.tar.gz
However now I’m at a complete loss as to what I need to script/configure in order to add this cookbook to my Chef server, such that when I SSH onto my target Ubuntu machine, I can bootstrap that machine with Chef and then run something to turn the Ubuntu machine into a RabbitMQ server. Any ideas?
Im trying to setup Jenkins to run tests on a Virtual Machine but im not to sure how to proceed.
What id like to be able to do is to get Jenkins to build the environment on the vm and then have Jenkins execute the test scripts on the vm environment. After the tests have passed/failed id then like Jenkins to clean the database and pull down the virtual environment.
Server box - Windows 7
Virtaul Machine - VMWare
So what im looking for is some information or tutorials on how to implement the above. It would also be helpful if you could recommend what Jenkins plugins I can use to implement the above or if you want to go above and beyond can you outline the steps needed to achieve the above.
Any help would be appreciated.
I'm doing just that in my environment using the vSphere Cloud Plugin. Here's a basic step-by-step guide:
Install the plugin
Configure your ESX/ESXi server as a new "vSphere Cloud"
Create a new Jenkins node, of type "Slave virtual computer running under vSphere Cloud" (which becomes available after Installing the plugin).
When configuring the new node, optionally specify a snapshot name. This will revert the VM to this snapshot when the node launches.
Use the node in a pipeline script: node("node-name-or-label") { ...your code here... }
I use the method above with about 10 Windows nodes, reverting each to a "Clean" snapshot to start each build with a known state.