On Friday 18 November 2005 23:22, Catalin Muresan wrote:
> ok, superb, serverul nu raspunde, continua cu tcpdump pe server, sa
> vezi acolo ce apare.
>
Da la o concluzie similara am ajuns si eu. Aici, din sapaturile facute pot fi
citeva cauze:
1. selinux (pe care l-am dezactivat definitiv si irevocabil).
# cat /etc/selinux/
SELINUX=disabled
SELINUXTYPE=targeted
2. serverul meu de timp (10.0.0.2) NU ESTE SINCRONIZAT cu cel de la care e pus
sa-si ia ora (in cazul meu am 3 servere externe stratum 1)...
# ntpq
ntpq> pe
remote refid st t when poll reach delay offset jitter
==============================================================================
*ntp1.usv.ro .GPS. 1 u 1004 1024 377 25.609 16.167 0.960
+ntp1.nl.net .GPS. 1 u 995 1024 377 118.662 9.215 23.668
+ntp1-rz.rrze.un .DCFp. 1 u 1001 1024 377 87.927 -10.880 0.114
LOCAL(0) LOCAL(0) 10 l 33 64 377 0.000 0.000 0.001
ntpq> rv
assID=0 status=0644 leap_none, sync_ntp, 4 events, event_peer/strat_chg,
version="ntpd [EMAIL PROTECTED] Mon Feb 21 17:54:52 GMT 2005 (1)"?,
processor="i686", system="Linux/2.6.9-22.0.1.ELsmp", leap=00, stratum=2,
precision=-20, rootdelay=25.609, rootdispersion=72.023, peer=27052,
refid=80.96.120.253,
reftime=c729ad7b.ff84230f Sat, Nov 19 2005 15:56:11.998, poll=10,
clock=0xc729b169.fc1fd9ba, state=4, offset=2.457, frequency=151.075,
noise=2.191, jitter=23.846, stability=9.858
ntpq> as
ind assID status conf reach auth condition last_event cnt
===========================================================
1 27052 9614 yes yes none sys.peer reachable 1
2 27053 9414 yes yes none candidat reachable 1
3 27054 9414 yes yes none candidat reachable 1
4 27055 9014 yes yes none reject reachable 1
ntpq>
Din ce vad eu aici, se pare totusi ca sunt sincronizat cu ntp1.usv.ro! Asta nu
ar fi de ajuns?
3. inca o setare prea restrictiva in /etc/ntp.conf pe serverul meu de timp
(10.0.0.2)!
# cat /etc/ntp.conf
server ntp1.usv.ro #stratum 1
server ntp1.nl.net #stratum 1
server ntp1.fau.de #stratum 1
restrict default nomodify notrap noquery
restrict 10.0.0.0 mask 255.255.0.0 notrust nomodify notrap
restrict 127.0.0.1
server 127.127.1.0
fudge 127.127.1.0 stratum 10
driftfile /var/lib/ntp/drift
broadcastdelay 0.008
keys /etc/ntp/keys
Vedeti ceva ciudat?
Iata un tcpdump pe serverul de timp (10.0.0.2) in timp ce clientul (10.0.0.19)
facea ntpdate -u 10.0.0.2. Vad ca spune: Client ... clock unsynchronized
(192)!
# tcpdump -v -ni eth1 udp port 123
16:02:13.008150 IP (tos 0x0, ttl 64, id 3, offset 0, flags [DF], proto 17,
length: 76) 10.0.0.19.51595 > 10.0.0.2.ntp: NTPv4, length 48
Client, Leap indicator: clock unsynchronized (192), Stratum 0, poll
4s, precision -6
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Root Delay: 1.000000, Root dispersion: 1.000000, Reference-ID:
(unspec)
Reference Timestamp: 0.000000000
Originator Timestamp: 0.000000000
Receive Timestamp: 0.000000000
Transmit Timestamp: 3341397753.047144999 (2005/11/19 16:02:33)
Originator - Receive Timestamp: 0.000000000
Originator - Transmit Timestamp: 3341397753.047144999 (2005/11/19
16:02:33)
pe client (10.0.0.19) am dat un ntpdate -ud -U ntp 10.0.0.2 si primesc
raspunsul:
Looking for host 10.0.0.2 and service ntp
host found : 10.0.0.2
transmit(10.0.0.2)
transmit(10.0.0.2)
transmit(10.0.0.2)
transmit(10.0.0.2)
transmit(10.0.0.2)
10.0.0.2: Server dropped: no data
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
server 10.0.0.2, port 123
stratum 0, precision 0, leap 00, trust 000
refid [10.0.0.2], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time: 00000000.00000000 Thu, Feb 7 2036 8:28:16.000
originate timestamp: 00000000.00000000 Thu, Feb 7 2036 8:28:16.000
transmit timestamp: c729aef9.0c11b1d9 Sat, Nov 19 2005 16:02:33.047
filter delay: 0.00000 0.00000 0.00000 0.00000
0.00000 0.00000 0.00000 0.00000
filter offset: 0.000000 0.000000 0.000000 0.000000
0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000
19 Nov 16:02:34 ntpdate[14086]: no server suitable for synchronization found
[EMAIL PROTECTED] ~]#
Din ce vad eu cu tcpdump pe server, pare sa fie ipoteza 2 (serverul meu de
timp INCA nu este SINCRONIZAT cu cel external) dar nu sunt sigur si tot nu
stiu care e problema ....
Alex
_______________________________________________
RLUG mailing list
[email protected]
http://lists.lug.ro/mailman/listinfo/rlug
