Article ID: 124772, created on Mar 9, 2015, last review on Nov 20, 2015

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

PDNS service does not functioning. When trying to check status the follow messages appears:

[root@server1 ~]# /etc/init.d/pdns status
not running

or

[root@server1 ~]# /etc/init.d/pdns monitor
Feb 13 14:31:14 Reading random entropy from '/dev/urandom'
Feb 13 14:31:14 This is a standalone pdns
Feb 13 14:31:14 It is advised to bind to explicit addresses with the --local-address option
Feb 13 14:31:14 UDP server bound to 0.0.0.0:53
Feb 13 14:31:14 TCP server bound to 0.0.0.0:53
Feb 13 14:31:14 PowerDNS 2.9.22.6 (C) 2001-2009 PowerDNS.COM BV (Jan 16 2012, 09:11:59, gcc 4.4.3) starting up
Feb 13 14:31:14 PowerDNS comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it according to the terms of the GPL version 2.
Feb 13 14:31:14 Got a signal 8, attempting to print trace:
Feb 13 14:31:14 [0x4732b0]
Feb 13 14:31:14 [0x625290]
Feb 13 14:31:14 /lib64/libc.so.6(+0x77d63) [0x7fb4b2dc4d63]
Feb 13 14:31:14 /lib64/libc.so.6(fclose+0x14d) [0x7fb4b2db2e3d]
Feb 13 14:31:14 /lib64/libnss_files.so.2(_nss_files_getgrnam_r+0x172) [0x7fb4b30d2622]
/etc/init.d/pdns: line 34:  8682 Aborted                 $pdns_server --daemon=no --guardian=no     --control-console --loglevel=9

Cause

This is a known issue with powerdns libraries on CentOS 6.0.

Resolution

Update OS in OBAS container per KB article: How to update the OS (minor) of a OBAS server.

Search Words

Got a signal 8, attempting to print trace:

It is advised to bind to explicit addresses with the --local-address option

powerdns

This is a standalone pdns

Reading random entropy from

not running

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 624ca542e40215e6f1d39170d8e7ec75 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF