|
||||||||||||||||||||||||||||||||||||||||||||
Kopie van http://www.swart.org.za/wordpress/urrgghh-frontpage.htmVoor eigen notes 20 December 2007: I have found enough time to spend hours on debugging the problem and I have successfully been able to get mod_frontpage working on my CentOS 5 server running Plesk 8.2.1 and Apache 2.2. I have updated the article below where needed.Version 8.0.1 was also never released for CentOS5 or Red Hat Enterprise Linux 5 (RHEL5), which means that there are effectively no RPMs for FPSE, that was compiled against Apache 2.2.x. You will need one of the older SWSoft FPSE RPM’s. I used frontpage-5.0-72psa.centos4.2 and frontpage-5.0-72psa.rhel4. The RPMs are located in the Plesk 8.0.1 .tar.gz file, in the ./opt/fpdirectory. You will need to install one of the above RPM’s onto your system. Once installed, do the following:
You should now have a frontpage-5.0.tgz file, that will be used. You need rpm-build Copy the frontpage-5.0.tgz to /usr/src/redhat/SOURCES
crash provided the following patches to have mod_frontpage compile against Apache 2.2.x. (The patches should allow you to compile mod_frontpage against Apache 2.0.x or Apache 2.2.x [There are a few tiny differences]) Download the patches: FrontPage Server Extension Patches for CentOS5 and Apache 2.2.x (The file was updated on 20 December 2007) You need to have the httpd-devel RPM installed. Now do the following:
If all goes well, the RPM build process should complete without any errors and you will have a brand new RPM to install FPSE with on CentOS5/RHEL5.
Credit to crash’s post. I discovered a few bugs in the patches originally provided by crash.
Tags: apache, centos, fp, fpse, frontpage, httpd, mod_frontpage, Plesk, rhel, rpm 9 Responses to “Urrgghh …. FrontPage!”
7920 |
I’ve found a problem in that patch you linked, that may explain why your FrontPage isn’t working….
at about line 840 after applying the patches… there is a part that is invalid… the patch made these changes…
- ap_table_set(r->notes,”FPexecfilename”, ap_pstrcat(r->pool, FPSTUB, NULL));
- r->filename = ap_pstrcat(r->pool, r->filename, szCgi, NULL);
+ execFilename = apr_pstrcat(r->pool, FP, szDir, szBuf, szBase, NULL);
+ apr_table_set(r->notes,”FPexecfilename”, execFilename);
which were not correct for what is being done, the first of those new lines should really be
execFilename = apr_pstrcat(r->pool, FPSTUB, NULL);
instead of …. FP, szDir, szBuf, szBase… as was incorrectly put in the patch
some of those (szDir/szBase) are uninitialized variables that make random stuff in the log like
“attempt to invoke directory as script: /usr/local/frontpage/version5.0\xa4\xc4\xcf\xbf_\xaf\xbf\xb7\xc0\xc4\xcf\xbf\xe6\xe1\x1f\xb7\x022523\xa5\n”
Now, if only I could figure out why it refuses to accept my password for the FPadmin login, i’d be all set.
@codepoet
You are indeed correct. That was part of the problem. The major problem however was that the patches that I made use of literally altered a piece of the mod_frontpage code. When I looked at the original Apache 1.3 code I discovered the problem and re-created the patches.
Have you made sure that all the permissions on the FPSE files are correct by running the set_default_perms.sh script in the /usr/local/frontpage/version5.0/ directory?
@carl
Yeah, I managed to get it figured out shortly after my last post here. Ended up needing to delete/re-add the domain into Plesk, not sure what exactly I’d broken, but that made everything start working again.
Thanks,
-Kenneth
The FP Webadmin layout is screwed up. I’m testing in Firefox, but th FP Webadmin looks fine on servers running “original Frontpage-module”, so there must be something wrong with this patched version. I’ve checked and the styles (webadmin.css) and images seem to be in the correct directories with the right permissions…
Anyone figure this out?
@CiViX
Sorry but everything on my side is working 100%. It has now been 10 days and all the clients are happy.
The only suggestion I have is to for you to start from the beginning.
Sorry that I can not be of more assistance.
Upgraded to apache 2.2.6 and now the Frontpage-support seems to be broken again :-/ Have any of you experienced this or found any fix? Would it be sufficient just to recompile the frontpage-rpm do you think?
Ah, seems the problem was that the httpd-update had overwritten the suexec. I fixed it by following this info: http://kb.swsoft.com/en/1322
(Btw, the upgrade was not to httpd-2.2.6, just from 2.2.3-10 to 2.2.3-11.)
At least one person has reported PLESK 8.3 breaking the new Frontpage-support. This seems unplausible to me as PLESK itself shouldn’t affect mod_frontpage?
Have any of you tried upgrading to PLESK 8.3, and did it screw up Frontpage or did it work fine?
@CiViX
I have only upgrade RHEL 4 servers running Apache 2.0.x to Plesk 8.3 and FrontPage continued working on all of them.
Thinking about your statement, yes, Plesk does not affect mod_frontpage. Plesk only controls Apache’s configuration files.