No subject
Mon Feb 21 10:55:38 CET 2011
On 15 March 2011 23:19, Balazs Scheidler <bazsi at 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 at globalgossip.net>
>> wrote:
>> =A0 =A0 =A0 =A0 Hi Hendrik,
>>
>>
>> =A0 =A0 =A0 =A0 Still having this problem of "No such DBI driver;
>> =A0 =A0 =A0 =A0 type=3D'mysql'"
>>
>>
>>
>> =A0 =A0 =A0 =A0 Strace is attached at:
>>
>>
>> =A0 =A0 =A0 =A0 http://pastebin.com/qaJZ2ZbE
>>
>> 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) =3D 9
> [pid 63416] fcntl64(9, F_SETFD, FD_CLOEXEC) =3D 0
> [pid 63416] getdents(9, /* 2 entries */, 32768) =3D 32
> [pid 63416] stat64("/usr/local/lib/dbd/.", {st_mode=3DS_IFDIR|0755, st_si=
ze=3D4096, ...}) =3D 0
> [pid 63416] stat64("/usr/local/lib/dbd/..", {st_mode=3DS_IFDIR|0755, st_s=
ize=3D4096, ...}) =3D 0
> [pid 63416] getdents(9, /* 0 entries */, 32768) =3D 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=3Dsy=
slog-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 in=
formation and any
disclosure or copying of this email is unauthorised and strictly prohibit=
ed. If you have received
this email in error, please promptly inform us by reply email or telephon=
e. You should also delete
this email and destroy any hard copies produced.
=0D
More information about the syslog-ng
mailing list