* Get the Innocence thread working
Maybe we could skip this one ...
I tried adding some bits to .htaccess that I thought would allow the old comment links to continue working, but looks like not. I assume apache need not be restarted to get it to work (and I assume apache is the server in use). Perhaps some guru-like person would like to take a stab?
I'm getting 500 errors when posting comments (they are there, if you hit back and refresh).
Also, I can see the database just fine. It lives in ~/.moveable_type/mtdb.
Or perhaps you meant from the web.
Type 500 errors, not 500 separate errors.
I see goofy question boxes instead of apostrophes. Surely you have someone on staff who can take care of that.
Becks, I'm a little bit in love with you for doing all of this. Or it's the new bra, I'm not sure which.
A bit slow, though. Or maybe that's on my end...
___
I just got the "malicious comment posting" notice.
Okay, that's weird: when I tried to post 10, it gave me a "internal servor error" page--but, clearly, it posted anyways.
__
Another malicious posting notice. Twice.
6 - I can see how it's hard to tell, Labs. Both my tits and the return of Unfogged are quite hooray-worthy.
Sorry, y'all. I'm likely not going to be able to investigate other errors until I get off work. Please continue to log them, though.
Good work.
In addition to all the static images, all the "cached" articles in the old /mt-static/directory have to be moved over, and their link structure checked or fixed or otherwise dealt with.
Not a bug, but something that we discussed: turning off trackbacks and putting links to technorati and blogsearch in the sidebar.
Both my tits and the return of Unfogged are quite hooray-worthy.
It would be a shame if only one of your tits was hooray-worthy.
Hooray! Becks' titties! Both of 'em! Hooray!
TODO: Make sure stat/referrer tracking works again.
And also, "Internal Server Error" after posting a comment. Which nonetheless seems to have shown up.
Except that time, when it just posted and returned me to this screen like a well-behaved little weblog.
Right, the 500 error is intermittent.
Are you really getting the old comment links to work? Because I'm not.
Some characters appear not to have made the transition well: "So I?m"
Also, becks, I really am. F'rinstance, this link takes me to the right place.
Actually ... it doesn't! It takes me to a thread with id 4442, but it's a different thread. That is not good.
That is not good at all. Also, you were just trying a link to a comment page. I was trying an actual link to a comment (mt-comments.cgi?entry_id=4643#109055 versus your mt-comments.cgi?entry_id=4643).
So, google thinks that "What To Call It" is entryid 4442, while the new install thinks it's entry id 4290. Other threads are similarly mismatched.
This suggests a fun, systemic problem!
George Bush doesn't care about comments.
The # shouldn't make a difference and, so far as I can tell, doesn't.
Oh fucksters; did the IDs get renumbered during the import? MT doesn't change the number, obviously, when a previous entry or comment is deleted, but if the deleted entries are ignored during an import...that's not good.
(Remember folks, if worse comes to worst, the blog remains, just as we left it, on Site5's server!)
You've done yeoperson's work in getting this back up. Offers to assist still stand, but... huzzah!
I did notice that the entry number for the Innocence thread was a different number than it had been previously.
Not a lot of room for things to go wrong:
#! /usr/local/bin/python
import cgitb, cgi
cgitb.enable()
form = cgi.FieldStorage()
eid = form.getvalue("entry_id", '')
print "Location: http://unfogged.com/cgi-sys/cgiwrap/unfogged/managed-mt/mt-comments.cgi?entry_id=%s" % eid
Ogged's diagnosis: probably correct! Is there a way to do a hella complicated re-importation such that the old ids are preserved? Or (de)normalize the db with reference to the old db which is helpfully in a different format?
Even funnier, the entry number that used to be assigned to Innocence is now assigned to a post entitled "Make It Stop".
And just before I go out of town!
It is neat to be back.
Actually, if we found out where the discontinuities were, it wouldn't be too complicated to modify the redirection script to take that into account. Perhaps the discovery of these discontinuities could be done automatically by someone with mad SQL skillz? Or, really, through the analysis of a db dump in a friendly format.
Don't worry friends! We'll see each other through this!
Do not despair. SMOP. Get the sequence of postids from the original database (doesn't take very mad SQL skillz) and atob() them, that's column A of a lookup table. Generate sequential new postids, that's column B. Now write a script that looks for references to posts, pulls out the postid, atob()'s it, searches column A for the atob() result (straight binary search) and substitutes whatever's in column B for it. Set that script to gently chew on the archives.
Or, you guys could go back in the archives wherever people linked to a previous comment, and just update each link individually.
Labs, you want to get cracking on that?
I'm willing to give you editing rights over the entire Intarweb, so you can update incoming links from everywhere. Use this power wisely.
Internal server error, followed by a surprisingly persistent malicious commenter notice (that is, waiting a bit and hitting 'post' again didn't fix it).
Could it be that the new server is better at recognizing hidden malice?
Also: how cool is it to have tech support commenting in the thread? It's like adult supervision.
Thanks, internal server error followed by malicious comment notice.
Punks.
Huzzah!!!!
Though I'm going to go back to pretending it doesn't work since my productivity has mysteriously spiked.
where do zee bloggers go to log in? The old site doesn't work.
(is that what you mean by "why can't we see the database?")
Hey, I am malice free!
That's not what I hear from little Mittens.
Not taking it lying down when that Mittens bitch gets in my face hardly counts as malice. And 'little'? Have you seen her lately?
Becks:
I think y'all might have forgotten to migrate the cock jokes, too. Or maybe the file is too large to upload. IYKWIM. AITYD.
38: does that mean that the new ids potentially have no relation to the old ones? Fuck.
does that mean that the new ids potentially have no relation to the old ones?
That is correct.
Fuck.
That is correct.
We're considering deleting the data and doing an export/import directly from/to MySQL instead of using MT's export/import. That's what Ogged's host did the last time he moved the site and it kept all of the entry_ids.
Actually, a little bit of comparison between the two dbs suggests that it's not completely arbitrary.
Can we get an inane and/or substantive post where we make fun of someone or something? It can be me, I don't care--I'll simply be comforted by my massive cock--I'm just saying that now that the smack-talking venue is open, it would be nice to talk some smack.
Hey, the new host has a python module on it to which I made a patch back 2001!
I just posted 2 (two) comments on the thread above this one; the second post got a 500 (five hundred) error but when I navigated back to the page I had posted from and reloaded it, my second comment had posted. Make of that what you will. (I kind of liked it, gave me a nostalgic feeling like I was back on the old Unfogged.)
The same thing happened to me with my latest comment on the black question mark thread.
The same mystery comment behavior used to happen at my site a lot, then disappeared totally when I changed servers. Make of that what you will.
But that's why we changed servers in the first place!
Here ya go, Chopper. Blame Stroll: I found it at his place. He says it's a spoof.
I'm afraid that when I wake up tomorrow morning, all my memories will be just as they were as of tonight, except with an extra "cgiwrap".
Yes, the Internal Server Errors totally suck. Fixing that is a high priority but out of our hands.
Huh, slow as (a good) fuck, but no 500 error, and it lets me post in quick succession. Anyone else?
Ogged, this is not slow like a good fuck. This is like "OK, you can finish now....Aaaanytime..."
It was working when I tried it Becks, I have no idea how you managed to break it again.
That worked too (you have to purr to it, baby), but it is very slow.
(67 was meant to the logical third member of the sequence started by 65 and 66. Except I think maybe it's "trying" that when intensified is "infuriating." Ah, I suck.
Anyway, not intended as a reflection on your and ogged's et al. doughty efforts, sorry if it came across that way.)
Shit, got the error. So much for purring. I wonder if the internal server error is really a time-out error.
Oooh! That one just worked for me, although slowly. I need some of your mojo.
Crap. Just got it, too. I've noticed that when we get the internal server error, the comment is logged but the sidebar and RSS feed aren't updated. It's like the database save is working but not whatever "update a bunch of stuff" notification it's trying to register.
It doesn't send the comment email when it gets the Internal Server Error, either.
I just took out the line that disables background tasks. There's a little script you can run to see if the server supports them, and this one does, so let's see if that helps.
Dude! I just ENABLED background tasks!
That worked too. Basically, each comment causes several rebuilds, first to the comment thread, then, like you notice, the sidebar and feeds. It's finishing the first, but crapping out on the others. Given that it's intermittent, I'm still suspecting a time-out. So I'm hopeful that enabling background tasks will help.
Nope, just got the error again. Fuckity fuck.
All of mine have worked so far. My setting (LaunchBackgroundTasks 1) is the one we're testing right now, BTW.
Crapola. You would thing throwing some tasks into the background would speed things up a bit, too.
I haven't had any problems since the setting changed, O.
I say we leave this setting in place and see what happens. I'm sure we can count on people to complain if they see the error.
My setting (LaunchBackgroundTasks 1) is the one we're testing right now, BTW.
Are you sure? Because I just uploaded my own version of the config file that just had LaunchBackroundTasks 0 commented out.
You guys have fun, I'm going to go axe-murder the—hey, maybe not necessary.
I'm looking at the file right now in emacs. The version in play is the LaunchBackgroundTasks 1 file.
When I edited the file, it had LaunchBackgroundVersion 0 commented out. I thought you had tried that earlier and it hadn't worked. I didn't realize you had just put a new file version up and hadn't time to test it yet.
It likes me. I haven't seen the error yet.
Y'all need to coördinate, people.
Hey, I just got an internal server error!
TODO: disallow the use of dieresis in comments.
Ben, dear, did you do anything with the database? I see a file called "w-lfs-n" in the database directory.
Just wondering because when I try to access the database, I get the error "Unable to open database: database disk image is malformed". My syntax could be off since I don't know SQLite but that message disturbs me.
Oh! Yes. I was scp-ing it back to my computer (in order to work on the revised redirection script), and I forgot the colon, so that initially it was just "scp mtdb w-lfs-n@coelacanth.dyndns.org", instead of "scp mtdb w-lfs-n@coelacanth.dyndns.org:". Feel free to delete that file.
Pardon me while I try to comment until I get the error...
Everything appears to be working so I don't think the DB is corrupted. Still, that is not A Happy Message.
Works fine for me:
[ulawun .movable_type 01:29:46]$ sqlite3 mtdb
SQLite version 3.2.5
Enter ".help" for instructions
sqlite>
Got the error. Had turned on all of IE's script debugging stuff, but it didn't complain about anything.
OK, SQLite is working for me now. I'm kind of torn about this arrangement - on the one hand, I love me some emacs. On the other, not liking the nonstandard syntax for SQLite so much.
I think the script debugging only works for client-side errors.
script debugging only works for client-side errors
This is true, but I'm trying everything google turns up...
Me too. What we really need to see are the server error logs. Maybe tomorrow they'll be around to give those to us. Night all!
We can check the server error logs ourselves with the new host. But there aren't any errors. Not helpful.
And the site decides to send me off to bed with an Internal Server Error. Motherfucker.
It loves me, like a pathetic little puppy!
Oh piss, it won't give me an error. If y'all, when next you comment, happen to see a more informative error message and "Internal Server Error," I'd be much obliged if you could copy and paste it into your next comment.
Not "and 'Internal Server Error," "than 'Internal Server Error."
Hey, it's back. Thanks for all of the hard work. As a token of my appreciation I'll note that the posts feed shows post authors, but the posts + comments feed (unfogged.xml) no longer does so on my copy of GreatNews. Unless this is how it always was and I've forgotten.
My 145 gave me an error, but the comment showed up immediately when I clicked back into the thread from the mainpage.
Error on 146 too. Here's what I got:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, unfogged@pair.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
A bit slow, not terribly, and no errors.
Okay, that one got me an error, but just the unhelpful "Internal Server Error".
Hey have you guys seen this intriguing message at the bottom of the comments pages (below all the buttons)?
Odd number of elements in hash assignment at lib/MT/App/Comments.pm line 68.
Use of uninitialized value in list assignment at lib/MT/App/Comments.pm line 68.
Also: does the title of this post indicate that you are planning to migrate Unfogged to DOS? Will it still work with my Windows computer?
I'm not getting the intriguing message at the bottom of this comment page, in either pop-up or non-pop-up modes (old version of Firefox on OS X Mac).
I am getting the intriguing message still. New version of Firefox on Windows XP.
Yay! It's back up! Becks is the hero!
Links to comment pages are back up, both from Google and within-blog! But links to individual comments don't seem to be working.
Out of revenge for my ingratitude, when I posted 161 it gave me the error message reproduced in 147.
I tried to comment, got this error message:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, unfogged@pair.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Refreshed, clicked retry and ended up with a double post.
