Re: OpenBSD as a NAS
On Sat, 5 Dec 2020, Georg Bege wrote: keep in mind that the ZFS supported versions may be quite different. The "one ZFS for many OS" isn't really working in reality, you may not be able to import your pool into different OS than the one you've created it with. Indeed there is this risk. I only superficially testet long ago compatibility between Ilumos and FreeBSD. But ist there a waranty that UFS partitions created in one system can be always mounted without big problems in other systems? Rod.
Re: OpenBSD as a NAS
On Sat, Dec 05, 2020 at 12:36:04PM +, Roderick wrote: > > On Sat, 5 Dec 2020, Georg Bege wrote: > > > keep in mind that the ZFS supported versions may be quite different. > > > > The "one ZFS for many OS" isn't really working in reality, > > > > you may not be able to import your pool into different OS than the one > > you've created it with. > > Indeed there is this risk. I only superficially testet long ago > compatibility between Ilumos and FreeBSD. > > But ist there a waranty that UFS partitions created in one system can > be always mounted without big problems in other systems? > > Rod. > In general there is no warranty at all, see the license. But there are good chances it will work, as long as the endianess of the old and new system are the same. -Otto
Boot Timeout
Hi all, i am trying to remove the pause at the boot prompt. According to boot(8) this can be done by echo "boot" > /etc/boot.conf However this does not work with hibernate as it always boots /bsd and does not switch to /bsd.booted Hibernate works fine for me without the boot command in boot.conf My current solution is to echo "set timeout 1" > /etc/boot.conf I was wondering if this is "the way"? Best regards Kai
clock not set on boot
Ever since updating to 6.8, I've had trouble with the system clock not getting set on boot. I know the easy answer is to script a call to rdate, but that feels like a bandaid solution. I'm running from an EdgeRouter Lite (octeon) that afaik does not have a persistent clock. Before 6.8, I always saw boot messages about how the kernel was going to set the clock based on the filesystem. I don't see those messages anymore, and instead see an ominous "WARNING: CHECK AND RESET THE DATE!" I assume there's been some changes into how dates and time are handled, but I haven't seen anything in the release notes. Can anyone point me in the right direction, or have a better bandaid idea than calling rdate?
Re: clock not set on boot
Perhaps add ntpd_flags="-s" to /etc/rc.conf.local
Re: clock not set on boot
On Sat, Dec 05, 2020 at 09:10:19PM +, Maurice McCarthy wrote: > Perhaps add > > ntpd_flags="-s" > > to /etc/rc.conf.local > -s doesn't exist anymore.
Re: clock not set on boot
andygoblins wrote: > Ever since updating to 6.8, I've had trouble with the system clock not > getting set on boot. > > I know the easy answer is to script a call to rdate, but that feels like a > bandaid solution. > > I'm running from an EdgeRouter Lite (octeon) that afaik does not have a > persistent clock. Before 6.8, I always saw boot messages about how the kernel > was going to set the clock based on the filesystem. I don't see those > messages anymore, and instead see an ominous "WARNING: CHECK AND RESET THE > DATE!" > > I assume there's been some changes into how dates and time are handled, but I > haven't seen anything in the release notes. > > Can anyone point me in the right direction, or have a better bandaid idea > than calling rdate? ntpd is run by default, and magically will correct the time almost immediately. Some significant effort went into this a few years ago. However, the kernel message will always be there. You can ignore it. Run ntpctl -s all, and you'll see the time has been corrected before significant daemons start.
Re: clock not set on boot
> From: "Theo de Raadt" > > ntpd is run by default, and magically will correct the time almost > immediately. > > Some significant effort went into this a few years ago. > > However, the kernel message will always be there. You can ignore it. > > Run ntpctl -s all, and you'll see the time has been corrected before > significant daemons start. ntpd is running, but the clock isn't getting corrected before significant daemons start. In fact, it's causing other daemons, like unbound, to fail. $ ntpctl -s all 5/5 peers valid, constraint offset 5355740s, clock unsynced, clock offset is 5355739014.329ms ... /var/messages: Oct 4 21:20:24 hostname ntpd[61157]: ntp engine ready Oct 4 21:20:25 hostname ntpd[61157]: constraint reply from 9.9.9.9: offset 5355740.057722 Oct 4 21:20:26 hostname unbound: [98456:0] notice: init module 0: validator Oct 4 21:20:26 hostname unbound: [98456:0] notice: init module 1: iterator Oct 4 21:20:26 hostname unbound: [98456:0] info: start of service (unbound 1.11.0). Oct 4 21:20:27 hostname ntpd[61157]: cancel settime because dns probe failed Oct 4 21:20:27 hostname unbound: [25295:1] info: failed to prime trust anchor -- DNSKEY rrset is not secure . DNSKEY IN ... Does ntpd need DNS to set the time? Because my reslov.conf points to 127.0.0.1 and unbound needs the time before it will work properly.
Re: clock not set on boot
You have filtered ntpd so much that it can't do the job it wants to do. Andy Goblins wrote: > > From: "Theo de Raadt" > > > > ntpd is run by default, and magically will correct the time almost > > immediately. > > > > Some significant effort went into this a few years ago. > > > > However, the kernel message will always be there. You can ignore it. > > > > Run ntpctl -s all, and you'll see the time has been corrected before > > significant daemons start. > > ntpd is running, but the clock isn't getting corrected before significant > daemons start. In fact, it's causing other daemons, like unbound, to fail. > $ ntpctl -s all > 5/5 peers valid, constraint offset 5355740s, clock unsynced, clock offset is > 5355739014.329ms > ... > > /var/messages: > Oct 4 21:20:24 hostname ntpd[61157]: ntp engine ready > Oct 4 21:20:25 hostname ntpd[61157]: constraint reply from 9.9.9.9: offset > 5355740.057722 > Oct 4 21:20:26 hostname unbound: [98456:0] notice: init module 0: validator > Oct 4 21:20:26 hostname unbound: [98456:0] notice: init module 1: iterator > Oct 4 21:20:26 hostname unbound: [98456:0] info: start of service (unbound > 1.11.0). > Oct 4 21:20:27 hostname ntpd[61157]: cancel settime because dns probe failed > Oct 4 21:20:27 hostname unbound: [25295:1] info: failed to prime trust > anchor -- DNSKEY rrset is not secure . DNSKEY IN > ... > > Does ntpd need DNS to set the time? Because my reslov.conf points to > 127.0.0.1 and unbound needs the time before it will work properly.
Re: clock not set on boot
Andy Goblins wrote: > Does ntpd need DNS to set the time? Because my reslov.conf points to > 127.0.0.1 and unbound needs the time before it will work properly. A problem of your own creation.
Re: clock not set on boot
On Sat, Dec 05, 2020 at 09:10:19PM +, Maurice McCarthy wrote: > Perhaps add > > ntpd_flags="-s" > > to /etc/rc.conf.local > Nope, that's no longer needed.
Re: clock not set on boot
On Sat, Dec 05, 2020 at 07:42:48PM -0700, Theo de Raadt wrote: > Andy Goblins wrote: > > > Does ntpd need DNS to set the time? Because my reslov.conf points to > > 127.0.0.1 and unbound needs the time before it will work properly. > > A problem of your own creation. > We do attept to work even in this situation, by doing CD (checking disbaled) queries if needed. But in some cases this does not work, esepcially if the net and/or unbound is slow to start. e.g. I have one machine that nees a !sleep 1 in it's hostname.if file since the network interface it tto slow to startup and ntpd gives up doing the initial settime. Add ntpd_flags=-vv and show me the /var/log/daemon lines. -Otto
Re: clock not set on boot
On Sun, Dec 06, 2020 at 08:33:33AM +0100, Otto Moerbeek wrote: > On Sat, Dec 05, 2020 at 07:42:48PM -0700, Theo de Raadt wrote: > > > Andy Goblins wrote: > > > > > Does ntpd need DNS to set the time? Because my reslov.conf points to > > > 127.0.0.1 and unbound needs the time before it will work properly. > > > > A problem of your own creation. > > > > We do attept to work even in this situation, by doing CD (checking > disbaled) queries if needed. But in some cases this does not work, > esepcially if the net and/or unbound is slow to start. > > e.g. I have one machine that nees a !sleep 1 in it's hostname.if > file since the network interface it tto slow to startup and ntpd > gives up doing the initial settime. > > Add ntpd_flags=-vv and show me the /var/log/daemon lines. > > -Otto > Ah, I see the info is already there in another post. This edgerouter is a slow machine. You can try what I suggested, e.g. by putting a sleep after unbound starts in /etc/rc. But an easier solution is not to rely on a single resolved and add another one in /etc/resolve.conf -Otto
Re: clock not set on boot
On Sun, Dec 06, 2020 at 08:39:36AM +0100, Otto Moerbeek wrote: > On Sun, Dec 06, 2020 at 08:33:33AM +0100, Otto Moerbeek wrote: > > > On Sat, Dec 05, 2020 at 07:42:48PM -0700, Theo de Raadt wrote: > > > > > Andy Goblins wrote: > > > > > > > Does ntpd need DNS to set the time? Because my reslov.conf points to > > > > 127.0.0.1 and unbound needs the time before it will work properly. > > > > > > A problem of your own creation. > > > > > > > We do attept to work even in this situation, by doing CD (checking > > disbaled) queries if needed. But in some cases this does not work, > > esepcially if the net and/or unbound is slow to start. > > > > e.g. I have one machine that nees a !sleep 1 in it's hostname.if > > file since the network interface it tto slow to startup and ntpd > > gives up doing the initial settime. > > > > Add ntpd_flags=-vv and show me the /var/log/daemon lines. > > > > -Otto > > > > Ah, I see the info is already there in another post. This edgerouter > is a slow machine. You can try what I suggested, e.g. by putting a > sleep after unbound starts in /etc/rc. > > But an easier solution is not to rely on a single resolved and add > another one in /etc/resolve.conf Sorry about the typos. *resolver and */etc/resolv.conf -Otto
