Information: I have filed a bug for this:
http://wiki.powerdns.com/trac/ticket/317
Nick
On 10/9/2010 6:43 μμ, Nikolaos Milas wrote:
In any case, I think this issue should be corrected for the next
release of powerdns authoritative server, because it makes no sense to
have logging in a differ
Hmm,
I am not sure if I'll manage to compile myself...
In any case, I think this issue should be corrected for the next release
of powerdns authoritative server, because it makes no sense to have
logging in a different time than system time. So I really hope that the
next releases and the as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
yesterday we had also a strange time drift on one of our machines. But
also PDNS had a very high latency and many 90% of the queries are not
answered also the query rate decreased to 10% of normal usage.
The solutions was that our remote sys
* Nikolaos Milas [100909 12:34]:
> I also installed compat-openldap and now I have:
>
>openldap-servers-2.3.43-12.el5_5.2
>nss_ldap-253-25.el5
>pdns-backend-ldap-2.9.21-4.el5.centos
>openldap-devel-2.3.43-12.el5_5.2
>python-ldap-2.2.0-2.1
>compat-openldap-2.3.43_2.2.29-12
Hi,
I have not had any info on that. How we define the path where
the configure script looks for libraries? I assume that the
script doesn't look by default in /usr/lib64 ?
Any clue? Sorry, I' m not very much used in compiling.
I also installed compat-openldap and now I have:
openldap-servers-2.3.43-12.el5_5.2
nss_ldap-253-25.el5
pdns-backend-ldap-2.9.21-4.el5.centos
openldap-devel-2.3.43-12.el5_5.2
python-ldap-2.2.0-2.1
compat-openldap-2.3.43_2.2.29-12.el5_5.2
openldap-2.3.43-12.el5_5.2
openlda
* Nikolaos Milas [100909 11:30]:
> Thanks Christian,
>
> I tried to configure, but it fails:
> ...
> configure: error: ldap library (libldap) not found
>
> But there is libldap:
>
># find / -name '*libldap*'
>/usr/lib/libldap_r-2.3.so.0.2.31
>/usr/lib/libldap-2.3.so.0
>/usr/li
By the way,
The autoserial feature is not supported with the ldap backend
according the documentation.
Nick
On 9/9/2010 11:27 πμ, Christian Hofstaedtler wrote:
> * Christian Hofstaedtler [100909 09:56]:
> probab
Thanks Christian,
I tried to configure, but it fails:
...
configure: error: ldap library (libldap) not found
But there is libldap:
# find / -name '*libldap*'
/usr/lib/libldap_r-2.3.so.0.2.31
/usr/lib/libldap-2.3.so.0
/usr/lib/libldap_r-2.3.so.0
/usr/lib/libldap-2.3.so.0.2.31
Ni
* Christian Hofstaedtler [100909 09:56]:
> Nikolas,
>
> The LDAP backend does indeed re-set the timezone to UTC.
> Why this propagates to your syslogd and into your log files, is
> beyond my imagination right now.
You could try out the following patch. It is compile-tested only, as
I don't have
Nikolas,
The LDAP backend does indeed re-set the timezone to UTC.
Why this propagates to your syslogd and into your log files, is
beyond my imagination right now.
Christian
--
christian hofstaedtler
___
Pdns-users mailing list
Pdns-users@mailman.pow
No other suggestions?
In the meantime, just in case, I have tried switching from the
2.9.22 rpm which I had found in a repository, to the more
standard 2.9.21-4 rpm included in the 'extras' CentOS
repositories, but the behavior is exactly the sam
Thanks Christian, {I
am resending in HTML format, to avoid auto line breaks which
make terminal output illegible.}
This problem happened to me only with pdns server logging. I've
never had a similar problem on this or on any of the other
Thanks Christian,
This problem happens only with pdns server logging. I've never had a
similar problem on this or on any of the other servers I'm managing
(mainly CentOS), all with the same locale, with various daemons and syslog.
The pdns daemons running are as follows:
# ps -ef | grep p
Nikolas,
* Nikolaos Milas [100903 08:18]:
> Hi,
>
> I'm running PDNS 2.9.22 and Recursor 3.1.5 (as packaged for CentOS
> 5) on CentOS 5.5.
>
> In log, I always notice many (actually most) log entries with -3
> hours (exactly) timestamp (I have changed the IP addresses):
[..]
glibc does not pr
Thanks Derrik for your reply,
But no, I am not running chroot'ed.
I did, however, tried copying the /etc/localtime file to /etc/pdns
(which is the directory where pdns.conf lies), but the same problem occurs.
This is strange. How can the same daemon send messages with a different
timezone n
On 09/03/2010 12:18 AM, Nikolaos Milas wrote:
> I'm running PDNS 2.9.22 and Recursor 3.1.5 (as packaged for CentOS 5) on
> CentOS 5.5.
>
> In log, I always notice many (actually most) log entries with -3 hours
> (exactly) timestamp (I have changed the IP addresses):
What timezone are you in? My g
Hi,
I'm running PDNS 2.9.22 and Recursor 3.1.5 (as packaged for CentOS 5) on
CentOS 5.5.
In log, I always notice many (actually most) log entries with -3 hours
(exactly) timestamp (I have changed the IP addresses):
Sep 3 08:49:56 vdns pdns[17892]: Scheduling exit on remote request
Sep 3
18 matches
Mail list logo
