Highlighted
Absent Member.
Absent Member.
3756 views

Timesync and/or XNTPD time one hour behind console!

[NW6.5SP8]
Hi all,

I've got an issue where the time displayed by either timesync OR the xntpd logger screen is exactly one hour behind the time shown by "time" at the console prompt (which is correct).

Our NW6.5SP8 servers were changed from timesync to xntpd. No problems at the time - about a month ago.

Issue today with an NW6.5 SP8 box primarily used as a print server.


  • xntpd/timesync/the console all think they're in sync, no errors.
  • DS is happily synced.
  • It's using the same NTP sources (SLES10SP2) as other servers running a mix of timesync and xntpd.
  • App 1 (McAfee Netshield) has the same time as timesync/xntpd.
  • App2 (Moonwalk) has the same time as the console.
  • Prior to issue, server hex dumped, abend in apache.
  • Server came back up.


We had a similar issue on a different NW6.5SP8 box running GroupWise 7 where the following occurred:


  • Timesync was unloaded and xntpd was loaded.
  • timeserv.ncf was updated to load xntpd instead of timesync
  • Time all OK.
  • Later on (days) the server abended (backup s/w) and was booted.
  • Issue the same as above occurred - mail was being stamped 1hr behind - POA displayed wrong time, console was correct.
  • GW components stopped, config double-checked in GW, verified OK.
  • GW started up, same problem.
  • GW unloaded. Server reverted back to timesync from xntpd. Timesync one hour out. Console still OK.
  • GW load commands commented out in autoexec. Server rebooted gracefully.
  • Server comes up OK - time all OK
  • GW loaded - time OK.


The NTP sources (3 of them) are sound.

Does this mean that any time a server abends that it needs to be rebooted again after coming back up?!?
Am I missing something here?

Any suggestions appreciated!
Labels (1)
0 Likes
15 Replies
Highlighted
Absent Member.
Absent Member.

Re: Timesync and/or XNTPD time one hour behind console!

alexstuart wrote:

>
> [NW6.5SP8]
> Hi all,
>
> I've got an issue where the time displayed by either timesync OR the
> xntpd logger screen is exactly one hour behind the time shown by
> "time" at the console prompt (which is correct).
>
> Our NW6.5SP8 servers were changed from timesync to xntpd. No problems
> at the time - about a month ago.
>
> Issue today with an NW6.5 SP8 box primarily used as a print server.
>
>
> - xntpd/timesync/the console all think they're in sync, no errors.
> - DS is happily synced.
> - It's using the same NTP sources (SLES10SP2) as other servers
> running a mix of timesync and xntpd.
> - App 1 (McAfee Netshield) has the same time as timesync/xntpd.
> - App2 (Moonwalk) has the same time as the console.
> - Prior to issue, server hex dumped, abend in apache.
> - Server came back up.
>
>
> We had a similar issue on a different NW6.5SP8 box running GroupWise 7
> where the following occurred:
>
>
> - Timesync was unloaded and xntpd was loaded.
> - timeserv.ncf was updated to load xntpd instead of timesync
> - Time all OK.
> - Later on (days) the server abended (backup s/w) and was booted.
> - Issue the same as above occurred - mail was being stamped 1hr
> behind - POA displayed wrong time, console was correct.
> - GW components stopped, config double-checked in GW, verified OK.
> - GW started up, same problem.
> - GW unloaded. Server reverted back to timesync from xntpd. Timesync
> one hour out. Console still OK.
> - GW load commands commented out in autoexec. Server rebooted
> gracefully.
> - Server comes up OK - time all OK
> - GW loaded - time OK.
>
>
> The NTP sources (3 of them) are sound.
>
> Does this mean that any time a server abends that it needs to be
> rebooted again after coming back up?!?
> Am I missing something here?
>
> Any suggestions appreciated!


Take a look at my cooltool page and ensure all settings are correct:

http://www.novell.com/coolsolutions/feature/17968.html


Also, check you server monitor console setting for time parameters and
ensure they are showing the correct settings. Mine are as follows for
California:

------------------------------------------------------------------------
Time Parameters
------------------------------------------------------------------------
Start Of Daylight Savings Time (MARCH SUNDAY SECOND 2:00 AM)
End Of Daylight Savings Time (NOVEMBER SUNDAY FIRST 2:00 AM)
Daylight Savings Time Offset +1:00:00
Time Zone PST8PDT





--

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Timesync and/or XNTPD time one hour behind console!

Thanks for that info Chris - impressive checklist!

I've done all of that, save for the fixntp.ncf part. I'll give it a bash when it happens again.

