[Voyage-linux] Strange problem with NTPD

[Mark Powell]

Greetings

I am currently running Voyage 0.8.5 on an ALIX2D13.

When I installed the build, I changed very little; I updated and
installed nano and ntpd with apt-get. I noticed there was a problem
with LOCALE errors so I sorted this out, although I can't remember the
exact steps.

I have been running ntpd absolutely fine, I peered with some stratum 2
servers in the UK and added the server to uk.pool.ntp.org. Within a
day or so my server was scoring 20 (Max) for availability and
accuracy.

One of the suggestions on the pool site was to run a www page on port
80 that informed anyone who accessed the fqdn of the server in their
browser some details of the server. Today, I installed nginx and
edited index.html to provide that info. My firewall logs all the
traffic to port 123 UDP of the server and produces a graph in png
format. I created a cron job to wget the image file every 10 minutes
and place it in the images folder I created in the default
usr/share/nginx/www folder.

If you go to ntp.typical.me.uk you can see for yourself that it's all
running fine except for one major problem - ntpd doesn't run properly
anymore. I received a mail from the pool administrator within a few
hours informing that me that the server is down. If I do a ntpq -p
ntp.typical.me.uk from another host on my LAN, I get either a 'read
connection refused' or a 'request timeout' error, whereas previously I
could always see the peers.

If I do /etc/init.d/ntp stop the first time I get

Stopping NTP server: ntpdstart-stop-daemon: warning: failed to kill
1759: No such process
.
but then I can restart, and the ntpd daemon is running, but unresponsive.

This is all very odd, and I would appreciate any suggestions as to
where I might be going wrong.

Regards

Mark Powell