Error Log

[testbot]

Originally Posted by Marco van Herwaarden

And how did you see this right away?

The error message is very clear and only indicates 1 thing: Not enough memory reserved for PHP.


This is not related to diskspace in any way.

Just edit your php.ini and assign at least 32 or 64Mb to PHP like already advised in the 2nd post in this thread.

For further advise please post in the server configuration forum on vB.com.

did you read the entire thread? i don't think you did.

my reply about disk space was not related directly to that error.

and i agree (as stated above) she should ask for server configuration advise over at vbulletin.com. especially for help with her cpu usage being at 100%.

anyway, sorry for getting involved. i had some downtime yesterday between meetings and thought i would read some threads in here.

[Marco van Herwaarden]

I just re-read the entire thread, and i still don't see where the conclusion is coming from that this is related to diskspace.

PS This might come over harsh, but i see this happening a lot lately where members will offer "solutions" without having a clue of what is going on. Sometimes those "solutions" are worse then the original problem. Nothing personal.

[testbot]

it's not related to disk space. she confused memory left with disk space left and i asked "is that disk space or mem?" so my reply was just to confirm that it was not memory but rather diskspace that she was talking about. i wasn't saying, yea disk space is causing that error.

beyond the error she asked why her cpu is at 100% so i went on to explain that she probably needs to configure my.cnf and ask eva (george) over at vbulletin.com. do you deny that when you're only using 1/3 of ram and your cpu is at 100% it's probably because my.cnf is not configured to allocate enough mem for mysql? if you're only using a 1/3 of ram and your cpu is at 100% then that's a start for that.

on a side note about disk space... although the error in the first post in this thread IS NOT RELATED TO DISK SPACE you should still keep an eye on logs and files taking up disk space because linux does have it's limits. that's just a side note not related to that specific error.

Ps- this might come over harsh, but i see this happening a lot lately where staff will have tunnel vision and try to answer a thread and move on dismissing everything else that was not asked in the first post. then they insult members by calling them clueless. that doesn't mean there's some really great staff here because their is.

pps- although i might have got a little off track here i have to mention a few more things. you know what makes open source great? it's community involvement and support. i haven't made a lot of posts but the majority of the posts i've made that give assistance to someone (mostly in mod threads) i've solved their problem within one post and received a thank you in response. but since i'm clueless i'll quit posting and i'll ask all other members to stop replying to threads because we're all clueless and it's the staffs job not ours. as a matter a fact, why don't you make a sticky thread at the top of this forum and tell everyone "don't reply to threads only create them... you are clueless and we will handle it. you might have to wait a week or we might not answer at all but please don't post."

[Marco van Herwaarden]

Originally Posted by testbot

yea, right away i can see that it was disk space you're running out of.

Sorry if i misunderstood this post. I really thought you where telling that you figured out her problem and it was related to diskspace.

PS vBulletin, nor vB.org, is open source.

[testbot]

i'm sorry about my last post. it was early here and didn't have enough coffee. overall i'm very happy with vb and vb's staff.

i thought open source might be a poor choice there but i didn't feel like looking it up to confirm. i was just trying to make a point. sorry. lol