NTPD – Segmentation fault

Kezdőlap Fórumok SOS! Bajban vagyok NTPD – Segmentation fault

1 / 1 bejegyzés megtekintése
  • Szerző
    Bejegyzés
  • #1880367
    admin
    Adminisztrátor

      ntpdate futtatása után ezt kapom:
      root@linux1:/# ntpdate clock.isc.org
      Looking for host clock.isc.org and service ntp
      host found : clock.isc.org
      10 Aug 16:09:12 ntpdate[26724]: adjust time server 204.152.184.72 offset -0.104676 sec
      root@linux1:/#

      Na eddig minden rendben.
      Ez után próbálom futtatni a ntpd daemon-t, de valamiért azonnal kilép. Ha a -d (debug) kapcsoló is be van kapcsolva, akkor ezt kapom:

      root@linux1:/# ntpd -d -c /etc/ntp.conf -l /var/log/ntp.log
      addto_syslog: logging to file /var/log/ntp.log
      ntpd 4.2.0@1.1161-r Mon Mar 29 22:23:49 PST 2004 (1)
      addto_syslog: logging to file /var/log/ntp.log

      addto_syslog: ntpd 4.2.0@1.1161-r Mon Mar 29 22:23:49 PST 2004 (1)

      addto_syslog: signal_no_reset: signal 13 had flags 4000000

      addto_syslog: precision = 2.000 usec

      create_sockets(123)
      addto_syslog: no IPv6 interfaces found

      bind() fd 3, family 2, port 123, addr 0.0.0.0, flags=8
      bind() fd 6, family 2, port 123, addr 192.168.64.3, flags=8
      bind() fd 7, family 2, port 123, addr 172.16.1.94, flags=8
      bind() fd 8, family 2, port 123, addr 127.0.0.1, flags=0
      init_io: maxactivefd 8
      local_clock: at 0 state 0
      Segmentation fault
      root@linux1:/#

      Na ez miért van? Az NTPD legújabb verzióját intallpkg csomagtelepítõvel raktam fel. Próbáltam forrásból is egy másikat, de az is ugyan ezt csinálja.

      A ntp.conf tartalma:

      root@linux1:/# cat /etc/ntp.conf
      # Sample /etc/ntp.conf: Configuration file for ntpd.
      #
      # Undisciplined Local Clock. This is a fake driver intended for backup
      # and when no outside source of synchronized time is available. The
      # default stratum is usually 3, but in this case we elect to use stratum
      # 0. Since the server line does not have the prefer keyword, this driver
      # is never used for synchronization, unless no other other
      # synchronization source is available. In case the local host is
      # controlled by some external source, such as an external oscillator or
      # another protocol, the prefer keyword would cause the local host to
      # disregard all other synchronization sources, unless the kernel
      # modifications are in use and declare an unsynchronized condition.
      #

      ##server 127.127.1.0 # local clock
      server clock.isc.org # time server
      server pool.ntp.org # time server

      ##fudge 127.127.1.0 stratum 10

      #
      # Drift file. Put this in a directory which the daemon can write to.
      # No symbolic links allowed, either, since the daemon updates the file
      # by creating a temporary in the same directory and then rename()’ing
      # it to the file.
      #
      driftfile /etc/ntp/drift
      logfile /var/log/ntpd.log
      multicastclient # listen on default 224.0.1.1
      broadcastdelay 0.008

      #
      # Keys file. If you want to diddle your server at run time, make a
      # keys file (mode 600 for sure) and define the key number to be
      # used for making requests.
      # PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote
      # systems might be able to reset your clock at will.
      #
      #keys /etc/ntp/keys
      #trustedkey 65535
      #requestkey 65535
      #controlkey 65535

      # Don’t serve time or stats or trust anyone else by default (more secure)
      restrict default noquery notrust nomodify
      # Trust ourselves. 🙂
      restrict 127.0.0.1
      root@linux1:/#

      A ntp.log tartalma:

      10 Aug 12:50:35 ntpd[30134]: logging to file /var/log/ntp.log
      10 Aug 12:50:35 ntpd[30134]: ntpd 4.2.0@1.1161-r Wed Aug 10 12:48:23 CEST 2005 (1)
      10 Aug 12:50:35 ntpd[30134]: signal_no_reset: signal 13 had flags 4000000
      10 Aug 12:50:35 ntpd[30134]: precision = 2.000 usec
      10 Aug 12:50:35 ntpd[30134]: no IPv6 interfaces found
      10 Aug 12:50:35 ntpd[30134]: kernel time sync status 0040
      10 Aug 12:54:52 ntpd[30764]: logging to file /var/log/ntp.log
      10 Aug 12:54:52 ntpd[30764]: ntpd 4.2.0@1.1161-r Wed Aug 10 12:48:23 CEST 2005 (1)
      10 Aug 12:54:52 ntpd[30764]: signal_no_reset: signal 13 had flags 4000000
      10 Aug 12:54:52 ntpd[30764]: precision = 2.000 usec
      10 Aug 12:54:52 ntpd[30764]: no IPv6 interfaces found
      10 Aug 12:54:52 ntpd[30764]: kernel time sync status 0040
      10 Aug 16:11:10 ntpd[26919]: logging to file /var/log/ntp.log
      10 Aug 16:11:10 ntpd[26919]: ntpd 4.2.0@1.1161-r Mon Mar 29 22:23:49 PST 2004 (1)
      10 Aug 16:11:10 ntpd[26919]: signal_no_reset: signal 13 had flags 4000000
      10 Aug 16:11:10 ntpd[26919]: precision = 2.000 usec
      10 Aug 16:11:10 ntpd[26919]: no IPv6 interfaces found
      10 Aug 16:11:10 ntpd[26919]: kernel time sync status 0040
      root@linux1:/var/log#

      Ha tudtok valami megoldást, akkor légyszi segítsetek. Az ntpd-nek azért kellene futnia, mert ez egy szerver gép lenne, és más gépek ettõl a géptõl kérdezgetnék le az idõt, ha futna a daemon. :blink:

    1 / 1 bejegyzés megtekintése
    • Be kell jelentkezni a hozzászóláshoz.