When installing openGauss, it hit the error:
GAUSS-506601: The port [26000] is occupied or the ip address is incorrectly configured.
Related
I am following the GRPC tutorials here https://grpc.io/docs/languages/python/.
In greeter_client.py over here - https://github.com/grpc/grpc/blob/master/examples/python/helloworld/greeter_client.py, instead of using
with grpc.insecure_channel('localhost:50051') as channel:
(the above code works fine), I use the following -
with grpc.insecure_channel('XX.XX.XX.XX:50051') as channel:
where XX.XX.XX.XX is my laptop's public IP address from https://www.whatsmyip.org/.
I get this error
raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "failed to connect to all addresses; last error: UNKNOWN: ipv4:XX.XX.XX.XX:50051: Failed to connect to remote host: Connection refused"
debug_error_string = "UNKNOWN:failed to connect to all addresses; last error: UNKNOWN: ipv4:XX.XX.XX.XX:50051: Failed to connect to remote host: Connection refused {created_time:"2022-12-29T23:18:44.033798+00:00", grpc_status:14}"
does anyone know why this happens? I think this might be a MacOS issue. Mine is a MacOS Monterey, and I have the firewalls all disabled, so I am not sure what else I should be doing. Is this expected behaviour?
Turns out, the best way to deal with this is by using ngrok. The steps would be something like -
Download ngrok (can use brew install ngrok)
Set up forwarding using something like ngrok tcp 50051
Once you click 'enter', there will be a field under Forwarding, which you should then use. Remember to remove the tcp://
I have installed HDP2.7.5. but When I start the yarn & hdfs Service.I have encountered the following problems.
The following error was encountered while trying to retrieve the URL:
http://n15hdp02:50070/webhdfs/v1/tmp?
Unable to determine IP address from host name n15hdp02
The DNS server returned:
Name Error: The domain name does not exist.
This means that the cache was not able to resolve the hostname presented in the URL. Check if the address is correct.
Your cache administrator is root.
enter image description here
enter image description here
General information
Minishift version: v1.34.3+4b58f89
OS: macOS
Hypervisor: hyperkit
Steps to reproduce
minishift start --show-libmachine-logs -v 5
Expected
minishift started successfully.
Actual
Error starting the VM: Error starting stopped host: IP address never found in dhcp leases file Temporary Error: Could not find an IP address for Generated MAC
Logs
-- minishift version: v1.34.3+4b58f89
-- Starting profile 'minishift'
Found binary path at /usr/local/bin/docker-machine-driver-hyperkit
Launching plugin server for driver hyperkit
Plugin server listening at address 127.0.0.1:50805
() Calling .GetVersion
Using API Version 1
() Calling .SetConfigRaw
() Calling .GetMachineName
(minishift) Calling .GetState
-- Check if deprecated options are used ... OK
-- Checking if https://github.com is reachable ... OK
-- Checking if requested OpenShift version 'v3.11.0' is valid ... OK
-- Checking if requested OpenShift version 'v3.11.0' is supported ... OK
-- Checking if requested hypervisor 'hyperkit' is supported on this platform ... OK
-- Checking if hyperkit is installed ...
Hyperkit is available at /usr/local/bin/hyperkit
Checking for setuid bit ... OK
-- Checking if hyperkit driver is installed ...
Driver is available at /usr/local/bin/docker-machine-driver-hyperkit
Checking for setuid bit ... OK
-- Checking the ISO URL ... OK
-- Checking if provided oc flags are supported ... OK
-- Starting the OpenShift cluster using 'hyperkit' hypervisor ...
-- Starting Minishift VM ....Found binary path at /usr/local/bin/docker-machine-driver-hyperkit
Launching plugin server for driver hyperkit
Plugin server listening at address 127.0.0.1:50813
() Calling .GetVersion
Using API Version 1
() Calling .SetConfigRaw
() Calling .GetMachineName
(minishift) Calling .GetState
(minishift) Calling .Start
(minishift) Using UUID 91b2bdde-f54b-11eb-b552-1c36bb1ab9e0
(minishift) Generated MAC 56:bb:6a:61:3c:34
(minishift) Starting with cmdline:
...................... FAIL E0804 23:28:48.938399 8469 start.go:499] Error starting the VM: Error starting stopped host: IP address never found in dhcp leases file Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34. Retrying.
Error starting the VM: Error starting stopped host: IP address never found in dhcp leases file Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Temporary Error: Could not find an IP address for 56:bb:6a:61:3c:34
Try this:
sudo vi /var/db/dhcpd_leases
add this
{
name=minishfit
ip_address=192.168.64.3
hw_address=1,56:bb:6a:61:3c:34
identifier=1,56:bb:6a:61:3c:34
lease=0x5e41592a
}
then minishift start
if you see time out error like this:
Error starting the VM: Error configuring authorization on host: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded.
try this:
minishift delete --force --clear-cache
minishift start
Openshift Cluster are now in version 4.7, I strongly recommend you to used CRC (code ready containers) in replacement of Minishift.
You can download a free version here: https://www.okd.io/crc.html
Minishift is not only deprecated, but it will be problematic to install on Mac OSX Monterey. And even though it kind of succeeds installing, various things are broken:
$ sudo du -hx -d2 '/'* 2>/dev/null | grep -ve $'M\t' -e $'K\t' -e $'B\t' | sort -k 2 ; echo Finished
# ONLY DELETE NON-ESSENTIAL FILES IN YOUR HOME DIRECTORY
$ softwareupdate --all --install --force
Downloaded macOS 10.14.6 Update
Installing macOS 10.14.6 Update
$ sudo reboot
# Note you may need to run softwareupdate several times depending on how outdated your computer is
# In fact, I would keep updating until you get the latest MacOSX version, which at the time of this writing is macOS Monterery
# Once your system is up-to-date, then install Docker Desktop: https://docs.docker.com/desktop/mac/install/
# Note if you are using the latest version of OSX and the latest version of Docker Desktop, then it will install and launch smoothly.
% which docker
/usr/local/bin/docker
# Now run “brew update && brew upgrade” or install homebrew if not installed:
% /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
==> This script will install:
/usr/local/bin/brew
/usr/local/share/doc/homebrew
/usr/local/share/man/man1/brew.1
/usr/local/share/zsh/site-functions/_brew
/usr/local/etc/bash_completion.d/brew
/usr/local/Homebrew
==> The following new directories will be created:
/usr/local/Cellar
/usr/local/Caskroom
==> The Xcode Command Line Tools will be installed.
# Use the hyperkit virtual machine. docker-machine-driver-xhyve is deprecated!
% brew install hyperkit
% brew install docker-machine-driver-hyperkit
% sudo chown root:wheel /usr/local/opt/docker-machine-driver-hyperkit/bin/docker-machine-driver-hyperkit
% sudo chmod u+s /usr/local/opt/docker-machine-driver-hyperkit/bin/docker-machine-driver-hyperkit
# THERE IS A HUGE BUG HERE. Basically, the setuid is correctly added to /usr/local/opt/docker-machine-driver-hyperkit/bin/docker-machine-driver-hyperkit BUT NOT the symlink at /usr/local/bin/docker-machine-driver-hyperkit. Consequently, I had to delete the symlink at /usr/local/bin/docker-machine-driver-hyperkit and then create a hard link to /usr/local/bin/docker-machine-driver-hyperkit and then add the setuid and change ownership there!
% ls -l /usr/local/bin/docker-machine-driver-hyperkit
-r-sr-xr-x 2 root wheel 11581712 Mar 1 2018 /usr/local/bin/docker-machine-driver-hyperkit
% brew install cask
% brew install --cask minishift
% which minishift
/usr/local/bin/minishift
% sudo vi /var/db/dhcpd_leases
{
name=minishfit
ip_address=192.168.64.3
hw_address=1,56:bb:6a:61:3c:34
identifier=1,56:bb:6a:61:3c:34
lease=0x5e41592a
}
% minishift start
Instead of using Minishift, you should be using RedHat CodeReady Containers. Instructions for Mac OSX are here (note you must have 35gb of disk space available on your machine):
https://access.redhat.com/documentation/en-us/red_hat_codeready_containers/1.0/html/getting_started_guide/getting-started-with-codeready-containers_gsg
What took 5 hours with minishift, only took 5 minutes with CRC.
for my case, I had my corporation antivirus running (particularly McAfee with a firewall activated), which was blocking the creation of dhcpd_leases. After turning that off and shutting the firewall temporarily, it got fixed.
We're trying to upgrade to Phusion Passenger Enterprise edition from the open source version but we're running into an issue. Passenger fails to connect to the licensing server with the following error message:
[ W 2018-03-27 10:20:55.2565 35498/T6 age/Cor/CloudUsageTracker.h:439 ]: Could not contact the Phusion Passenger Enterprise licensing server (HTTP error: Failed to connect to www.phusionpassenger.com port 443: Connection timed out). To ensure proper access to the licensing server, please try these:
- Ensure that your network connection to https://www.phusionpassenger.com works.
- If you can only access https://www.phusionpassenger.com via a proxy, please set the config option 'PassengerCtl licensing_proxy PROXY_URL' (Apache) or 'passenger_ctl licensing_proxy PROXY_URL' (Nginx). 'PROXY_URL' takes the format of protocol://username:password#hostname:port, where 'protocol' is either 'http' or 'socks5'.
We need to use a proxy for all outgoing HTTP connections, so I have added the recommended config option:
passenger_ctl licensing_proxy http://OURPROXY:3128;
However the issue persist with the same error message.
Using curl to hit this URL through the proxy works as expected:
$ curl -x http://OURPROXY:3128 https://www.phusionpassenger.com
We are using nginx with Passenger on Ubuntu 14.04 LTS, Passenger Enterprise is installed from the official APT repository.
What could be causing this error? Any help would be much appreciated.
I have received an answer to this question from the Phusion Passenger support. They had accidentally misspelled the name of the relevant config option in the error message.
The correct way to set this option is:
passenger_ctl licensing_proxy_url http://OURPROXY:3128;
Related to this question, if you want Passenger to check for security updates behind a proxy, you will also need to set that separately:
passenger_security_update_check_proxy http://OURPROXY:3128;
I use Visual Studio Apache Cordova for a hybrid application. I try to connect a Mac computer using remote connection. I made settings correctly. A few days ago, ip address of Mac computer has changed. And ı can not connect Mac computer with remote connection. It gives below error:
Error: An error occurred uploading to the build server https://192.168.95.26:3000/cordova: Error: Hostname/IP doesn't match certificate's altnames: "IP: 192.168.95.12 is not in the cert's list , 192.168.95.87"
Try to do following steps.
First on Mac terminal give this command
remotebuild --secure false
Then find the IP address of the Mac.
Go to the Tools->Options of visual studio
In the Options dialog box, open Tools for Apache Cordova, and then choose iOS Configuration.
Give the IP of Mac in Host and Port as 3000. Then put secure mode to false
More details could be found from this link https://taco.visualstudio.com/en-us/docs/ios-guide/
Error: An error occurred uploading to the build server https://192.168.95.26:3000/cordova: Error: Hostname/IP doesn't match certificate's altnames: "IP: 192.168.95.12 is not in the cert's list , 192.168.95.87"
It is a known issue. When the IP address changed, the previously generated certificate become invalid. You can fix this by following steps:
Stop the remote agent on your Mac.
In terminal run remotebuild certificates reset.
In terminal run remotebuild certificates generate.
Change the VS remote build configurations in VS.
For details, you can refer to Possible issue 2: The host name or IP address of your Mac has changed.