When trying to do a sync the following error will crop up at inconsistent times

Fatal error: Maximum execution time of 30 seconds exceeded in ../roster/lib/functions.lib.php on line 1259

1. WoWRoster Version: v1.9.9.1614
2. ArmorySync Version: v2.6.0.351
3. Update setting (per page/character): Tried both settings same error
4. Fetch timeout: 12
5. Reload wait time: 8
6. Using Ajax? - Yes and have tried No as well.

Any other info you need, I'll be happy to provide.

Well, 3x12=36 > 30

Set fetch timeout to 4 and reload wait time to 2. use per page update. using ajax or not shouldn't make any difference.

I changed the settings as you asked and... same error. I can run the sync over and over again both with the new settings and the old settings and it still terminates in different spots. Sometimes it will do the first 4 characters then terminate and once I actually made it to the last character. It's never consistent.

With your max_execution_time don't try per character update. it must fail.

How exactly is it terminating on per page update. Any messages?

If it still exceeds time. Are you using curl or fsock?

I have only been using per page update.

Fatal error: Maximum execution time of 30 seconds exceeded in ../roster/lib/functions.lib.php on line 1259

And that is the only error message I get. My server is using curl.

I took some screen shots - During:
http://persistenceguild.net/files/During.JPG

And After this pops up:
http://persistenceguild.net/files/After.JPG

The line described in the second picture is part of the fsock code of urlgrabber. so you are NOT using curl.

Anyway, interesting that fsock still doesn't time correctly.

How do I check and see which it's using because I looked up on my server and didn't see any fsock files. I see curl files...

Is there a way I can make roster use curl instead of fsock?

You will need a phpinfo file

This is just a file called phpinfo.php with this content:

Code: Select all

<?php
   phpinfo();
?>


Save it somewhere on your webserver a open it in your browser.

If curl is enabled you shoul find a curl section showing the following:

Code: Select all

curl
cURL support    enabled
cURL Information    libcurl/7.16.0 OpenSSL/0.9.8e zlib/1.2.3


After that you should delete the phpinfo file.

If php is compiled with curl support it must still be enabled in php.ini

Yep, it's enabled. I don't have access to php.ini this is a hosted site. I did submit a support ticket and they confirmed that Curl is enabled via php.ini

Code: Select all

curl
cURL support    enabled
cURL Information    libcurl/7.16.0 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5

So why is it using fsock and can I force it to use curl instead?

Hmmm, try another small php file with this content:

Code: Select all

<?php
   if( function_exists('curl_init') )
   {
      print "Curl enabled";
   }
   else
   {
      print "Curl disabled";
   }
?>


Let me know what its doing.

Well I guess I should have asked to talk to an actual server admin and not some tech support flunky because I was just told that curl_exec and curl_init are disabled for security reasons.

Well, that really sucks...

k, then be patient till I investigated fsock not timing out correctly. Stay tuned!

Take your time, I'm glad I can help... let me know if there is anything you would like me to test.

Yes, you can. Update to latest svn and give it a try