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?
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
------
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.