Funny thing is that at around 9pm that night, xntpd skipped 9pm and when straight to 10pm! The apps didn't work it out without a restart of them, but something weird nonetheless.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Timesync and/or XNTPD time one hour behind console!

I'd try reducing your 3 NTP sources to one. It gets confused if there is even the slightest difference between multiple sources.

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Timesync and/or XNTPD time one hour behind console!

Just had another server abend.

When it came up the story was the same - xntpd was 1 hr behind. Restarted the server gracefully, no joy.

Tried unload xntpd and doing ntpdate - no joy.

Tried reducing ntp sources to one, no joy.

Grrrrr.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Timesync and/or XNTPD time one hour behind console!

Try copying the XNTPD.NLM from a different server to the one that
abends(Backup the old one first.) and reload. Wait to see if the
problem returns.



--

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Timesync and/or XNTPD time one hour behind console!

Also, does the abending server have any cron jobs running???? Could
that be causing the issue??



--

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Timesync and/or XNTPD time one hour behind console!

Sorry, my last post wasn't clear.

I had different server abend, not another "server abend", sorry for the confusion.

The problem doesn't seem to be related to boxes that abend. We had a power outage at a remote site resulting in a graceful shutdown. When we looked at the server this morning dhcpsrvr was trying to load after pdhcp which left dhcpsrvr prompting for a 'press any key...'. Anyway, since this stopped other modules loading properly we gracefully rebooted the box and when it came up XNTPD was an hour behind!

So, even when it goes down 'nicely' it still comes up 'crappy'.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Timesync and/or XNTPD time one hour behind console!

And there's no CRON jobs running.

Here's our ntp.conf file:

**********************************
# Server settings
#
server 10.248.X.X prefer #Time Server 1
server 10.248.X.Y #Time Server 2
server 10.21.Z.Z #Time Server 3


server 127.127.1.0 #Local clock
fudge 127.127.1.0 stratum 15

driftfile sys:\system\drift.ntp
logfile sys:\system\ntp.log
logconfig =syncstatus +sysevents
**********************************

Logging works OK.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Timesync and/or XNTPD time one hour behind console!

Try this. On all Time Consumer Servers (in my network this is all
servers except one [the Time Provider]), configure the NTP.CONF file as
follows:

NTP.CONF
**************************************************************
# Local Clock used as Time Provider - Self Synchronized Mode
# server 127.127.1.0
# fudge 127.127.1.0 stratum 3

# Time Provider
# This would be the Time Provider Server in your Network
# In my network all other server point to it.
server IP_Address_of_TimeProvider prefer

#
# Monitoring/Logging Options
driftfile sys:\system\drift.ntp
*************************************************************


Now, for your Time Provider, configure the NTP.CONF file as follows:

NTP.CONF
**************************************************************
# Local Clock used as Time Provider - Self Synchronized Mode
server 127.127.1.0
# fudge 127.127.1.0 stratum 3

# Time Provider
# This would be the Time Provider Server from "time.nist.gov"
# I use "server 192.43.244.18 prefer" and "server 137.65.1.100 prefer"
server IP_Address_of_TimeProvider prefer

# Step the time to the source clock for slewing
stepclock

#
# Monitoring/Logging Options
driftfile sys:\system\drift.ntp
*************************************************************

Let this run for a while and see if you still get the abends.


--

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Timesync and/or XNTPD time one hour behind console!

The servers don't seem to be abending in xntpd. It doesn't seem to matter if the server abended or went down nicely.

In the attached jpg, the server had been rebooted and showed the issue of xntpd being an hour behind.

If you look closely at the log you'll notice that 1am has been skipped and it's now correct.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Timesync and/or XNTPD time one hour behind console!

alexstuart wrote:

>
> The servers don't seem to be abending in xntpd. It doesn't seem to
> matter if the server abended or went down nicely.
>
> In the attached jpg, the server had been rebooted and showed the issue
> of xntpd being an hour behind.
>
> If you look closely at the log you'll notice that 1am has been skipped
> and it's now correct.
>
>
> +---------------------------------------------------------------------
> -+
> > Filename: xnptd (Small).JPG
> > | Download:
> > http://forums.novell.com/attachment.php?attachmentid=2502 |

> +---------------------------------------------------------------------
> -+


Did you change all the NTP.CONF files as recommended? That way we can
pair down problems. How many servers does your environment have? All
my servers are pointing to one Time-provider (internal to my network).
That server is the one pointing out to the "Internent Time Providers".

In other words, all my servers NTP.CONF files are the same, except the
Time-provider. It is different in that it points out-bound.

--

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.