TinyPortal

Development => Support => Topic started by: DarkAngel612 on January 09, 2010, 09:25:07 AM

Title: not sure if this is the right section but
Post by: DarkAngel612 on January 09, 2010, 09:25:07 AM
i got this in the error log and not sure what I need to do to fix it:

PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /home/xxx/public_html/attic/Sources/TPmodules.php on line 1478

this is the section and the line in red
// Open the actual datafile:

   $fp = fopen($backend, "r");
   
   $xmlerr='';
   // Run through it line by line and parse:
   while ($data = fread($fp, 4096))
   {
      xml_parse($xml_parser, $data, feof($fp)) or $xmlerr=(sprintf("XML error: %s at line %d",
      xml_error_string(xml_get_error_code($xml_parser)),
      xml_get_current_line_number($xml_parser)));
      if($xmlerr!='')
         break;
   }
Title: Re: not sure if this is the right section but
Post by: ZarPrime on January 15, 2010, 04:31:38 PM
DarkAngel612,

This issue could have had something to do with the issues we had on TP.net earlier this month, or it could be a server issue on your end.  Please give us an update on this, whether it seems to be working better now or not.

ZarPrime
Title: Re: not sure if this is the right section but
Post by: DarkAngel612 on January 16, 2010, 12:39:46 AM
well, let me tell ya, if looks over the net could kill our host would be laying on the floor...lol

we have been going round and round with them due to our entire server going through slowness that starts out slow and ends up with either crawling or not doing anything at all. double posting cause people think it did not go through, 404 or 500 errors.

I got this error and these:
[09-Jan-2010 03:10:41] PHP Warning:  [eAccelerator] Can not create shared memory area in Unknown on line 0
[09-Jan-2010 03:10:41] PHP Warning:  Unknown(): Unable to initialize module 'eAccelerator' in Unknown on line 0
[09-Jan-2010 03:11:34] PHP Warning:  [eAccelerator] Can not create shared memory area in Unknown on line 0
[09-Jan-2010 03:11:34] PHP Warning:  Unknown(): Unable to initialize module 'eAccelerator' in Unknown on line 0
[09-Jan-2010 06:35:12] PHP Warning:  Unknown(): Unable to load dynamic library '/usr/local/php4/lib/php/extensions/no-debug-non-zts-20020429/eaccelerator.so' - /usr/local/php4/lib/php/extensions/no-debug-non-zts-20020429/eaccelerator.so: failed to map segment from shared object: Cannot allocate memory in Unknown on line 0

from dec 29 til the other day did they finally check everything including the other entities sharing our VPS. They did discover 2 that were hogging it up and moved them to a new server, "forced" the c-panel update and "tweaked " a few things (unknown what since they did not elaborate). Speed is finally back, in a fashion, and so far no more errors of any kind and that error has not returned either.

So for now it seems to have straightened out a bit. Gave the whole bit to you in case that helps you any in figuring things out.

Also there had been no update, no installations  nor packages done when it started.
Title: Re: not sure if this is the right section but
Post by: ZarPrime on January 16, 2010, 12:53:23 AM
Yeah, those errors definitely look like server errors but Ichbin would know more about those than I would.  Sometimes having too many resources on a server can really muck things up.  I'm glad things seem to be working better for you now. O0

ZarPrime
Title: Re: not sure if this is the right section but
Post by: DarkAngel612 on January 16, 2010, 01:00:42 AM
lol, we still have some slowness but not any other errors....yet
Title: Re: not sure if this is the right section but
Post by: IchBin on January 16, 2010, 01:19:17 AM
Definitely a badly configured server. eAccelerator is the cache/optimizing library that can be used on servers. It would seem they needed to fix their server. Shared hosts are bound to run into these types of problems. Glad you're "ok" for now. We'll see how long that lasts eh? ;P
Title: Re: not sure if this is the right section but
Post by: DarkAngel612 on January 16, 2010, 02:54:33 AM
they are under a watchful eye for my partners are threatening to charge them for off time...lol
Title: Re: not sure if this is the right section but
Post by: thelufias on March 02, 2010, 02:30:50 AM
lol--spammer got sanctioned I see...lol

thought to let you all know that after many days of hammering the host with errors and different things....they finally found that the real problem was that 2 other clients were hogging up the resources. Once they moved them from our VPS things got straightened out...oh yea and fixed my htaccess file to  not force php4...no idea how that happened cause we started out with php5...lol
Title: Re: not sure if this is the right section but
Post by: ZarPrime on March 02, 2010, 02:35:50 AM
As quickly as I could grab the bat. ;) 17 posts ~ Amazing. :knuppel2: Now my left mouse finger is wore out. ::)

Glad you got the problem sorted.  That happened to me once and my host moved me to a new server and I haven't had any problems since <knock on wood :D>.

ZarPrime
Title: Re: not sure if this is the right section but
Post by: Skhilled on March 06, 2010, 10:02:22 PM
You could also try turning off the accelerator in SMF settings. That might help some.
Title: Re: not sure if this is the right section but
Post by: thelufias on March 06, 2010, 11:48:39 PM
QuoteYou could also try turning off the accelerator in SMF settings. That might help some.

accelerator??? where is it hiding and how...lol
Title: Re: not sure if this is the right section but
Post by: ZarPrime on March 07, 2010, 06:31:06 AM
I am guessing that you can find that in Admin --> Configuration --> Server Settings --> Caching

Just try setting it to "no caching" and see if it helps.

ZarPrime
Title: Re: not sure if this is the right section but
Post by: thelufias on March 07, 2010, 09:43:39 AM
well thanks but they are all set to no cacheing...so I actually did something right...lol
Title: Re: not sure if this is the right section but
Post by: Skhilled on March 07, 2010, 10:17:19 AM
Didn't hurt to check. So now we know it is strictly a hosting issue.