Bitcoin Forum
May 06, 2024, 12:31:02 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Warning: computer's date and time are incorrect!  (Read 2436 times)
Miner-TE (OP)
Hero Member
*****
Offline Offline

Activity: 499
Merit: 500



View Profile
September 11, 2013, 12:04:29 AM
 #1

Anyone else seeing the following warning? I've checked the system clock and synchronized with NTP.  System clock appears sane/valid.

My node is currently fully synced with the blockchain.

Warning: Please check that your computer's date and time are correct! If your clock is wrong Bitcoin will not work properly


BTC - 1PeMMYGn7xbZjUYeaWe9ct1VV6szLS1vkD - LTC - LbtcJRJJQQBjZuHr6Wm7vtB9RnnWtRNYpq
1714955462
Hero Member
*
Offline Offline

Posts: 1714955462

View Profile Personal Message (Offline)

Ignore
1714955462
Reply with quote  #2

1714955462
Report to moderator
1714955462
Hero Member
*
Offline Offline

Posts: 1714955462

View Profile Personal Message (Offline)

Ignore
1714955462
Reply with quote  #2

1714955462
Report to moderator
1714955462
Hero Member
*
Offline Offline

Posts: 1714955462

View Profile Personal Message (Offline)

Ignore
1714955462
Reply with quote  #2

1714955462
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714955462
Hero Member
*
Offline Offline

Posts: 1714955462

View Profile Personal Message (Offline)

Ignore
1714955462
Reply with quote  #2

1714955462
Report to moderator
1714955462
Hero Member
*
Offline Offline

Posts: 1714955462

View Profile Personal Message (Offline)

Ignore
1714955462
Reply with quote  #2

1714955462
Report to moderator
1714955462
Hero Member
*
Offline Offline

Posts: 1714955462

View Profile Personal Message (Offline)

Ignore
1714955462
Reply with quote  #2

1714955462
Report to moderator
will1982
Member
**
Offline Offline

Activity: 122
Merit: 10



View Profile
September 11, 2013, 12:55:50 AM
 #2

Are you using BitcoinQT?
theymos
Administrator
Legendary
*
Offline Offline

Activity: 5194
Merit: 12972


View Profile
September 11, 2013, 01:04:57 AM
 #3

How many connections do you have?

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
Miner-TE (OP)
Hero Member
*****
Offline Offline

Activity: 499
Merit: 500



View Profile
September 11, 2013, 02:42:03 AM
 #4

Bitcoin-QT V0.8.4-beta with 18 connection currently.  Seems the problem went away after the restart just now.

Earlier, at lunch, I restarted the PC and went back to work.  Didn't look too closely at Bitcoin-QT but I didn't see any warnings. Came home about 4 hrs later and the client was 2hrs behind in the blockchain and had the clock warning.  I checked the clock and sync'd with NTP just to be sure but it was correct.  The client at this time began catching up in the blockchain but still showed the warning message.  Closed/restarted QT and the warning remained.  I saw connections at this time.

Restarted the PC just after my post, then went to the store.  Returned and started QT....  Warning gone and all is back to normal.

I must have become disconnected from the bitcoin network but I was still connected to the internet. 

 
{
"version" : 80400,
"protocolversion" : 70001,
"walletversion" : 10500,
"blocks" : 257229,
"timeoffset" : 0,
"connections" : 18,
"proxy" : "",
"difficulty" : 86933017.77119441,
"testnet" : false,
"keypoololdest" : 1323652058,
"keypoolsize" : 100,
"paytxfee" : 0.00050000,
"unlocked_until" : 0,
"errors" : ""
}

BTC - 1PeMMYGn7xbZjUYeaWe9ct1VV6szLS1vkD - LTC - LbtcJRJJQQBjZuHr6Wm7vtB9RnnWtRNYpq
nomnomnom
Sr. Member
****
Offline Offline

Activity: 313
Merit: 250



View Profile
September 11, 2013, 07:45:17 PM
 #5

