My webhost botched an eAccelerator confiuration, now my scripts don't work

Discussion in 'Apache' started by schmidte, Aug 23, 2007.

  1. #1
    When I went to check my sites, I got a 500 internal server error, I submitted a ticket. I also checked my error log only to find about 50 eAccelerator errors. My webhost says they fixed everything, but a particular php script won't work. I have the script in several directories and it won't work in any of them. It's worked fine for 2+ years and hasn't worked since the internal server error.

    Here's their response:"The problem was that php.ini was setup to use eAccelerator, but unfortunately eAccelerator no longer works with php cgi,we deleted the lines from this module's starting, please check"

    My script makes a call to the Google API and then displays Google results.

    Do any of you apache wizards have any suggestions that I can relay to my webhost (www.webhostingbuzz.com) regarding getting php to work properly after something like this happens. I'm starting to get really irratated.

    ED
     
    schmidte, Aug 23, 2007 IP
  2. cyanide

    cyanide Peon

    Messages:
    483
    Likes Received:
    26
    Best Answers:
    0
    Trophy Points:
    0
    #2
    I think we need a bit more info from you, specifically versions.
    Some versions of eacc don;t work with php5, etc..

    Better yet, can you create a phpinfo page?
    Then we can see what you're running.
    Maybe they upgraded to a different php version that your script is not compatible with?
     
    cyanide, Aug 23, 2007 IP
  3. schmidte

    schmidte Peon

    Messages:
    345
    Likes Received:
    18
    Best Answers:
    0
    Trophy Points:
    0
    #3
    Here's my php info:
    http://www.smallmouthbass.biz/info.php

    Also, right after they said they fixed the problem, this error came up when I tried doing a call to the google api:

    Fatal error: Method SOAP_Client::__call() must take exactly 2 arguments in /home/schmidte/public_html/google4/google2/google/SOAP/Client.php on line 335

    I found an updated version of it (soap) and I no longer have the error, however no search results appear when doing a query to the api.

    I see that there are SOAP values that can be configured, do you see anything in there that might be the culprit?

    Thanks for your help....
    ED
     
    schmidte, Aug 23, 2007 IP
  4. powerspike

    powerspike Peon

    Messages:
    312
    Likes Received:
    10
    Best Answers:
    0
    Trophy Points:
    0
    #4
    have you asked them if they have enabled the soap extensions in php, it looks like it's the soap that is having the issues above, they might of enabled/disabled other modules besides eaccel.
     
    powerspike, Aug 23, 2007 IP