Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Frontpage Extensions 2002 on Apache 1.3.23 under FreeBSD - need help

Status
Not open for further replies.

OmegaGX

ISP
Mar 17, 2002
3
US
Hi Everyone
I spent the last few days trying to install Frontpage Extensions 2002 on FreeBSD. I did considerable research and was able to fix a lot of errors along the way. But now it seems I am finally stuck. Please help. I am going to describe below exactly what I did in detail, hoping that someone could read it and either tell me what I did I wrong or most probably what I missed. You can reply on this forum or if you could cc me your reply to kublakan60@hotmail.com, I'd really really appreciate it.
Here goes:



I am running FreeBSD 3.3-RELEASE #13.
I had mod_frontpage.c version 1.6.1. I got it from

I got fp-patch-apache_1.3.22 from
ftp://ftp.rtr.com/pub/fp-patch-apache_1.3.22.Z - I patched my source of apache with it like this:

patch –p0 <fp-patch-apache_1.3.22

I did this in the source directory of apache.
I installed Apache 1.3.23 with static support for perl and php. This is the command I used to compile the apache server.

./configure --with-layout=Apache --prefix=/usr/local/apache23 --enable-module=so --enable-module=rewrite --enable-module=auth_dbm --enable-suexec --suexec-uidmin=100 --suexec-gidmin=100 --suexec-docroot=/web1/users --activate-module=src/modules/fastcgi/libfastcgi.a --activate-module=src/modules/php4/libphp4.a --activate-module=src/modules/perl/libperl.a --add-module=mod_frontpage.c

I ran fp_install.sh but I did not replace my httpd with their stock 1.3.19 httpd without any of my modules. I kept my httpd with mod_frontpage.c module enabled.

I installed apache to /usr/local/apache23/ because I still have an old functioning version of apache for backup purposes in /usr/local/apache.
The homepage of the user who needs to have it installed is in /web1/users/u370/docs. After installation nothing changed in the httpd.conf file for some reason.

This is an excerpt from the apache log after it started:

[notice] FastCGI: wrapper mechanism enabled (wrapper: /usr/local/apache23/bin/suexec)
[notice] FastCGI: process manager initialized (pid 8361)
[notice] Apache/1.3.23 (Unix) FrontPage/5.0.2.2623 mod_perl/1.26 PHP/4.1.2 mod_fastcgi/2.2.12 configured - resuming normal operations
[notice] suEXEC mechanism enabled (wrapper: /usr/local/apache23/bin/suexec)
[notice] Accept mutex: flock (Default: flock)

This shows that everything is enabled.

Then I ran command:
./owsadm.exe -o setadminport -s /usr/local/apache23/conf/httpd.conf -port 8090 -username admin -pw password

That added the following lines to the httpd.conf
Listen 8090
Listen 80

<VirtualHost _default_:8090>
DocumentRoot /usr/local/frontpage/version5.0/admin-exes
DirectoryIndex fpadmcgi.exe
<Directory /usr/local/frontpage/version5.0/admin-exes/>
AddHandler cgi-script .exe
Options ExecCGI
</Directory>
</VirtualHost>



User370 has domain mydomain.com and his httpd.conf entry looks like this:

<VirtualHost 192.168.0.15>
DocumentRoot /web1/users/u370/docs
ServerName mydomain.com
ServerAdmin root@mydomain.com
LogFormat &quot;%h %l %u %t \&quot;%r\&quot; %s %b \&quot;%{Referer}i\&quot; \&quot;%{User-agent}i\&quot;&quot;
TransferLog /web1/ErrorLog /web1/User u370
Group u370
ScriptAlias /cgi-bin/ /web1/users/u370/docs/cgi-bin/
Alias /site-stats /web1/http-stats/u370/
</VirtualHost>

So, now I tried adding the Frontpage 2002 extensons support for that user. I tried it using this command:
./owsadm -o install -s /usr/local/apache23/conf/httpd.conf -p 8090 -m mydomain.com -u u370 -pw password -xu www

But here it gave me this error:
Note: Local version of Apache must use the FrontPage Apache patch.
Error: 'mydomain.com:8090' server is not a valid virtual server.

I didn't know what to do at this point. I tried going to but it gave me an error saying - unauthorized access. So I edited the httpd.conf entry to look like this:
<VirtualHost _default_:8090>
DocumentRoot /usr/local/frontpage/version5.0/admin-exes
DirectoryIndex fpadmcgi.exe
<Directory /usr/local/frontpage/version5.0/admin-exes/>
AllowOverride All
Order allow,deny
Allow from all
AddHandler cgi-script .exe
Options ExecCGI
</Directory>
</VirtualHost>


I basically added these options:
AllowOverride All
Order allow,deny
Allow from all

Now when I went to - it gave me a login prompt. I logged in with l: admin p: password. And was able to extend the server to mydomain.com. This created these directories in /web1/users/u370/docs

drwxr-xr-x 4 u370 u370 512 Mar 17 13:47 _vti_bin
drwxr-xr-x 2 u370 u370 22528 Mar 17 13:48 _vti_cnf
-rw-r--r-- 1 u370 u370 1754 Mar 17 13:47 _vti_inf.html
drwxr-xr-x 2 u370 u370 512 Mar 17 13:47 _vti_log
drwxr-xr-x 2 u370 u370 512 Mar 17 13:48 _vti_pvt
drwxr-xr-x 2 u370 u370 512 Mar 17 13:47 _vti_txt

with various .htaccess files and other _vti files and subdirectories in them. However, the user still cannot publish using frontpage and the command
./owsadm.exe -o install -s /usr/local/apache23/conf/httpd.conf -p 8090 -m mydomain.com -u u370 -pw password -xu www

still doesn't work.
What am I doing wrong? There were no other changes to the default httpd.conf. Should there be any other entries there that let that user use Frontpage Extensions? Any other command I forgot to run? I wrote exactly what I did, above.

Any tips, help, comments, suggestions would be greatly appreciated. I spent so much time on this already.

I used these sites as reference:


Thank you very much for any help.

Mike.
 
I made some progress: I ran this command and here's what happened:

bash-2.03# ./owsadm.exe -o install -s /usr/local/apache23/conf/httpd.conf -m mydomain.com -u u370 -pw password -xu www
Note: Local version of Apache must use the FrontPage Apache patch.
Starting install, port: mydomain.com.

Created: 17 Mar 2002 18:47:45 -0000
Version: 5.0.2.2623
Server extensions already installed on port mydomain.com.
Reverting to upgrade.

Starting upgrade, port: mydomain.com.

Created: 17 Mar 2002 18:47:45 -0000
Version: 5.0.2.2623
Chowning Content in service /.
Port mydomain.com: Upgrade completed.
Upgraded Version: 5.0.2.2623.



It doesn't look like I can connect though.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top