I am new to Cosmos SDK and I just forked the official Cosmos SDK nameservice tutorial. It works well on my local machine so I just deployed it to cloud server and I want to access it thru nscli from my local machine.
First I configured nscli to set the node to remote server address on my local machine
nscli config node tcp://{{my remote server ip here}}:26657
Then I tried to run the following query
nscli query account $(nscli keys show jack -a)
Finally I got some error like ERROR: ABCIQuery: Post failed: Post "{{my remote server ip}}:26657": dial tcp : connect: connection refused
I am curios since I don't think there is any network related problem in my case. Did I mis-configured something?
Thank you very much!
Best,
Min
My config file is configured to listen on 127.0.0.1:26657, which should be set to 0.0.0.0:26657 instead. So the connection succeeded if I start the daemon node like tendermint node --rpc.laddr=tcp://0.0.0.0:26657
Related
I was trying to follow a tutorial from devto.io and to send transactions to the smart contract, I would need to connect my MetaMask wallet using one of the accounts created when I ran npx hardhat node command.
To do so, I opened MetaMask and updated the network to be Localhost 8545, but Metamask didn't connect to it and showed errors like the following screenshot.
I think that you probably interrupted the node you launched when you typped :
npx hardhat node
You should keep it running, open another terminal for the rest of the tutorial.
Also you could check the output of this command. Is it indicating something else than ? :
Started HTTP and WebSocket JSON-RPC server at http://127.0.0.1:8545/
You most likely entered wrong URL into RPC-URL input: "http://localhost:8545". SInce in config file, hardhat has chainId:1337, it may be using ganache under the hood.
If you entered correct config but it still does not connect, you could use ganache-cli. http://localhost:8545 is for ganache-cli. You should be installing ganache-cli globally and then start the server on terminal if your hardhat node has an issue
ganache-cli
When you run the command on the terminal, you will get the local public and private keys:
After setting the network you could import an account in one of those private keys:
if you click on the logo next to the network name, you will see the option import account. note that everytime you run a new command ganache-cli it will generate new private keys, so you have import a new account.
ganache gui listens to "7545" but ganache-cli listens to "8545"
What worked for me, in this case, is This video
I downloaded Ganache from the following link
Installed it and just hit the Quick Start
It will launch the ganache as shared below in the screenshot. You can see the Network ID and RPC Server details.
As a Next step, delete the HTTP://localhost:8545 network and create a new network with Ganache RPC Server details and Network ID as shared below. I have just changed my port from default to 3000.
Here you Go!
Hope it helps. Also, feel free to share your thoughts if you have other approaches as I am also in the learning phase :-)
Thanks.
What helped me was following these steps :
Step 1: Install Ganache and then launch the application.
Step 2: Check the RPC SERVER on the navigation bar and note it down.
Step 3: Open Metamask network settings. Delete the original localhost network.
Step 4: Add a new Ganache localhost network with the following configuration:
Network name - Whatever you want (Example: Ganache localhost)
New RPC URL - RPC server noted from Ganache.
Chain ID - 1337
Currency Symbol - ETH
Press Add network
You probably have a IPv6 address that is not listening on that port.
e.g.
$ ping localhost
PING localhost.localdomain (::1)...
either remove that line from /etc/hosts (e.g. ::1 localhost.localdomain localhost) or point ethermask to 127.0.0.1 instead of localhost
The error is most simple that you probably think, the default chain id for test networks in metamask is not the same as the hardhat chain id, you should go to metamask, then config, networks, localhost and change chain id to 31337
I am attempting to take my existing cloud composer environment and connect to a remote SQL database (Azure SQL). I've been banging at my head at this for a few days and I'm hoping someone can point out where my problem lies.
Following the documentation found here I've spun up a GKE Service and SQL Proxy workload. I then created a new airflow connection as show here using the full name of the service azure-sqlproxy-service:
I test run one of my DAG tasks and get the following:
Unable to connect: Adaptive Server is unavailable or does not exist
Not sure on the issue I decide to remote directly into one of the workers, whitelist that IP on the remote DB firewall, and try to connect to the server. With no command line MSSQL client installed I launch python on the worker and attempt to connect to the database with the following:
connection = pymssql.connect(host='database.url.net',user='sa',password='password',database='database')
From which I get the same error above with both the Service and the remote IP entered in as host. Even ignoring the service/proxy shouldn't this airflow worker be able to reach the remote database? I can ping websites but checking the remote logs the DB doesn't show any failed logins. With the generic error and not many ideas on what to do next I'm stuck. A few google results have suggested switching libraries but I'm not quite sure how, or if I even need to, within airflow.
What troubleshooting steps could I take next to get at least a single worker communicating to the DB before moving on the the service/proxy?
After much pain I've found that Cloud composer uses ubuntu 1804 which currently breaks pymssql as per here:
https://github.com/pymssql/pymssql/issues/687
I tried downgrading to 2.1.4 to no success. Needing to get this done I've followed the instructions outlined in this post to use pyodbc.
Google Composer- How do I install Microsoft SQL Server ODBC drivers on environments
I'm using AWS to host my Chef server, and I've connected to it from my workstation using Knife. However, after shutting down and turning the server on, the Public DNS changed, and I'm unable to reconnect to the server, resulting in this message:
ERROR: Error connecting to https://*.compute-1.amazonaws.com/organizations/*/cookbooks?num_versions=all
Is there any way to change the address of the Chef server on the workstation without making the workstation think it's connecting to an entirely new server?
You need to reconfigure the Chef Server, possibly updating it's config file first to ensure the right hostname is in the right places. After that, make sure you update the chef_server_url in the knife.rb or client.rb of every machine.
503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x7fc8bad2f810] _serverNamespace = /vsphere-client _isRedirect = false _port = 9090)
This is the error i'm constantly getting when trying to connect to the vCenter Server Web Client.
Details :
I'v installed the vCS Appliance 6.0 on an ESXi 6.0 host. It's running on top of it along other VMs.
I can access the vCS appliance thourght an SSH client, but every attempt to access the web client ends with the error above.
I'v found that causes for this error are: the server being overloaded or under maintenance. However, I'm the only one to have access to this platform.
Any ideas ?
EDIT: Solved
I had a copy of the current vCenter appliance stored on the same ESXi. This created an IP conflict. I changed the IP address of the backup before its creation and the problem was solved
I found the answer:
The problem was that I made a backup of the current vCenter appliance and stored it on the ESXi 6.0 without changing it's IP address. This created an access conflict. All I had to do is to change the IP address of the backup during its creation and the problem was solved
I was getting that 503 error, but my case was a little different:
I changed the IP address of my VCSA 6.0 Update 2 plus its default gateway via the GUI (https://x.x.x.x:5480).
I was able to ping it and ssh into it afterwards, but I was not able to login using either the old (thick) client or the web client. Both were giving me the 503 Server error.
I tried rebooting, but nothing.
After the reboot, I SSHd into it and was able to see that the web client service was not running. The vpxd service was running though. So I started it:
vcsa6:~ # service vsphere-client status
VMware vSphere Web Client is not running.
vcsa6:~ # service vmware-vpxd status
vmware-vpxd is running
vcsa6:~ # service vsphere-client start
Last login: Sat Dec 10 23:40:00 UTC 2016 on console
Starting VMware vSphere Web Client...
Waiting for VMware vSphere Web Client......
running: PID:22433
vcsa6:~ # service vsphere-client status
VMware vSphere Web Client is running: PID:22433, Wrapper:STARTED, Java:STARTED
I was still getting the 503.
I found then this link, which basically told me to edit the /etc/hosts file of the VCSA and voila: the VCSA FQDN entry in there was still pointing to the old IP address. I changed it and rebooted and now both clients, web and thick, work as before.
I had 503 error issues on my lab/test vCenter 6.0 Update 1. I installed the integrated VCSA on a host that has limited memory, so I dropped the default 8G RAM and multiple CPU to 1 CPU and 4G. I would not go below those and use the default values if you can as webclient 503 errors occur and inventory service connection issues arise without the required RAM. I experienced no issues on the fat client.
I've solved it with:
/etc/init.d/vpxa restart
Then I had some problems with hostd.
/etc/init.d/hostd restart
It worked great after.
ESXi 6.5 here.
check to see if the vmware-vpxd is not stopped. If it is, start it.
-Putty into vcenter (VCSA)-
I did a lot of research for following matter and I got a lot of helpful information but the matter still remains, so I'm going to write it with full details
I'm trying to run "Remote Server Administration" with VisualSVN Server (Enterprise Edition), the server is Windows Server 2008 connected to the internet via router with port forwarding to this server. The client is not at local network so I use a static IP for the server.
Also I did every things written at this URL: http://www.visualsvn.com/support/topic/00025/
but I still get the following error message Connot connect to WMI namespace "..." : the RPC server is unavalible (0x800706ba) when I'm trying to "connecting to another computer".
On the other-hand, I can browsing the "Repositories" content by any web-browser successfully.
How can I manage the Repositories at remote servers?
"...the RPC server is unavalible (0x800706ba)" error indicates a connectivity issue to the remote machine.
Accessing WMI remotely requires port 135 TCP/UDP and all TCP ports above 1024 (1024-65535) to be opened (and forwarded), by default. You can setup fixed port for WMI to simplify the port-forwarding / proxy setup task. In order to setup the fixed port, follow steps described in the article "Setting Up a Fixed Port for WMI". After you follow these steps you are required to setup port forwarding and proxy rewrites (if any) for 135 TCP/UDP and port 24158 TCP.
"...Access is denied (0x80070005)" error indicates insufficient permissions to access WMI remotely. Add your user account to the local group on the remote machine: "Distributed COM Users".