Re: Can't get named_sdb to load postgres modules?

On Tue, May 12, 2009 at 1:00 PM, Mike Toler
<[email protected]> wrote:
> I saw the srpms on atkacs page, but the el5 version was 9.3.4.  I just

I usually just rebuild the latest FC version on my CentOS box, doesn't
usually cause me grief.

> went out and grabbed the 9.5 binaries from pbone.net.  Not sure what the
> "pp" stands for.  Honestly hadn't noticed it till you pointed it out.

I'll have to dig for that.  I don't recognize it as any of the
standard RH/CentOS repos.

>> And it's also tempting to assume that you are calling the named-sdb
>>binary and not a script named named_sdb like you pasted.  Is that
>>true?
> Ok, you've confused me there.   I'm calling the named_sdb executable

Interesting.  The packages from atkac produce named-sdb, not
named_sdb.  I don't know what to think about that.

>              logging {
>             channel named_info {
>                 // log to syslog instead of a file
>                 syslog;
>                 // include the category of the event in the log
>                 print-category yes;
>                 // include the severity of the event in the log
>                 print-severity yes;
>                 // include the time of the event in the log
>                 print-time yes;
>             };
>
>             category client { null; };
>             category config { null; };
>             category database { null; };
>             category default { null; };
>             category general { null; };
>             category notify { null; };
>             category network { null; };
>             category resolver { null; };
>             category security { null; };
>             category update { null; };
>             category queries { null; };
>             category xfer-in { null; };
>             category xfer-out { null; };
>             };

I would start turning on logging for a few of those and see what it says.

You mentioned about debug output saying that it was loading the SDB
modules. If you check the named_sdb binary and see dynamic links to
mysql, ldap, and postgres libs, I think we can say that your binary
has the proper support, but the debug output is authoritative.  Mine
has the modules built in and it also spits out the SDB debug info, so
I suspect that means that yours should too.

CentOS52[root@ivdns51 ~]# /usr/sbin/named-sdb -u named -n 1 -t
/var/named/chroot -g
12-May-2009 20:32:43.867 starting BIND 9.5.0-P1 -u named -n 1 -t
/var/named/chroot -g
12-May-2009 20:32:43.877 found 1 CPU, using 1 worker thread
12-May-2009 20:32:43.877 SDB ldap zone database module loaded.
12-May-2009 20:32:43.877 SDB postgreSQL DB zone database module loaded.
12-May-2009 20:32:43.877 SDB sqlite3 DB zone database module loaded.
12-May-2009 20:32:43.878 SDB directory DB zone database module loaded.
12-May-2009 20:32:43.879 loading configuration from '/etc/named.conf'

Take a look at the named_sdb and make sure that it's not a symlink to
the generic named binary.

> dlz "postgres zone" {
>   database "postgres 1
>   {host=int-dbs port=5432 dbname=dns_data user=postgres}
>   {select zone from dns_records where zone = '%zone%'}
>   {select ttl, type, mx_priority, case when lower(type)='txt' then '\"'
>         || data || '\"' when lower(type)='soa' then data || ' ' ||
> resp_person || ' '
>         || serial || ' ' || refresh || ' ' || retry || ' ' || expire ||
> ' ' || minimum
>         else data end from dns_records where zone = '%zone%' and host =
> '%record%'}
>   {}
>   {select ttl, type, host, mx_priority, case when lower(type)='txt'
> then '\"'
>         || data || '\"' else data end, resp_person, serial, refresh,
> retry, expire,
>        minimum from dns_records where zone = '%zone%'}
>   {select zone from xfr_table where zone = '%zone%' and client =
> '%client%'}";
> };

I use mysql instead of postgresql, so I don't know if the above is
proper or not.

Good luck.

-- 
Regards...      Todd

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com