I'm using STS (SpringSource Tool Suite) which comes with VMware vFabric tc Server Developer Edition v2.6. The problem is, every time I start it, it shows the following error:
Port 8080 required by VMware vFabric tc Server Developer Edition v2.6
is already in use. The server may already be running in another
process, or a system process may be using the port. To start this
server you will need to stop the other process or change the port
number(s).
I don't have anything using that port that I know of. It has always worked fine until today.
I've also tried to change the port number but it doesn't accept the changes. If I change it to 8081, for example, and then restart STS it overwrites the port and sets it back to 8080.
Can anyone offer some ideas to fix this?
FYI I'm running STS in VirtualBox.
Thanks!
This applies to the latest STS version - 3.0.0
When you open STS, in the Package Explorer view (on the left), you should see a project folder called Servers.
Open Servers > VMware vFabric tc Server Developer Edition v2.7-config > catalina.properties
At the bottom of the file, you will see 2 properties defined:
bio.http.port
bio.https.port
Change bio.http.port to some other port than 8080 (e.g. 8081)
Change bio.https.port to some other port than 8443 (e.g. 8444)
Click 'Save'.
Now, when you do your right-click deploys to the built-in tc Server and start it up, it should run on the new port(s). Good luck!
In the Servers view, double click the server you wish to change the ports on. This brings up the Overview page.
Expand the Ports tab and enter your desired port settings.
The reason STS uses this configuration page is it allows you to configure a workspace server without altering the configuration in your server installation directory.
Or you might want to directly kill the zombie process still bound to that port with an oneliner:
sudo kill -9 `lsof -ti:8080`
In conjunction with Gareth's suggestion, this is what workerd for me:
In the Servers view, right click your server and click Monitoring -> Properties
Stop the monitor listening on port 8080.
Save changes and start the server.
Related
I am installing VMware vSphre ESXi 7.0.2. But I cannot use web client (http://<ip_address>/ui)
When installed first time, I can connect with https://<IP_address> (It will be redirect to https://<IP_address>/ui ) and can create VM. But I found I cannot use some SDD/HDD. So I have re-installed ESXi after created the RAID partitions.
Re-Install was look OK, and I can see DCUI and set IP, DNS etc... After all set, I've tried to use https://<IP_address>. But it was timed out. (I have checked several things, then I found the ping does not work.)
I restarted the server then ping is OK. But when I try to connect with https://<IP_address> then the ping became "Destination net unreachable". (I have confirmed it with "-t" option.)
I thought it is firewall settings. So, I changed "--default-action" and "--enabled" but it still not working. Just in case, I have stop to use RAID disks and re-install it again (it is same as first installation), but it was same results.
There's likely still a networking-related misconfiguration. Use DCUI to verify IP/subnet mask/gateway/VLAN tag (if necessary) and that the appropriate NIC has been configured.
If those are set correctly, the DCUI also has some built-in testing options which allows you to do some outbound ping testing. By default it will check 3 hosts, including the gateway and usually two DNS names, but those can be changed to other options.
My windows server 2016 is not connecting using RDP. It was working till yesterday but today it is not working. I had just rebooted the server and no other change was done. I am able to connect using Interactive Serial Console. Following are the findings:
Faulty server is not reachable from any other working server in the same subnet. Neither ICMP (ping) nor with TCP. For TCP, I checked with Test-NetConnection -Port 3389 and result was a failure.
Surprisingly, The faulty server is able to reach other servers with ping and Test-NetConnection on port 3389.
RDP is in running state. Verified by sc query SessionEnv, sc query TermService, sc query UmRdpService, sc query RpcSs, sc query RpcEptMapper. All these services are running. Also, restarted services.
Netstat -a shows that RDP is listening on port 3389.
netstat -a | findstr 3389
TCP 0.0.0.0:3389 IPADDRESS:0 LISTENING
TCP [::]:3389 IPADDRESS:0 LISTENING
UDP 0.0.0.0:3389 *:*
UDP [::]:3389 *:*
Verified No antivirus, windows firewall, security blockage.
Followed the steps given on https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-rdp and output is PASSED. For NLA and SecureLayer the output was different and added the required changes to registry.
Can someone please help me to fix this? Is it possible to verify if RDP is broken?
Error screenshot when attempted RDP connect from server in same subnet:
by default windows desktop is blocked and disabled by windows firewall,
follow these steps to enable it
1.Open Windows Firewall (Start button > Windows System > Control Panel) - From the Control Panel Go to Systems and Security > Windows Defender Firewall.
2.From the Firewall, Click on the Allow and app or feature through Windows Defender Firewall link in the left pane.
3.Click Change settings and then check the box next to Remote Desktop, for both private and public networks.
4.Click OK to save the new settings.
you can refer this link for more details
I have been trying to setup Docker in Windows Server 2016 in an AWS instance to run an IIS program.
From this question,
Cannot access an IIS container from browser - Docker, IIS has been setup inside a container and it is accessible from the host without port mapping.
However, if I want to allow other users from the Internet/Intranet to access the website, after Google-ing it, I guess we do need port mapping...
The error I have encountered in port mapping is given in the above question so... I guess using nat is not the correct option. Therefore, my team and I tried to create another network (custom/bridge) following instructions from
https://docs.docker.com/v17.09/engine/userguide/networking/#user-defined-networks
However, we cannot create a network as follows:
; Googled answer:
https://github.com/docker/for-win/issues/1960
My team guessed maybe its because AWS blocked that option, if anyone can confirm me, please do.
Another thing that I notice is: when we create an ECS instance in AWS,
So... only default = NAT network mode is accepted in Windows server?
Our objective: put the container hosted IIS application to Internet/Intranet in Windows Server 2016...
If anyone has any suggestion/advice, please tell me, many thanks.
I don't know what's wrong with it. Here is a screenshot.
(first image is what i've done in terminal to log in my EC2 server
second image is what i've set in "System preference --> sharing --> remote login)
Yosemite is my OS. Please help me,
Assuming that you have the right key file, you could be running into some security settings issues. Check your security group and make sure that the server is accepting connections on port 22 from all addresses. Also, I generally use the IP address when SSHing into an EC2 box instead of a url, as it is much shorter and more concise. Also, make sure that your server is running Ubuntu. I know that different OS's on EC2 use different default usernames.
Your default username can be found at this page:
http://alestic.com/2014/01/ec2-ssh-username
In the end, your ssh command should be something like
ssh -i otkey.pem [username for your os]#[ip of your box]
Hope this helps!
You've got the right command for an ubuntu server. Check to make sure that security groups are configured and that you don't have Network Access Control Lists configured on your VPC. The configuration you made to the settings of your laptop are to open it up for people to log into your laptop, they don't do anything to facilitate you connecting out.
tldr; This question was to get help setting up Micro Cloud Foundry on Windows XP behind a corporate firewall as an innovation-demonstration project for a Fortune 500 IT departent. Basically, the project stalled, despite this stackoverflow page - the magic wasn't strong enough. I am accepting #DanHigman answer below, but if anyone sees this and can provide a simple straight-forward answer, by all means...
Can anyone provide a clear step-by-step on setting up MCF on a Windows (XP in my case) machine behind a corporate firewall, for demostrating the feasibility of PaaS in the corporate IT world?
My VM is installed and running and I can use the menu ok. I have vmc working. I have a test Node.js server app, that works on local, ready to push. But I can't get past that stage.
The firewall gave me trouble so I lowered my goal to just work offline. I followed the instructions noted below as best I could, but often the instructions are mac oriented - I would like them for a Windows command line (especially SSH tunneling):
http://blog.cloudfoundry.com/2011/09/08/working-offline-with-micro-cloud-foundry/
http://support.cloudfoundry.com/entries/20332921-micro-cloud-foundry-trouble-shooting-help
This blogger may have half-way covered my problem doing the SSH tunnel settings, but all it gives is "use Putty" - more detail would help:
http://support.cloudfoundry.com/entries/20419943-using-micro-cloud-locally
Also, whenever the vmc obviously gets an error or other message, it only outputs the following in the command line:
vmc target http://api.vcap.me
<<<
[200, "<html><body>SNP/2.0/102/Unknown Command 'info'</body></html>\r\n\r\n", {}
]
>>>
Thanks for any help. BTW - I know I could do this on my mac, the big obstacle is the windows and firewall environment.
Update:
#Dan and #ebottard: Thanks to your help, I'm almost there. ping is working now, hosts file seems right, but the vmc target api.vcap.me still does not find the VM at that 192.168.253.128 IP - even tho ping does. In the first link above, Martin wrote the following, but assuming we are doing it on a mac:
After the update is complete, you will need to make some changes on your local system. What you will need to do is to set up an SSH tunnel to access your Micro Cloud Foundry VM (note that you will need to supply the IP address in the command below with the actual IP of your VM, which is displayed in the console).
sudo ssh -L 80:192.168.168.149:80 vcap#192.168.168.149
Password:
vcap#192.168.168.149's password:Â
The first password being prompted is the sudo password for your machine, as it is needed to open port 80 which requires root privileges. The second password is the vcap user password which you entered during the initial configuration of your Micro Cloud Foundry.
I need to have these instructions translated into Windows, and all I have to go on is that I might use puTTy (which I have downloaded) to do it. Any more ideas?
Looks like you're running an application on your Windows machine called "Snarl" (a poor Windows-based clone of the OS 10 app Growl :-p). It looks like it's interfering with communication to the MCF intstance, close it and have another try.