I got this too recently on my vps, after restarting bitcoind...
Restarting it another 2 or 3 times fixes it usually...

Not sure what is causing it, my vps is located in U.S. but I have
european timezone setup. Internal it probably uses UTC or unixseconds
anyway I think?

{
    "version" : 80400,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 257379,
    "timeoffset" : -3,
    "connections" : 93,
    "proxy" : "",
    "difficulty" : 86933017.77119441,
    "testnet" : false,
    "keypoololdest" : 1367298191,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""
}

$date
Wed Sep 11 21:44:41 CEST 2013
kneim
Legendary
*
Offline Offline

Activity: 1666
Merit: 1000


View Profile
September 11, 2013, 07:58:39 PM
 #6

On Unix also check with command "date -u". This should ouput the "Universal Time Zone (UTC)", equal to "Greenwitch Mean Time (GMT)".

On Unix system the local clock should be set to UTC (or GMT), it's better for administration.

gmaxwell
Staff
Legendary
*
Offline Offline

Activity: 4158
Merit: 8382



View Profile WWW
September 11, 2013, 08:26:00 PM
 #7

Can people please open up the debug console and run getpeerinfo  when the error first happens and paste the results here?
macbook-air
Sr. Member
****
Offline Offline

Activity: 324
Merit: 260


View Profile WWW
September 11, 2013, 10:20:28 PM
 #8

Can people please open up the debug console and run getpeerinfo  when the error first happens and paste the results here?

