I haven't had a chance to read through this entire thread yet, but
wanted to post this in case it helps someone.
ntpd was working fine for me for a while, and then I started getting
this exact same error. After a few weeks, I finally started
troubleshooting and it turned out that I had, at
I haven't had a chance to read through this entire thread yet, but
wanted to post this in case it helps someone.
ntpd was working fine for me for a while, and then I started getting
this exact same error. After a few weeks, I finally started
troubleshooting and it turned out that I had, at
ly ignore this.
>
> Brian
>
> -Original Message-
> From: owner-freebsd-sta...@freebsd.org
> [mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of Matthew Doughty
> Sent: Friday, 18 May 2012 1:03 AM
> To: freebsd-stable@freebsd.org
> Subject: ntpd couldn't res
Bjoern:
I've done a fresh install of version FreeNAS-8.0.4-RELEASE-*p2*-x64. and
the problem is solved. The last line says:
*
freenas ntpd[1485]: time reset +0.946762 s*
Is that the correct now?
Matthew
On 18 May 2012 11:14, Bjoern A. Zeeb wrote:
>
> On 18. May 2012, at 13:28 , Matthew Doug
On 18. May 2012, at 13:28 , Matthew Doughty wrote:
> Hello Bjoern,
>
> It's still a problem for me. Here is a list of my system information:
>
>
> Hostname freenas.local
> FreeNAS Build FreeNAS-8.0.4-RELEASE-p1-x64 (11059)
> Platform AMD Athlon(tm) II X2 250 Processor
> Memory
Hello Bjoern,
It's still a problem for me. Here is a list of my system information:
Hostname freenas.local FreeNAS Build FreeNAS-8.0.4-RELEASE-p1-x64 (11059)
Platform AMD Athlon(tm) II X2 250 Processor Memory 8144MB System Time Fri
May 18 09:07:22 2012 Uptime 9:07AM up 6 mins, 0 users Load
On 17. May 2012, at 15:03 , Matthew Doughty wrote:
> Dear Jerermy,
>
> Whilst searching for a solution to a problem, I found your post:
> http://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064350.html
>
> Please could you explain how I can implement the netwait script to solve
> the
Thanks Vince, I'll give it a go.
Regards,
Matthew
On 17 May 2012 14:49, Vincent Hoffman wrote:
> On 17/05/2012 17:13, Matthew Doughty wrote:
> > Hi, thanks for your quick reply.
> >
> > Please could you explain how to do that? Or if you know a post that
> > explains
>
> Its not that obviou
On 17/05/2012 17:13, Matthew Doughty wrote:
> Hi, thanks for your quick reply.
>
> Please could you explain how to do that? Or if you know a post that
> explains
Its not that obvious but...
man 5 rc.conf
and have a look at the netwait_* variable options (particularly
netwait_enable)
Basically
Hi, thanks for your quick reply.
Please could you explain how to do that? Or if you know a post that
explains
Thanks,
Matthew
On 17 May 2012 11:42, wrote:
> Matthew,
>
> netwait script is already implemented:
> http://lists.freebsd.org/pipermail/svn-src-head/2011-June/028593.html
>
> So,
Matthew,
netwait script is already implemented:
http://lists.freebsd.org/pipermail/svn-src-head/2011-June/028593.html
So, you shuld just add netwit_* entries in your rc.conf file.
2012/5/17 Matthew Doughty :
> Dear Jerermy,
>
> Whilst searching for a solution to a problem, I found your post:
> h
Dear Jerermy,
Whilst searching for a solution to a problem, I found your post:
http://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064350.html
Please could you explain how I can implement the netwait script to solve
the problem? I'm new to freenas/BSD but am willing to try working fro
On Tue, 25 Oct 2011, Miroslav Lachman wrote:
Hi all,
I have a problem with ntpd on many of our servers running 8.2-RELEASE or
newer. Some of them are newly installed, most of them are 7.x upgraded to 8.2
or 8-STABLE amd64 with GENERIC.
hmm, could it be I didn't MFC all fixes I had done to h
On Tue, 25 Oct 2011, Miroslav Lachman wrote:
Paul Schenkeveld wrote:
On Tue, Oct 25, 2011 at 05:51:08AM -0700, Jeremy Chadwick wrote:
On Tue, Oct 25, 2011 at 11:20:12AM +0200, Paul Schenkeveld wrote:
On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote:
The one shortcoming of netw
Paul Schenkeveld wrote:
On Tue, Oct 25, 2011 at 05:51:08AM -0700, Jeremy Chadwick wrote:
On Tue, Oct 25, 2011 at 11:20:12AM +0200, Paul Schenkeveld wrote:
On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote:
The one shortcoming of netwait is that it doesn't support waiting for
mult
On Tue, Oct 25, 2011 at 05:51:08AM -0700, Jeremy Chadwick wrote:
> On Tue, Oct 25, 2011 at 11:20:12AM +0200, Paul Schenkeveld wrote:
> > On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote:
> > > The one shortcoming of netwait is that it doesn't support waiting for
> > > multiple NICs.
On Tue, Oct 25, 2011 at 11:20:12AM +0200, Paul Schenkeveld wrote:
> On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote:
> > The one shortcoming of netwait is that it doesn't support waiting for
> > multiple NICs. Some people have dual-homed environments where they
> > really would lik
On Mon, Oct 24, 2011 at 06:03:27PM -0700, Jeremy Chadwick wrote:
> The one shortcoming of netwait is that it doesn't support waiting for
> multiple NICs. Some people have dual-homed environments where they
> really would like to wait for both, say, em0 and em1, to come up and be
> functional befor
Jeremy Chadwick wrote:
On Tue, Oct 25, 2011 at 12:50:29AM +0200, Miroslav Lachman wrote:
I have a problem with ntpd on many of our servers running
8.2-RELEASE or newer. Some of them are newly installed, most of them
are 7.x upgraded to 8.2 or 8-STABLE amd64 with GENERIC.
Ntpd can't resolve host
On Tue, Oct 25, 2011 at 12:36:56AM +0100, Steven Hartland wrote:
> - Original Message - From: "Jeremy Chadwick"
>
>
> >The problem is that the networking layer is not TRULY available by the
> >time ntpd starts. This does have to do with NIC drivers, but the same
> >behaviour can be seen
- Original Message -
From: "Jeremy Chadwick"
The problem is that the networking layer is not TRULY available by the
time ntpd starts. This does have to do with NIC drivers, but the same
behaviour can be seen on all NICs, including excellent ones like em(4).
This is generally caused
On Tue, Oct 25, 2011 at 12:50:29AM +0200, Miroslav Lachman wrote:
> I have a problem with ntpd on many of our servers running
> 8.2-RELEASE or newer. Some of them are newly installed, most of them
> are 7.x upgraded to 8.2 or 8-STABLE amd64 with GENERIC.
>
> Ntpd can't resolve host names on boot.
Hi all,
I have a problem with ntpd on many of our servers running 8.2-RELEASE or
newer. Some of them are newly installed, most of them are 7.x upgraded
to 8.2 or 8-STABLE amd64 with GENERIC.
Ntpd can't resolve host names on boot. This error did not existed on 7.x
Oct 24 12:45:22 vcela kernel
23 matches
Mail list logo