• Industry Solutions
    • Managed Service Providers
    • Enterprise Solutions
    • Developers & Startups
    • Healthcare
    • Trading and Financial
      • Chicago Managed Trading Servers
      • Trading and Financial Colocation: Chicago & New Jersey
    • IBM AS/400 and iSeries Users
  • Support
    • Register
    • View Tickets
    • Submit a Ticket
    • Knowledgebase
    • News
  • Steadfast Blog
  • Steadfast Podcasts
  • Contact Us
Home
  • Call Us
  • Call | 888.281.9449
  • Login
  • Search

This form logs you into your management portal account. To access your help desk account, click here and use the form to the right of the news.

  • Cloud Hosting
    • Cloud Hosting
    • Private Cloud
    • Hybrid Cloud
    • Public Cloud
    • Cloud Storage
      • Secure File Share
      • Wasabi Cloud Storage
    • Virtual Data Center Platform
  • Managed Hosting
    • Bare Metal Dedicated Servers
      • Deep Learning GPU Dedicated Servers
      • Linux Dedicated Servers
      • Windows Dedicated Servers
    • Virtual Private Servers
    • Data Center Colocation
      • Managed Colocation
      • Chicago: 350 E Cermak
      • Chicago: 725 S Wells
      • Edison, New Jersey
    • Security & Compliance
      • Managed Firewall
      • SSL VPN
      • DDoS Protection
      • Email Security
  • Backup & Disaster Recovery
    • Backup
    • Disaster Recovery
    • Veeam Backup & Replication
    • Veeam Cloud Connect
    • Wasabi Cloud Storage
  • Why Steadfast
    • Why Steadfast?
    • About Steadfast
      • Our History
      • News and Press
    • Data Centers & Network
      • Our Data Centers
      • Our Network
      • Network Test
      • Peering Policy
    • Customer Stories
    • Service Level Agreement
  • Industry Solutions
    • Managed Service Providers
    • Enterprise Solutions
    • Developers & Startups
    • Healthcare
    • Trading and Financial
      • Chicago Managed Trading Servers
      • Trading and Financial Colocation: Chicago & New Jersey
    • IBM AS/400 and iSeries Users
  • Support
    • Register
    • View Tickets
    • Submit a Ticket
    • Knowledgebase
    • News
  • Steadfast Blog
  • Steadfast Podcasts
  • Contact Us
Close
  • Support Home
  • Register
  • Submit a Ticket
  • Knowledgebase
  • News
 Login Subscribe

Log into the help desk to manage support tickets.


Lost password

Subscribe to general maintenance announcements and advisories.



 
 Knowledgebase
39Steadfast Cloud Platform 3Full Management 38Dedicated Servers & Colocation 4Control Panels 19Other
Search
Knowledgebase: Dedicated Servers & Colocation
My server's clock and time zone did not update on March 11th, 2007.
Posted by Kevin Stange, Last modified by Kevin Stange on 16 March 2007 09:33 PM
Due to recent changes in Daylight Savings Time laws in the United States, your server may require an update in order properly handle changing over to Daylight Savings Time. Please see the following tips for proper time zone updates for various server operating systems.

CentOS 3 and 4, Fedora Core 5 and 6

If you are running CentOS 3 or 4, or Fedora Core 5 or 6, you can run the following commands to fix your clock if it did not automatically update for the time change:

yum -y install tzdata system-config-date redhat-config-date
setup

Select "Timezone Configuration" and press Enter. Then, tab to the OK button and press Enter to reset the time zone. Finally, tab to the Quit button and press Enter. Run the following command to confirm the time zone is correct:

date

Your time zone should now show as CDT (for US Central Time) or whatever the appropriate time zone abbreviation is for your server's time zone. If the time zone is shown correctly but the clock is still wrong, run the following command (this will not work for a VPS):

rdate -s time-a.nist.gov

Fedora Core 1 - 4, Red Hat 9, Fedora Core 2 VPS Servers

If your server is running an older Fedora or Red Hat release, software updates are no longer being provided. The following directions will allow you to update your time zone data and correct your clock using files from newer Linux distributions.

For Fedora Core 2 - 4 (including Fedora Core 2 VPS servers), use these commands:

yum -y install rhpl htmlview
rpm -Uhv http://mirror.steadfast.net/fedora/core/updates/6/i386/tzdata-2007c-1.fc6.noarch.rpm http://mirror.steadfast.net/centos/4/os/i386/CentOS/RPMS/system-config-date-1.7.15-0.RHEL4.3.noarch.rpm
system-config-date

If you have Fedora Core 1 or Red Hat 9, you'll need these commands instead:

up2date rhpl htmlview
rpm -Uhv http://mirror.steadfast.net/fedora/core/updates/6/i386/tzdata-2007c-1.fc6.noarch.rpm http://mirror.steadfast.net/centos/3/os/i386/RedHPMS/redhat-config-date-1.5.22-3.noarch.rpm
redhat-config-date

Tab to the OK button and press Enter to reset the time zone. Run the following command to confirm the time zone is correct:

date

Your time zone should now show as CDT (for US Central Time) or whatever the appropriate time zone abbreviation is for your server's time zone. If the time zone is shown correctly but the clock is still wrong, run the following command (this will not work for a VPS):

rdate -s time-a.nist.gov

Debian and Ubuntu

You can run the following commands to fix your clock if it did not automatically update for the time change:

Note: If you are using Ubuntu, please remember to prefix each command with "sudo" and enter your "admin" user's password if prompted.

apt-get update tzdata
tzconfig

Follow these steps to complete the configuration with tzconfig:

  1. You will see your current time zone and be asked if you want to change it. Type "y" and press enter.
  2. At the next prompt, select the region. For standard US time zones, enter the number for "US time zones" or select a region that is more appropriate and enter that number, then press enter.
  3. You will now be given a list of possible zone names. Find one that matches the zone name or nearest city sharing the same time zone as you want to use. Make sure to enter the name exactly as it is shown, including any uppercase letters and underscores, then press enter.
  4. You will be shown the system time in the new time zone, as well as the time in UTC. Verify these are correct.

If the time zone is shown correctly but the clock is still wrong, run the following command:

rdate -s time-a.nist.gov

Windows Server 2003 and other Windows Platforms

If you are running Windows Server software on your system, please see the following Microsoft support page for assistance in ensuring your Microsoft products are capable of handling the transition properly:

http://support.microsoft.com/gp/cp_dst

Windows Server 2003 users can obtain the system clock update via Windows Update or by downloading the following updater:

http://www.microsoft.com/downloads/details.aspx?FamilyID=554a94fe-a478-47a7-b004-0277a292e90e&DisplayLang=en

Further Assistance

If you have any questions or need assistance, please feel free to submit a support ticket.

(298 vote(s))
Helpful
Not helpful

Comments (0)

I consent to allow Steadfast to process my data and agree to the Acceptable Use and Privacy Policies

  • 312.602.2689
  • ColoHouse Sales
  • Facebook
  • Twitter
  • YouTube
  • LinkedIn

Services

  • Cloud Hosting
  • Managed Hosting
  • Backup & Disaster Recovery

Solutions By Industry

  • Enterprise Solutions
  • Trading & Financial
  • Healthcare
  • Developers & Startups
© 2023 Steadfast
  • Log In
  • Site Map
  • Legal Info & Privacy Policy