Problem

[Frisky]

Warning: main([path]/includes/functions_bigthree.php): failed to open stream: Cannot allocate memory in [path]/forumdisplay.php on line 103
Fatal error: main(): Failed opening required '/usr/local/pem/vhosts/203271/webspace/httpdocs/forums/includes/functions_bigthree.php' (include_path='.:/php/includes') in /usr/local/pem/vhosts/203271/webspace/httpdocs/forums/forumdisplay.php on line 103





-----------------------------------------------

Goodluck !

[dmark101]

yeah, the boards are "fucked up" again. :shrug:


let me see if there are any error emails.

[dmark101]

kris [frisky],

i checked my email through the day yesterday and earlier this morning and i never received any error messages relating to the problem you reported. i'm not sure what might have happened, but i'm hoping it was a browser issue and nothing more serious.

i did receive a few bounced email notifications for a particular user. i'll have to contact him and ask that he change his email address or default subscription notification, but that's nothing major.



on another note, did anyone have a really hard time trying to connect to the site over the last hour or so?

i did, to the point that i couldn't even log onto the FTP. i opened up a ticket but i can almost guess what the response will be.

[Martini]

the site hit a brick wall thats what happend.

[dmark101]

no, the host has people that shouldn't be in the jobs they're in. they're helpless and hopeless.

[Enorbit3]

damon, the boards were inaccessible for the past hour or so...fredo and i couldnt login, from either of our computers.

[dmark101]

damon, the boards were inaccessible for the past hour or so...fredo and i couldnt login, from either of our computers.
thanks. that's what i figured happened. let me see if i can squeeze an answer out of these knuckleheads.

[Martini]

*shakes magic 8-ball*

all possibilities point to NO

[dmark101]

they'll probably give me some canned response. i get that a lot unless i press the issue. :shrug:

[ka0tyk]

everytime someone clicks a link an apache child is used/spawned. every apache child consumes memory. then when php is called it uses additional memory based on the setting within the php.ini.


basically your server was out of memory. which usually results in swapping, and ends in ultra sluggish performance. which is why ftp and everything else was affected. why it was out of memory could either be from abusive website traffic, sluggish db (apache+php sits around and waits for queries to finish and eventually snowballs), ftp virus scanning, or email spam scanning... those are the usual culprits in shared web hosting. it doesnt have to be from this site, it could be from any customers site on that machine. usually new customers are put on the "latest server in the rotation" which has a lot of initial traffic from people uploading sites and configuration... and usually BAD configuration. it would be worthwhile to ask for the site to be transfered to another server as this one seems to be problematic.


id suggest looking into "website monitoring sites" for free so you can provide your webhost with downtimes and get credits for it. they usually have in their policy a "guaranteed uptime" and anything outside of that involves a refund of some sort. and refunds usually end up with quick action from someone higher up in the food chain on getting your problem resolved. =)

[RedRyder]

everytime someone clicks a link an apache child is used/spawned. every apache child consumes memory. then when php is called it uses additional memory based on the setting within the php.ini.


basically your server was out of memory. which usually results in swapping, and ends in ultra sluggish performance. which is why ftp and everything else was affected. why it was out of memory could either be from abusive website traffic, sluggish db (apache+php sits around and waits for queries to finish and eventually snowballs), ftp virus scanning, or email spam scanning... those are the usual culprits in shared web hosting. it doesnt have to be from this site, it could be from any customers site on that machine. usually new customers are put on the "latest server in the rotation" which has a lot of initial traffic from people uploading sites and configuration... and usually BAD configuration. it would be worthwhile to ask for the site to be transfered to another server as this one seems to be problematic.


id suggest looking into "website monitoring sites" for free so you can provide your webhost with downtimes and get credits for it. they usually have in their policy a "guaranteed uptime" and anything outside of that involves a refund of some sort. and refunds usually end up with quick action from someone higher up in the food chain on getting your problem resolved. =)

:lolwut:

[dmark101]

everytime someone clicks a link an apache child is used/spawned. every apache child consumes memory. then when php is called it uses additional memory based on the setting within the php.ini.


basically your server was out of memory. which usually results in swapping, and ends in ultra sluggish performance. which is why ftp and everything else was affected. why it was out of memory could either be from abusive website traffic, sluggish db (apache+php sits around and waits for queries to finish and eventually snowballs), ftp virus scanning, or email spam scanning... those are the usual culprits in shared web hosting. it doesnt have to be from this site, it could be from any customers site on that machine. usually new customers are put on the "latest server in the rotation" which has a lot of initial traffic from people uploading sites and configuration... and usually BAD configuration. it would be worthwhile to ask for the site to be transfered to another server as this one seems to be problematic.


id suggest looking into "website monitoring sites" for free so you can provide your webhost with downtimes and get credits for it. they usually have in their policy a "guaranteed uptime" and anything outside of that involves a refund of some sort. and refunds usually end up with quick action from someone higher up in the food chain on getting your problem resolved. =)
thanks derek. i was starting to look into some of the reasons why that would happen after talking to a couple of people today. i'll definitely look into doing this. :pouce:

[Martini]

what about the apaches? theyre great people and do no deserve to be used in such an abusive manner :look:

[1EVLPNY]

Got this message in the chatbox just now: Warning: main(/usr/local/pem/vhosts/203271/webspace/httpdocs/forums/includes/init.php): failed to open stream: Cannot allocate memory in /usr/local/pem/vhosts/203271/webspace/httpdocs/forums/global.php on line 20 Fatal error: main(): Failed opening required '/usr/local/pem/vhosts/203271/webspace/httpdocs/forums/includes/init.php' (include_path='.:/php/includes') in /usr/local/pem/vhosts/203271/webspace/httpdocs/forums/global.php on line 20

[dmark101]

that sounds like the issue kris had. odd because i'm not getting any error notifications on that.

[JustSpencer]

I felt like such a Neanderthal reading this