
madmardy at madmardy
May 22, 2000, 7:01 PM
Post #5 of 58
(3183 views)
Permalink
|
I have tried pulling in *any* DBI or DBD module one at a time and ALL of them cause the server to fail to start. There is no error log message. This is true whether I use the PerlModule config directive, or 'use' the module in the script defined in the PerlScript directive. I have other modules in the script, and until the database module is used, it starts OK. Is there an order I must use them in? Apache::DBI installed without a hitch, are there other pitfalls of which I should be aware? Perrin Harkins wrote: > On Mon, 22 May 2000, Mark Holt wrote: > > > Newbie to the list, apologies if this is a FAQ, but I checked the > > archives... > > I built a modperl-enabled server, (Apache/1.3.9 Ben-SSL/1.37 (Unix) > > mod_perl/1.21) and have been running it for some time. I have the > > mod_perl as a shared module, and I recently enabled it to start > > development. I have a startup script in operation and things work fine, > > until I try to preload any sort of DBI module. I tried Mysql, > > DBI::mysql, Apache::DBI, all to no avail. The server gives no error > > message, it simply acts as though it is starting, but does not show up > > in the process list. Is there something I'm missing? > > Are you pulling in the DBI and DBD modules in your startup.pl? Is there > any message in the error_log? Apache::DBI is not at all like DBD::mysql, > so it sounds like you may have a problem totally unrelated to DBI. > > - Perrin
|