Re: problem getting work mod_log_sql under gentoo with apache2
blue-dragon <[email protected]> Tue, 02 May 2006 18:08:38 +0200
| Newsgroups | gmane.comp.apache.mod-log-sql |
|---|---|
| Message-ID | <[email protected]> |
Hi, thanks for all replys. No my http.conf has no errors and the modul is load correctly. But there are still some errors: i connected a few times to my server and there are now some log lines in the tables. But i think they are not correct. - the tables notes,headers_in,headers_out,notes are after ca. 100 connections from the internet still empty - there are some new tables like access_83.186_134_27 etc. - but i want that all accesses are logged in the access_log - in the access_*ip* tables there are some values, but these fields are always(!) empty: id, agent, child_pid, cookie, machine_id, request_file, remote_logname, request_line, request_time, request_args. server_port, ssl_cipher, ssl_keysize, ssl_maxkeysize... with empty i mean "null" - the access_log table is empty..... Hoping for your help again Max Bob Apthorpe schrieb: > Hi, > > blue-dragon wrote: > >> here I am again, >> i think now i know whats the error by take a look at the startuperror >> log from apache. >> The error is by trying to load the module; >> i tried two diferent versions witch i found on some internet sites: >> here are the two versions with the errors i become: >> >> LoadModule log_sql_mysql_module modules/mod_log_sql_mysql.so >> >> Cannot load /usr/lib/apache2/modules/mod_log_sql_mysql.so into server: >> /usr/lib/apache2/modules/mod_log_sql_mysql.so: undefined symbol: >> log_sql_register_driver >> >> LoadModule sql_log_module libexec/mod_log_sql.so >> >> Cannot load /usr/lib/apache2/libexec/mod_log_sql.so into server: >> /usr/lib/apache2/libexec/mod_log_sql.so: cannot open shared object file: >> No such file or directory >> >> Can anybody help my? >> I think its an very easy error but i never tried to use a module or >> configure my apache so i dont understand wats going wrong >> > > Make sure that log_sql is loaded before log_sql_mysql. Also, use > absolute paths to specify the modules to load, e.g.: > > LoadModule log_sql_module /usr/lib/apache2-prefork/mod_log_sql.so > LoadModule log_sql_mysql_module > /usr/lib/apache2-prefork/mod_log_sql_mysql.so > > instead of > > LoadModule log_sql_mysql_module modules/mod_log_sql_mysql.so > LoadModule sql_log_module libexec/mod_log_sql.so > > This error message looks like it's caused by modules being loaded in the > wrong order: > > >> Cannot load /usr/lib/apache2/modules/mod_log_sql_mysql.so into server: >> /usr/lib/apache2/modules/mod_log_sql_mysql.so: undefined symbol: >> log_sql_register_driver >> > > I've been bitten by this, especially when upgrading. The solution was to > load log_sql_module before log_sql_mysql_module. Think of it as loading > the generic SQL logging module followed by the database-specific module. > > The second error message is more straightforward: > > >> Cannot load /usr/lib/apache2/libexec/mod_log_sql.so into server: >> /usr/lib/apache2/libexec/mod_log_sql.so: cannot open shared >> object file: No such file or directory >> > > Does /usr/lib/apache2/libexec/mod_log_sql.so exist? If not, you need to > change the path or put the file there. This is why specifying an > absolute module path helps - there's no guessing where > libexec/mod_log_sql.so is supposed to be loading from. > > hth, > > -- Bob > _______________________________________________ > Download the latest version at http://www.outoforder.cc/projects/apache/mod_log_sql/ > > To unsubscribe send an e-mail to > mod_log_sql-unsubscribe-7qY7E20V6GW73k+5HYS8LQqVMODqnSLI@public.gmane.org > > _______________________________________________ Download the latest version at http://www.outoforder.cc/projects/apache/mod_log_sql/ To unsubscribe send an e-mail to mod_log_sql-unsubscribe-7qY7E20V6GW73k+5HYS8LQqVMODqnSLI@public.gmane.org