I have a user on a recently-rebuilt FreeBSD system, running MT 3.34. It was a fairly significant (though sadly necessary) server config change, moving from apache 1.x to 2.x, enabling suEXEC, among other things. Since the upgrade, when he tries to publish pages, Movable Type writes empty, zero-byte files. It generates no visible errors, acts as if it's publishing successfully, but there's simply nothing there.
I presume it's not a permissions error, since it is writing files.
The OS version was not changed (FreeBSD 6.2), so the BSDDB format should be unchanged.
All the admin pages work correctly. mt-check.cgi returns no errors (just notices about missing optional items).
I've noticed the following errors in his log which could be related:
[Tue Oct 30 16:53:42 2007] [error] [client 70.171.164.156] script not found or unable to stat: /usr/local/home/swssoft/cgi-bin/moveabletype
(This is an unsurprising error, as his mt installation directory is named "mt" not "moveabletype" -- probably a spammer searching for a script.)
[Tue Oct 30 16:55:54 2007] [error] [client 71.227.147.205] Deep recursion on subroutine "Image::Magick::AUTOLOAD" at /usr/local/lib/perl5/site_perl/5.8.8/mach/Image/Magick.pm line 42.
[Tue Oct 30 16:56:02 2007] [error] [client 71.227.147.205] Out of memory during request for
[Tue Oct 30 16:56:02 2007] [error] [client 71.227.147.205] 4084
[Tue Oct 30 16:56:02 2007] [error] [client 71.227.147.205] bytes, total sbrk() is
[Tue Oct 30 16:56:02 2007] [error] [client 71.227.147.205] 536799232
[Tue Oct 30 16:56:02 2007] [error] [client 71.227.147.205] bytes!
Indeed, Image::Magick is identified as a missing module, but is also listed as optional.
Can't see anything else that looks like a likely culprit...any thoughts? Thanks!
Full Version: Blank Pages
I have no real idea, but as far as collecting information, let's back up a little.
What happens if you just do a simple file association? So, create a new template module or index, put some filler information in, link it to a file and save. Basically, we're just trying to see if MT writes data at all before even worrying about the rebuild process.
If that works, then try a minimal index template, like:
...which if works, might imply that there's trouble with particular tags and not just the whole system.
Does nothing show up in the activity log? You mentioned some server-based stuff, but nothing from within MT itself.
What happens if you just do a simple file association? So, create a new template module or index, put some filler information in, link it to a file and save. Basically, we're just trying to see if MT writes data at all before even worrying about the rebuild process.
If that works, then try a minimal index template, like:
CODE
<html>
<body><$MTBlogName$></body>
</html>
<body><$MTBlogName$></body>
</html>
...which if works, might imply that there's trouble with particular tags and not just the whole system.
Does nothing show up in the activity log? You mentioned some server-based stuff, but nothing from within MT itself.
QUOTE (Su- @ Oct 30 2007, 07:06 PM) 
I have no real idea, but as far as collecting information, let's back up a little.
What happens if you just do a simple file association? So, create a new template module or index, put some filler information in, link it to a file and save. Basically, we're just trying to see if MT writes data at all before even worrying about the rebuild process.
If that works, then try a minimal index template, like:
...which if works, might imply that there's trouble with particular tags and not just the whole system.
Does nothing show up in the activity log? You mentioned some server-based stuff, but nothing from within MT itself.
What happens if you just do a simple file association? So, create a new template module or index, put some filler information in, link it to a file and save. Basically, we're just trying to see if MT writes data at all before even worrying about the rebuild process.
If that works, then try a minimal index template, like:
CODE
<html>
<body><$MTBlogName$></body>
</html>
<body><$MTBlogName$></body>
</html>
...which if works, might imply that there's trouble with particular tags and not just the whole system.
Does nothing show up in the activity log? You mentioned some server-based stuff, but nothing from within MT itself.
As a matter of fact, nothing shows up in the activity log, which I found odd as it was clearly doing something. I shall try your suggestions tomorrow and post again, thanks.
Heh -- OK, I feel dumb. I was so fixated on the server changes being the cause that I didn't even think to check his disk quota, which was full. Sorry to have wasted all your time!
So it appears I need to reopen this question. It appears that the user's quota is being filled up by perl core dumps caused by the ImageMagick error I posted above. Any idea what would cause this "deep recursion" error? MT's setup script appears to be aware that ImageMagick is not installed.
Are you using any CAPTCHA's?
QUOTE (OtherNiceMan @ Dec 3 2007, 11:39 PM)
Are you using any CAPTCHA's?
I'm the user in question. No, i'm not using any captchas, and I can confirm that the perl core dumps didn't start until the 4.0.1 upgrade. According to mt-check:
Image::Magick
Your server does not have Image::Magick installed, or Image::Magick requires another module that is not installed. This module is needed if you would like to be able to create thumbnails of uploaded images. Please consult the installation instructions for help in installing Image::Magick.
According to mt-check, the only other optional modules missing are:
XML::Atom
Your server does not have XML::Atom installed, or XML::Atom requires another module that is not installed. This module enables the use of the Atom API. Please consult the installation instructions for help in installing XML::Atom.
Digest::SHA1
Your server does not have Digest::SHA1 installed, or Digest::SHA1 requires another module that is not installed. This module and its dependencies are required in order to allow commenters to be authenticated by OpenID providers including Vox and LiveJournal. Please consult the installation instructions for help in installing Digest::SHA1.
Crypt::DSA
Your server does not have Crypt::DSA installed, or Crypt::DSA requires another module that is not installed. This module accelerates comment registration sign-ins. Please consult the installation instructions for help in installing Crypt::DSA.
The upgrade itself ran smoothly once I got a good download. No errors, nothing odd. But the perl dumps are making it rather hard to get work done ;-)
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.