Front page author.exe %CPU 99.9

rockster

Well-Known Member
Apr 19, 2003
63
1
156
we are having a problem with front page for one web site.

the following demonstrates that the site is using .99 percent of CPU when they use frontpage to update their site.....

******************

User Domain %CPU %MEM Mysql Processes
mXXXX mXXXXXXXX.org 0.91 0.16 0.0
Top Process %CPU 99.9 /usr/local/frontpage/version5.0/exes/_vti_bin/_vti_aut/author.exe
Top Process %CPU 62.0 /usr/local/frontpage/version5


*********************

anyone have this occurring?


thanks

rock

cPanel.net Support Ticket Number:
 

Website Rob

Well-Known Member
Mar 23, 2002
1,501
1
318
Alberta, Canada
cPanel Access Level
Root Administrator
Although I don't have this problem, it would be good to know, if you are using Apache 1.3.28 and also what version of FP is being used by the Client.

Just noticed a Client using FP and Server load is at .04 -- I use Apache 1.3.27, not sure what version of FP the Client is using.
 
Last edited:

rockster

Well-Known Member
Apr 19, 2003
63
1
156
WHM 6.4.2 Cpanel 6.4.2-S75 RedHat 7.3 -
Apache Core 1.3.28
FrontPage 5.0.2.2634

dual xeon system with 2 gigs ram...

have to find out what is what here...

cPanel.net Support Ticket Number:
 

andyf

Well-Known Member
Jan 7, 2002
249
0
316
UK
Was this ever solved? Just come accross a very similar (if not the same) problem.
 
C

cPanelBilly

Guest
Does anyone have a ticket # so I can look into the issue?
 

dave9000

Well-Known Member
Apr 7, 2003
888
1
168
arkansas
cPanel Access Level
Root Administrator
Is the %99 process level staying active or is the high load only happening while the authoring is actually going on ?

FP will use all available resources during active authoring.

If the high load levels are only occuring when someone edits a page then this is normal behavor
 

andyf

Well-Known Member
Jan 7, 2002
249
0
316
UK
My ticket on this was resolved by cpanel. In my case this was caused by a word doc (.doc file) in the web root of the account. Removing/moving this elsewhere resolved the problem.

Hope this helps!