Skip to content
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

Time-date does not reliably update on headnode #14

Closed
GoogleCodeExporter opened this issue Apr 29, 2015 · 3 comments
Closed

Time-date does not reliably update on headnode #14

GoogleCodeExporter opened this issue Apr 29, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

Not sure how to reproduce, but sometimes the date sits in 1970 forever on Mt. 
View HN.  must test with new build of headnode

Original issue reported on code.google.com by berko...@gmail.com on 8 Feb 2011 at 8:53

@GoogleCodeExporter
Copy link
Author

This seems like a timing issue. If it takes a while for the headnode to get net 
on boot then the process fails.  I believe it will try again later, but it 
takes a long time.  Maybe there's an interval setting somewhere?

Original comment by berko...@gmail.com on 16 Feb 2011 at 4:40

@GoogleCodeExporter
Copy link
Author

Issue 5 has been merged into this issue.

Original comment by berko...@gmail.com on 28 Feb 2011 at 12:44

@GoogleCodeExporter
Copy link
Author

The 1970 bug was an issue in /etc/fabfi-scripts/logstatus where the ln7 should 
be:

if (test "2010" -gt `date +"%Y"`)

This is fixed in r266, however there is a lot more brokenness in time syncing 
in OpenWRT that we're just working around with a sledgehammer.  As of this 
revision, updating to r25818 and will test if these issues are fixed.  

Original comment by berko...@gmail.com on 1 Mar 2011 at 7:04

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant