01-16-2012
Thanks for sharing your story. It's very true that most of the times we do not bother to check the time of the clock before scheduling stuffs.
We maintain IT infrastructure for a big pharma company. For any SLA (service level agreement) breach, my employer has to pay a real big amount of money to the client. Now that's been told, once my colleague had to schedule a maintenance on an AIX server. We have a procedure to do that. There's a lot of approvals from service delivery managers of both the client and our company required. After getting those, this guy went on scheduling the reboot of the machine in maintenance mode in cron a day before. The next day, I got a call from IT Incident management people saying a server is down before it's scheduled maintenance window. It happened around 20 minutes before the scheduled time. We had to raise a severity for this. Upon checking the root cause of this later, we found somehow the server was failing to sync with the NTP server and the clock was going 20 minutes faster than the actual time.
And yes, because of all these, we breached the SLA!
This User Gave Thanks to admin_xor For This Post:
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
can anybody tel lme,how to instal NTS -150 on a unix network,it needs some patch to fetch time frm serve,,?? (2 Replies)
Discussion started by: pesty
2 Replies
2. Shell Programming and Scripting
Is there anyway to get the start time and end time / status of a crontab job which was just completed? Of course, we know the start time of the crontab job since we are scheduling. But I would like to know process start and time recorded somewhere or can be fetched from a command like 'ps'. ... (3 Replies)
Discussion started by: thambi
3 Replies
3. Shell Programming and Scripting
Hi guys,
I know that this topic has been discuss numerous times, and I have search the net and this forum for it.
However, non able to address the problem I faced so far.
I am on Solaris Platform and unable to install additional packages like the GNU date and gawk to make use of their... (5 Replies)
Discussion started by: DrivesMeCrazy
5 Replies
4. Shell Programming and Scripting
Hello All,
I have a problem calculating the time difference between start and end timings...!
the timings are given by 24hr format..
Start Date : 08/05/10 12:55
End Date : 08/09/10 06:50
above values are in mm/dd/yy hh:mm format.
Now the thing is, 7th(08/07/10) and... (16 Replies)
Discussion started by: smarty86
16 Replies
5. Solaris
I have a cluster of two Solaris server (veritas cluster). one working and the other is standby
I am going to change the date on them , and am looking for a secure solution as it is giving an important service.
my opinion is that the active one doesn't need to be restarted (if I don't change the... (1 Reply)
Discussion started by: barry1946
1 Replies
6. Shell Programming and Scripting
Hi guys thanks for the help for my previous posts.Now i have a requirement that i download a XMl file which has UTC time stamp.I need to convert UTC time into Unix server timezone.
For ex if the time zone of unix server is CDT then i need to convert into CDT.whatever may be the system time... (5 Replies)
Discussion started by: mohanalakshmi
5 Replies
7. Programming
Dear all,
I am kindly seeking assistance on the following issue.
I am working with data that is sampled every 0.05 hours (that is 3 minutes intervals) here is a sample data from the file
5.00000 15.5030
5.05000 15.6680
5.10000 16.0100
5.15000 16.3450
5.20000 16.7120
5.25000... (4 Replies)
Discussion started by: malandisa
4 Replies
8. Shell Programming and Scripting
Hi All,
I have one file which contains time for request and response.
I want to calculate time difference in milliseconds for each line.
This file can contain 10K lines.
Sample file with 4 lines.
for first line.
Request Time: 15:23:45,255
Response Time: 15:23:45,258
Time diff... (6 Replies)
Discussion started by: Raza Ali
6 Replies
LEARN ABOUT ULTRIX
ntp.conf
ntp.conf(5) File Formats Manual ntp.conf(5)
Name
ntp.conf - Network Time Protocol configuration file
Description
The file is the configuration file for the Network Time Protocol (NTP) daemon, This file must be configured on your system before running
Any host names that you specify in the file must have an entry in the file, or an entry in the master database, if the database is being
served to your system by BIND/Hesiod or Yellow Pages.
The file has four entry formats:
trusting no
This entry guarantees that your system synchronizes only to the NTP servers identified in the peer and server entries specified. Dig-
ital recommends that all systems include the entry.
peer server
This entry identifies server as one of the NTP servers that your system trusts, and from which your system will accept time synchro-
nization. Your system may also provide time synchronization to this server. Servers can be identified by host name or internet
address.
NTP servers should be configured with entries.
server server
This entry identifies server as one of the NTP servers that your system trusts, and from which your system will accept time synchro-
nization. Your system can not provide time synchronization to this server. Servers can be identified by host name or internet
address.
NTP clients should be configured with entries.
peer /dev/null LOCL 1 -5 local
This entry identifies your system as a local reference clock. A local reference clock is the most accurate system clock available at
your site. If you receive time synchronization from the Internet NTP service, you should not include this entry on any of your sys-
tems. At most, one system in a set of nodes running should be identified as a local reference clock.
A host which specifies this entry should not specify any or entries.
Examples
This is a sample configuration file for an NTP client which receives time synchronization from the NTP servers: and Lines beginning with a
number sign (#) are comments.
#
# NTP Configuration File
# This file is mandatory for the ntpd daemon
#
#
#
# ** A L L **
#
# "trusting no" prevents this host from synchronizing
# to any host that is not listed below. It is recommended
# that all hosts include the line "trusting no".
#
trusting no
#
#
# ** S E R V E R **
#
# If you are configuring a server, use "peer" entries to
# synchronize to other NTP servers. For example, server1,
# server2, and server3.
#
#peer server1
#peer server2
#peer server3
#
#
#
#
# ** C L I E N T **
#
# If you are configuring a client, use "server" entries to
# synchronize to NTP servers. For example, server1, server2,
# and server3.
#
server server1
server server2
server server3
#
#
#
# ** L O C A L R E F E R E N C E C L O C K **
#
# If you are configuring a local reference clock, include the
# following entry and the "trusting no" entry ONLY.
#
#peer /dev/null LOCL 1 -5 local
#
See Also
ntp(1), ntpd(8), ntpdc(8)
RFC 1129--Internet time synchronization: The Network Time Protocol
Introduction to Networking and Distributed System Services
ntp.conf(5)