There was one problem, we use the system for backup of symantec netbackup version 8.1.1
There is a task to reinstall the master server and restore all data. I created a catalog policy, everything worked out with a Bang, the system was demolished and re-installed, the directory was restored successfully, but, the media server and all clients can not connect to the new master, the error "The vnetd proxy encountered an error"
What could be the problem?
screenshots:
ibb.co/GCNgd2q
ibb.co/V9Gp3QL
ibb.co/dLZhxHZ
Check connectivity over pbx.
You can do that with bptestconn -v {hostname}.
Ensure pbx is running. Verify with bpps -x.
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 installed Rabbitmq on my server. Suddenly I needed to remove a queue and I could not. I decided to remove and reinstall Rabbitmq but now I can not run it. I user this article https://linoxide.com/ubuntu-how-to/install-setup-rabbitmq-ubuntu-16-04/ and got this error:
https://imgur.com/a/lL0xln6
Problem was related to some DNS and Hostname settings on my server. I just try to use a new server for AMQP as Saas.
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 am using IBM MobileFirst 6.3, with Apple, Android, Blackberry and Windows Environments.
I have enabled Push Notifications for Apple, Android and Windows environment. I mistakenly uploaded application with sandbox certificate on my production server. On noticing the mistake, I removed the version with Sandbox certificate and uploaded the production certificate version properly and restarted the Websphere Liberty server.
After the restart, push notification is NOT WORKING for any platform.
Earlier I got APNS SSL connection error in my logs, but now I can not see any Push related error in my logs, I enabled trace on com.ibm.pushworks.server.notification.apns.*=all, and still got nothing back.
The only error I get is of could not piggyback ... , which I believe even IBM is suggesting to suppress. I have attached the finest level trace here
I have checked through Wireshark, and server receives request on HTTP GET method and replies with status 200. But what happens after that is a mystery.
P.S. The push notification worked once while the SandBox certificate version was enabled, but didn't work after the restart at all.
#eshaa when you use to change in certificate related settings in client side code you need to take new build i means new .wlapp files to be upload to the server then it will be effect whatever changes you done.
I have a VM running Windows Server 2016 Technical Preview, and have installed the Containers feature, and then run the Install-ContainerHost.ps1 script from Microsoft's container tools repo
https://github.com/Microsoft/Virtualization-Documentation/tree/master/windows-server-container-tools/Install-ContainerHost
I can now run the Docker Deamon on Windows. Next I want to copy the certificates to a client machine so that I can issue commands to the host remotely. But I don't know where the certificates are stored on the host.
In the script the path variable is set to %ProgramData%\docker\certs.d
The certificates on windows are located in the .docker folder in the current user directory.
docker --help command will show the exact path details
AFAIK there are no certificates generated when you do what you are doing. If you drop certificates in the path you found then it will use them, and be secured. But otherwise there is none on the machine. Which explains why it isn't exposed by default.
On my setup I connected without TLS but that was on a VM that I could only access on my dev machine. Obviously anything able to be accessed over a network shouldn't do that.
Other people doing this are here: https://social.msdn.microsoft.com/Forums/en-US/84ca60c0-c54d-4513-bc02-14bd57676621/connect-docker-client-to-windows-server-2016-container-engine?forum=windowscontainers and here https://social.msdn.microsoft.com/Forums/en-US/9caf90c9-81e8-4998-abe5-837fbfde03a8/can-i-connect-docker-from-remote-docker-client?forum=windowscontainers
When I dug into the work in progress post it has this:
Docker clients unsecured by default
In this pre-release, docker communication is public if you know where to look.
https://msdn.microsoft.com/en-us/virtualization/windowscontainers/about/work_in_progress#DockermanagementDockerclientsunsecuredbydefault
So eventually this should get better.