Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #196791 > unrolled thread

Ntp not working

Back to article view | Back to linux.debian.user

Contents

  Ntp not working David Baron <dbaron770@gmail.com> - 2018-06-20 09:10 +0200
    Re: Ntp not working David Baron <dbaron770@gmail.com> - 2018-06-20 11:30 +0200
      Re: Ntp not working Mike <debian@norgie.net> - 2018-06-20 11:50 +0200
        Re: Ntp not working Mike <debian@norgie.net> - 2018-06-20 16:40 +0200
          Re: Ntp not working David Baron <dbaron770@gmail.com> - 2018-06-21 09:10 +0200
            Re: Ntp not working Mike <debian@norgie.net> - 2018-06-22 14:50 +0200
              Re: Ntp not working David Baron <dbaron770@gmail.com> - 2018-06-23 21:10 +0200

#196791 — Ntp not working

[Multipart message — attachments visible in raw view] — view raw

Cannot find valid servers. I have the conf and hosts files from the
distro.(Sid)

Fix?

[toc] | [next] | [standalone]

#196796

[Multipart message — attachments visible in raw view] — view raw

On Wed, Jun 20, 2018, 12:01 PM Alexandre GRIVEAUX <agriveaux@deutnet.info>
wrote:

> Hello,
>
> > Cannot find valid servers. I have the conf and hosts files from the
> > distro.(Sid)
>
> Can you show the config file because not all have machine running SID
> or show ntpq -p ?
>
> > Fix?
>
>
>
> Ntpq -p yields "Connection refused"

[toc] | [prev] | [next] | [standalone]

#196797

[Multipart message — attachments visible in raw view] — view raw

On Wed, Jun 20, 2018 at 12:22:38PM +0300, David Baron wrote:
> > Hello,
> >
> > > Cannot find valid servers. I have the conf and hosts files from the
> > > distro.(Sid)
> >
> > Can you show the config file because not all have machine running SID
> > or show ntpq -p ?
> >
> > > Fix?
> >
> > Ntpq -p yields "Connection refused"
> 
>

Can you provide the npt.conf please?

ntp -p will yield connection refused if ntpd is not running.

There should be some lines begining "pool" or "server" in ntp.conf.  Can
you ping them?  If so, do you have a firewall that might be blocking
UDP/123?

Mike. 

[toc] | [prev] | [next] | [standalone]

#196799

[Multipart message — attachments visible in raw view] — view raw

On Wed, Jun 20, 2018 at 04:50:34PM +0300, David Baron wrote:
> Attached ntp.conf
> Attached service.text
> 

OK, so your NTP servers are:

pool 0.debian.pool.ntp.org iburst
pool 1.debian.pool.ntp.org iburst
pool 2.debian.pool.ntp.org iburst
pool 3.debian.pool.ntp.org iburst

What happens if you do:

ping 0.debian.pool.ntp.org

?

Most likely you are blocking UDP/123.  However, if you fail to resolve
the IP when you ping it, you have a DNS issue.

Mike.

[toc] | [prev] | [next] | [standalone]

#196830

[Multipart message — attachments visible in raw view] — view raw

On Wed, Jun 20, 2018, 5:33 PM Mike <debian@norgie.net> wrote:

> On Wed, Jun 20, 2018 at 04:50:34PM +0300, David Baron wrote:
> > Attached ntp.conf
> > Attached service.text
> >
>
> OK, so your NTP servers are:
>
> pool 0.debian.pool.ntp.org iburst
> pool 1.debian.pool.ntp.org iburst
> pool 2.debian.pool.ntp.org iburst
> pool 3.debian.pool.ntp.org iburst
>
> What happens if you do:
>
> ping 0.debian.pool.ntp.org
>
> ?
>
> Most likely you are blocking UDP/123.  However, if you fail to resolve
> the IP when you ping it, you have a DNS issue.
>
> Mike.
>

