Maximum execution time exceeded.

I migrated over a stack of blogs to my new Dolphin 7 setup today. It worked beautifully.

A litter later I went to write a blog manually. I hit submit and I got this error.

Fatal error:  Maximum execution time of 30 seconds exceeded in /var/www/vhosts/<domain-name>/httpdocs/community/plugins/phpids/IDS/Monitor.php on line 498

I SSH'd in, changed php.ini to reflect 120 seconds (that should be plenty), restarted. Tried again.

This time I got this error after a 2 minute wait.

Fatal error:  Maximum execution time of 120 seconds exceeded in /var/www/vhosts/<-domain-name>/httpdocs/community/plugins/phpids/IDS/Monitor.php on line 498

It has me a bit perplexed. I'm not sure where to look to solve this one.

Any suggestions are appreciated.

Cheers!

Happened to me aswell but I copied and pasted something from a word file. Seems like they didn´t fix it till now

Yup you are correct.

The blog I was entering had been cut & paste from an email. I think it considers the spaces between paragraphs as white space etc. Not to mention any embedded stuff.

It appears that all of the security scanning can take some time on a larger blog.

I increased PHP execution time to 3 minutes. It worked. Well kind of. I got one of those "Security Attack" messages.

After increasing security threshold impact to 75 I finally got the blog through.

I obviously feel a little uncomfortable leaving it at 75 when it should be a little closer to 25. Hopefully this will be addressed soon as it's not impossible to picture bloggers cutting and pasting their content from an external editor.

Gotta love computers.

Cheers!

it may help if you have cache turned on?

im not too sure about this whole security gimmick to tell you the truth. if a site is maintained and the server has any type of security at all, this site was rather safe on 6.1.6 without all the BS of checking every move you make.

what gets me is that if a member is logged in these attack messages are going to phreak them out to the point that they may never return to the site. i think that was a bad choice in words as a display, and furthermore i think the security could have been written a little more user-friendly for the dolphin environment.

with all of the interaction that a user would have with this site, i dont feel that any of it was tested once the security gig was implemented.

Regards,

DosDawg

So let me get this straight, I have to turn off or down security in the advanced settings to stop this purifier going nuts? Is that the "Total security impact threshold to send report" and "Total security impact threshold to send report and block aggressor" fields? Crank them down to zero yeah?

A user on my site got the same error. I was able to replicate it after they sent the text through with the formating i.e.

"Fatal error: Maximum execution time of 30 seconds exceeded in
/home/cbass/public_html/socialathens.com/plugins/phpids/IDS/Monitor.php on line 498"

When I removed all the formating it went through fine. People regularly put things into Word first and then paste things into a blog. One very scary thing I noticed was that during that 30 second my server CPU usage hit 100% for this activity and the website nor any other website on the server would work until the offending php process had finished its paranoid scanning activity.

No, you turn the numbers up. The higher the number, the more tolerant it becomes. Or -1 to disable.

But i am not convinced -1 completely shuts it off. I still believe it is run through the filter anyway so timeouts might still ocure if your max execution time setting in your php.ini is set to low.

Thanks Deano. I really do not want to set the time out too high as 30 seconds 100% CPU activity is more than I can bare. Nothing has ever caused the CPU activity to flip out like that until now. Highest I have ever seen it is 4%. I shall try disabling it with -1 and take it from there. Thanks for the input Bro!

Sorry. I should say that I have seen it spike to 100% but only briefly. Never have I seen it at 100% for almost 30 seconds.