-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NAV 6.0.2 QT stuck at time sync #800
Comments
We have a PR that addresses this issue, might be in next release.
…On Wed, Feb 24, 2021, 09:07 Pawel Cioch ***@***.***> wrote:
Linux Mint 19.3 (Ubuntu 18.04)
2021-02-24 01:04:04 Navcoin version v6.0.2.0-0e69844e
2021-02-24 01:04:04 InitParameterInteraction: parameter interaction:
-whitelistforcerelay=1 -> setting -whitelistrelay=1
2021-02-24 01:04:04 GUI: Could not parse stylesheet of object
0x5579b13de860
2021-02-24 01:04:04 INFO: Updating prices
2021-02-24 01:04:04 INFO: Automatic price update set to 300000ms
2021-02-24 01:04:04 INFO: Updated prices
2021-02-24 01:04:05 Default data directory /home/skiron/.navcoin4
2021-02-24 01:04:05 Using data directory /media/skiron/Blockchains/nav
2021-02-24 01:04:05 Using config file
/media/skiron/Blockchains/nav/navcoin.conf
2021-02-24 01:04:05 Using at most 125 connections (1024 file descriptors
available)
2021-02-24 01:04:05 Using 4 threads for script verification
2021-02-24 01:04:05 Using BerkeleyDB version Berkeley DB 5.3.28:
(September 9, 2013)
2021-02-24 01:04:05 scheduler thread start
2021-02-24 01:04:05 Using wallet temp.wallet
2021-02-24 01:04:05 init message: Verifying wallet...
2021-02-24 01:04:05 CDBEnv::Open:
LogDir=/media/skiron/Blockchains/nav/database
ErrorFile=/media/skiron/Blockchains/nav/db.log
2021-02-24 01:04:05 INFO: CDBEnv::Open: Encryption Disabled
2021-02-24 01:04:05 INFO: CDBEnv::Open: CALL DBEnv->open
2021-02-24 01:04:05 INFO: CDBEnv::Open: DIR /media/skiron/Blockchains/nav
2021-02-24 01:04:05 INFO: CDBEnv::Verify: CODE: 0 MESSAGE: BDB0062
Successful return: 0
2021-02-24 01:04:05 init message: Synchronizing clock...
2021-02-24 01:04:05 [NTP] Starting clock sync...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#800>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIDAKLBFQR3TBLSPLLA6XLTARGN5ANCNFSM4YDQU25A>
.
|
@skironDotNet the fix for this is now merged into master branch, should be included in next release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Linux Mint 19.3 (Ubuntu 18.04)
2021-02-24 01:04:04 Navcoin version v6.0.2.0-0e69844e
2021-02-24 01:04:04 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2021-02-24 01:04:04 GUI: Could not parse stylesheet of object 0x5579b13de860
2021-02-24 01:04:04 INFO: Updating prices
2021-02-24 01:04:04 INFO: Automatic price update set to 300000ms
2021-02-24 01:04:04 INFO: Updated prices
2021-02-24 01:04:05 Default data directory /home/skiron/.navcoin4
2021-02-24 01:04:05 Using data directory /media/skiron/Blockchains/nav
2021-02-24 01:04:05 Using config file /media/skiron/Blockchains/nav/navcoin.conf
2021-02-24 01:04:05 Using at most 125 connections (1024 file descriptors available)
2021-02-24 01:04:05 Using 4 threads for script verification
2021-02-24 01:04:05 Using BerkeleyDB version Berkeley DB 5.3.28: (September 9, 2013)
2021-02-24 01:04:05 scheduler thread start
2021-02-24 01:04:05 Using wallet temp.wallet
2021-02-24 01:04:05 init message: Verifying wallet...
2021-02-24 01:04:05 CDBEnv::Open: LogDir=/media/skiron/Blockchains/nav/database ErrorFile=/media/skiron/Blockchains/nav/db.log
2021-02-24 01:04:05 INFO: CDBEnv::Open: Encryption Disabled
2021-02-24 01:04:05 INFO: CDBEnv::Open: CALL DBEnv->open
2021-02-24 01:04:05 INFO: CDBEnv::Open: DIR /media/skiron/Blockchains/nav
2021-02-24 01:04:05 INFO: CDBEnv::Verify: CODE: 0 MESSAGE: BDB0062 Successful return: 0
2021-02-24 01:04:05 init message: Synchronizing clock...
2021-02-24 01:04:05 [NTP] Starting clock sync...
The text was updated successfully, but these errors were encountered: