not able to send transactions out of my wallet (Unable to reach time API: NTP error: NTP server is not provided.. Make sure that your clock is synchronized.) #6632

fidaaayoub · 2017-10-04T10:54:52Z

Before filing a new issue, please provide the following information.

I'm running: parity 1.7

Parity version: 1.7

Operating system: MacOS

And installed: via installer

Unable to reach time API: NTP error: NTP server is not provided.. Make sure that your clock is synchronized.

I am getting Unable to make a connection to the Parity Secure API. in status. chain synchronized, and i have 3/25 peers, but still getting time synchronized as NO. i have check my time.is and it's exact!
i was trying to make transaction, it never went out. transaction showing under Signer tab, local transaction.... if i try to cancel or anything, it creates a zero value transaction between me and myself! within the wallet, and keep going

fidaaayoub · 2017-10-04T11:09:43Z

10/4/2017, 3:08:45 PM] IO Worker #2 TRACE sync Status timeout 41

[10/4/2017, 3:08:44 PM] IO Worker #0 TRACE sync Status timeout 41

[10/4/2017, 3:08:43 PM] IO Worker #3 TRACE sync == Disconnecting 7: Parity/v1.8.0-unstable-339f63a-20170922/x86_64-linux-gnu/rustc1.20.0

[10/4/2017, 3:08:43 PM] IO Worker #0 TRACE sync Sending status to 7, protocol version 2

[10/4/2017, 3:08:43 PM] IO Worker #0 TRACE sync == Connected 7: Parity/v1.8.0-unstable-339f63a-20170922/x86_64-linux-gnu/rustc1.20.0

[10/4/2017, 3:08:43 PM] IO Worker #0 TRACE sync Status timeout 41

[10/4/2017, 3:08:43 PM] IO Worker #3 TRACE sync == Disconnecting 9: Parity/v1.6.7-beta-e128418-20170518/x86_64-linux-gnu/rustc1.17.0

[10/4/2017, 3:08:43 PM] IO Worker #0 DEBUG sync Error sending status request: Expired

[10/4/2017, 3:08:43 PM] IO Worker #0 TRACE sync Sending status to 9, protocol version 2

[10/4/2017, 3:08:43 PM] IO Worker #0 TRACE sync == Connected 9: Parity/v1.6.7-beta-e128418-20170518/x86_64-linux-gnu/rustc1.17.0

[10/4/2017, 3:08:42 PM] IO Worker #3 TRACE sync == Disconnecting 6: Parity/v1.8.0-unstable-339f63a-20170922/x86_64-linux-gnu/rustc1.20.0

[10/4/2017, 3:08:42 PM] IO Worker #0 TRACE sync Sending status to 6, protocol version 2

[10/4/2017, 3:08:42 PM] IO Worker #0 TRACE sync == Connected 6: Parity/v1.8.0-unstable-339f63a-20170922/x86_64-linux-gnu/rustc1.20.0

[10/4/2017, 3:08:42 PM] IO Worker #1 TRACE sync Status timeout 41

[10/4/2017, 3:08:41 PM] IO Worker #1 TRACE sync == Disconnecting 12: Parity/v1.8.0-unstable-339f63a-20170922/x86_64-linux-gnu/rustc1.20.0

[10/4/2017, 3:08:41 PM] IO Worker #0 TRACE sync Sending status to 12, protocol version 2

[10/4/2017, 3:08:41 PM] IO Worker #0 TRACE sync == Connected 12: Parity/v1.8.0-unstable-339f63a-20170922/x86_64-linux-gnu/rustc1.20.0

[10/4/2017, 3:08:41 PM] IO Worker #2 TRACE sync Status timeout 41

[10/4/2017, 3:08:40 PM] IO Worker #0 TRACE sync == Disconnecting 4: Parity/v1.8.0-unstable-339f63a-20170922/x86_64-linux-gnu/rustc1.20.0

[10/4/2017, 3:08:40 PM] IO Worker #0 TRACE sync Sending status to 4, protocol version 2

[10/4/2017, 3:08:40 PM] IO Worker #0 TRACE sync == Connected 4: Parity/v1.8.0-unstable-339f63a-20170922/x86_64-linux-gnu/rustc1.20.0

[10/4/2017, 3:08:40 PM] IO Worker #1 TRACE sync Status timeout 41

[10/4/2017, 3:08:39 PM] IO Worker #1 TRACE sync == Disconnecting 73: Parity/v1.8.0-unstable-339f63a-20170922/x86_64-linux-gnu/rustc1.20.0

