Messages

1

16.1 Legacy Series / Re: NTPD problem on OPNsense 16.1.2-amd64

« on: February 15, 2016, 02:30:54 pm »

Ah yes, sorry. It's a KVM/QEMU guest in red hat.

I switched my local NTP server to a physical machine and all the problems went away. I think the issue was the physical host for this VM was syncing time to this guest, which was then syncing it's hardware clock with the physical host.

2

16.1 Legacy Series / [SOLVED] NTPD problem on OPNsense 16.1.2-amd64

« on: February 06, 2016, 08:54:49 pm »

I upgraded to 16 and now NTPD won't sync upstream. Here's a query right after restarting the service (note it looks happy):

Code: [Select]

# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*com1243.eecs.ut 130.207.244.240  2 u    -   64    1   52.187  -1370.1 602.678
+ec2-52-0-56-137 198.82.247.108   3 u    3   64    1   30.554  -1196.4 604.234
+time-a.timefreq .ACTS.           1 u    2   64    1   72.799  -1190.5 604.624
+131.107.13.100  .ACTS.           1 u    3   64    1  109.730  -1088.2 602.899

This log entry will appear:

Code: [Select]

Feb  6 14:43:02 fw ntpd[58138]: 0.0.0.0 c618 08 no_sys_peer

And then it falls over:

Code: [Select]

# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 com1243.eecs.ut 130.207.244.240  2 u   59   64    3   48.302  -6736.5 5828.65
 ec2-52-0-56-137 198.82.247.108   3 u   64   64    3   31.480  -6288.3 5556.01
 time-a.timefreq .ACTS.           1 u   63   64    3   72.770  -6281.8 5555.80
 131.107.13.100  .ACTS.           1 u   63   64    3  107.870  -6273.4 5648.01

status_ntpd.php says "Unreach/Pending" for all four: (see attached)

Here's the config file:

Code: [Select]

#
# OPNsense ntp configuration file
#

tinker panic 0
# Orphan mode stratum
tos orphan 12


# Upstream Servers
server 0.debian.pool.ntp.org iburst maxpoll 9
server 1.debian.pool.ntp.org iburst maxpoll 9
server 2.debian.pool.ntp.org iburst maxpoll 9
server 3.debian.pool.ntp.org iburst maxpoll 9


disable monitor
statsdir /var/log/ntp
logconfig =syncall +clockall +peerall +sysall
driftfile /var/db/ntpd.drift
restrict default nomodify notrap
restrict -6 default nomodify notrap

interface ignore all
interface listen vtnet0


3

15.7 Legacy Series / Re: [SOLVED] Cant restart DHCP Server

« on: July 12, 2015, 02:32:38 am »

I had this problem as well. What I saw in the logs was this:

Code: [Select]

opnsense: /status_services.php: The command '/usr/local/sbin/dhcpd -user dhcpd -group dhcpd -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid em0' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.2.8 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ no such user: dhcpd If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhcp-bugs at isc.org mailing list, please read the section on the README about submitting bug reports and requests for help. Please do not under any circumstances send requests for help directly to the authors of this software - please send them to the appropriate mailing list as described in the README file. exiting

I checked /etc/passwd and sure enough there was no dhcpd user. The next closest thing was "_dhcp":

Code: [Select]

_dhcp:*:65:65:dhcp programs:/var/empty:/usr/sbin/nologin

I ssh'd in and manually created a system account named dhcpd, gave it rights to the pid file dhcpd wanted and the service started properly at the next request.

The fix does not survive a reboot. I am running RAM disks like OP.