Problem Installing Apache-MP3 on FreeBSD

Hi,

My first post here.

I have a FreeBSD system with Apache 2.0 installed. I tried installing the Apache-MP3 software via the ports collection (navigate to the port folder for the program, type "make install clean"). It installed the program and all the other required programs.

I then configured my httpd.conf file according to the readme file. When I tried to restart the Apache server, though, it gives me the following error:

"Syntax error on line 357 of /usr/local/apache2/conf/httpd.conf:
Invalid command 'PerlHandler', perhaps mis-spelled or defined by a module not included in the server configuration"

After Googling that error, it looks like it is because I don't have a "LoadModule" line in my httpd.conf for mod_perl. I tried to find the mod_perl.so file but it is nowhere to be found on my machine. I deinstalled mod_perl, and then reinstalled it and still can't find it. I need to know its location in order to point the LoadModule line to it, right?

For the record, I tried installing PHP 4 recently and thought that everything went properly, but when I tried to test it out, it didn't work. I had to manually copy the PHP 4 .so file to the right location, but it still won't work. Is it possible that I have Apache installed in a way that doesn't support shared objects or something?

When I issue an "httpd -l" command, here's what I get:

Compiled-in modules:
http_core.c
mod_so.c
suexec: disabled; invalid wrapper /usr/local/sbin/suexec


When I run "httpd -V", I get the following:

Server version: Apache/1.3.31 (Unix)
Server built: Jun 29 2004 16:26:55
Server's Module Magic Number: 19990320:16
Server compiled with....
-D HAVE_MMAP
-D USE_MMAP_SCOREBOARD
-D USE_MMAP_FILES
-D HAVE_FLOCK_SERIALIZED_ACCEPT
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D DYNAMIC_MODULE_LIMIT=64
-D HARD_SERVER_LIMIT=512
-D SO_ACCEPTFILTER
-D ACCEPT_FILTER_NAME="httpready"
-D HTTPD_ROOT="/usr/local"
-D SUEXEC_BIN="/usr/local/sbin/suexec"
-D DEFAULT_PIDLOG="/var/run/httpd.pid"
-D DEFAULT_SCOREBOARD="/var/run/httpd.scoreboard"
-D DEFAULT_LOCKFILE="/var/run/httpd.lock"
-D DEFAULT_ERRORLOG="/var/log/httpd-error.log"
-D TYPES_CONFIG_FILE="etc/apache/mime.types"
-D SERVER_CONFIG_FILE="etc/apache/httpd.conf"
-D ACCESS_CONFIG_FILE="etc/apache/access.conf"
-D RESOURCE_CONFIG_FILE="etc/apache/srm.conf"


If there's another forum or website that would be better/more appropriate to ask this question, please point me in that direction.

Thanks.....Doug

Howdy Doug.. welcome to the DevShed,

The "mod_so" is compiled into apache, so your good there. The dynamic modules should work fine. As far as mod_perl.so goes, did you use find to locate it?

If you are using locate, is the locate's database current? (i.e. have you run locate.updatedb)

Are you possibly searching as an un- or underprivileged user?

...try looking in:

/usr/local/libexec/apache2/

-Steven

I *did* use "find" to try to locate mod_perl.so, and just now ran it again exactly the way you typed it. I ran the command while superuser and am not able to locate mod_perl.so

I tried looking in the location you specified:

/usr/local/libexec/apache2/

I actually don't have a folder called "apache2" in libexec. I have one called "apache", though. There were lots of other .so files in there, but not mod_perl.so

Thanks for any help you or others can provide. I don't have very many resources I can turn to for Unix help.

Doug

I just noticed that you are actually running apache 1.3. :

Okay...I've been wondering that. I'm an idiot, I guess. It says Apache2 in several locations, so i assumed it was Apache 2.0. I guess not.

Does that change things at all? Any further advice?


Thanks......Doug

Did you notice any errors during the installation (make install distclean) of mod_perl?

-Steven

Hi Doug,

I deinstalled apache-2.0.50 and mod_perl-1.99.4(mod_perl2) which used mod_perl.so.

I then installed apache-1.3.31 and mod_perl-1.29 from the ports. Viewing the last lines of the installation output:



you can see that it creates a backup of the current httpd.conf and replaces it with a modified version. It adds the following two lines:



before that it copied the libperl.so to said directory.

Further, it creates the directory /user/local/include/apache/perl/ and copies the necessary header files into it. If these steps were all successful, I would bet that your mod_perl is installed. Just don't forget to restart the httpd to activate the new module:

kill -HUP [PID_of_httpd]

or better:

apachectl restart

-Steven

Well, I tried pointing to that file and I'm not getting that error anymore...unfortunately, I'm now getting a different one. Here's what happened when I tried to start apache after modifying the httpd.conf file:

./apachectl start

Syntax error on line 259 of /usr/local/apache2/conf/httpd.conf:
Cannot load /usr/local/libexec/apache/libperl.so into server: /usr/local/libexec
/apache/libperl.so: Undefined symbol "ap_null_cleanup"


It sounds like maybe that "ap_null_cleanup" error is somehow related to installing the wrong version of mod_perl. Maybe I need 1.99 or something to run with Apache 2 (why is it version 1.3.xx if they're calling it Apache 2?).

If you've got any thoughts, I'd sure appreciate the help. I really want to get this darn mp3 streamer going.

I'm going to try installing mod_perl 1.99.x to see if that helps.

you will have a mess if your apache13 is looking to the apache2 httpd.conf. That is odd behaviour. Maybe it is caused by a command line option. What is the output when you type in the following:

ps -aux| grep httpd

the last column contains the command and any options...

-Steven

When I do it as myself (dsdavis) it's this:




When I su to root and enter that command, I don't get any results.

Does that mean anything?

Hi Doug,

I don't check my inbox often, but I finally got your pm.

ps didn't show apache, because it is not running, likely due to the fact that it is choking on the conf file.

I am no expert, but it appears you have had multiple binaries (installations) at one time on your system and somehow apachectl ís confused and is crossed the wrong binary with the wrong configfile (in this case, two wrongs don't make a right). To make this as painless as possible, I would suggest deinstalling apache and apache2 (and deps) with pkg_deinstall (or by descending into the ports tree and using 'make deinstall') and then deciding on a version and installing it. Make sure that all the old stuph is gone before reinstalling ('find' and remove all occurences of httpd and apachectl and get rid of the /usr/local/etc/apachex folders).

My apologies for the late and, admittedly, somewhat terse answer.

-Steven

Steven,

Thanks for all the help you've provided. I think I'm going to just start from scratch on a new computer. The one I have been having problems with is technically a "production" server with live webpages that get quite a few hits, so I shouldn't be mucking about, anyway.

I'll just do it all the right way on the new system.

Thanks, again!