[10/4/2017, 3:08:39 PM] IO Worker #0 TRACE sync Sending status to 73, protocol version 2

[10/4/2017, 3:08:39 PM]

here is some logs

fidaaayoub · 2017-10-04T11:11:39Z

10/4/2017, 3:11:06 PM] IO Worker #3 TRACE sync Status timeout 41

[10/4/2017, 3:11:05 PM] IO Worker #0 DEBUG sync Sent up to 8 transactions to 1 peers.

[10/4/2017, 3:11:05 PM] IO Worker #0 TRACE sync 52 <- Transactions (8 entries)

[10/4/2017, 3:11:05 PM] IO Worker #0 TRACE sync Status timeout 41

[10/4/2017, 3:11:04 PM] IO Worker #0 DEBUG sync Sent up to 64 transactions to 2 peers.

[10/4/2017, 3:11:04 PM] IO Worker #0 TRACE sync 55 <- Transactions (8 entries)

[10/4/2017, 3:11:04 PM] IO Worker #0 TRACE sync 52 <- Transactions (64 entries)

[10/4/2017, 3:11:04 PM] IO Worker #0 TRACE sync Status timeout 41

[10/4/2017, 3:11:03 PM] IO Worker #2 TRACE sync 55 -> Transactions (64 entries)

[10/4/2017, 3:11:03 PM] IO Worker #3 TRACE sync Status timeout 41

[10/4/2017, 3:11:02 PM] IO Worker #3 TRACE sync Status timeout 41

[10/4/2017, 3:11:02 PM] IO Worker #2 TRACE sync Skipping peer 52, force=false, td=Some(1096706072558633511825), our td=1096706072558633511825, state=Idle

[10/4/2017, 3:11:02 PM] IO Worker #2 TRACE sync Considering peer 55, force=false, td=None, our td=1096706072558633511825, latest=5dfc…8f9b, have_latest=true, state=Idle

[10/4/2017, 3:11:02 PM] IO Worker #2 TRACE sync Syncing with peers: 2 active, 2 confirmed, 2 total

[10/4/2017, 3:11:02 PM] IO Worker #2 DEBUG sync Disconnected 51

[10/4/2017, 3:11:02 PM] IO Worker #2 TRACE sync == Disconnecting 51: Parity/v1.4.9-beta-48924e9-20170109/x86_64-linux-gnu/rustc1.13.0-beta.2

[10/4/2017, 3:11:02 PM] IO Worker #1 TRACE sync 51: Fork mismatch

[10/4/2017, 3:11:02 PM] IO Worker #2 TRACE sync 51 -> GetBlockHeaders: returned 1 entries

[10/4/2017, 3:11:02 PM] IO Worker #2 TRACE sync 51: Returning cached fork header

[10/4/2017, 3:11:02 PM] IO Worker #2 TRACE sync 51 -> GetBlockHeaders (number: 1920000, max: 1, skip: 0, reverse:false)

[10/4/2017, 3:11:02 PM] IO Worker #0 TRACE sync 51 <- GetForkHeader: at 1920000

[10/4/2017, 3:11:02 PM] IO Worker #0 DEBUG sync Connected 51:Parity/v1.4.9-beta-48924e9-20170109/x86_64-linux-gnu/rustc1.13.0-beta.2

[10/4/2017, 3:11:02 PM] IO Worker #0 TRACE sync New peer 51 (protocol: 1, network: 1, difficulty: Some(130648582509878175955), latest:6c85…48bf, genesis:d4e5…8fa3, snapshot:Some(0))

[10/4/2017, 3:11:02 PM] IO Worker #1 TRACE sync Sending status to 51, protocol version 1

[10/4/2017, 3:11:02 PM]

10/4/2017, 3:11:24 PM] IO Worker #3 TRACE sync Status timeout 41

[10/4/2017, 3:11:23 PM] IO Worker #3 TRACE sync Status timeout 41

[10/4/2017, 3:11:22 PM] IO Worker #2 TRACE sync Status timeout 41

[10/4/2017, 3:11:21 PM] IO Worker #0 TRACE sync Status timeout 41

[10/4/2017, 3:11:20 PM] IO Worker #1 DEBUG sync Sent up to 211 transactions to 2 peers.

[10/4/2017, 3:11:20 PM] IO Worker #1 TRACE sync 55 <- Transactions (211 entries)

[10/4/2017, 3:11:20 PM] IO Worker #1 TRACE sync 52 <- Transactions (1 entries)

[10/4/2017, 3:11:20 PM] IO Worker #1 TRACE sync Status timeout 41

