1 million blocks behind after v0.18.3.3 upgrade #4304
Comments
|
We released v0.18.3.2 about a month ago and have not received a single other report about this. Can you share the output of "status" and "sync_info" from monerod? |
|
You have to enter it without quotes |
|
It says 99%. Did you already sync up most of the missing 1/3? |
|
nope weird huh.
|
|
It seems you are conflating wallet and daemon sync. The daemon did not lose 1/3 of the progress, it's the wallet that is resyncing. But something seems wrong, why does the "status" output not work for example? Without it the GUI won't function correctly. Can you go to Settings -> Info and share
Also do you manually start monerod.exe or do you let monero-gui handle the start / stopping? |
|
No manual intervention. |
|
Did you change the wallet restore height? It says 2024731 which is about the 1/3 you are re-syncing. |
|
That is from when wallet was added a few months ago. |
|
Also do you have Node -> Daemon start flags set? |
|
everything in this gui is default, no flags. |
|
When was the last time you had monerod synced up on this Windows PC? |
|
within the last few weeks. |
|
I noticed something else weird but would rather not post it here, can you pm me on bitcointalk or we can use irc? |
|
you can PM me on IRC (selsta), i don't have a bitcointalk account |
|
kk |
Apparently I'm not the only one who has this problem that arose after the update. I have formatted and returned to version 18.3.1 and it is still the same. I better stop wasting time mining. Al parecer no soy el único que tiene ese problema que surgió después de la actualización. He formateado y he vuelto a la versión 18.3.1 y sigue igual. Mejor dejo de perder el tiempo minando. |
I've found a work around, you can set wallet restore height to current date. |
|
@Kanopola from which version to which version did you upgrade? and can you explain in detail what happened? which operating system are you using? |
I think it was from 3.1 to 3.3. I have been updating until after 3.3 the Nodes do not synchronize and everything started to cause problems. I will try to explain what I have done (I am attaching some screenshots of different events): 1.- I thought it was the Kaspersky antivirus and I deleted it; I also disabled all of Windows Defender, but the problem still persisted. 2.- I tried going back to versions 3.2 and 3.1, but it's still the same. 3.- I have uninstalled the program with Revo Unistaller and I have cleaned the Laptop with everything and registered with Glary Utilities to reinstall everything again, but the problem continued. 4.- Finally I formatted and only with the defender I installed the latest version and the problem continued even though I had given permissions in the firewall for the monero and P2Pool folders and files, and I added the port that it suggests for the Mini. 5.- I have also added them to exclusions and finally I have also disabled all the antivirus functions, but the problem continues. Now the Nodes take time to synchronize and new ones are added, and also the wallet starts synchronizing from 3 million blocks and I have to wait more than 2 hours until it finishes. 6.- I have removed, cleaned and put on again, and it is still the same. 7.- I have also tried using the current date when I restore the wallet, but it continues to synchronize the wallet and the Nodes. Sometimes it shows that everything is synchronized, but when I hit it to start, it keeps starting P2Pool and does not show the Hashes it mines or does anything else. I suggest doing something one click like the "Vertcoin One Click Miner" I'm using as it's great to just boot up and start mining in the Pool without any issues. Well, I'll wait for a next version with all these new problems corrected, since I don't plan to continue wasting my time with this as it is now. Details of my Laptop: Laptop: Dell Precision M4700 Greetings! ----------------- Creo que fue de la 3.1 a la 3.3. He ido actualizando hasta que después de la 3.3 los Nodos no se sincronizan y todo empezó a dar problemas. Te intentaré explicar lo que he hecho (adjunto algunas capturas de pantallas de diferentes eventos): 1.- Pensé que era el antivirus Kaspersky y lo eliminé; también deshabilité todo de Windows Defender, pero seguía el problema. 2.- Probé volver a las versiones 3.2 y 3.1, pero sigue igual. 3.- He desintalado el programa con Revo Unistaller y he limpiado la Laptop con todo y registro con Glary Utilities para volver a instalar todo de nuevo, pero seguía el problema. 4.- Finalmente formatee y solo con el defender instalé la última versión y seguía el problema a pesar de que había dado permisos en el cortafuegos para las carpetas y archivos de monero y de P2Pool, y agregué el puerto que sugiere para la Mini. 5.- También los he agregado a exclusiones y finalmente también he deshabilitado todas las funciones del antivirus, pero sigue el problema. Ahora los Nodos tardan en sincronizar y se van agregando nuevos, y también la billetera se empiezar a sincronizar desde los 3 millones de bloques y debo esperar más de 2 horas hasta que termine. 6.- He vuelto a quitar, limpiar y poner, y sigue igual. 7.- También he probado usar la fecha actual cuando restauro la billetera, pero sigue sincronizando la billetera y los Nodos. A veces muestra que está todo sincronizado, pero cuando le doy a empezar, se queda iniciando el P2Pool y no muestra a los Hash que mina ni hace más nada. Sugiero que hagan algo de un solo clic como el "Vertcoin One Click Miner" que estoy usando, ya que, es una maravilla que iniciar solo y empieza a minar en la Pool sin problemas. Bueno, esperaré una próxima versión con todos estos problemas nuevos corregidos, ya que, no pienso seguir perdiendo el tiempo con esto como está ahora. Detalles de mi Laptop: Laptop: Dell Precision M4700 ¡Saludos!
|
Chain was fully synced before upgrade and now it seems to be re-syncing about 1/3rd of the db.
I was on monero-gui-install-win-x64-v0.18.3.2 or v0.18.3.1 before upgrade.
Is this a winblows Gui thing only?
I'm not going to upgrade anything else until this is addressed.
The text was updated successfully, but these errors were encountered: