2 replies to this topic

[DEViANT]

Im currently experiencing a problem with a script running on a local server. I wrote a little script that uses the Zend Google Calendar API to add events to a given user's calendar. Running on a remote server on hostmonster, this poses no problems. The script is ran, The event is created and everything works fine. I transferred this script dirrectly off the server without any changes being made, to our companies mail/webserver running FreeBSD 7.1.. The script executes, it creates the callendar event, but thereafter switch between givving error messages such as Firefoxs' 'The connection was reset' or '504 Gateway Timeout'.

Now I've increased the timeout limit for the script to 30 seconds, and enabled keep allive... However the same problem still occurs. In essance the script is working, It authenticates with google calendar and adds the event, but its as if though the script just isnt accepting the response.

Logged into the local server via terminal I can succesfully run a curl command on google to authenticate a username & password and I DO receive a response. After hours of googel'ing the problem I find myself lost and without a clue. It cant be port forwarding settings, otherwise I would not even be able to run the curl command in terminal and receive a valid response.

Is there anyone who can give some advice in which directions to start troubleshooting?

[DEViANT]

I apologise for the bump, but after two weeks this post has moved to the second page. I would like to get some fresh eyes on it as I'm still struggling with this issue. Does anyone have any ideas on the matter?

[Alexander]

There are just too many changes in Apache versions, CURL libraries and different codebases in PHP revisions for large scripts such as that to work off the bat somewhere else. If you can pinpoint at what specific point the error is thrown, for example function X attempts connection to site Y and is rejected. This can be done through profiling on local server, setting timeout to a high value, debugging connections or writing to log at each step of the script, boiling down the offending code and fixing it. It could be anything without more information, it could be an underlying bug in any of the platforms.