aspect
commented
1 month ago It is more of a Kaspa NG issue, which should be filed at https://github.com/aspectron/kaspa-ng/issues (albeit it does look like the daemon is having trouble starting up, which can be related to Rusty Kaspa daemon itself).
This looks environmental or state/PC related as people are running KNG on Windows without encountering such issues.
Regardless, I have the following questions and suggestions:
1) Does the machine have enough free disk space?
2) Does switching network type have any effect? (mainnet vs testnet-11)
3) What does the Log tab show when this occurs? (Under certain circumstances, the p2p node can start re-indexing the database on startup. This can take a few minutes on regular machines. However, when this occurs, logs should state that the node is re-indexing data. If this is the case, one should wait for the re-indexing to complete.)
4) Can you please exit Kaspa NG and run the node manually from the command line. You can do this by downloading the latest release from https://github.com/kaspanet/rusty-kaspa/releases and running it as kaspad --utxoindex.
Only after you check 3) and try 4) (as running the node manually can present additional clues), can you please go to C:\Users\<username>\AppData\Local\ and rename rusty-kaspa folder to rusty-kaspa-01 (or you can also delete it). (This will help in case there has been any type of data corruption. This does not occur under normal circumstances but you never know - desktop PCs can exhibit various strange behaviors.)
You should join Kaspa Discord#help-kaspa-ng channel and ask the questions there (there are more people and it is faster to get feedback/ideas in relation to any problems).
LMK if anything I just described helps or has any effect.
Jinxsyns
Describe the bug Unsure what may have caused it but I all of a sudden can't get the p2p node to start when using the integrated daemon. If i go to a remote node it works though. it just seems to get stuck in starting (it just says not connected and starting)
To Reproduce Steps to reproduce the behavior: All I did was open the program. it worked fine the last time I ran it? And like i said switching to a remote node to sync off of works but even switching back to integrated daemon doesn't work to start up the integrated daemon Expected behavior It to function? I apologize if that sounds rude not my intention it just isn't functioning at all (the node specifically the rest of the program works)
Screenshots
Desktop (please complete the following information):
Additional context Add any other context about the problem here.