What is the output of ntpq -p ?
--
ntpd doesn't work - time is not synchronized
https://bugs.launchpad.net/bugs/238805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
I started again ntp (because I disabled it to run ntpdate by hand just
now) and then the output is:
after minute or so
[EMAIL PROTECTED]:~# ntpq -p
remote refid st t when poll reach delay offset jitter
==
I believe this is a duplicate of ticket #104091
--
ntpd doesn't work - time is not synchronized
https://bugs.launchpad.net/bugs/238805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can wo
Important information is missing here. This Linux machine was running
under VMware. Such configuration needs extra parameter to kernel to keep
correct time.
More detail can be found here, for example.
http://communities.vmware.com/message/776326
http://support.ntp.org/bin/view/Support/VMWareNTP
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
ntpd doesn't work - time is not synchronized
https://bugs.launchpad.net/bugs/238805
You received this bug notification because you
Closing again per last comment.
** Changed in: ntp (Ubuntu)
Status: Incomplete => Invalid
--
ntpd doesn't work - time is not synchronized
https://bugs.launchpad.net/bugs/238805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
To clarify:
1. yes, ntpd was running (ps aux)
2. yes, the time drifts slowly away from real tim
3. yes, I have ntp servers configured (the default) /etc/ntp.conf
server ntp.ubuntu.com
server pool.ntp.org
4. no, I dont have no strange special settings or nothing like that
5. I was testing it f
Perhaps it is a problem with adjtime() ?
also ntpdate also fails to synchronize the time if offset if less then 0.5
second - so when it uses adjtime()
but works fine for biggest drifts, when settimeofday() is used (according to
man ntpdate)
perhaps ntpd tries to use adjtime() and thats why it
I dont think this has anything to do with #104091, but #114
Initially on system boot ntpd fails to start properly and comes up to
early. Immediately after boot ntpq -p shows no assoc IDs, then when you
do /etc/init.d/ntp restart everything is fine - which is why the above
behaviour has occured.
oops that first ID should be #114505.
There is an additional problem here in that /etc/init.d/ntp doesnt call
ntpdate-debian during start/restart so therefore if your server is > min
drift which stops auto sync you are left having to fix ntpdate by hand
(ntpdate-debian is a better way than simply
** Changed in: ntp (Ubuntu)
Status: Invalid => New
--
ntpd doesn't work - time is not synchronized
https://bugs.launchpad.net/bugs/238805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I just reopened the bug. It is affecting me too. I am running 64 bit
Karmic Koala up to date. This computer is always on. It has continuous
access to the internet and is not a virtual machine.
> sudo /etc/init.d/ntp status
* NTP server is running.
> grep ^server /etc/ntp.conf
server ntp.ubuntu.c
ntpd won't reset the clock if the time difference is above 0.5s (or
something of this order). I'd suggest to first adjust your time
manually, then run ntpd.
** Changed in: ntp (Ubuntu)
Status: New => Incomplete
--
ntpd doesn't work - time is not synchronized
https://bugs.launchpad.net/bug
Ok, but then the question is. How/why did this happen? Did ntpdate not
get called when I first installed package ntp? (Years ago), and my clock
has been always out of sync and drifting I did just notice? (possible)
or did the clock get out of sync when I turned off the machine for a
couple of weeks
Ok, after further research, it seems that ntp really is not working on my
system:
ntpdate returns "no server suitable for synchronization found" every time
regardless of what server I point it too, and ntpq -p does not have star next
to any server and reach, delay, offset, and jitter all show 0.
Never mind... Our firewall seems to block the ntp port. Synchronizing
with an internal server makes both ntp and ntddate work. Sorry for the
confusion.
--
ntpd doesn't work - time is not synchronized
https://bugs.launchpad.net/bugs/238805
You received this bug notification because you are a membe
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
18 matches
Mail list logo