[10/4/2017, 3:11:20 PM] Verifier #0 INFO import Imported #4335958 d56b…5404 (50 txs, 6.66 Mgas, 273.90 ms, 15.83 KiB)

[10/4/2017, 3:11:20 PM] Verifier #0 TRACE sync Re-broadcasting transactions to a random peer.

[10/4/2017, 3:11:20 PM] Verifier #0 TRACE sync Sending proposed blocks to [52, 55]

[10/4/2017, 3:11:20 PM] Verifier #0 TRACE sync Sending NewBlocks to []

[10/4/2017, 3:11:20 PM] Verifier #0 TRACE sync Sending NewHashes to []

[10/4/2017, 3:11:20 PM] Verifier #0 TRACE sync Checking peer our best d56b…5404 their best d56b…5404

[10/4/2017, 3:11:20 PM] Verifier #0 TRACE sync Propagating blocks, state=Idle

[10/4/2017, 3:11:20 PM] IO Worker #2 TRACE sync Considering peer 55, force=false, td=None, our td=1096708945834891318526, latest=d56b…5404, have_latest=true, state=Idle

[10/4/2017, 3:11:20 PM] IO Worker #2 TRACE sync Skipping peer 52, force=false, td=Some(1096708945834891318526), our td=1096708945834891318526, state=Idle

[10/4/2017, 3:11:20 PM] IO Worker #2 TRACE sync Syncing with peers: 2 active, 2 confirmed, 2 total

[10/4/2017, 3:11:20 PM] IO Worker #2 TRACE sync New block hash already in chain d56b26e6a3b2a793685b5462da6e8cfe7e42a02dcae636c810bb241e485c5404

[10/4/2017, 3:11:20 PM] IO Worker #2 TRACE sync 55 -> NewHashes (1 entries)

[10/4/2017, 3:11:19 PM] IO Worker #1 TRACE sync Sync complete

[10/4/2017, 3:11:19 PM] IO Worker #1 TRACE sync Considering peer 52, force=false, td=None, our td=1096708945834891318526, latest=d56b…5404, have_latest=true, state=NewBlocks

[10/4/2017, 3:11:19 PM]

fidaaayoub · 2017-10-04T11:20:38Z

@tomusdrw @5chdn

5chdn · 2017-10-05T08:00:26Z

Does the transaction show up on etherscan? Can you open APPLICATIONS > TX QUEUE VIEWER and locate your transaction there?

fidaaayoub · 2017-10-05T09:14:30Z

@5chdn , i opened applications, tx queue viewer, and I can see all these zero transactions between myself

5chdn · 2017-10-05T09:58:44Z

You set the gas price to 0 which means no miner will probably accept it. Try increasing the gas price to at least 1 shannon.

fidaaayoub · 2017-10-05T10:04:21Z

i didn't set anything.... these they got created by automatically when i was cancelling 1 transaction

i was trying to contribute in some fund raise and i created transaction, with 300k gas. it was hanging and never went to network.

i tried to cancel. then all these created by themselves

fidaaayoub · 2017-10-05T10:06:41Z

@5chdn i want to cancel them. i was trying to cancel , each time i click cancel, it creates another one of those zero transactions

5chdn · 2017-10-05T10:36:45Z

Ah okay, what you see are the cancelled transactions. Probably. Try restarting your node with --no-persistent-txqueue

fidaaayoub · 2017-10-05T11:10:56Z

@5chdn how i can run this command? from where? sry i am not an expert in parity

5chdn · 2017-10-05T11:42:00Z

open a terminal, change directory

cd /Applications/Parity\ Ethereum.app/Contents/MacOS/

and run

parity --no-persistent-txqueue

fidaaayoub · 2017-10-05T12:27:27Z

i have done that, but still as is

Client service error: Client(Database("IO error: lock /XXXXX/XXXX/Library/Application Support/io.parity.ethereum/chains/ethereum/db/XXXXXXXXXXX/overlayrecent/db/LOCK: Resource temporarily unavailable"))
PCNAMEs-mbp:MacOS XXXX$

5chdn · 2017-10-05T14:25:08Z

Yes, your node is already running. Stop it first :)

fidaaayoub · 2017-10-05T15:26:03Z

I have tried to shut the node down and run but the same result... maybe i even tried to restart Best Regards, Fidaa Ayoub, PMP Program Manager

…

On Oct 5, 2017, at 6:25 PM, Afri Schoedon ***@***.***> wrote: Yes, your node is already running. Stop it first :) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

