- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Clock change
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 12:26 AM
тАО04-04-2006 12:26 AM
Re: Clock change
Europe/London Sun Mar 26 00:59:59 2006 GMT = Sun Mar 26 00:59:59 2006 GMT isdst=0 gmtoff=0
Europe/London Sun Mar 26 01:00:00 2006 GMT = Sun Mar 26 02:00:00 2006 BST isdst=1 gmtoff=3600
Europe/London Sun Oct 29 00:59:59 2006 GMT = Sun Oct 29 01:59:59 2006 BST isdst=1 gmtoff=3600
Europe/London Sun Oct 29 01:00:00 2006 GMT = Sun Oct 29 01:00:00 2006 GMT isdst=0 gmtoff=0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 01:09 AM
тАО04-04-2006 01:09 AM
Re: Clock change
Since the system continued to say GMT rather than BST, it's clear that it didn't switch when it was supposed to. If you haven't manipulated the date or the timezone files recently, I'm at a loss to explain this.
If you have the freedom to do so, it would be interesting to set the time back to 26 Mar 00:55 (5 minutes before the scheduled change) and let the time advance normally to see if it changes properly.
Martin
A quick resolution to technical issues for your HPE products is just a click away HPE Support Center
See Self Help Post for more details
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 01:59 AM
тАО04-04-2006 01:59 AM
Re: Clock change
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 02:45 AM
тАО04-04-2006 02:45 AM
Re: Clock change
Mine can be configured to switch to BST (or other daylight saving time) and output this in the NTP stream.
Hence my questions about NTP config. However you say the NTP server is non-existant so that should not be a problem.
On TruCluster 1.6, I would have checked all cluster members had a consistent config for the localtime symlink. However I don't have experience of 5.1A clustering, if you have separate root filesystems on your cluster systems you ought to check this.
You should be able to use date, but I know you have to be carefull setting the clock back in time, as the system can get very confused.
Martin may be able to advise you better?
I have seen this clock jump issue before (about 3 years ago) but I cannot remember what the cause was, sorry.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 02:57 AM
тАО04-04-2006 02:57 AM
Re: Clock change
The safest way to reset the time would be during a period when you can have the production services down for an hour:
1. Shut down production services.
2. Wait at least one hour.
3. Set the time back. You may even want to drop to single-user mode to do this.
4. Restart services.
To answer Howard's question, the timezone files on a V5 cluster are in cluster_root, i.e., not member-specific. But this is worth a check. Please ensure that /etc/zoneinfo and none of the files under it are CDSL's. Something like:
ls -lR /etc/zoneinfo | grep '{'
Martin
A quick resolution to technical issues for your HPE products is just a click away HPE Support Center
See Self Help Post for more details
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 03:27 AM
тАО04-04-2006 03:27 AM
Re: Clock change
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 03:46 AM
тАО04-04-2006 03:46 AM
Re: Clock change
A quick resolution to technical issues for your HPE products is just a click away HPE Support Center
See Self Help Post for more details
- « Previous
-
- 1
- 2
- Next »