From: David R. <dr...@ri...> - 2001-01-29 20:40:48
|
Andre - Thanks for the advice, however, after checking all of the permissions, I still am getting the same error (see original message below). Any other ideas - anyone? All help is most appreciated. - David -----Original Message----- From: Andre Felipe Machado [mailto:and...@te...] Sent: Monday, January 29, 2001 12:56 PM To: sql...@li... Subject: [SQL-Ledger-users] Re: Problems with logging in to sql-ledger Hello, I am a newbie, but I struggled with similar problem. Well, your dbd:pg and dbi installations found "utils" at @inc include path. Fine. But I guess that your problem is with directory and file permissions to Apache. Try to set utils subdirectory, and its files, to user and group nobody.nobody (or nobody.nogroup at some distributions) default Apache user and group settings permissions. Also, check for executable and read write permission. Good luck. Andre Felipe Machado >>>>>>>>>>>>>>>>>> Mensagem anterior <<<<<<<<<<<<<<<<<< No dia 29/01/01, 12:21:14, David Rippel <dr...@ri...> escreveu o seguinte sobre o tema [SQL-Ledger-users] Problems with logging in to sql-ledger: > I've got everything working up to this point, but when I go to my login.cgi > and attempt to authenticate, here's what shows up in my error_log (from > apache) > install_driver(Pg) failed: Can't locate loadable object for module DBD::Pg > in @INC (@INC contains: utils /usr/lib/perl5/i386-linux /usr/lib/perl5 > /usr/lib/perl5/site_perl/i386-linux /usr/lib/perl5/site_perl .) at (eval 1) > line 3 > Compilation failed in require at (eval 1) line 3. > Perhaps a module that DBD::Pg requires hasn't been fully installed > at /usr/local/apache/htdocs/sql-ledger/login.cgi line 66 > [Mon Jan 29 09:19:20 2001] [error] [client 192.168.3.179] Premature end of > script headers: /usr/local/apache/htdocs/sql-ledger/login.cgi > I've done a full make install for both DBI and DBD::Pg, and all the tests > complete successfully. The paths for the postgres libs are in my global > ldconfig. There is a valid user for the system and no errors are coming from > the database end (in other words, I don't think it's getting that far). Any > ideas? > Thanks, > David. |