Bitcoin Forum
May 13, 2024, 10:10:49 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Date issue with Primecoin HP client  (Read 746 times)
MadMao (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
November 27, 2013, 11:34:14 PM
 #1

Hi guys,

I've built from source the last version of High Performance Primecoin miner and now I'm trying to use it on a VPS.

The trouble is that the program won't synchronize. Instead, block count stalls in a low number and I have this error: "Warning: Please check that your computer's date and time are correct! If your clock is wrong Primecoin will not work properly.". I checked the date and it is fine, the time is OK too, except for time zone differences. I'm not sure if this warning is stopping the client from syncing but in other machines when the client could not connect to the server I would get a error saying so.

I'm using Ubuntu 12.04.

Does anybody have a clue?

Thanks!

Mao
"The nature of Bitcoin is such that once version 0.1 was released, the core design was set in stone for the rest of its lifetime." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715595049
Hero Member
*
Offline Offline

Posts: 1715595049

View Profile Personal Message (Offline)

Ignore
1715595049
Reply with quote  #2

1715595049
Report to moderator
1715595049
Hero Member
*
Offline Offline

Posts: 1715595049

View Profile Personal Message (Offline)

Ignore
1715595049
Reply with quote  #2

1715595049
Report to moderator
1715595049
Hero Member
*
Offline Offline

Posts: 1715595049

View Profile Personal Message (Offline)

Ignore
1715595049
Reply with quote  #2

1715595049
Report to moderator
MadMao (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
December 04, 2013, 05:49:22 PM
 #2

Just a heads up.

It said it was an issue with the time so it was a problem with... time!

I got a bit confused about timezones and stuff, but was able to understand the problem. The server was indeed late, about 7 hours. It's not possible to change a VPS time, so I had to talk with support.

If you have the same issue you can use "date +%s" command to check the seconds elapsed since the Epoch. After this you just have to execute the same command in another box and compare the result. If the difference is too big (more or less on the fourth more significant digit) you will have to adjust time.

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!