Topic: [XMR] Monero - A secure, private, untraceable cryptocurrency - page 88. (Read 4671660 times)

Quote from: dEBRUYNE on June 27, 2019, 04:04:56 PM

Hi,
I upgraded my wallet from v12 to v14. But I am having an issue: monero-wallet-gui.exe does not work. It only appears in Task Manager for a second, and then immediately exits. No log file is created so I am at a loss what happens. Previous version worked OK.
I downloaded the archive from official website (not the installer) and replaced all files in my Monero folder as usual. Since then, monero-wallet-gui.exe did not work.
I then ran monerod.exe, which worked OK. At first it upgraded blockchain database from version 1 to version 2, then 3, then 4 (if I remember correctly). It is synchronizing blocks as I write this post. So my blockchain db is not corrupt. I tried running the GUI wallet while monerod.exe is running, same result. And turned off Avast antivirus temporarily, same result.
Can anyone advise what to do, please?

Do you have active AV (AntiVirus) software on that system?

Yes and Monero folder is under exclusions. And disabling AV makes no difference. Previous version (v12) worked without problems.

Can you try launching via the start-low-graphics-mode.bat batch file that is included?

That was one of the first things I tried but forgot to mention... same result: the gui exe only appears in task manager and then immediately quits, with no log created.

I have a feeling your AV is still deleting necessary files (i.e. files required in order for the GUI to run properly). Can you perhaps try these steps:

1. Reboot to ensure all Monero related processes are closed.

2. Apply this guide -> https://monero.stackexchange.com/questions/10798/my-antivirus-av-software-blocks-quarantines-the-monero-gui-wallet-is-there

3. Note that step 2. implies that you have to re-extract the .zip file.

4. Start monero-wallet-gui.exe again. Does it launch properly now?

Mek

jr. member

Activity: 75

Merit: 7

mtc.mekweb.eu - mega transistor clock

Quote from: Mek on June 27, 2019, 02:41:40 PM

Quote from: dEBRUYNE on June 27, 2019, 04:05:21 PM

Hi,
I upgraded my wallet from v12 to v14. But I am having an issue: monero-wallet-gui.exe does not work. It only appears in Task Manager for a second, and then immediately exits. No log file is created so I am at a loss what happens. Previous version worked OK.
I downloaded the archive from official website (not the installer) and replaced all files in my Monero folder as usual. Since then, monero-wallet-gui.exe did not work.
I then ran monerod.exe, which worked OK. At first it upgraded blockchain database from version 1 to version 2, then 3, then 4 (if I remember correctly). It is synchronizing blocks as I write this post. So my blockchain db is not corrupt. I tried running the GUI wallet while monerod.exe is running, same result. And turned off Avast antivirus temporarily, same result.
Can anyone advise what to do, please?

Do you have active AV (AntiVirus) software on that system?

Yes and Monero folder is under exclusions. And disabling AV makes no difference. Previous version (v12) worked without problems.

Can you try launching via the start-low-graphics-mode.bat batch file that is included?

That was one of the first things I tried but forgot to mention... same result: the gui exe only appears in task manager and then immediately quits, with no log created.

anubizz

full member

Activity: 345

Merit: 124

Same problem, but this time the error happened at 9% sync. Huh

Seems to be a SSL problem...

anubizz

full member

Activity: 345

Merit: 124

Quote from: anubizz on June 27, 2019, 03:03:08 PM

Quote from: dEBRUYNE on June 27, 2019, 12:48:23 PM

Quote from: anubizz on June 27, 2019, 03:03:08 PM

You said that the „—prune blockchain“ option needs to be includet every time the daemon is started, right!?
My problem:
To be safe i deleted the old blockchain database and started a fully new sync. The daemon was running till 66% and then he stoped and shut down. I don‘t know why..
When i start monerod again with „--prune blockchain“ i get the error „could not start sync- to many dirty blocks“. When i do the same with „-db salve“ instead of „-prune blockchain“ it starts to sync again but also shuts down some hours later.

The last version of the daemon was slower but worked constant. What could be the problem?

You may have accidentally corrupted the blockchain. There's also a bug in v0.14.1.0 due to which pruning on a sync from scratch does not function properly. I'd suggest to perform a normal resync from scratch and thereafter utilize the pruning tool.

A very interresting update on my situation:
I deleted the whole .bitmonero folder, cleaned up and started from scratch without the prune-tool-> same issue! At 66% the sync stops for reasons i can not find.

So just to have all tried, i created a completely new node on a different device (bananapi pro) and started sync from beginning. As i checked the logs some minutes ago i see the same problem at 66% as on the other device:
"

2019-06-27 03:24:22.495   [P2P9]   INFO   global   src/cryptonote_protocol/cryptonote_protocol_handler.inl:1390   [1;33mSynced 1237971/1865802 (66%, 627831 left)[0m
2019-06-27 15:49:30.527    b6f14210   INFO   logging   contrib/epee/src/mlog.cpp:273   New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,serialization:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO
2019-06-27 15:49:30.529    b6f14210   INFO   global   src/daemon/main.cpp:281   Monero 'Boron Butterfly' (v0.14.1.0-release)
2019-06-27 15:49:30.532    b6f14210   INFO   global   contrib/epee/src/net_ssl.cpp:124   Generating SSL certificate
2019-06-27 15:49:46.772    b6f14210   ERROR   msgwriter   src/common/scoped_message_writer.h:102   Error: Couldn't connect to daemon: 192.168.0.171:18088

"
Whats the problem Huh

------
Edit:

I started the sync again and watched it . After about 100 blocks it stopped with comment Segmentation fault

Do you have sufficient free disk space on both systems? Also, why are you using a non default port?

Used: 15.48GB (14.13%) Free: 94.06GB Total: 109.53GB
So space is not the problem.

I choosed a random port. Is that important? I changed to 18081 now.

Could you perhaps, for testing purposes, try a full resync from scratch with the default port?

My plan was to to delete EVERYTHING on my cubietruck! Flat all content and then start with a fresh OS and daemon.
What makes me confused the most is that i had it synced to 100% already... then i wanted to be save in every way and deleted the blockchain folder to start new, and now a lot of problems come up..

But to answer your question: Yes, i can do so!
p2p on port 18080 (opened firewall port) bound to ip 0.0.0.0
rpc on port 18081 (port closed on fw) bound to internal ip 192.168.xxx

I will let you know soon.

dEBRUYNE

legendary

Activity: 2268

Merit: 1141

Quote from: dEBRUYNE on June 27, 2019, 12:48:23 PM

Quote from: Mek on June 27, 2019, 02:41:40 PM

You said that the „—prune blockchain“ option needs to be includet every time the daemon is started, right!?
My problem:
To be safe i deleted the old blockchain database and started a fully new sync. The daemon was running till 66% and then he stoped and shut down. I don‘t know why..
When i start monerod again with „--prune blockchain“ i get the error „could not start sync- to many dirty blocks“. When i do the same with „-db salve“ instead of „-prune blockchain“ it starts to sync again but also shuts down some hours later.

The last version of the daemon was slower but worked constant. What could be the problem?

You may have accidentally corrupted the blockchain. There's also a bug in v0.14.1.0 due to which pruning on a sync from scratch does not function properly. I'd suggest to perform a normal resync from scratch and thereafter utilize the pruning tool.

A very interresting update on my situation:
I deleted the whole .bitmonero folder, cleaned up and started from scratch without the prune-tool-> same issue! At 66% the sync stops for reasons i can not find.

So just to have all tried, i created a completely new node on a different device (bananapi pro) and started sync from beginning. As i checked the logs some minutes ago i see the same problem at 66% as on the other device:
"

2019-06-27 03:24:22.495   [P2P9]   INFO   global   src/cryptonote_protocol/cryptonote_protocol_handler.inl:1390   [1;33mSynced 1237971/1865802 (66%, 627831 left)[0m
2019-06-27 15:49:30.527    b6f14210   INFO   logging   contrib/epee/src/mlog.cpp:273   New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,serialization:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO
2019-06-27 15:49:30.529    b6f14210   INFO   global   src/daemon/main.cpp:281   Monero 'Boron Butterfly' (v0.14.1.0-release)
2019-06-27 15:49:30.532    b6f14210   INFO   global   contrib/epee/src/net_ssl.cpp:124   Generating SSL certificate
2019-06-27 15:49:46.772    b6f14210   ERROR   msgwriter   src/common/scoped_message_writer.h:102   Error: Couldn't connect to daemon: 192.168.0.171:18088

"
Whats the problem Huh

------
Edit:

I started the sync again and watched it . After about 100 blocks it stopped with comment Segmentation fault

Do you have sufficient free disk space on both systems? Also, why are you using a non default port?

Used: 15.48GB (14.13%) Free: 94.06GB Total: 109.53GB
So space is not the problem.

I choosed a random port. Is that important? I changed to 18081 now.

Could you perhaps, for testing purposes, try a full resync from scratch with the default port?

dEBRUYNE

legendary

Activity: 2268

Merit: 1141

Quote from: dEBRUYNE on June 27, 2019, 12:48:23 PM

Hi,
I upgraded my wallet from v12 to v14. But I am having an issue: monero-wallet-gui.exe does not work. It only appears in Task Manager for a second, and then immediately exits. No log file is created so I am at a loss what happens. Previous version worked OK.
I downloaded the archive from official website (not the installer) and replaced all files in my Monero folder as usual. Since then, monero-wallet-gui.exe did not work.
I then ran monerod.exe, which worked OK. At first it upgraded blockchain database from version 1 to version 2, then 3, then 4 (if I remember correctly). It is synchronizing blocks as I write this post. So my blockchain db is not corrupt. I tried running the GUI wallet while monerod.exe is running, same result. And turned off Avast antivirus temporarily, same result.
Can anyone advise what to do, please?

Do you have active AV (AntiVirus) software on that system?

Yes and Monero folder is under exclusions. And disabling AV makes no difference. Previous version (v12) worked without problems.

Can you try launching via the start-low-graphics-mode.bat batch file that is included?

anubizz

full member

Activity: 345

Merit: 124

You said that the „—prune blockchain“ option needs to be includet every time the daemon is started, right!?
My problem:
To be safe i deleted the old blockchain database and started a fully new sync. The daemon was running till 66% and then he stoped and shut down. I don‘t know why..
When i start monerod again with „--prune blockchain“ i get the error „could not start sync- to many dirty blocks“. When i do the same with „-db salve“ instead of „-prune blockchain“ it starts to sync again but also shuts down some hours later.

The last version of the daemon was slower but worked constant. What could be the problem?

You may have accidentally corrupted the blockchain. There's also a bug in v0.14.1.0 due to which pruning on a sync from scratch does not function properly. I'd suggest to perform a normal resync from scratch and thereafter utilize the pruning tool.

A very interresting update on my situation:
I deleted the whole .bitmonero folder, cleaned up and started from scratch without the prune-tool-> same issue! At 66% the sync stops for reasons i can not find.

So just to have all tried, i created a completely new node on a different device (bananapi pro) and started sync from beginning. As i checked the logs some minutes ago i see the same problem at 66% as on the other device:
"

2019-06-27 03:24:22.495   [P2P9]   INFO   global   src/cryptonote_protocol/cryptonote_protocol_handler.inl:1390   [1;33mSynced 1237971/1865802 (66%, 627831 left)[0m
2019-06-27 15:49:30.527    b6f14210   INFO   logging   contrib/epee/src/mlog.cpp:273   New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,serialization:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO
2019-06-27 15:49:30.529    b6f14210   INFO   global   src/daemon/main.cpp:281   Monero 'Boron Butterfly' (v0.14.1.0-release)
2019-06-27 15:49:30.532    b6f14210   INFO   global   contrib/epee/src/net_ssl.cpp:124   Generating SSL certificate
2019-06-27 15:49:46.772    b6f14210   ERROR   msgwriter   src/common/scoped_message_writer.h:102   Error: Couldn't connect to daemon: 192.168.0.171:18088

"
Whats the problem Huh

------
Edit:

I started the sync again and watched it . After about 100 blocks it stopped with comment Segmentation fault

Do you have sufficient free disk space on both systems? Also, why are you using a non default port?

Used: 15.48GB (14.13%) Free: 94.06GB Total: 109.53GB
So space is not the problem.

I choosed a random port. Is that important? I changed to 18081 now.

Mek

jr. member

Activity: 75

Merit: 7

mtc.mekweb.eu - mega transistor clock

Hi,
I upgraded my wallet from v12 to v14. But I am having an issue: monero-wallet-gui.exe does not work. It only appears in Task Manager for a second, and then immediately exits. No log file is created so I am at a loss what happens. Previous version worked OK.
I downloaded the archive from official website (not the installer) and replaced all files in my Monero folder as usual. Since then, monero-wallet-gui.exe did not work.
I then ran monerod.exe, which worked OK. At first it upgraded blockchain database from version 1 to version 2, then 3, then 4 (if I remember correctly). It is synchronizing blocks as I write this post. So my blockchain db is not corrupt. I tried running the GUI wallet while monerod.exe is running, same result. And turned off Avast antivirus temporarily, same result.
Can anyone advise what to do, please?

Do you have active AV (AntiVirus) software on that system?

Yes and Monero folder is under exclusions. And disabling AV makes no difference. Previous version (v12) worked without problems.

dEBRUYNE

legendary

Activity: 2268

Merit: 1141

You said that the „—prune blockchain“ option needs to be includet every time the daemon is started, right!?
My problem:
To be safe i deleted the old blockchain database and started a fully new sync. The daemon was running till 66% and then he stoped and shut down. I don‘t know why..
When i start monerod again with „--prune blockchain“ i get the error „could not start sync- to many dirty blocks“. When i do the same with „-db salve“ instead of „-prune blockchain“ it starts to sync again but also shuts down some hours later.

The last version of the daemon was slower but worked constant. What could be the problem?

You may have accidentally corrupted the blockchain. There's also a bug in v0.14.1.0 due to which pruning on a sync from scratch does not function properly. I'd suggest to perform a normal resync from scratch and thereafter utilize the pruning tool.

A very interresting update on my situation:
I deleted the whole .bitmonero folder, cleaned up and started from scratch without the prune-tool-> same issue! At 66% the sync stops for reasons i can not find.

So just to have all tried, i created a completely new node on a different device (bananapi pro) and started sync from beginning. As i checked the logs some minutes ago i see the same problem at 66% as on the other device:
"

2019-06-27 03:24:22.495   [P2P9]   INFO   global   src/cryptonote_protocol/cryptonote_protocol_handler.inl:1390   [1;33mSynced 1237971/1865802 (66%, 627831 left)[0m
2019-06-27 15:49:30.527    b6f14210   INFO   logging   contrib/epee/src/mlog.cpp:273   New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,serialization:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO
2019-06-27 15:49:30.529    b6f14210   INFO   global   src/daemon/main.cpp:281   Monero 'Boron Butterfly' (v0.14.1.0-release)
2019-06-27 15:49:30.532    b6f14210   INFO   global   contrib/epee/src/net_ssl.cpp:124   Generating SSL certificate
2019-06-27 15:49:46.772    b6f14210   ERROR   msgwriter   src/common/scoped_message_writer.h:102   Error: Couldn't connect to daemon: 192.168.0.171:18088

"
Whats the problem Huh

------
Edit:

I started the sync again and watched it . After about 100 blocks it stopped with comment Segmentation fault

Do you have sufficient free disk space on both systems? Also, why are you using a non default port?

anubizz

full member

Activity: 345

Merit: 124

You said that the „—prune blockchain“ option needs to be includet every time the daemon is started, right!?
My problem:
To be safe i deleted the old blockchain database and started a fully new sync. The daemon was running till 66% and then he stoped and shut down. I don‘t know why..
When i start monerod again with „--prune blockchain“ i get the error „could not start sync- to many dirty blocks“. When i do the same with „-db salve“ instead of „-prune blockchain“ it starts to sync again but also shuts down some hours later.

The last version of the daemon was slower but worked constant. What could be the problem?

You may have accidentally corrupted the blockchain. There's also a bug in v0.14.1.0 due to which pruning on a sync from scratch does not function properly. I'd suggest to perform a normal resync from scratch and thereafter utilize the pruning tool.

A very interresting update on my situation:
I deleted the whole .bitmonero folder, cleaned up and started from scratch without the prune-tool-> same issue! At 66% the sync stops for reasons i can not find.

So just to have all tried, i created a completely new node on a different device (bananapi pro) and started sync from beginning. As i checked the logs some minutes ago i see the same problem at 66% as on the other device:
"

2019-06-27 03:24:22.495   [P2P9]   INFO   global   src/cryptonote_protocol/cryptonote_protocol_handler.inl:1390   [1;33mSynced 1237971/1865802 (66%, 627831 left)[0m
2019-06-27 15:49:30.527    b6f14210   INFO   logging   contrib/epee/src/mlog.cpp:273   New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,serialization:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO
2019-06-27 15:49:30.529    b6f14210   INFO   global   src/daemon/main.cpp:281   Monero 'Boron Butterfly' (v0.14.1.0-release)
2019-06-27 15:49:30.532    b6f14210   INFO   global   contrib/epee/src/net_ssl.cpp:124   Generating SSL certificate
2019-06-27 15:49:46.772    b6f14210   ERROR   msgwriter   src/common/scoped_message_writer.h:102   Error: Couldn't connect to daemon: 192.168.0.171:18088

"
Whats the problem Huh

------
Edit:

I started the sync again and watched it . After about 100 blocks it stopped with comment Segmentation fault

dEBRUYNE

legendary

Activity: 2268

Merit: 1141