Just wanted to confirm that this is spot on -- I ran into this same
thing a few weeks back and had to do the same head scratching, RFC
look-up, google, etc.
--Augie
On Mon, Mar 1, 2010 at 11:25 AM, Julian Mehnle wrote:
> Leen Besselink wrote:
>
>> You can also see that here:
>>
>> http://doc.pow
On 08.03.2010, at 17:27, Matthias Cramer wrote:
> This seams to be a XEN issue not related to powerdns!
>
> See: http://blog.brachium-system.net/archives/56-Xen-4gb-seg-fixup-Etch.html
>
> I have the same on my two xen dns servers. It also apears for other
> processes.
4gb seg fixup,
Matthias,
Thanks. It appears not to effect the performance of the machine, but it
was curious. Did you install the libc6-xen as the blog suggested, or
are you just living with the console messages.
Thanks agian for the response.
Steve
Matthias Cramer wrote:
> Hi Steve
>
> This seams to be a
Hi Steve
This seams to be a XEN issue not related to powerdns!
See: http://blog.brachium-system.net/archives/56-Xen-4gb-seg-fixup-Etch.html
I have the same on my two xen dns servers. It also apears for other
processes.
Regards
Matthias
Steve Spencer wrote:
> Forgot to respond to all: Yes, i
Forgot to respond to all: Yes, it is.
Thanks,
Steve
Matthias Cramer wrote:
> Hi Steve
>
> Are you running on XEN ?
>
> Regards
>
> Matthias
>
> Steve Spencer wrote:
>> Ok, post update 3.2-1, I'm getting these message recurring on the
>> console of the updated machine:
>>
>> 4gb seg fixup, pr
Hi Steve
Are you running on XEN ?
Regards
Matthias
Steve Spencer wrote:
> Ok, post update 3.2-1, I'm getting these message recurring on the
> console of the updated machine:
>
> 4gb seg fixup, process pdns_recursor (pid 30520), cs:ip 73:080e3a38
>
> Is this normal?
>
> Thanks,
> Steve
>
>
Ok, post update 3.2-1, I'm getting these message recurring on the
console of the updated machine:
4gb seg fixup, process pdns_recursor (pid 30520), cs:ip 73:080e3a38
Is this normal?
Thanks,
Steve
Steve Spencer wrote:
> Thanks Stefan, I forced the update and restarted the recursor and all
> seem
Hi All,
try to compile the new recursor and get finally this error:
CXXFLAGS=-I/opt/src/build/boost_1_42_0/ gmake
[..]
g++ syncres.o misc.o unix_utility.o qtype.o logger.o arguments.o
lwres.o pdns_recursor.o recursor_cache.o dnsparser.o dnswriter.o
dnsrecords.o rcpgenerator.o base64.o zoneparse
Thanks Stefan, I forced the update and restarted the recursor and all
seems to be running as it should.
Stefan Schmidt wrote:
> On 08.03.2010, at 15:27, Steve Spencer wrote:
>
>> Just want to make sure this package is actually newer. I'm getting this
>> message when I attempt to update the recur
On 08.03.2010, at 15:27, Steve Spencer wrote:
> Just want to make sure this package is actually newer. I'm getting this
> message when I attempt to update the recursor on an CentOS5.x box:
>
> rpm -Uvh pdns-recursor-3.2-1.i386.rpm
> Preparing...##
Just want to make sure this package is actually newer. I'm getting this
message when I attempt to update the recursor on an CentOS5.x box:
rpm -Uvh pdns-recursor-3.2-1.i386.rpm
Preparing...###
[100%]
package pdns-recursor-3.1.7.2-1.e
On 08.03.2010, at 10:30, Stefan Priebe - allied internet ag wrote:
Hello all,
Hey Stefan,
in the online documentation still the fork flag is mentioned. I was
searching for the replacement flag. But wasn't able to find one.
Also in the pdns_recursor.1 file is still fork mentioned. I thought
Hello all,
in the online documentation still the fork flag is mentioned. I was
searching for the replacement flag. But wasn't able to find one.
Also in the pdns_recursor.1 file is still fork mentioned. I thought this
was completely replaced so that pdns_recursor can also run on 4 Cores
and more.
13 matches
Mail list logo