I have been unable to publish via FTP since July 7th, getting the
endless 'Your publish is taking longer than expected' error.
(I first reported it on this thread:
http://groups.google.com/group/blogger-help-publishing/browse_thread/... but the thread has turned to a different discussion.)
The blog is alcademics.com
hosted at GoDaddy.com
and FTP publishing works from elsewhere, just not from Blogger
I have tried:
- publishing additional posts and manipulating posts and settings.
this failed- it was still hung on 'taking longer than expected'.
- changing the publishing settings to publish the same blog on a
different server. this works and all the files upload to the other
server (hosted at the same hosting service). so relocating my blog to
another domain worked.
- created a new blog with a single entry and tried to publish it to
the original host. This fails, and hangs in the same way to the server
with 'taking longer than expected'.
- publishing the original blog with a known error: wrong password or
ftp pathname. This fails, and hangs in the same way to the server with
'taking longer than expected'. It does not give me an 'incorrect
password' or other error.
It appears then that any post from blogger to the alcademics.com
domain hangs up early on. Does this reveal anything about my potential
problem, or does anyone have suggestions on what else to try?
Additionally, I spoke with the help desk at my hosting service. They
looked at the server log and said, "There are no external connections
to the server currently." So although I am getting no connection
errors (and Blogger still says publish is taking longer than expected
as if it is connected), it appears the Blogger is not successfully
connecting to my server.
> I have been unable to publish via FTP since July 7th, getting the
> endless 'Your publish is taking longer than expected' error.
> (I first reported it on this thread:http://groups.google.com/group/blogger-help-publishing/browse_thread/...
> but the thread has turned to a different discussion.)
> The blog is alcademics.com
> hosted at GoDaddy.com
> and FTP publishing works from elsewhere, just not from Blogger
> I have tried:
> - publishing additional posts and manipulating posts and settings.
> this failed- it was still hung on 'taking longer than expected'.
> - changing the publishing settings to publish the same blog on a
> different server. this works and all the files upload to the other
> server (hosted at the same hosting service). so relocating my blog to
> another domain worked.
> - created a new blog with a single entry and tried to publish it to
> the original host. This fails, and hangs in the same way to the server
> with 'taking longer than expected'.
> - publishing the original blog with a known error: wrong password or
> ftp pathname. This fails, and hangs in the same way to the server with
> 'taking longer than expected'. It does not give me an 'incorrect
> password' or other error.
> It appears then that any post from blogger to the alcademics.com
> domain hangs up early on. Does this reveal anything about my potential
> problem, or does anyone have suggestions on what else to try?
> Additionally, I spoke with the help desk at my hosting service. They
> looked at the server log and said, "There are no external connections
> to the server currently." So although I am getting no connection
> errors (and Blogger still says publish is taking longer than expected
> as if it is connected), it appears the Blogger is not successfully
> connecting to my server.
Interesting. Definitely narrowing the diagnosis.
Does the log show connection attempts, or successful connections? Was
the log examined WHILE you were trying to publish, or after? For the
relevant time period?
What does this mean?
"- changing the publishing settings to publish the same blog on a
different server."
Did you change to a different GoDaddy server? Or did you try another
hosting company? Or did you publish from another blogging service
(not Blogger) to GoDaddy?
The server log only tracks successful connections, so attempted
connections would not be recorded.
They looked at it while the endless loop of 'taking a while to
publish, click here to wait' cycle was going, but not at the instant
of clicking the 'publish' button- afterwards when it tells me it's
still publishing.
> "- changing the publishing settings to publish the same blog on a
> different server."
I pointed the same blog (alcademics) at another domain I own, also
hosted by GoDaddy, and published it there without a problem. (I should
note that I have two other blogs on two other domains also hosted with
GoDaddy and neither of them has any of these problems. I can publish
fine.) So this test was to see if it was something funky about the
content of my alcademics blog. As it publishes fine to another domain
hosted by the same host, I think there is not a problem with content
formatting.
I have not tried posting from another blogging service to the same
domain, as FTP works fine to that domain with the same user/password.
> > Additionally, I spoke with the help desk at my hosting service. They
> > looked at the server log and said, "There are no external connections
> > to the server currently." So although I am getting no connection
> > errors (and Blogger still says publish is taking longer than expected
> > as if it is connected), it appears the Blogger is not successfully
> > connecting to my server.
> Interesting. Definitely narrowing the diagnosis.
> Does the log show connection attempts, or successful connections? Was
> the log examined WHILE you were trying to publish, or after? For the
> relevant time period?
> What does this mean?
> "- changing the publishing settings to publish the same blog on a
> different server."
> Did you change to a different GoDaddy server? Or did you try another
> hosting company? Or did you publish from another blogging service
> (not Blogger) to GoDaddy?
> The server log only tracks successful connections, so attempted
> connections would not be recorded.
> They looked at it while the endless loop of 'taking a while to
> publish, click here to wait' cycle was going, but not at the instant
> of clicking the 'publish' button- afterwards when it tells me it's
> still publishing.
> > "- changing the publishing settings to publish the same blog on a
> > different server."
> I pointed the same blog (alcademics) at another domain I own, also
> hosted by GoDaddy, and published it there without a problem. (I should
> note that I have two other blogs on two other domains also hosted with
> GoDaddy and neither of them has any of these problems. I can publish
> fine.) So this test was to see if it was something funky about the
> content of my alcademics blog. As it publishes fine to another domain
> hosted by the same host, I think there is not a problem with content
> formatting.
> I have not tried posting from another blogging service to the same
> domain, as FTP works fine to that domain with the same user/password.
The one that is not working is Linux, with "hosting configuration
2.0", PHP 5.x,
The other two that are connecting fine are:
Linux, "hosting configuration 1.0", PHP 4.x
Windows, ASP.Net 1.1, IIS 6.0
The broken domain was recently renewed for hosting right about the
time it broke, but the GoDaddy customer service person said nothing
should have changed when it was renewed.
He said the hosting configuration change from 1.0 to 2.0 should have
happened several months ago (though he couldn't say when exactly). The
hosting configuration change, which deals with scripting languages
that seem to have nothing to do with FTP, is outlayed here:
http://help.godaddy.com/article/1076
Anyway, they said that regardless I can't downgrade to the 1.0 hosting
config.
I instructed them to switch my hosting for the non-working domain to a
Windows server instead. They did this. It's been 3 hours so far, and
it's not working yet. I know I have to be patient and keep trying in
case the server DNS changes haven't propagated everywhere yet.
If in the meantime you have any other ideas please let me know. I'll
certainly post if it starts working again. Thanks.
> > The server log only tracks successful connections, so attempted
> > connections would not be recorded.
> > They looked at it while the endless loop of 'taking a while to
> > publish, click here to wait' cycle was going, but not at the instant
> > of clicking the 'publish' button- afterwards when it tells me it's
> > still publishing.
> > > "- changing the publishing settings to publish the same blog on a
> > > different server."
> > I pointed the same blog (alcademics) at another domain I own, also
> > hosted by GoDaddy, and published it there without a problem. (I should
> > note that I have two other blogs on two other domains also hosted with
> > GoDaddy and neither of them has any of these problems. I can publish
> > fine.) So this test was to see if it was something funky about the
> > content of my alcademics blog. As it publishes fine to another domain
> > hosted by the same host, I think there is not a problem with content
> > formatting.
> > I have not tried posting from another blogging service to the same
> > domain, as FTP works fine to that domain with the same user/password.
> The one that is not working is Linux, with "hosting configuration
> 2.0", PHP 5.x,
> The other two that are connecting fine are:
> Linux, "hosting configuration 1.0", PHP 4.x
> Windows, ASP.Net 1.1, IIS 6.0
> The broken domain was recently renewed for hosting right about the
> time it broke, but the GoDaddy customer service person said nothing
> should have changed when it was renewed.
> He said the hosting configuration change from 1.0 to 2.0 should have
> happened several months ago (though he couldn't say when exactly). The
> hosting configuration change, which deals with scripting languages
> that seem to have nothing to do with FTP, is outlayed here:http://help.godaddy.com/article/1076
> Anyway, they said that regardless I can't downgrade to the 1.0 hosting
> config.
> I instructed them to switch my hosting for the non-working domain to a
> Windows server instead. They did this. It's been 3 hours so far, and
> it's not working yet. I know I have to be patient and keep trying in
> case the server DNS changes haven't propagated everywhere yet.
> If in the meantime you have any other ideas please let me know. I'll
> certainly post if it starts working again. Thanks.
This is excellent detail. Kudos.
I'm going to proceed on the presumption that the hosting configuration
change, that "should have happened several months ago", happened in
actuality when you renewed your hosting.
It's too early to celebrate anything yet. FTP publishing to the now-
Windows host server still isn't working.
Here is some odd behavior. For ease, say Domain 1 is the problem, and
Domain 2 works fine with the same Windows web hosting configuration
(though probably on different servers) through GoDaddy.
1. 1. Post to Domain 1 Fails with 'upload taking longer than expected'
that never ends
2. Post same blog to Domain 2 Succeeds
3. retry Post to Domain 1 Fails with 'upload taking longer than
expected' that never ends
Also,
1. Post to Domain 1 Fails with 'upload taking longer than expected'
that never ends
2. Post same blog to Domain 2 succeeds
3. Post to Domain 1 using wrong password fails with error messages
like:
/2008/07/sf-events.html failed to upload file: sf-events.html with
reason: 550 /2008/07/sf-events.html: The system cannot find the path
specified.
4. Post to Domain 1 with proper password Fails with 'upload taking
longer than expected' that never ends
5. retrying step 3 (improper password to Domain 1) Fails with 'upload
taking longer than expected' that never ends- do not get same error as
previous time!
So the only time I get an error of any sort on Domain 1 is after
pointing at Domain 2 then putting in a mistake. Once I have attempted
to post to Domain 1 (with the correct or incorrect settings) I will no
longer get error messages. This behavior is reproduceable.
> > The one that is not working is Linux, with "hosting configuration
> > 2.0", PHP 5.x,
> > The other two that are connecting fine are:
> > Linux, "hosting configuration 1.0", PHP 4.x
> > Windows, ASP.Net 1.1, IIS 6.0
> > The broken domain was recently renewed for hosting right about the
> > time it broke, but the GoDaddy customer service person said nothing
> > should have changed when it was renewed.
> > He said the hosting configuration change from 1.0 to 2.0 should have
> > happened several months ago (though he couldn't say when exactly). The
> > hosting configuration change, which deals with scripting languages
> > that seem to have nothing to do with FTP, is outlayed here:http://help.godaddy.com/article/1076
> > Anyway, they said that regardless I can't downgrade to the 1.0 hosting
> > config.
> > I instructed them to switch my hosting for the non-working domain to a
> > Windows server instead. They did this. It's been 3 hours so far, and
> > it's not working yet. I know I have to be patient and keep trying in
> > case the server DNS changes haven't propagated everywhere yet.
> > If in the meantime you have any other ideas please let me know. I'll
> > certainly post if it starts working again. Thanks.
> This is excellent detail. Kudos.
> I'm going to proceed on the presumption that the hosting configuration
> change, that "should have happened several months ago", happened in
> actuality when you renewed your hosting.
> It's too early to celebrate anything yet. FTP publishing to the now-
> Windows host server still isn't working.
> Here is some odd behavior. For ease, say Domain 1 is the problem, and
> Domain 2 works fine with the same Windows web hosting configuration
> (though probably on different servers) through GoDaddy.
> 1. 1. Post to Domain 1 Fails with 'upload taking longer than expected'
> that never ends
> 2. Post same blog to Domain 2 Succeeds
> 3. retry Post to Domain 1 Fails with 'upload taking longer than
> expected' that never ends
> Also,
> 1. Post to Domain 1 Fails with 'upload taking longer than expected'
> that never ends
> 2. Post same blog to Domain 2 succeeds
> 3. Post to Domain 1 using wrong password fails with error messages
> like:
> /2008/07/sf-events.html failed to upload file: sf-events.html with
> reason: 550 /2008/07/sf-events.html: The system cannot find the path
> specified.
> 4. Post to Domain 1 with proper password Fails with 'upload taking
> longer than expected' that never ends
> 5. retrying step 3 (improper password to Domain 1) Fails with 'upload
> taking longer than expected' that never ends- do not get same error as
> previous time!
> So the only time I get an error of any sort on Domain 1 is after
> pointing at Domain 2 then putting in a mistake. Once I have attempted
> to post to Domain 1 (with the correct or incorrect settings) I will no
> longer get error messages. This behavior is reproduceable.
> Does this lead us anywhere?
I would bet that this is good detail that should get Blogger engineers
closer to a solution.
I have no idea what your moving, on the fly, from a Linux to a Windows
server client would entail. I would have hoped that it would be
transparent, and the Blogger FTP script would pick up the difference.
Maybe not.
My guess is, if you are looking for a resolution, it will only come
after personal intervention by Blogger engineers. And my second guess
is that your resolution will come quicker if you are on a PHP V5.x
client, rather then a Windows IIS client.
If GoDaddy is unable to provide you with any relevant client
configuration changes involved from migrating from Linux to Windows
(maybe there aren't any that you, personally, can process), I would
bet that you'll be better served requesting that they put your service
back on Linux V2.0, and waiting for Blogger to tweak their PHP v5.x
client code.
That's my prognosis, anyway. You're welcome to play it any way that
you wish, and whatever you go with, I would bet that Blogger and
GoDaddy personnel will be the richer from the experience.
> > It's too early to celebrate anything yet. FTP publishing to the now-
> > Windows host server still isn't working.
> > Here is some odd behavior. For ease, say Domain 1 is the problem, and
> > Domain 2 works fine with the same Windows web hosting configuration
> > (though probably on different servers) through GoDaddy.
> > 1. 1. Post to Domain 1 Fails with 'upload taking longer than expected'
> > that never ends
> > 2. Post same blog to Domain 2 Succeeds
> > 3. retry Post to Domain 1 Fails with 'upload taking longer than
> > expected' that never ends
> > Also,
> > 1. Post to Domain 1 Fails with 'upload taking longer than expected'
> > that never ends
> > 2. Post same blog to Domain 2 succeeds
> > 3. Post to Domain 1 using wrong password fails with error messages
> > like:
> > /2008/07/sf-events.html failed to upload file: sf-events.html with
> > reason: 550 /2008/07/sf-events.html: The system cannot find the path
> > specified.
> > 4. Post to Domain 1 with proper password Fails with 'upload taking
> > longer than expected' that never ends
> > 5. retrying step 3 (improper password to Domain 1) Fails with 'upload
> > taking longer than expected' that never ends- do not get same error as
> > previous time!
> > So the only time I get an error of any sort on Domain 1 is after
> > pointing at Domain 2 then putting in a mistake. Once I have attempted
> > to post to Domain 1 (with the correct or incorrect settings) I will no
> > longer get error messages. This behavior is reproduceable.
> > Does this lead us anywhere?
> I would bet that this is good detail that should get Blogger engineers
> closer to a solution.
> I have no idea what your moving, on the fly, from a Linux to a Windows
> server client would entail. I would have hoped that it would be
> transparent, and the Blogger FTP script would pick up the difference.
> Maybe not.
> My guess is, if you are looking for a resolution, it will only come
> after personal intervention by Blogger engineers. And my second guess
> is that your resolution will come quicker if you are on a PHP V5.x
> client, rather then a Windows IIS client.
> If GoDaddy is unable to provide you with any relevant client
> configuration changes involved from migrating from Linux to Windows
> (maybe there aren't any that you, personally, can process), I would
> bet that you'll be better served requesting that they put your service
> back on Linux V2.0, and waiting for Blogger to tweak their PHP v5.x
> client code.
> That's my prognosis, anyway. You're welcome to play it any way that
> you wish, and whatever you go with, I would bet that Blogger and
> GoDaddy personnel will be the richer from the experience.
