News:

SMF 2.1.4 has been released! Take it for a spin! Read more.

Main Menu

GoDaddy Announce Topic Issue

Started by TheMortician4, January 29, 2011, 07:19:35 PM

Previous topic - Next topic

TheMortician4

I have been Running SMF on Godaddy for over 3 years. Just in the last 3 days, when I announce a topic, I get an Internal Server 500 Error. I called GoDaddy and they told me that this is an issue that they do not support. That the issue is their server does not support emailing to free Email systems, IE: Gmail etc. Why after all this time has the system worked seamlessly, and all of a sudden I started getting this error? They did suggest that I look into the script that generates the message to their relay servers, Like I would even know what I was looking at anyway.

Does anyone have a clue as to why this is happening, how to fix it, and why this started only in the last 3 days?

SlammedDime

500 errors indicate that the *server* had a problem processing the request.  As SMF normally does not have this problem when the server is configured properly, I would say that go daddy has a crappily configured server (not surprising) which has some restrictions in place that may be causing SMF some issues.  500 errors are normally very generic to the end user and can be very cryptic.  The only way to know how or why they were thrown is to look at the server error log and see a more detailed message on the error.  If the error was not logged, then go daddy does not have proper error reporting enabled (wouldn't surprise me).

Basically, it boils down to needing to know what the error is that Apache threw to really diagnose the problem.
SlammedDime
Former Lead Customizer
BitBucket Projects
GeekStorage.com Hosting
                      My Mods
SimpleSEF
Ajax Quick Reply
Sitemap
more...
                     

TheMortician4

#2
Here is a copy of the Error log from the last skew:


67.82.140.25] FastCGI: comm with (dynamic) server "/var/chroot/home/content/t/h/e/themortician4/html-x-httpd-php5" aborted: (first read) idle timeout (60 sec)
[Sat Jan 29 17:38:14 2011] [error] [client 67.82.140.25] FastCGI: incomplete headers (0 bytes) received from server "/var/chroot/home/content/t/h/e/themortician4/html-x-httpd-php5"

Illori


TheMortician4

Sorry, I forgot to throw the error log in here:

Here is a copy of the Error log from the last skew:


67.82.140.25] FastCGI: comm with (dynamic) server "/var/chroot/home/content/t/h/e/themortician4/html-x-httpd-php5" aborted: (first read) idle timeout (60 sec)
[Sat Jan 29 17:38:14 2011] [error] [client 67.82.140.25] FastCGI: incomplete headers (0 bytes) received from server "/var/chroot/home/content/t/h/e/themortician4/html-x-httpd-php5"

Oldiesmann

Send the error messages to GoDaddy and tell them to fix the issue. Basically, the way they have FastCGI configured, it's set to automatically kill the process if it thinks that the process is idle for 60 seconds. The second error is related to that.

However, given their response the first time (the "we don't support emailing free email hosts like gmail" thing), I would just recommend you find a better host.
Michael Eshom
Christian Metal Fans

TheMortician4

The issue was that the new grid servers were having a slight bottle necking issue going out. This has now been resolved and is working again seamlessly. I have not had any issues running SMF on GoDaddy. Quite honestly, I have to say that it has been a very painless experience for me, then again I am but one in the many who may feel otherwise.

Acans

Glad to hear the issue is resolved. I'll mark this topic as solved.
"The Book of Arantor, 17:3-5
  And I said unto him, thy database query shalt always be sent by the messenger of $smcFunc
  And $smcFunc shall protect you against injections and evil
  And so it came to pass that mysql_query was declared deprecated and even though he says he is not
  dead yet, the time was soon to come to pass when mysql_query shall be gone and no more

Advertisement: