Topic: Warning: Please check that the computer's date and time... 0.8.2 Client - page 2. (Read 5528 times)
June 13, 2013, 04:35:04 PM
check the next line. If fMatch is false, then the warning triggers.
June 13, 2013, 11:51:06 AM
Code:
// If nobody has a time different than ours but within 5 minutes of ours, give a warning
bool fMatch = false;
BOOST_FOREACH(int64 nOffset, vSorted)
if (nOffset != 0 && abs64(nOffset) < 5 * 60)
fMatch = true;
Give a warning if the time offset is 0 ?
June 12, 2013, 05:42:38 PM
Have you tried manually synchronizing your time with window's time servers? If you fail to synchronize with windows time, it means there's an issue. In some cases, your computer time may appear to be correct, but your timezone is set incorrectly, resulting in incorrect time.
All good guesses. Checked the timezone is set correctly for Utah and it sync'd just fine to the server. Still have the message. I have a file synchronizer program I wrote a few years ago and if there was anything wrong with my systems date/time it would be barfing up 10 thousand files, but it is working fine. Maybe it's time I pulled in the bitcoin source and started becoming a power-user myself.
check the source for the warning: src/util.cpp
so either:
a) every peer you're connected to is trolling you
or
b) your system time isn't correct.
June 12, 2013, 04:23:30 PM
Have you tried manually synchronizing your time with window's time servers? If you fail to synchronize with windows time, it means there's an issue. In some cases, your computer time may appear to be correct, but your timezone is set incorrectly, resulting in incorrect time.
All good guesses. Checked the timezone is set correctly for Utah and it sync'd just fine to the server. Still have the message. I have a file synchronizer program I wrote a few years ago and if there was anything wrong with my systems date/time it would be barfing up 10 thousand files, but it is working fine. Maybe it's time I pulled in the bitcoin source and started becoming a power-user myself.
June 12, 2013, 04:05:32 PM
Have you tried manually synchronizing your time with window's time servers? If you fail to synchronize with windows time, it means there's an issue. In some cases, your computer time may appear to be correct, but your timezone is set incorrectly, resulting in incorrect time.
June 12, 2013, 09:23:37 AM
Yes, I did check the year. And I think it started the day after the power went out last Sunday. I've double checked the date and times on both my local DHCP router and my Internet modem. It doesn't appear to be stopping the program, but it is a mystery.
I had this warning on my linux client. It didn't cause any problems though and I think it disappeared after a while. Date was correct in my case too.
June 12, 2013, 08:13:57 AM
Yes, I did check the year. And I think it started the day after the power went out last Sunday. I've double checked the date and times on both my local DHCP router and my Internet modem. It doesn't appear to be stopping the program, but it is a mystery.
June 12, 2013, 12:52:29 AM
I hate to ask this, but have you double-checked that the year was correct?
June 11, 2013, 11:52:55 PM
Has it been there for a while?
June 11, 2013, 11:48:36 PM
I've checked that both my CMOS and Windows 7 date and time are correct, yet I have this warning plastered across my client. Any Ideas?
Jump to: