Re: Can't get named_sdb to load postgres modules?
Todd Lyons <[email protected]> Tue, 12 May 2009 14:52:06 -0700
| Newsgroups | gmane.network.dns.bind9.dlz |
|---|---|
| Message-ID | <[email protected]> |
On Tue, May 12, 2009 at 2:30 PM, Mike Toler <[email protected]> wrote: > I think .pp. is for the compiler of the RPM (Peter Pramburger). The Ok, just hadn't heard of the guy. > rpm.pbone.net download page seems to indicate that I have the right > executables. Good. > Executable is definitely a file, not link. And it has the MySql and > Postgres libs. I'm just at a loss. > . . . > libmysqlclient.so.15 => /usr/lib64/mysql/libmysqlclient.so.15 > (0x0000003b6e000000) > libpq.so.4 => /usr/lib64/libpq.so.4 (0x00002ae007249000) > libsqlite3.so.0 => /usr/lib64/libsqlite3.so.0 > (0x0000003bba400000) Good. > > I'll try turning up the logs in the named.conf file and see what > happens. I would do as the other poster said and trim down your dlz config to just the first two things. You say that there is no data and that's fine. But the tables it's trying to query do exist, right? Even so, I would NOT expect that to mask the SDB debug output as the named_sdb starts up. Find and fix that, and you'll be on your way. Oh, and make sure that you can connect from localhost to the specified db as the specified user. If you can't connect, bind_sdb won't be able to either. -- 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