Jump to content

Recommended Posts

Posted

I am using Movaeable Type 3.2 and getting some odd error messages showing up in the Sever Error log, and entries are not posting correctly. MT freezes when posting, and does not complete the pinging and posting cycle.

 

It tracking down the problem, I looked at the Error Log on the server. It has error message showing MT trying to access the old version of mt in a different directory.

 

"[2005-10-22 11:03:04]: error: file has no execute permission: (/home/domain/public_html/cgi-bin/mt-comments.cgi)"

 

The problem here is that the program should be looking in .../mt32/cgi-bin/ not in .../cgi-bin/mt/. My MT configuration file is correct. Any ideas of why this is happening?

 

Thanks,

rowan

Posted

Welcome to the forums, rowan! :huh:

 

I think you're talking about two different issues here:

 

I looked at the Error Log on the server. It has error message showing MT trying to access the old version of mt in a different directory.

 

"[2005-10-22 11:03:04]: error: file has no execute permission: (/home/domain/public_html/cgi-bin/mt-comments.cgi)"

I'd need to see the access log entry that caused this error to know for sure, but I believe what you're seeing here is a spammer trying to hit your old mt-comments.cgi. Spammers are often slow to adjust to a new location of the mt-comments.cgi script. I moved mine a couple of months ago and still get hundreds of hits per day on my old MT comment and trackback URLs.

 

As far as I know, MT does not call mt-comments.cgi at all during the entry posting process, so posting an entry would not cause this error to occur.

 

...and entries are not posting correctly. MT freezes when posting, and does not complete the pinging and posting cycle.

There's a number of things that could cause this, but you haven't really provided enough information that would help point out where the problem is. Complexity of templates, installed plugins, number and types of archive templates that get rebuilt when a new entry is posted, and configuation settings in both the MT config file (such as the PingTimeout setting) and the weblog config (such as whether Trackback AutoDiscovery is enabled) can affect the time MT needs to post a new entry.

Posted

Thanks for the welcome, and thank you for the response. :dance:

 

Welcome to the forums, rowan! :huh:

 

I think you're talking about two different issues here:

I'd need to see the access log entry that caused this error to know for sure, but I believe what you're seeing here is a spammer trying to hit your old mt-comments.cgi. Spammers are often slow to adjust to a new location of the mt-comments.cgi script. I moved mine a couple of months ago and still get hundreds of hits per day on my old MT comment and trackback URLs.

 

As far as I know, MT does not call mt-comments.cgi at all during the entry posting process, so posting an entry would not cause this error to occur.

There's a number of things that could cause this, but you haven't really provided enough information that would help point out where the problem is. Complexity of templates, installed plugins, number and types of archive templates that get rebuilt when a new entry is posted, and configuation settings in both the MT config file (such as the PingTimeout setting) and the weblog config (such as whether Trackback AutoDiscovery is enabled) can affect the time MT needs to post a new entry.

 

 

I have been working on this for almost two weeks, and when I found the error log messages I had high hopes that it was related to the original problem. I fear you are correct in saying it is two - though the spammer issue is pretty easily resolved.

 

I upgraded from MT 3.17 to 3.2. The upgrade seemed to go relatively flawlessly and everything seemed to work ok - for awhile. Then about two weeks ago I started having the problem of MR freezing during post (no error messages in the Activity log). It would start the post cycle and stop after a while without posting to the site or going through the ping cycle. It only occurs on medium to long posts that utilize the extended entry portion of MT. Short posts using only the entry field seem to have no problems. IF I publish a second time, it does post to the site.

 

I have not changed my templates in anyway from the old version of mt to the new. Plugins did change with the upgrade. I have installed the standard MT plugins that come with 3.2 (notifier, template refresh, and spam lookup). I additionally have Glue, GlobalListings, MTFastInclude, otherblog, and Nofollow installed.

 

I have tried turning off both pings anf trackbacks to see if that makde any difference - it did not.

 

This problem is happening on two different installs or two different servers, so I had thought that perhaps it was a conflict with a new perl module.

 

In My mt-config file I have not changed any of the default values except that

Safemode is set to 0

GenerateTrackBackRSS 0

LaunchBackgroundTasks 0

 

PingTimeOut is at the default vaule.

 

This blog has the following archives : individual, monthly, and category

Posted

I discovered the "culprit." It was a plugin conflcit which I discovered by disabling one plugin at a time.

 

The actual problem was with waypath, and I will contact them to see if there have been changes at their site.

 

Thanks for the help! :huh:

 

Thanks for the welcome, and thank you for the response. :dance:

I have been working on this for almost two weeks, and when I found the error log messages I had high hopes that it was related to the original problem. I fear you are correct in saying it is two - though the spammer issue is pretty easily resolved.

 

I upgraded from MT 3.17 to 3.2. The upgrade seemed to go relatively flawlessly and everything seemed to work ok - for awhile. Then about two weeks ago I started having the problem of MR freezing during post (no error messages in the Activity log). It would start the post cycle and stop after a while without posting to the site or going through the ping cycle. It only occurs on medium to long posts that utilize the extended entry portion of MT. Short posts using only the entry field seem to have no problems. IF I publish a second time, it does post to the site.

 

I have not changed my templates in anyway from the old version of mt to the new. Plugins did change with the upgrade. I have installed the standard MT plugins that come with 3.2 (notifier, template refresh, and spam lookup). I additionally have Glue, GlobalListings, MTFastInclude, otherblog, and Nofollow installed.

 

I have tried turning off both pings anf trackbacks to see if that makde any difference - it did not.

 

This problem is happening on two different installs or two different servers, so I had thought that perhaps it was a conflict with a new perl module.

 

In My mt-config file I have not changed any of the default values except that

Safemode is set to 0

GenerateTrackBackRSS 0

LaunchBackgroundTasks 0

 

PingTimeOut is at the default vaule.

 

This blog has the following archives : individual, monthly, and category

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...