123 udp allowed both ways.
The destination is resolved do dns ok.
Ping still fails, unreachable,sendmsg operation not permitted.

>

[toc] | [prev] | [next] | [standalone]

#196857

[Multipart message — attachments visible in raw view] — view raw

On Thu, Jun 21, 2018 at 10:04:24AM +0300, David Baron wrote:
> On Wed, Jun 20, 2018, 5:33 PM Mike <debian@norgie.net> wrote:
> 
> >
> > OK, so your NTP servers are:
> >
> > pool 0.debian.pool.ntp.org iburst
> > pool 1.debian.pool.ntp.org iburst
> > pool 2.debian.pool.ntp.org iburst
> > pool 3.debian.pool.ntp.org iburst
> >
> >
> > Most likely you are blocking UDP/123.  However, if you fail to resolve
> > the IP when you ping it, you have a DNS issue.
> >
> > Mike.
> >
> 
> 123 udp allowed both ways.
> The destination is resolved do dns ok.
> Ping still fails, unreachable,sendmsg operation not permitted.
>

The npt config is correct and the servers should be reachable.  This
points to some kind of networking issue at your end.

That ping error is a little curious.  It does sounds like a permissions
issue.  One needs to be root to send the ICMP messages that ping uses.
Ping gets around this issue by having setuid set on /usr/bin/ping, so
that anyone who can run it runs it effectively as root.  I've never
tried it but I suspect that if you remove setuid from /usr/bin/ping
you'd probably see the above error.  Having said that, I did a quick
seearch with a well-known Internet search engine and it the results
suggested that iptables could also cause the above error.

Anyway, speculation aside, the error (and I've ran ping many, many times
and never seen that error before) does suggest that something isn't
right on your box and it's not the NTPd config.  I'd start by looking at
your iptables config.  I'd be fairly sure something is blocking UDP/123,
whereever it is.

Mike. 

[toc] | [prev] | [next] | [standalone]

#196873

[Multipart message — attachments visible in raw view] — view raw

On Fri, Jun 22, 2018, 3:45 PM Mike <debian@norgie.net> wrote:

> On Thu, Jun 21, 2018 at 10:04:24AM +0300, David Baron wrote:
> > On Wed, Jun 20, 2018, 5:33 PM Mike <debian@norgie.net> wrote:
> >
> > >
> > > OK, so your NTP servers are:
> > >
> > > pool 0.debian.pool.ntp.org iburst
> > > pool 1.debian.pool.ntp.org iburst
> > > pool 2.debian.pool.ntp.org iburst
> > > pool 3.debian.pool.ntp.org iburst
> > >
> > >
> > > Most likely you are blocking UDP/123.  However, if you fail to resolve
> > > the IP when you ping it, you have a DNS issue.
> > >
> > > Mike.
> > >
> >
> > 123 udp allowed both ways.
> > The destination is resolved do dns ok.
> > Ping still fails, unreachable,sendmsg operation not permitted.
> >
>
> The npt config is correct and the servers should be reachable.  This
> points to some kind of networking issue at your end.
>
> That ping error is a little curious.  It does sounds like a permissions
> issue.  One needs to be root to send the ICMP messages that ping uses.
> Ping gets around this issue by having setuid set on /usr/bin/ping, so
> that anyone who can run it runs it effectively as root.  I've never
> tried it but I suspect that if you remove setuid from /usr/bin/ping
> you'd probably see the above error.  Having said that, I did a quick
> seearch with a well-known Internet search engine and it the results
> suggested that iptables could also cause the above error.
>
> Anyway, speculation aside, the error (and I've ran ping many, many times
> and never seen that error before) does suggest that something isn't
> right on your box and it's not the NTPd config.  I'd start by looking at
> your iptables config.  I'd be fairly sure something is blocking UDP/123,
> whereever it is.
>
> Mike.


I just Port forwarded on the router. May!! be working.

>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web