Last night Mist wallet shower only about 1000 blocks left to sync, this morning it was over 2 million. I closed Mist and ran geth console, and it started downloading from 0 again.
Using Mac.
Does Oct 18 hardfork require redownload of entire ethereum blockchain? Didn't see any reference in documentation.
Thanks
No, the fork only requires your client update.
It seems your old version of geth rewinded the chain. What you can do is
update your Mist version, geth will be also updated.
or
you can only update geth , start it first and then launch Mist wallet. It will attach to the running geth instance.
Related
I am running an ethereum node on Windows 11. I am using Geth for my execution client along with Prysm for my consensus client. They have been syncing for the past two days but no data is being written to my hard drive by Geth and no progress is being made towards a working ethereum node.
I installed Geth through the download page.
I installed Prysm with this command in an administrative Git Bash in the Prysm directory;
curl https://raw.githubusercontent.com/prysmaticlabs/prysm/master/prysm.bat --output prysm.bat
I run both Geth and Prysm in separate administrative command prompts.
This is the command I use to start Geth;
geth --datadir D:\ethereum --authrpc.addr localhost --authrpc.port 8551 --authrpc.vhosts localhost --authrpc.jwtsecret jwt.hex
This is the command I use to start Prysm;
prysm.bat beacon-chain --execution-endpoint=http://localhost:8551 --jwt-secret=jwt.hex --suggested-fee-recipient=0x01234567722E6b0000012BFEBf6177F1D2e9758D9
I always start Prysm after starting Geth.
My Geth terminal repeats the message "Beacon client online, but never received consensus updates. Please ensure your client is operational to follow the chain"
My Prysm terminal commonly displays messages such as
←[90m[2023-01-17 20:30:44]←[0m ←[32m INFO←[0m←[36m initial-sync:←[0m Waiting for enough suitable peers before syncing ←[32mrequired←[0m=3 ←[32msuitable←[0m=0
Below are screenshots of my Geth and Prysm terminals.
Geth terminal
Prysm terminal
Why is Geth not writing any data? My friend who has a working node says it should write about 800gb.
If your node does not find any peers in the peer-to-peer network, it cannot download any data and sync.
This is usually a sign of a local network issue. Make sure your node has a public IP address or has properly exposed ports to Internet. Preferably any computer in Internet should be able to connect to your computer running Prysm.
See the documentation here.
I am using Fiware IDM version 6.2 and i have issues with keystone server (running on port 5000)..
Keystone is working fine until server is not used for some amount of time (around 1 hour) after that first call that arrive ( in my case from pep-proxy checking auth token) it simply enter into unresponsive mode, meaning it does not send anything back. When i cancel request and send it again it start working normal.
I would like to know if there is something on my part that i missed or failed to check.
I am using docker to run Fiware IDm enviroment.
Picture of logs
You are using an old version both Keyrock and Wilma. Currently, both of them are in version 7.5.1. Please take a look on Hub Docker (https://hub.docker.com/u/fiware). Nevertheless, the issue that you mention is due to security management. The admin tokens expire after 1h, therefore you need to obtain a new one to continue working with it.
I am starting to learn ethereum. I have downloaded the Ethereum Wallet, created two accounts and using Rinkeby faucet I got 3 ethers in one of the account. I can see the balance in my wallet. I then ran geth --testnet --datadir d:\data and it started syncing. I let it run for a day and now it slowly adds new blocks. I started another get console and attached it to get.ipc. On the console, I did:
eth.accounts
I see both the accounts in my wallet with first account set as coinbase. But when I ran
eth.getBalance(accounts[0])
I get 0 balance. What might be something I might have overlooked? Thanks in advance
connect to Rinkeby faucet using metamask chrome extension. Provide your account details there you can check that you received ether or not.
It will show you the balance once it has completed syncing. For me it took more than one day to sync, then I could see the account balance properly.
Try eth.syncing to check the status and if eth.blockNumber gives 0 as output that means syncing hasn't finished yet.
Yesterday I tried to delete an Instance by invoking the "halt" command through SSH. Unlike AWS, GCE does not allow us to choose the behavior of the VM shutdown and stop the instance by default (the instance status is TERMINATED).
Today I was browsing the Google Compute Engine REST API documentation and I found the following description :
status : [Output Only] The status of the instance. One of the following values: PROVISIONING, STAGING, RUNNING, STOPPING, STOPPED, TERMINATED.
What is this "STOPPPED" status ? Both the instances stopped through the Web console or the "halt" command have the "TERMINATED" status.
Any ideas ?
This STOPPED state is a new feature added a few weeks ago which you can reach via the compute engine API.
This method stops a running instance, shutting it down cleanly, and allows you to restart the instance at a later time. Stopped instances do not incur per-minute, virtual machine usage charges while they are stopped, but any resources that the virtual machine is using, such as persistent disks and static IP addresses,will continue to be charged until they are deleted. For more information, see Stopping an instance.
I think this is similar to the AWS option you mention.
For anyone stumbling on this question years later, a detailed lifecycle diagram of instances can be found here
There is no STOPPED status anymore, instances are going from STOPPING to TERMINATED, whatever the stopping method is.
However a new state, that may be closer to what halt does, has been introduced since: SUSPENDED. It's still in beta though, and not sure that invoking halt would induce this state or simply terminates the instance.
See here for more details
I have deployed a java web application in openshift using tomcat server.Application is running fine. But after 1-2 days automatically tomcat server gets killed.so i have to manually start the server.can any one tell me what is going wrong here.i'm using free account.
Thanks,
A.G.Ishara
Applications on the free account get idled automatically after 24 hours of no external http requests. The application should then automatically restart itself once a request is made.