FrontPage Permissions Problems. Help requested.

[Drake]

Hi Folks,


Will someone please shed some light on this Front Page malfunction for me?

I did a brand new build to replace an aging and crashing server, now we've got Front Page problems.

WHM 11.15.0 cPanel 11.17.0-C19353
Apache Version 1.3.39
Cpanel::Easy::Apache v3.2.0 rev3624
Operating System: Fedora 7
Frontpage Version 5.0


I had to import the accounts by using Restore, from the old server's CP Backup tar-ball backups.


./sh latest Originally installed as it "Stable" tree, but then even tried changing to "CURRENT" tree to see if I could eliminate any random potential bug. Still no F.P. succes.


Have tried uninstalling and reinstalling FP extensions on the domains.

Have even created a new account with one of our spare domain names in order to not cause damage to a customer's account, as well as ruling out any corrupted files / perms on the accounts imported from the old server/

Have ran scripts: fixfrontpageperm, initfpsuexec, and also updatefrontpage

Originally installed as "Stable" tree, but then even tried changing to "CURRENT" tree to see if I could eliminate any random potential bug. Still no succes.

Even ran upcp with the --force option.


***************
The FrontPage Client receives this message:

500 Internal Server Error
Internal Server Error The server is temporarily unable to service your request due to Cannot open /home/USERNAME/public_html/_vti_pvt/service.pwd uid=99 gid=99 99.
***************
(The FP Client error changes after I have tried altering file perms, see below)


I had tried various adjustments to the permissions and ownership of "service.pwd" and even the _vti_pvt directory.

Then the FP Client error message changed slightly to say that UID 99 couldn't read /usr/local/apache/conf/sites/DOMAIN-NAME.conf

Next tried adjusting ownership & group and permissions of the DOMAIN-NAME.conf file. Still no success.

Have also tried changing owner & group for service.pwd. Even made it world readable as a debugging test. No success.

When I run /ust/local/apache/bin/httpd -l (lower case L) I confirm that FrontPage IS compiled in. Mod Security is NOT compiled in, nor is it in use as a DSO.

It appears that Apache SU Exec is enabled, output as follows:
suexec: enabled; valid wrapper /usr/local/apache/bin/suexec


I can confirm that my suspicions about file perms and ownership are true via /usr/local/apache/logs/error_log and also /var/log/messages.


This one seems really odd too.
If Apache Su Exec is enabled, then why are the files trying to be accessed by UID 99 (nobody) ?

The closest I can get to FP access (by massaging the DOMAIN-NAME.conf and _vti_cnf/service.pwd) is a FrontPage client listing all the directories, but when you try to create a "new page" which is a "write" function, the FrontPage client asks for user name and password again, and again, and again, then fails.

I have attempted to utilize various versions of MS FrontPage client including FP-2000 t0 FP-XP.

I really don't want to be bald from pulling out my hair, but this definitely seems to be some sort of file permissions problem.

Any help from other CPanel or other bulletin board members would be appreciated.

Thanks,
~Drake

 

[TheStarKillers]

Having this same exact problem

 

[Drake]

Another question about my Front page permissions issue.

Is the Front Page RPM necessary ? (my system stats are located just below)
Can someone confirm this for me?

rpm -qa reveals no front page rpm's, but is it really necessary anymore in RPM on the new builds?


Also, does anyone know if changing from Current Release to Edge will fix the front page problem?
I had went from Stable to Current but no success. I'd rather not go up to bleeding Edge unless absolutely necessary.

Thanks,
~Drake P.


WHM 11.15.0 cPanel 11.17.0-C19353
Apache Version 1.3.39
Cpanel::Easy::Apache v3.2.0 rev3624
Operating System: Fedora 7
Frontpage Version 5.0

 

[sitekeeper]

rpm -qa shows "frontpage-2002-SR1.2" as being listed.
WHM 11.15.0 cPanel 11.17.0-S19434
CENTOS Enterprise 4.6 i686

Can you get to the frontpage admin panel?

Bob

 

[cPanelNick]

Try

/scripts/initfpsuexec

 

[sitekeeper]

Have ran scripts: fixfrontpageperm, initfpsuexec, and also updatefrontpage

Thanks,
~Drake

The OP said he tried initfpsuexec which I would have thought should fixed it.

Bob

 

[Drake]

I had tried initfpsuexec, but no success. Even afterward, had uninstalled & re-installed FP extensions on the FP customers' accounts. Still no succes.

Can I get to the FP Admin panel? If you mean the WHManager section to install & uninstall FP Extensions... Yes, I have that. But if you mean some other FP Admin panel? then I don't know what you're spealing of.

 

[sitekeeper]

Try going to http://domain.com/_vti_bin/_vti_adm/fpadmcgi.exe?page=webadmin.htm replace domain.com with one of your frontpage domains. You will be at FrontPage's admin panel. Login with the frontpage users name and password. If this does not come up frontpage is not installing properly on the server.

Bob

 

[Todd Mitchell]

Check to make sure SuExec is enabled within WHM >> SuExec & PHP Config editor.

If it is set to Off, change this to On then run /scripts/initfpsuexec.

See if that helps the problem at all.

 

[Drake]

Have got FP Extensions working.

Thanks all, for your replies. I finally used a combination of the various suggestions to get it working.

It seems that the following steps corrected the Front Page files permissions that I had originally created this posting about.... upgrading from stable to current, and doing a /scripts/upcp --force, then enabling suexec in the PhP & Suexec menu, then running /scripts/initfpexec Then, of course, any acount that had FP extensions installed, had to uninstall & reinstall them. I can not say if the exact sequence I performed those steps was critical, but the issue corrected iteslf. Since it was a brand new CPAnel installation, who knows,,,, maybe something was corrupted, even an FP install script. However, when I suddenly saw blank (no options) in the pull-down menu in PhP & Suexec, I knew knew something had to be --force updated.

Thanks again all who replied !!