On 01/04/2012 16:24, George Kontostanos wrote:
> Greetings everyone,
>
> I was testing DNSSec resolution on BIND 9.8.1-P1 by adding the
> following options:
>
> options {
> ...
> dnssec-enable yes;
> dnssec-validation auto;
> ...
> };
>
> Unfortunately immediately after named is restarted one CP
On Saturday, January 07, 2012 5:06:46 pm Phil Kulin wrote:
> kproc_info system and user time is broken for processes with threads,
> when fetch then by kvm_getprocs() function call.
> For example, modern 'ps' on server running mysqld (145 precached threads)
>
> # ps -ax -o comm,cputime,systime,use
On Mon, Jan 9, 2012 at 11:47 AM, Doug Barton wrote:
> On 01/04/2012 16:24, George Kontostanos wrote:
>> Greetings everyone,
>>
>> I was testing DNSSec resolution on BIND 9.8.1-P1 by adding the
>> following options:
>>
>> options {
>> ...
>> dnssec-enable yes;
>> dnssec-validation auto;
>> ...
>> }
TB --- 2012-01-09 14:44:10 - tinderbox 2.8 running on freebsd-legacy.sentex.ca
TB --- 2012-01-09 14:44:10 - starting RELENG_8 tinderbox run for amd64/amd64
TB --- 2012-01-09 14:44:10 - cleaning the object tree
TB --- 2012-01-09 14:44:51 - cvsupping the source tree
TB --- 2012-01-09 14:44:51 - /usr/
Good morning,
Just wondering if anyone else has run into a similar issue.
We have a ZFS storage server that was running 8.2-STABLE (from around
beginning of Dec 2011) without any issues, that was upgraded to
9.0-RELEASE (to consolidate all the ZFS and networking fixes/updates
and bring it up to v
On Sat, 07 Jan 2012 14:23:46 -0600, Hiroki Sato wrote:
It is an unexpected behavior and the flag should be set on all
interfaces. Can you send me your /etc/rc.conf, /etc/sysctl.conf, and
the result of "ifconfig -a"?
Back at work so I have access to the machine again:
rc.conf:
hostname="
On Mon, Jan 9, 2012 at 9:50 AM, John Nielsen wrote:
> From what you've said I strongly suspect that you have some kind of hardware
> issue. Dodgy RAM is my first guess, something cooling-related is my 2nd, and
> PSU is my 3rd. It is a little suspicious that you only started having
> problems af
Small correction: these are AMD Opteron 6218 CPUs, not 2218.
> Hardware (alphadrive):
> Chenbro 5U rackmount chassis with 24 hot-swap drive bays
> SuperMicro H8DGi-F motherboard
> AMD Opteron 6218 CPU (8-cores at 2.0 GHz)
> 24 GB DDR3-SDRAM
> 3x SuperMicro AOC-USAS-L8i SATA controllers (mult
TB --- 2012-01-09 16:16:53 - tinderbox 2.8 running on freebsd-legacy.sentex.ca
TB --- 2012-01-09 16:16:53 - starting RELENG_8 tinderbox run for i386/i386
TB --- 2012-01-09 16:16:54 - cleaning the object tree
TB --- 2012-01-09 16:17:21 - cvsupping the source tree
TB --- 2012-01-09 16:17:21 - /usr/bi
On Jan 9, 2012, at 12:40 PM, Freddie Cash wrote:
> Just wondering if anyone else has run into a similar issue.
>
> We have a ZFS storage server that was running 8.2-STABLE (from around
> beginning of Dec 2011) without any issues, that was upgraded to
> 9.0-RELEASE (to consolidate all the ZFS and
On Mon, Jan 09, 2012 at 09:55:58AM -0800, Freddie Cash wrote:
> On Mon, Jan 9, 2012 at 9:50 AM, John Nielsen wrote:
> > From what you've said I strongly suspect that you have some kind of
> > hardware issue. Dodgy RAM is my first guess, something cooling-related is
> > my 2nd, and PSU is my 3rd.
TB --- 2012-01-09 17:20:03 - tinderbox 2.8 running on freebsd-legacy.sentex.ca
TB --- 2012-01-09 17:20:03 - starting RELENG_8 tinderbox run for i386/pc98
TB --- 2012-01-09 17:20:03 - cleaning the object tree
TB --- 2012-01-09 17:20:30 - cvsupping the source tree
TB --- 2012-01-09 17:20:30 - /usr/bi
On Jan 9, 2012, at 8:03 PM, Freddie Cash wrote:
> Small correction: these are AMD Opteron 6218 CPUs, not 2218.
>
>> Hardware (alphadrive):
>> Chenbro 5U rackmount chassis with 24 hot-swap drive bays
>> SuperMicro H8DGi-F motherboard
>> AMD Opteron 6218 CPU (8-cores at 2.0 GHz)
You meant Opt
2012/1/9 Daniel Kalchev :
> On Jan 9, 2012, at 8:03 PM, Freddie Cash wrote:
>
>> Small correction: these are AMD Opteron 6218 CPUs, not 2218.
>>
>>> Hardware (alphadrive):
>>> Chenbro 5U rackmount chassis with 24 hot-swap drive bays
>>> SuperMicro H8DGi-F motherboard
>>> AMD Opteron 6218 CPU (8
TB --- 2012-01-09 18:10:38 - tinderbox 2.8 running on freebsd-legacy.sentex.ca
TB --- 2012-01-09 18:10:38 - starting RELENG_8 tinderbox run for ia64/ia64
TB --- 2012-01-09 18:10:38 - cleaning the object tree
TB --- 2012-01-09 18:11:05 - cvsupping the source tree
TB --- 2012-01-09 18:11:05 - /usr/bi
Mark Felder wrote
in :
fe> On Sat, 07 Jan 2012 14:23:46 -0600, Hiroki Sato
fe> wrote:
fe>
fe> > It is an unexpected behavior and the flag should be set on all
fe> > interfaces. Can you send me your /etc/rc.conf, /etc/sysctl.conf, and
fe> > the result of "ifconfig -a"?
fe>
fe> Back at work
On Mon, Jan 09, 2012 at 11:25:45AM -0800, Freddie Cash wrote:
> 2012/1/9 Daniel Kalchev :
> > On Jan 9, 2012, at 8:03 PM, Freddie Cash wrote:
> >
> >> Small correction: ??these are AMD Opteron 6218 CPUs, not 2218.
> >>
> >>> Hardware (alphadrive):
> >>> ??Chenbro 5U rackmount chassis with 24 hot-sw
On Mon, 09 Jan 2012 13:02:24 -0600, Hiroki Sato wrote:
re0 seems to have ACCEPT_RTADV. What is the problem?
That's because I haven't rebooted
Let's start fresh.
The normal ipv6 configuration anyone would use:
-ipv6_activate_all_interfaces="YES" in rc.conf
-NO mention of net.inet6.ip6
TB --- 2012-01-09 20:23:00 - tinderbox 2.8 running on freebsd-legacy.sentex.ca
TB --- 2012-01-09 20:23:00 - starting RELENG_8 tinderbox run for powerpc/powerpc
TB --- 2012-01-09 20:23:00 - cleaning the object tree
TB --- 2012-01-09 20:23:17 - cvsupping the source tree
TB --- 2012-01-09 20:23:17 - /
TB --- 2012-01-09 20:34:25 - tinderbox 2.8 running on freebsd-legacy.sentex.ca
TB --- 2012-01-09 20:34:25 - starting RELENG_8 tinderbox run for sparc64/sparc64
TB --- 2012-01-09 20:34:25 - cleaning the object tree
TB --- 2012-01-09 20:34:44 - cvsupping the source tree
TB --- 2012-01-09 20:34:44 - /
Mark Felder wrote
in :
fe> On Mon, 09 Jan 2012 13:02:24 -0600, Hiroki Sato
fe> wrote:
fe>
fe> > re0 seems to have ACCEPT_RTADV. What is the problem?
fe>
fe> That's because I haven't rebooted
fe>
fe> Let's start fresh.
fe>
fe> The normal ipv6 configuration anyone would use:
fe>
fe> -ipv6_a
On Mon, 09 Jan 2012 19:56:47 -0600, Hiroki Sato wrote:
This is an expected behavior. ACCEPT_RTADV is disabled by default on
9.X.
Thanks for clarifying. I'll make sure I update our documentation at work
regarding how exactly to get ACCEPT_RTADV working so this is clarified.
Regards,
22 matches
Mail list logo
