Solved NTPD Service no longer start after upgrade

JoseMR

JoseMR

Hello, apology if this was already asked but the search results don't show hints regarding my issue.

I has been upgrading my server with no major issues since my last system rebuild on 2019-12-30, however from my recent release upgrade from 13.x to 14.x I've noticed that some custom services, and cron where misbehaving, i.e being late starting and host date mismatch againts VM's and jails.

Then it turned out that the NTPD(8) service was no longer starting with the following error:

Code: 
# service ntpd start
Starting ntpd.
su: /bin/csh: Permission denied
/etc/rc.d/ntpd: WARNING: failed to start ntpd
So I've started checking ntpd related files and directories ownership/permissions compared from a working 14.3-RELEASE development VM, but everything looks good at least at first glance.

Then I wanted to debug further and run the "/etc/rc.d/ntpd" script with "set -x" and I've found the failing command as shown below:
Code: 
+ eval $' limits -C daemon  su -m ntpd -c \'sh -c " /usr/sbin/ntpd  -p /var/db/ntp/ntpd.pid -c /etc/ntp.conf -f /var/db/ntp/ntpd.drift -g"\''
+ limits -C daemon su -m ntpd -c 'sh -c " /usr/sbin/ntpd  -p /var/db/ntp/ntpd.pid -c /etc/ntp.conf -f /var/db/ntp/ntpd.drift -g"'
su: /bin/csh: Permission denied
+ _return=1
So I've replaced the related ntpd files(obtained from the working VM) and give it a shot under a new boot environment, unfortunately ntpd behaved with the same results.

Further more I can manually execute either of the below commands with no errors at all:
Code: 
ntpd -q -g ${TIMESERVER}
ntpdate -u ${TIMESERVER}

So my current workaround is to execute the below command with a daily cron in order to keep the server date on sync:
Code: 
ntpdate -u pool.ntp.org

However I really wan to know what is actually causing the above ntpd startup issue and/or what I can debug further as I'm running out of clues, fortunately a fresh system rebuild is not an urge as this is already workaround though.

Regards
 
Hello, while the OP was still under approval, I did find a very old thread HERE with a similar issue in regards the "su: /bin/csh: Permission denied".

So I've created another boot environment to test with and the problem was solved with the below command:
Code: 
mtree -U -f /etc/mtree/BSD.root.dist

I don't know when or what could caused this permissions change but I'm glad that I found a quick solution here after few search retries.

Regards
 
You must log in or register to reply here.
Back
Top