fidaaayoub · 2017-10-06T09:19:15Z

@5chdn can you please help? i tried even after restart, still no luck.
i tried to initiate another transaction from my parity to myethwallet..... and same thing, nothing going through!!!

5chdn · 2017-10-06T09:53:10Z

More drastic approach would be

stop parity
back up your keys
uninstall parity
remove all parity files (except your keys)
install parity
run parity
import your keys

fidaaayoub · 2017-10-06T09:55:40Z

that’s too risky, i have many ICO contributions and i would be worried to lose tokens in between…… no safer step? is there a command to fully shut down parity? then run the 2 commands you recommended? or it’s just closing the browser?

…

On Oct 6, 2017, at 1:53 PM, Afri Schoedon ***@***.***> wrote: More drastic approach would be stop parity back up your keys uninstall parity remove all parity files (except your keys) install parity run parity import your keys — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6632 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AcRZJq48SwbjivzNnWyWbgjWr-ee9BHqks5spfiMgaJpZM4PtbfN>.

5chdn · 2017-10-06T09:58:59Z

You need to stop the Parity daemon. Closing the browser does not do it. Have you tried clicking the system tray icon?

fidaaayoub · 2017-10-06T10:18:47Z

how is that?

…

On Oct 6, 2017, at 1:59 PM, Afri Schoedon ***@***.***> wrote: You need to stop the Parity daemon. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6632 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AcRZJrd1RREx4POMlKeMga6fgVDCg6jxks5spfnqgaJpZM4PtbfN>.

fidaaayoub · 2017-10-06T10:21:09Z

here is the logs 10/6/2017, 2:20:43 PM] IO Worker #1 TRACE sync 11 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #3 TRACE sync 49 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #2 TRACE sync 67 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #3 TRACE sync 47 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #0 TRACE sync 10 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #0 TRACE sync 19 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #1 TRACE sync 11 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #3 TRACE sync 11 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #2 TRACE sync 19 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #1 TRACE sync 30 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #0 TRACE sync 11 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #1 TRACE sync == Disconnecting 44: Geth/v1.6.7-stable-ab5646c5/linux-amd64/go1.7.3 [10/6/2017, 2:20:43 PM] IO Worker #2 TRACE sync 11 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #1 TRACE sync 11 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #0 TRACE sync 11 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #1 TRACE sync Sending status to 70, protocol version 1 [10/6/2017, 2:20:43 PM] IO Worker #1 TRACE sync == Connected 70: Parity/v1.4.9-beta-48924e9-20170109/x86_64-linux-gnu/rustc1.13.0-beta.2 [10/6/2017, 2:20:43 PM] IO Worker #0 TRACE sync 49 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #0 TRACE sync 67 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #1 TRACE sync 47 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #3 TRACE sync 10 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #0 TRACE sync 11 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM] IO Worker #3 TRACE sync 50 -> Transactions (1 entries) [10/6/2017, 2:20:43 PM]

…

On Oct 6, 2017, at 1:59 PM, Afri Schoedon ***@***.***> wrote: You need to stop the Parity daemon. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6632 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AcRZJrd1RREx4POMlKeMga6fgVDCg6jxks5spfnqgaJpZM4PtbfN>.

fidaaayoub · 2017-10-06T10:26:13Z

XXXXXXs-MacBook-Pro:~ XXXXXX$ parity --chain testnet Loading config file from /Users/XXXXXX/Library/Application Support/io.parity.ethereum/config.toml 2017-10-06 14:24:28 main INFO parity::run Starting Parity/v1.7.0-beta-5f2cabd-20170727/x86_64-macos/rustc1.18.0 2017-10-06 14:24:28 main INFO parity::run Keys path /Users/XXXXXX/Library/Application Support/io.parity.ethereum/keys/Kovan 2017-10-06 14:24:28 main INFO parity::run DB path /Users/XXXXXX/Library/Application Support/io.parity.ethereum/chains/kovan/db/9bf388941c25ea98 2017-10-06 14:24:28 main INFO parity::run Path to dapps /Users/XXXXXX/Library/Application Support/io.parity.ethereum/dapps 2017-10-06 14:24:28 main INFO parity::run State DB configuration: fast 2017-10-06 14:24:28 main INFO parity::run Operating mode: active 2017-10-06 14:24:28 main INFO ethcore::service Configured for Kovan using AuthorityRound engine 2017-10-06 14:24:29 main WARN ethsync::api Network port V4(0.0.0.0:30303) is already in use, make sure that another instance of an Ethereum client is not running or change the port using the --port option. 2017-10-06 14:24:29 main ERROR ws Unable to listen on 127.0.0.1:8546 WebSockets address 127.0.0.1:8546 is already in use, make sure that another instance of an Ethereum client is not running or change the address using the --ws-port and --ws-interface options. pthread lock: Invalid argument XXXXXXXs-MacBook-Pro:~ XXXXXX$

