Quote from: Valerian77 on January 16, 2017, 12:24:11 PM

Quote from: burbuscratch on January 16, 2017, 11:29:30 AM

Quote from: Valerian77 on January 16, 2017, 05:52:35 AM

...

I still have the same issue - v3.7 works seemless and v3.9 does not connect

here is the latest debug log tail:

Quote

init message: Laden abgeschlossen
GUI: QObject::connect: No such signal ClientModel::showProgress(QString,int)
GUI: QObject::connect: (receiver name: 'navcoin')
GUI: QObject::connect: Cannot connect (null)::showProgress(QString,int) to BitcoinGUI::showProgress(QString,int)
GUI: QObject::connect: No such signal WalletModel::balanceChanged(qint64, qint64, qint64, qint64)
GUI: QObject::connect: (receiver name: 'SendCoinsDialog')
No valid UPnP IGDs found
upnp thread exit
Loading addresses from DNS seeds (could take a while)
keypool reserve 10
keypool return 10

at this point the NAVcoin-qt client hangs with a steady process load of 12%. If I exit the client it does not stop but becomes non interactive and hangs with 12% process load. I can kill it then with the task manager. Starting v3.7 with the absolute same configuration connects immediately. Environment is Win10.

If somebody has a explanation that leads to solve the problem I will tip 10 NAV

Is active UPnP on your router? Must be activated

no idea - but v3.7 works seamless and the v3.7 log shows the same entry

If somebody has a better explanation that leads to solve the problem I will tip 20 NAV now

According to

Quote from: shahim on January 17, 2017, 09:35:17 AM

Hi guys,

... I would just let it run a few hours or a day and check again.

I let my node run for more than 19 hours now and it still produces constant 12% processor load and does not connect.
But there is another log entry now:

Quote

...
Loading addresses from DNS seeds (could take a while)
GUI: QObject::connect: Cannot connect (null)::numI2PConnectionsChanged(int) to BitcoinGUI::setNumI2PConnections(int)
dumpaddr thread stop
msghand thread interrupt
net thread interrupt

that does not look surprising and may not give a hint - but there is also another log "db.log" that could give a hint:

Quote

Unacceptable log file C:\Users\\AppData\Roaming\NavCoin2\database\log.0000000059: unsupported log version 17
Invalid log file: log.0000000059: Invalid argument
PANIC: Invalid argument
process-private: unable to find environment
process-private: unable to find environment

is it possible that the upgrade from v3.7 to v3.9 uses a different data structure somewhere?