NTPDATE - Help please

[BiancaP.]

Bad news...=/

[root@lab2 /]# ifdown eth1
[root@lab2 /]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1C:C4:68:42:54
inet addr:172.27.109.43 Bcast:172.27.109.255 Mask:255.255.255.0
inet6 addr: fe80::21c:c4ff:fe68:4254/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1079269 errors:0 dropped:0 overruns:0 frame:0
TX packets:8156804 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:115892461 (110.5 MiB) TX bytes:530162668 (505.6 MiB)
Interrupt:169 Memory:f8000000-f8012100

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:5856 errors:0 dropped:0 overruns:0 frame:0
TX packets:5856 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7835880 (7.4 MiB) TX bytes:7835880 (7.4 MiB)



[root@lab2 /]# service ntpd stop
[root@lab2 /]# ntpdate 172.27.109.56
[root@lab2 /]#
[root@lab2 /]# date
Sat May 17 18:43:17 BRT 2008
[root@lab2 /]#
[root@lab2 /]# service ntpd start

[BiancaP.]

I am trying to configure remote....
I enter direct in the server and i get this message:

[root@lab1~]ntpdate 172.27.109.56
audit(1214373854.865:437): avc: denied { read } for pid=25149 comm= "ntpdate"
name="services"dev=cciss/c0d0p3 ino=1998855 scontext=root:system_r:ntpd_t tcontext=root:object_r:tmp_t tclass=file

but i can ping:

PING 172.27.109.56 (172.27.109.56) 56(84) bytes of data.
64 bytes from 172.27.109.56: icmp_seq=0 ttl=64 time=1.34 ms
64 bytes from 172.27.109.56: icmp_seq=1 ttl=64 time=0.596 ms
64 bytes from 172.27.109.56: icmp_seq=2 ttl=64 time=0.558 ms

--- 172.27.109.56 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 0.558/0.833/1.345/0.362 ms, pipe 2

[BiancaP.]

My friend help me....
the solution:

vi /etc/selinux/config

SELINUX=disabled (before was enforcing)


thanks for all !!!

[Court Campbell]

Well, I think disabling eth1 helped. I say this because you got different errors before that seemed network related. After that you started getting the errors with avc in them. Anytime you see avc in logs, etc you should think selinux. Anyway, glad it;s working.