Er...any chance of getting the fscked-up comment engine to work better? Or even getting the main page to not look quite so clunky?
Hopin'.
Rand Simberg wrote:
Better hope for the latter than the former, unfortunately, unless my financial fortunes change sufficiently to hire a Moveable Type guru.
Jonathan wrote:
The main page looks fine.
I found that publishing a comment in the comment window, and then, while that comment is being published, going to the main window and clicking the comments link to a different post, results in the published comment being displayed in only a few seconds -- IOW, the comment publishes long before the timeout.
Let me try it again...
Jonathan wrote:
...yes, that worked. It took less than 10 seconds to publish the above comment. It appears that the process that is hanging comes after publishing and before refreshing the comment window. But perhaps this was obvious.
David Summers wrote:
Since you are testing, I thought I'd let you know that I didn't see this... ;-}
More seriously, most times when I have run into this type of issue it has been a DNS problem. Very hard to troubleshoot from here, of course, but hopefully this may be at least a little helpful:
The posting process (as I understand it) is:
1) The comment is written to the database
2) An email is sent to you
3) The commentor gets the final page
The most likely time for a DNS error is when the email is sent to you. Do you have admin access to server? If so, what happen when you manually use sendmail to email the address you get messages from the server on?
Some quick things to try:
1) Add the server's name (what's in the from address) to /etc/hosts
2) Add your email server's name (what's in the to address) to /etc/hosts
3) Make sure your email is not configured to try ip6 DNS first - this became the default at some point, but unless your DNS supports ip6 you get a long delay.
Anyway, if I can help at all, just let me know - otherwise I'll leave you alone about this, I know sometimes back seat admins can be annoying!
Rand Simberg wrote:
It's not an email problem. I have other blogs, both MT and Wordpress, on the server that have no problems. It's a problem with this specific installation (and I suspect my database). It doesn't just time out for commenting. It times out every time I put up or update a post.
Jonathan wrote:
Did you compare the structures of this blog's DB and another MT blog's DB?
Did you compare the values of blog parameters that are saved in the DB (i.e., is a parameter value outside of its permitted range)?
Rand Simberg wrote:
Did you compare the structures of this blog's DB and another MT blog's DB?
No, but I suspect there's a problem, because MT hiccuped trying to upgrade (even though it was from an earlier-version MT blog).
Did you compare the values of blog parameters that are saved in the DB (i.e., is a parameter value outside of its permitted range)?
No. I have neither the expertise (though I could acquire it with study) or time to do so. That's why I need an MT guru. Or at least someone more familiar with MT and MySQL than I am.
Leave a comment
Note: The comment system is functional, but timing out when returning a response page. If you have submitted a comment, DON'T RESUBMIT IT IF/WHEN IT HANGS UP AND GIVES YOU A "500" PAGE. Simply click your browser "Back" button to the post page, and then refresh to see your comment.
About this Entry
This page contains a single entry by Rand Simberg published on July 23, 2008 10:30 AM.
Er...any chance of getting the fscked-up comment engine to work better? Or even getting the main page to not look quite so clunky?
Hopin'.
Better hope for the latter than the former, unfortunately, unless my financial fortunes change sufficiently to hire a Moveable Type guru.
The main page looks fine.
I found that publishing a comment in the comment window, and then, while that comment is being published, going to the main window and clicking the comments link to a different post, results in the published comment being displayed in only a few seconds -- IOW, the comment publishes long before the timeout.
Let me try it again...
...yes, that worked. It took less than 10 seconds to publish the above comment. It appears that the process that is hanging comes after publishing and before refreshing the comment window. But perhaps this was obvious.
Since you are testing, I thought I'd let you know that I didn't see this... ;-}
More seriously, most times when I have run into this type of issue it has been a DNS problem. Very hard to troubleshoot from here, of course, but hopefully this may be at least a little helpful:
The posting process (as I understand it) is:
1) The comment is written to the database
2) An email is sent to you
3) The commentor gets the final page
The most likely time for a DNS error is when the email is sent to you. Do you have admin access to server? If so, what happen when you manually use sendmail to email the address you get messages from the server on?
Some quick things to try:
1) Add the server's name (what's in the from address) to /etc/hosts
2) Add your email server's name (what's in the to address) to /etc/hosts
3) Make sure your email is not configured to try ip6 DNS first - this became the default at some point, but unless your DNS supports ip6 you get a long delay.
Anyway, if I can help at all, just let me know - otherwise I'll leave you alone about this, I know sometimes back seat admins can be annoying!
It's not an email problem. I have other blogs, both MT and Wordpress, on the server that have no problems. It's a problem with this specific installation (and I suspect my database). It doesn't just time out for commenting. It times out every time I put up or update a post.
Did you compare the structures of this blog's DB and another MT blog's DB?
Did you compare the values of blog parameters that are saved in the DB (i.e., is a parameter value outside of its permitted range)?
Did you compare the structures of this blog's DB and another MT blog's DB?
No, but I suspect there's a problem, because MT hiccuped trying to upgrade (even though it was from an earlier-version MT blog).
Did you compare the values of blog parameters that are saved in the DB (i.e., is a parameter value outside of its permitted range)?
No. I have neither the expertise (though I could acquire it with study) or time to do so. That's why I need an MT guru. Or at least someone more familiar with MT and MySQL than I am.