I have install docker desktop, increase its memory to 10GB and the pull the HDP sandbox
Then i set the environment variable is the host file, after that when I am trying to launch dashboard it saying Bad Gateway because Ambari server is not running 8080, I have checked that port nothing is running on that port and still Ambari is not running on it
I have attached Picture below to show the error and random port on Ambari server starts running
Related
Error at master node trying to connect to remote jmter slave node in same network
You need to ensure that at least port 1099 is open, check out How to open ports to a virtual machine with the Azure portal article for more details.
Apart from port 1099 you need to open:
The port you specify as the server.rmi.localport on slaves
The port you specify as the client.rmi.localport on master
More information:
Remote hosts and RMI configuration
JMeter Distributed Testing with Docker
JMeter Remote Testing: Using a different port
I have an app that is running on host: http://localhost:1111, when I try to access it through my server ip as follow: xxx.xx.xxx.xx:1111 it is not showing anything. When I run my app on my local pc it is running perfectly good
I tried to open ports, ping the ip with the port
I'm currently running vsftpd locally on port 21 and have a node program that pulls data from it and that also works great.
I have containerised the deployment of the program on my local machine and it deploys fine but complains it can't connect to the FTP server on port 21 which I realised was because that port wasn't open.
Now if I open that port with something like -p 21:21 then this is blocking the FTP server which is bound to 21. I don't understand how I can run a test FTP server and this container at the same time?
Is it possible?
If the "containerised program" is only the node app, then if you connect to the ftp server via localhost:21 it will fail because inside that container there is no ftp server running on port 21. If you want to use the ftp server that runs on your host os, you need to run the container with --net="host", then the node app should connect to the ftp server with 127.0.0.1:21.
Another approach would be creating another container for the ftp server and using docker dns system to communicate the containers.
I guess I will start at the start of my application.
I am making a full mean-stack application and I want it to run in docker. To use docker I am using a virtualbox with Ubuntu. When I run my docker-compose, everything is working on localhost:4200. Now I want to open my application on my host machine (Windows 7).
When I go to my application via (ip addres should be kept secret, right?) xxx.xxx.xx.xxx:4200/login the page looks fine, but I get these errors:
I am using Angular cli 1.4.1 with node 8.4.0
Why am I getting these errors and how do I fix them?
My docker-compose
Your server which is listening on port 4200 is listening on your xxx.xxx.xxx.xxx interface (not necessary to hide lan IP, but nevermind...).
Your angular application is running on your host system. the localhost is the localhost of your host system, not the guest. so you have two solutions:
changing your urls inside the angular application to point to xxx.xxx.xxx.xxx:4200 instead of localhost:4200.
Forwarding your 4200 port from your host to your guest system using virtual box :
shutdown guest.
select guest and click on settings
go to the network tab.
click on "advanced"
then select "ports redirections" and bind your host 127.0.0.1:4200 to your guest's 4200 port
I created an Azure virtual machine with Ubuntu 14.04 LTS OS.
I installed a mean.io application version 0.3.3, on this virtual machine, with nginx that proxy the requests in the http port 3000 over the port 80.
I opened one endpoint in azure portal, for the TCP protocol on private port 3000 and public port 80.
I installed the latest version of node on Azure VM.
The database (mongoDB) is hosted on compose.io.
With pm2 (https://www.npmjs.org/package/pm2) I created a daemon that run the application.
All apparently works fine: the cpu was with no load and the memory was empty (only 100MB).
But after a period, node.js cannot process the request.
I have tried to do a 'curl' in localhost 3000 but i dont have any response.
The problem persists only in Azure VM: I tried the same application, with the same configuration, on my dev machine (ubuntu 14.04 desktop), and on Digital Ocean (another distro of ubuntu 14.04 server) and all works fine without problem.
Can you help me to find the problem?
I have tried to dockerize all infrasctructure, in the same machine (a CoreOS vm on azure):
1 container with mean app,
1 container with MongoDB,
the problem still persisted!!!
finally, i have found the solution: keep the connection to MongoDB alive.
i have modified the server.js file from the mean app in this mode:
var options = {
server: {
socketOptions: { keepAlive: 1 }
}
};
var db = mongoose.connect(config.db, options);
In this mode the connection still alive and the problem was solved.