Wow... do I have a major problem.

Everything was working and without doing a thing I can't host Fmphp anymore. plain html is possible and plain php also.

This is the message when I try to request index.php:

[color:red]Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 393216 bytes) in /Library/WebServer/xImI/FileMaker/Implementation/Parser/FMResultSet.php on line 72

The Filemaker is working (it adds a line on entry of the request) and also IWP is hosting without problems.

But where do I need to look? Is it a apache thing that causes the error.

I run a Xserve 10.5.6 FmServerAdvanced 9.0.3.326 (as client FMProAdvanced 10)

Kind regards,

Xim

Do you have 32MB+ of unutilized ram?

Well as a starter you're running an unapproved OS, so it's very likely something is afoot at the OS level, possibly with Apache. Do you have another machine running 10.5.4 you can try this on?

Steven

it's very likely something is afoot at the OS level, possibly with Apache

With all respect, doubtful in terms of the Apache linkage. It is PHP that allocates the memory and PHP that's outputing the error. Looking at the error again, it seems that the FMResultset script is using greater than the 16mb of allocated memory - for whatever reason (either the script itself is flawed and stuck in some sort of recursive loop or fms is outputting mass amounts of xml via cwp - that being said 16mb its pretty excessive)

Edited January 11, 200916 yr by Guest

Do you have 32MB+ of unutilized ram?

Can you help me out how to answer this question?

The only app running on the server is FmServerAdv. The machine has 2Gb ram. That should do the trick I think.

I have restarted the server and it didn't change. I'm afraid I have not enough knowledge of php or unix to solve this on a skill level. ... I think I'm lost..

What I can do (but I rather don't) is a clean install of the OS. The server is about 300km away from my location. Remote install is a option but you understand... I would like to know where this all came from or how it occurred.

either the script itself is flawed and stuck in some sort of recursive loop or fms is outputting mass amounts of xml via cwp - that being said 16mb its pretty excessive

Is there a tool to monitor this process?

Don't re-install the OS. What's changed from when it was working?

What's in index.php?

I can't recall anything or anyone changing the system or the files.

I created a fresh "test" db and also a test.php but that came up with the same error.

I created a info.php and that worked just fine.

Even getting the source from the "error" index.php takes a while. Looks like it is trying to get something from the server but I can't find or see it.

I can send the index.php to your mail account for security reasons.

Tia,

Genx, I think I located the problem.

I took a closer look at the index.php and cleared the code that adds a log line to a different db.

That worked. So It seems the log is the problem.

I think I can get around this by creating a form submit that adds a line to the log.

Thanks for thinking with me. And If I may can I contact you for some questions regarding FMfunctions etc? I need to learn some basics and it seems you are a master in it. :.

You can contact me directly only if you're really desperate :

Just post in the forums first, there are a couple of experts in the area other than me who can contribute as well. Plus ists better if everyone has access to this info later :)