Code:
[
    {
        "addr" : "91.121.58.230:35696",
        "services" : "00000001",
        "lastsend" : 1378937840,
        "lastrecv" : 1378937840,
        "bytessent" : 697,
        "bytesrecv" : 534,
        "conntime" : 1378937720,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.99/",
        "inbound" : true,
        "startingheight" : 1,
        "banscore" : 0
    },
    {
        "addr" : "199.193.117.228:15681",
        "services" : "00000001",
        "lastsend" : 1378937840,
        "lastrecv" : 1378937840,
        "bytessent" : 395,
        "bytesrecv" : 342,
        "conntime" : 1378937720,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.99/",
        "inbound" : true,
        "startingheight" : 1,
        "banscore" : 0
    },
    {
        "addr" : "46.228.6.35:42682",
        "services" : "00000001",
        "lastsend" : 1378937840,
        "lastrecv" : 1378937840,
        "bytessent" : 395,
        "bytesrecv" : 342,
        "conntime" : 1378937720,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.99/",
        "inbound" : true,
        "startingheight" : 1,
        "banscore" : 0
    },
    {
        "addr" : "178.33.43.149:44082",
        "services" : "00000001",
        "lastsend" : 1378937850,
        "lastrecv" : 1378937850,
        "bytessent" : 450,
        "bytesrecv" : 342,
        "conntime" : 1378937720,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.99/",
        "inbound" : true,
        "startingheight" : 1,
        "banscore" : 0
    },
    {
        "addr" : "88.198.41.74:54638",
        "services" : "00000001",
        "lastsend" : 1378937846,
        "lastrecv" : 1378937846,
        "bytessent" : 505,
        "bytesrecv" : 342,
        "conntime" : 1378937720,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.99/",
        "inbound" : true,
        "startingheight" : 1,
        "banscore" : 0
    },
    {
        "addr" : "144.76.70.73:28727",
        "services" : "00000001",
        "lastsend" : 1378937850,
        "lastrecv" : 1378937850,
        "bytessent" : 505,
        "bytesrecv" : 342,
        "conntime" : 1378937720,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.99/",
        "inbound" : true,
        "startingheight" : 1,
        "banscore" : 0
    },
    {
        "addr" : "5.9.203.20:41235",
        "services" : "00000001",
        "lastsend" : 1378937840,
        "lastrecv" : 1378937840,
        "bytessent" : 395,
        "bytesrecv" : 342,
        "conntime" : 1378937720,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.99/",
        "inbound" : true,
        "startingheight" : 1,
        "banscore" : 0
    },
    {
        "addr" : "5.9.245.121:26373",
        "services" : "00000001",
        "lastsend" : 1378937850,
        "lastrecv" : 1378937850,
        "bytessent" : 590,
        "bytesrecv" : 342,
        "conntime" : 1378937720,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.99/",
        "inbound" : true,
        "startingheight" : 1,
        "banscore" : 0
    },
    {
        "addr" : "5.9.30.207:17827",
        "services" : "00000001",
        "lastsend" : 1378937840,
        "lastrecv" : 1378937840,
        "bytessent" : 395,
        "bytesrecv" : 342,
        "conntime" : 1378937720,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.99/",
        "inbound" : true,
        "startingheight" : 1,
        "banscore" : 0
    },
    {
        "addr" : "23.92.25.118:8333",
        "services" : "00000001",
        "lastsend" : 1378937857,
        "lastrecv" : 1378937850,
        "bytessent" : 10455,
        "bytesrecv" : 92643,
        "conntime" : 1378937720,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.3/",
        "inbound" : false,
        "startingheight" : 257401,
        "banscore" : 0,
        "syncnode" : true
    },
    {
        "addr" : "[2001:0:4137:9e76:102d:19b5:934b:b38f]:8333",
        "services" : "00000001",
        "lastsend" : 1378937857,
        "lastrecv" : 1378937857,
        "bytessent" : 9746,
        "bytesrecv" : 84911,
        "conntime" : 1378937724,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.1/",
        "inbound" : false,
        "startingheight" : 257401,
        "banscore" : 0
    },
    {
        "addr" : "[2001:41d0:1:646a::1]:8333",
        "services" : "00000001",
        "lastsend" : 1378937857,
        "lastrecv" : 1378937858,
        "bytessent" : 9182,
        "bytesrecv" : 83348,
        "conntime" : 1378937725,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.4/",
        "inbound" : false,
        "startingheight" : 257401,
        "banscore" : 0
    },
    {
        "addr" : "66.168.20.180:8333",
        "services" : "00000001",
        "lastsend" : 1378937853,
        "lastrecv" : 1378937857,
        "bytessent" : 9228,
        "bytesrecv" : 84200,
        "conntime" : 1378937725,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.3/",
        "inbound" : false,
        "startingheight" : 257401,
        "banscore" : 0
    },
    {
        "addr" : "[2001:470:8:42:4e72:b9ff:fe7b:8dbf]:8333",
        "services" : "00000001",
        "lastsend" : 1378937857,
        "lastrecv" : 1378937858,
        "bytessent" : 26949,
        "bytesrecv" : 77782,
        "conntime" : 1378937727,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.3/",
        "inbound" : false,
        "startingheight" : 257401,
        "banscore" : 0
    },
    {
        "addr" : "94.230.206.200:8333",
        "services" : "00000001",
        "lastsend" : 1378937857,
        "lastrecv" : 1378937852,
        "bytessent" : 650763,
        "bytesrecv" : 925124,
        "conntime" : 1378937733,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.1/",
        "inbound" : false,
        "startingheight" : 257401,
        "banscore" : 0
    },
    {
        "addr" : "24.156.59.38:8333",
        "services" : "00000001",
        "lastsend" : 1378937858,
        "lastrecv" : 1378937857,
        "bytessent" : 43061,
        "bytesrecv" : 78932,
        "conntime" : 1378937734,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.0/",
        "inbound" : false,
        "startingheight" : 257401,
        "banscore" : 0
    },
    {
        "addr" : "87.236.27.142:8333",
        "services" : "00000001",
        "lastsend" : 1378937857,
        "lastrecv" : 1378937855,
        "bytessent" : 270917,
        "bytesrecv" : 855036,
        "conntime" : 1378937771,
        "version" : 70001,
        "subver" : "/Satoshi:0.8.0/",
        "inbound" : false,
        "startingheight" : 257401,
        "banscore" : 0
    }
]

My clock is correct. getinfo reports timeoffset at -7 initially, now at -3. Kind of another attack?

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!