Bug 151394 - ntpdate shows no output, even with -v flag
ntpdate shows no output, even with -v flag
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: selinux-policy-targeted (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Depends On:
Blocks: 156322
  Show dependency treegraph
Reported: 2005-03-17 11:10 EST by Abel Lopez
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version: RHBA-2005-645
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-05 12:33:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:645 qe-ready SHIPPED_LIVE SELinux policy bug fix update 2005-10-05 00:00:00 EDT

  None (edit)
Description Abel Lopez 2005-03-17 11:10:40 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0

Description of problem:
Running ntpdate with the -v (verbose) flag, creates no output
date ; ntpdate -v -u pool.ntp.org ; date
Thu Mar 17 08:06:35 PST 2005
Thu Mar 17 08:06:35 PST 2005

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. run ntpdate -v [your.clock.here]


Actual Results:  running ntpdate from strace shows that is actually working, but running it from the shell shows nothing

Expected Results:  you should see
ntpdate -u pool.ntp.org
17 Mar 08:09:58 ntpdate[29184]: adjust time server offset 0.002957 sec

Additional info:
Comment 1 Rob Kearey 2005-03-29 04:47:29 EST
Reproduced here.

[root@trousers ~]# ntpdate -v -u ntp.internode.on.net
[root@trousers ~]#

service ntpd start silently fails too.
Comment 2 ptlee 2005-04-05 04:36:53 EDT
ditto. I don't see any output either.
Comment 3 Ian Petts 2005-04-12 00:22:00 EDT
Same here.

I also can't seem to get ntpd to synchronize to the server. I imagine it's the
same problem.
Comment 4 David Lehman 2005-04-26 16:09:33 EDT
FWIW, the output problem is caused by selinux policy. Reassigning...
Comment 5 Daniel Walsh 2005-04-27 07:52:57 EDT
Fixed in U1 policy.

Pre release available in 

Comment 8 Ian Petts 2005-05-03 00:34:00 EDT
Ignore the ntpd comment. I had a configuration error <sigh>.
Comment 13 Phil Mayers 2005-09-03 08:43:48 EDT
I still see the error (or rather; see nothing):

[root@monhost2 files]# rpm -q selinux-policy-targeted 

[root@monhost2 files]# ll -Z /usr/sbin/ntpdate
-rwxr-xr-x  root     root     system_u:object_r:ntpdate_exec_t /usr/sbin/ntpdate

[root@monhost2 files]# /usr/sbin/ntpdate -v
[root@monhost2 files]# strace /usr/sbin/ntpdate -v
getpid()                                = 23202
write(1, " 3 Sep 13:39:39 ntpdate[23202]: "..., 89) = 89
time(NULL)                              = 1125751179
write(2, " 3 Sep 13:39:39 ", 16)        = 16
write(2, "ntpdate[23202]: no servers can b"..., 48) = 48
munmap(0xb7fff000, 4096)                = 0
exit_group(1)                           = ?

[root@monhost2 files]# ll -Z /proc/self/fd
lrwx------  root     root                                      0 -> /dev/pts/0
lrwx------  root     root                                      1 -> /dev/pts/0
lrwx------  root     root                                      2 -> /dev/pts/0
lr-x------  root     root                                      3 -> /proc/23319/fd
[root@monhost2 files]# ll -Z /dev/pts/0
crw--w----  nsg      tty      root:object_r:devpts_t           /dev/pts/0

Comment 15 Red Hat Bugzilla 2005-10-05 12:33:54 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.