…

On Oct 6, 2017, at 1:59 PM, Afri Schoedon ***@***.***> wrote: You need to stop the Parity daemon. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6632 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AcRZJrd1RREx4POMlKeMga6fgVDCg6jxks5spfnqgaJpZM4PtbfN>.

fidaaayoub · 2017-10-06T19:46:04Z

i was trying to make a transaction to my other wallet. i kept increase gas until it got mined, but still i am not able to clear the queue…. how i can cancel all these transactions

…

On Oct 6, 2017, at 1:59 PM, Afri Schoedon ***@***.***> wrote: You need to stop the Parity daemon. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6632 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AcRZJrd1RREx4POMlKeMga6fgVDCg6jxks5spfnqgaJpZM4PtbfN>.

fidaaayoub changed the title ~~not able to send transactions out of my wallet~~ not able to send transactions out of my wallet (Unable to reach time API: NTP error: NTP server is not provided.. Make sure that your clock is synchronized.) Oct 4, 2017

5chdn added the Z1-question 🙋‍♀️ Issue is a question. Closer should answer. label Oct 5, 2017

5chdn closed this as completed Oct 5, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

not able to send transactions out of my wallet (Unable to reach time API: NTP error: NTP server is not provided.. Make sure that your clock is synchronized.) #6632

not able to send transactions out of my wallet (Unable to reach time API: NTP error: NTP server is not provided.. Make sure that your clock is synchronized.) #6632

fidaaayoub commented Oct 4, 2017 •

edited

Loading

fidaaayoub commented Oct 4, 2017

fidaaayoub commented Oct 4, 2017

fidaaayoub commented Oct 4, 2017

5chdn commented Oct 5, 2017

fidaaayoub commented Oct 5, 2017

5chdn commented Oct 5, 2017

fidaaayoub commented Oct 5, 2017

fidaaayoub commented Oct 5, 2017

5chdn commented Oct 5, 2017

fidaaayoub commented Oct 5, 2017

5chdn commented Oct 5, 2017

fidaaayoub commented Oct 5, 2017

5chdn commented Oct 5, 2017

fidaaayoub commented Oct 5, 2017 via email

fidaaayoub commented Oct 6, 2017

5chdn commented Oct 6, 2017

fidaaayoub commented Oct 6, 2017 via email

5chdn commented Oct 6, 2017 •

edited

Loading

fidaaayoub commented Oct 6, 2017 via email

fidaaayoub commented Oct 6, 2017 via email

fidaaayoub commented Oct 6, 2017 via email

fidaaayoub commented Oct 6, 2017 via email

not able to send transactions out of my wallet (Unable to reach time API: NTP error: NTP server is not provided.. Make sure that your clock is synchronized.) #6632

not able to send transactions out of my wallet (Unable to reach time API: NTP error: NTP server is not provided.. Make sure that your clock is synchronized.) #6632

Comments

fidaaayoub commented Oct 4, 2017 • edited Loading

fidaaayoub commented Oct 4, 2017

fidaaayoub commented Oct 4, 2017

fidaaayoub commented Oct 4, 2017

5chdn commented Oct 5, 2017

fidaaayoub commented Oct 5, 2017

5chdn commented Oct 5, 2017

fidaaayoub commented Oct 5, 2017

fidaaayoub commented Oct 5, 2017

5chdn commented Oct 5, 2017

fidaaayoub commented Oct 5, 2017

5chdn commented Oct 5, 2017

fidaaayoub commented Oct 5, 2017

5chdn commented Oct 5, 2017

fidaaayoub commented Oct 5, 2017 via email

fidaaayoub commented Oct 6, 2017

5chdn commented Oct 6, 2017

fidaaayoub commented Oct 6, 2017 via email

5chdn commented Oct 6, 2017 • edited Loading

fidaaayoub commented Oct 6, 2017 via email

fidaaayoub commented Oct 6, 2017 via email

fidaaayoub commented Oct 6, 2017 via email

fidaaayoub commented Oct 6, 2017 via email

fidaaayoub commented Oct 4, 2017 •

edited

Loading

5chdn commented Oct 6, 2017 •

edited

Loading