After importing the .vmdk file and creating the virtual machine, during the startup the machine halts and a message is displayed:'The machine has stopped due to a critical error.'
Related
I recently had to reinstall IntelliJ IDEA, and ever since then, I've been unable to run this one app that runs on Payara. I have Payara 5.2022.3 (full) installed and the project is using java 11.
This is the server log:
Artifact my_project-ear:ear exploded: Waiting for server connection to start artifact deployment…
Detected server admin port: 4848
Detected server http port: 8080
And then nothing happens.
And if I terminate the process I get a message:
Application Server was not connected before run configuration stop, reason: Unable to ping server at localhost:4848
Based on my observation it seems like a process starts running on port 4848 for a few seconds but then stops abruptly.
I checked the CrashDumps and here is the .dpm file in question.
https://drive.google.com/file/d/1AyLU2HOyXKxREjaDNyIU9eRYMnzaBspw/view?usp=sharing
I'd already tried:
Running it on a different port./ Checking if there was not a process blocking used ports.
"Renewing" the domain.xml in case it was corrupted somehow.
Using different JDK.
Reinstalling Windows
I'm positive there is no problem with the app's code (seen a friend run it on his computer today) and I also think no changes happened to the run/debug configuration or the payara and domain configuration ever since it was working before the IDEA reinstall.
(I'm also very new to payara, and software development in general, so I'm not quite as skilled in solving this kind of problem.)
Thank you for all your answers.
It looks like a bug in the Java version/vendor you are using which is causing the crash of the process. Updating to a more recent Java build or to a different JVM vendor should help.
I have an Azure Container Instance created from the base image microsoft/windowsservercore:ltsc2016. The image has mercurial installed and checks out a private repo using hg clone but fails with the result abort: error: getaddrinfo failed. When run on my workstation using Docker for Windows, the container successfully checks out the repo.
I believe this is a network connectivity issue, because if I run powershell Invoke-WebRequest http://microsoft.com the container also logs an error that the request could not be completed due to failure to connect to the server.
The Windows container on ACI has a known issue about the out-bound network. It is suggested to add a retry logic on any network request or add a 30 seconds' delay before you start your application.
https://learn.microsoft.com/en-us/azure/container-instances/container-instances-troubleshooting#windows-containers-slow-network-readiness
The issue only impacts the Windows Server 2016. It is fixed in Windows Server 2019. Once ACI adapts WS2019, the workaround will be no longer needed.
I'm trying create a simple web server inside Azure using SQLite as a database and PHP with Apache as a backend. I was able to create a VM in the new portal, access it with SSH, git clone the software inside it, and add an Inbound security rule to port 80. Still my application is not accessible on my browser. Is there any other configuration I am missing?
Here are the steps I did on azure portal:
Virtual Machines -> Add -> Chose ubuntu server 14.04, and deployment model "Resource Manager", clicked on Create.
Filled in a name, username to connect to the vm, password authentication, created a new resource group, and the location closer to me (Brazil South).
Selected "A0 Basic" size
On settings I clicked on "network security group", and added a new rule for port 80, with priority 1010.
Finally on summary I clicked OK and waited for about 4-5 min to the console show me an OK message.
After that I log into the VM with ssh, ran sudo apt-get update followed by sudo apt-get install apache2.
When I type the public IP of the VM in the browser, it just keeps loading forever but doesn't show anything. Neither and error, nor the apache default page.
I launched an Ubuntu virtual machine on microsoft azure and connected via ssh into the instance.
I followed all the installation instructions at:
http://bugzilla.readthedocs.org/en/latest/installing/quick-start.html
After following the installation instructions, I am able to login into bugzilla via lynx.
The installation worked except I cannot log in to bugzilla on my PC via my browser, (chrome/ edge).
Typing in the IP address results in a timeout error (ERR_CONNECTION_TIMED_OUT). I would expect instead to see the bugzilla login page.
I went to var/www/data and set urlbase in params.json:
"urlbase" : "http://40.127.99.16",
But still I cannot login.
Any ideas what I am doing wrong?
Typing in the IP address result in a timeout error (ERR_CONNECTION_TIMED_OUT). I would expect instead to see the bugzilla login page.
This typically means that something between your browser and the server is preventing the connection. Typical culprits are either firewall rules on the remote server itself (managed with iptables), or in the remote cloud environment (managed using some some sort of platform-specific web interface or API).
I am running a small selenium project using grid setup. All is fine when I run locally which has the hub and the node running in the same machine. What I did next was kept the hub running in my local machine and tried running the test through teamcity. I presume that the test will run in one of the build agents. When I kick start the build job, I got the following exception. Not sure what the issue is.
Test(s) failed. System.Net.WebException : Unable to connect to the remote server ---->
System.Net.Sockets.SocketException : A connection attempt failed because the connected
party did not properly respond after a period of time, or established connection failed
because connected host has failed to respond 192.168.6.121:80 at
System.Net.HttpWebRequest.GetResponse()
Also, the team city build agent IP is 192.168.7.132 whereas I am getting a message that it is unable to contact 192.168.6.121
Is there something happening which I am not aware of.
The selenium server is up and running in my local machine. and all is fine at the server end.
Any pointers will be much helpful