Thanks guys, it works! The lib/dbd directory was indeed empty, and I recompiled the libdbi-drivers with the correct switches: ./configure --disable-docs --without-oracle \ --with-dbi --with-dbi-incdir='${prefix}/include/' --with-dbi-libdir='${prefix}/lib/' \ --with-freetds --with-mysql --with-pgsql \ --with-sqlite3 --without-sqlite \
From the bash file and everything works sweet as! thank you once again for the help:)
On 15 March 2011 23:19, Balazs Scheidler <bazsi@balabit.hu> wrote:
On Mon, 2011-03-14 at 12:54 +0200, Hendrik Visage wrote:
On Mon, Mar 14, 2011 at 6:37 AM, Eshan Bhide <ebhide@globalgossip.net> wrote: Hi Hendrik,
Still having this problem of "No such DBI driver; type='mysql'"
Strace is attached at:
I see libdbi getting loaded, but what I am missing in that strace, is the libdbi searching for it's drivers....
your dbd directory seems empty:
[pid 63416] open("/usr/local/lib/dbd", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 9 [pid 63416] fcntl64(9, F_SETFD, FD_CLOEXEC) = 0 [pid 63416] getdents(9, /* 2 entries */, 32768) = 32 [pid 63416] stat64("/usr/local/lib/dbd/.", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 [pid 63416] stat64("/usr/local/lib/dbd/..", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 [pid 63416] getdents(9, /* 0 entries */, 32768) = 0
As you can see, getdents() returns 2 entries, the one for '.' and the one for '..'.
No .so files there. Can you please "ls -l /usr/local/lib/dbd" to confirm?
If there are no .so files, we should find out why. Probably libdbi-drivers compilation went bad?
-- Bazsi
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html
------------------------------------------------- IMPORTANT NOTICE : The information in this email is confidential and may also be privileged. If you are not the intended recipient, any use or dissemination of the information and any disclosure or copying of this email is unauthorised and strictly prohibited. If you have received this email in error, please promptly inform us by reply email or telephone. You should also delete this email and destroy any hard copies produced.