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?
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.
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).
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!)
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?
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.
Internal server error, followed by a surprisingly persistent malicious commenter notice (that is, waiting a bit and hitting 'post' again didn't fix it).
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.
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.
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.)
(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.)
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.
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.
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.
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.
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 wolfson@coelacanth.dyndns.org", instead of "scp mtdb wolfson@coelacanth.dyndns.org:". Feel free to delete that file.
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.
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.
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.
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.
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 there is scads o' comment spma this A.M., I am thinking perhaps these two messages are something relating to a broken spma filter?
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.
* 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?
Posted by ben wolfson | Link to this comment | 04-13-06 1:53 PM
I'm getting 500 errors when posting comments (they are there, if you hit back and refresh).
Posted by apostropher | Link to this comment | 04-13-06 1:54 PM
Also, I can see the database just fine. It lives in ~/.moveable_type/mtdb.
Or perhaps you meant from the web.
Posted by ben wolfson | Link to this comment | 04-13-06 1:55 PM
Type 500 errors, not 500 separate errors.
Posted by apostropher | Link to this comment | 04-13-06 1:55 PM
I see goofy question boxes instead of apostrophes. Surely you have someone on staff who can take care of that.
Posted by Armsmasher | Link to this comment | 04-13-06 1:58 PM
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.
Posted by FL | Link to this comment | 04-13-06 1:59 PM
Woohoo!
Posted by Chopper | Link to this comment | 04-13-06 2:02 PM
Hurrah!
Posted by Jackmormon | Link to this comment | 04-13-06 2:04 PM
Yipee!
Posted by Idealist | Link to this comment | 04-13-06 2:06 PM
A bit slow, though. Or maybe that's on my end...
___
I just got the "malicious comment posting" notice.
Posted by Jackmormon | Link to this comment | 04-13-06 2:07 PM
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.
Posted by Jackmormon | Link to this comment | 04-13-06 2:08 PM
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.
Posted by Becks | Link to this comment | 04-13-06 2:11 PM
Yipee!
Posted by Idealist | Link to this comment | 04-13-06 2:13 PM
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.
Posted by ogged | Link to this comment | 04-13-06 2:15 PM
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!
Posted by apostropher | Link to this comment | 04-13-06 2:15 PM
TODO: Make sure stat/referrer tracking works again.
Posted by Becks | Link to this comment | 04-13-06 2:15 PM
Becks is teh hero!!!
Posted by bitchphd | Link to this comment | 04-13-06 2:25 PM
Old comment links should work.
Posted by ben wolfson | Link to this comment | 04-13-06 2:28 PM
And also, "Internal Server Error" after posting a comment. Which nonetheless seems to have shown up.
Posted by bitchphd | Link to this comment | 04-13-06 2:30 PM
Except that time, when it just posted and returned me to this screen like a well-behaved little weblog.
Posted by bitchphd | Link to this comment | 04-13-06 2:32 PM
Right, the 500 error is intermittent.
Posted by ben wolfson | Link to this comment | 04-13-06 2:32 PM
Becks, this is awesome.
Posted by Joe Drymala | Link to this comment | 04-13-06 2:33 PM
Are you really getting the old comment links to work? Because I'm not.
Posted by Becks | Link to this comment | 04-13-06 2:34 PM
Some characters appear not to have made the transition well: "So I?m"
Posted by ben wolfson | Link to this comment | 04-13-06 2:36 PM
Also, becks, I really am. F'rinstance, this link takes me to the right place.
Posted by ben wolfson | Link to this comment | 04-13-06 2:37 PM
Actually ... it doesn't! It takes me to a thread with id 4442, but it's a different thread. That is not good.
Posted by ben wolfson | Link to this comment | 04-13-06 2:39 PM
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).
Posted by Becks | Link to this comment | 04-13-06 2:41 PM
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!
Posted by ben wolfson | Link to this comment | 04-13-06 2:42 PM
George Bush doesn't care about comments.
Posted by Armsmasher | Link to this comment | 04-13-06 2:44 PM
The # shouldn't make a difference and, so far as I can tell, doesn't.
Posted by ben wolfson | Link to this comment | 04-13-06 2:45 PM
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!)
Posted by ogged | Link to this comment | 04-13-06 2:46 PM
You've done yeoperson's work in getting this back up. Offers to assist still stand, but... huzzah!
Posted by Matthew Harvey | Link to this comment | 04-13-06 2:46 PM
I did notice that the entry number for the Innocence thread was a different number than it had been previously.
Posted by apostropher | Link to this comment | 04-13-06 2:47 PM
Not a lot of room for things to go wrong:
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?
Posted by ben wolfson | Link to this comment | 04-13-06 2:48 PM
Even funnier, the entry number that used to be assigned to Innocence is now assigned to a post entitled "Make It Stop".
Posted by apostropher | Link to this comment | 04-13-06 2:49 PM
And just before I go out of town!
It is neat to be back.
Posted by A White Bear | Link to this comment | 04-13-06 2:52 PM
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!
Posted by ben wolfson | Link to this comment | 04-13-06 2:53 PM
CRAP CRAP CRAP. Is this true???
Posted by Becks | Link to this comment | 04-13-06 2:55 PM
Uh oh.
Posted by apostropher | Link to this comment | 04-13-06 3:01 PM
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.
Posted by jim | Link to this comment | 04-13-06 3:15 PM
Or, you guys could go back in the archives wherever people linked to a previous comment, and just update each link individually.
Posted by Joe Drymala | Link to this comment | 04-13-06 3:16 PM
Labs, you want to get cracking on that?
Posted by apostropher | Link to this comment | 04-13-06 3:18 PM
I'm willing to give you editing rights over the entire Intarweb, so you can update incoming links from everywhere. Use this power wisely.
Posted by Matt Weiner | Link to this comment | 04-13-06 3:32 PM
Internal server error, followed by a surprisingly persistent malicious commenter notice (that is, waiting a bit and hitting 'post' again didn't fix it).
Posted by Matt Weiner | Link to this comment | 04-13-06 3:34 PM
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.
Posted by Jackmormon | Link to this comment | 04-13-06 3:44 PM
Thanks, internal server error followed by malicious comment notice.
Punks.
Posted by Jackmormon | Link to this comment | 04-13-06 3:46 PM
Huzzah!!!!
Though I'm going to go back to pretending it doesn't work since my productivity has mysteriously spiked.
Posted by Saheli | Link to this comment | 04-13-06 4:12 PM
where do zee bloggers go to log in? The old site doesn't work.
Posted by Tia | Link to this comment | 04-13-06 5:08 PM
(is that what you mean by "why can't we see the database?")
Hey, I am malice free!
Posted by Tia | Link to this comment | 04-13-06 5:10 PM
That's not what I hear from little Mittens.
Posted by Matt Weiner | Link to this comment | 04-13-06 5:20 PM
I emailed you the URL, Tia.
Posted by apostropher | Link to this comment | 04-13-06 5:41 PM
Not taking it lying down when that Mittens bitch gets in my face hardly counts as malice. And 'little'? Have you seen her lately?
Posted by Tia | Link to this comment | 04-13-06 5:52 PM
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.
Posted by SomeCallMeTim | Link to this comment | 04-13-06 6:07 PM
38: does that mean that the new ids potentially have no relation to the old ones? Fuck.
Posted by ben wolfson | Link to this comment | 04-13-06 7:39 PM
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.
Posted by Becks | Link to this comment | 04-13-06 7:43 PM
Actually, a little bit of comparison between the two dbs suggests that it's not completely arbitrary.
Posted by ben wolfson | Link to this comment | 04-13-06 7:59 PM
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.
Posted by Chopper | Link to this comment | 04-13-06 8:05 PM
Hey, the new host has a python module on it to which I made a patch back 2001!
Posted by ben wolfson | Link to this comment | 04-13-06 8:08 PM
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.)
Posted by Teh Modesto Kid | Link to this comment | 04-13-06 8:25 PM
The same thing happened to me with my latest comment on the black question mark thread.
Posted by teofilo | Link to this comment | 04-13-06 8:27 PM
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.
Posted by apostropher | Link to this comment | 04-13-06 8:33 PM
But that's why we changed servers in the first place!
Posted by Becks | Link to this comment | 04-13-06 8:34 PM
Here ya go, Chopper. Blame Stroll: I found it at his place. He says it's a spoof.
Posted by bitchphd | Link to this comment | 04-13-06 8:53 PM
Funny, isn't it?
Posted by apostropher | Link to this comment | 04-13-06 8:58 PM
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".
Posted by Standpipe Bridgeplate | Link to this comment | 04-13-06 9:18 PM
Testing
Posted by Becks | Link to this comment | 04-13-06 10:09 PM
more testing
Posted by Becks | Link to this comment | 04-13-06 10:16 PM
positively infuriating
Posted by Matt Weiner | Link to this comment | 04-13-06 10:16 PM
Yes, the Internal Server Errors totally suck. Fixing that is a high priority but out of our hands.
Posted by Becks | Link to this comment | 04-13-06 10:21 PM
Testing.
Posted by ogged | Link to this comment | 04-13-06 10:48 PM
That worked. I wonder if this will.
Posted by ogged | Link to this comment | 04-13-06 10:48 PM
Huh, slow as (a good) fuck, but no 500 error, and it lets me post in quick succession. Anyone else?
Posted by ogged | Link to this comment | 04-13-06 10:49 PM
Testing some more
Posted by Becks | Link to this comment | 04-13-06 10:51 PM
And another one right quick
Posted by Becks | Link to this comment | 04-13-06 10:51 PM
And another one
Posted by Becks | Link to this comment | 04-13-06 10:52 PM
Just got the 500. Try again?
Posted by Becks | Link to this comment | 04-13-06 10:53 PM
Ogged, this is not slow like a good fuck. This is like "OK, you can finish now....Aaaanytime..."
Posted by Becks | Link to this comment | 04-13-06 10:54 PM
Testing
Posted by Becks | Link to this comment | 04-13-06 10:57 PM
It was working when I tried it Becks, I have no idea how you managed to break it again.
Posted by ogged | Link to this comment | 04-13-06 11:00 PM
That worked too (you have to purr to it, baby), but it is very slow.
Posted by ogged | Link to this comment | 04-13-06 11:00 PM
It briefly worked for me, too.
Posted by Becks | Link to this comment | 04-13-06 11:00 PM
(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.)
Posted by Matt Weiner | Link to this comment | 04-13-06 11:01 PM
Shit, got the error. So much for purring. I wonder if the internal server error is really a time-out error.
Posted by ogged | Link to this comment | 04-13-06 11:02 PM
Oooh! That one just worked for me, although slowly. I need some of your mojo.
Posted by Becks | Link to this comment | 04-13-06 11:02 PM
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.
Posted by Becks | Link to this comment | 04-13-06 11:03 PM
It doesn't send the comment email when it gets the Internal Server Error, either.
Posted by Becks | Link to this comment | 04-13-06 11:04 PM
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.
Posted by ogged | Link to this comment | 04-13-06 11:09 PM
Slow, but worked.
Posted by ogged | Link to this comment | 04-13-06 11:09 PM
New setting! More tests!
Posted by Becks | Link to this comment | 04-13-06 11:10 PM
Dude! I just ENABLED background tasks!
Posted by Becks | Link to this comment | 04-13-06 11:11 PM
Per this
Posted by Becks | Link to this comment | 04-13-06 11:11 PM
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.
Posted by ogged | Link to this comment | 04-13-06 11:11 PM
Nope, just got the error again. Fuckity fuck.
Posted by ogged | Link to this comment | 04-13-06 11:11 PM
All of mine have worked so far. My setting (LaunchBackgroundTasks 1) is the one we're testing right now, BTW.
Posted by Becks | Link to this comment | 04-13-06 11:12 PM
Crapola. You would thing throwing some tasks into the background would speed things up a bit, too.
Posted by Becks | Link to this comment | 04-13-06 11:13 PM
Purrrrrr....it likes me so far.
Posted by Becks | Link to this comment | 04-13-06 11:14 PM
And another....
Posted by Becks | Link to this comment | 04-13-06 11:14 PM
Yet another...
Posted by Becks | Link to this comment | 04-13-06 11:15 PM
I haven't had any problems since the setting changed, O.
Posted by Becks | Link to this comment | 04-13-06 11:15 PM
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.
Posted by Becks | Link to this comment | 04-13-06 11:16 PM
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.
Posted by ogged | Link to this comment | 04-13-06 11:17 PM
You guys have fun, I'm going to go axe-murder the—hey, maybe not necessary.
Posted by Standpipe Bridgeplate | Link to this comment | 04-13-06 11:17 PM
I'm looking at the file right now in emacs. The version in play is the LaunchBackgroundTasks 1 file.
Posted by Becks | Link to this comment | 04-13-06 11:17 PM
Ok, it is your version.
Posted by ogged | Link to this comment | 04-13-06 11:18 PM
And I just got the error again.
Posted by ogged | Link to this comment | 04-13-06 11:18 PM
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.
Posted by Becks | Link to this comment | 04-13-06 11:18 PM
It likes me. I haven't seen the error yet.
Posted by Becks | Link to this comment | 04-13-06 11:20 PM
Y'all need to coördinate, people.
Posted by ben wolfson | Link to this comment | 04-13-06 11:21 PM
Or get a room.
Posted by ben wolfson | Link to this comment | 04-13-06 11:22 PM
Hey, I just got an internal server error!
Posted by ben wolfson | Link to this comment | 04-13-06 11:22 PM
That's it. It doesn't like boys.
Posted by Becks | Link to this comment | 04-13-06 11:23 PM
TODO: disallow the use of dieresis in comments.
Posted by ogged | Link to this comment | 04-13-06 11:24 PM
Ben, dear, did you do anything with the database? I see a file called "wolfson" in the database directory.
Posted by Becks | Link to this comment | 04-13-06 11:26 PM
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.
Posted by Becks | Link to this comment | 04-13-06 11:27 PM
Still no errors, guys.
Posted by Becks | Link to this comment | 04-13-06 11:27 PM
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 wolfson@coelacanth.dyndns.org", instead of "scp mtdb wolfson@coelacanth.dyndns.org:". Feel free to delete that file.
Posted by ben wolfson | Link to this comment | 04-13-06 11:28 PM
Pardon me while I try to comment until I get the error...
Posted by ogged | Link to this comment | 04-13-06 11:29 PM
Everything appears to be working so I don't think the DB is corrupted. Still, that is not A Happy Message.
Posted by Becks | Link to this comment | 04-13-06 11:30 PM
Not yet...
Posted by ogged | Link to this comment | 04-13-06 11:30 PM
Works fine for me:
[ulawun .movable_type 01:29:46]$ sqlite3 mtdb
SQLite version 3.2.5
Enter ".help" for instructions
sqlite>
Posted by ben wolfson | Link to this comment | 04-13-06 11:30 PM
Do de do...
Posted by ogged | Link to this comment | 04-13-06 11:30 PM
116 - So polite.
Posted by Becks | Link to this comment | 04-13-06 11:30 PM
I just got it for the first time.
Posted by Becks | Link to this comment | 04-13-06 11:31 PM
Got the error. Had turned on all of IE's script debugging stuff, but it didn't complain about anything.
Posted by ogged | Link to this comment | 04-13-06 11:31 PM
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.
Posted by Becks | Link to this comment | 04-13-06 11:33 PM
I think the script debugging only works for client-side errors.
Posted by Becks | Link to this comment | 04-13-06 11:34 PM
script debugging only works for client-side errors
This is true, but I'm trying everything google turns up...
Posted by ogged | Link to this comment | 04-13-06 11:34 PM
worth a shot
Posted by Becks | Link to this comment | 04-13-06 11:36 PM
Just got it.
Posted by Becks | Link to this comment | 04-13-06 11:39 PM
I'm getting kinda sleepy.
Posted by Becks | Link to this comment | 04-13-06 11:40 PM
Might have to bail soon.
Posted by Becks | Link to this comment | 04-13-06 11:40 PM
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!
Posted by ogged | Link to this comment | 04-13-06 11:42 PM
We can check the server error logs ourselves with the new host. But there aren't any errors. Not helpful.
Posted by Becks | Link to this comment | 04-13-06 11:42 PM
And the site decides to send me off to bed with an Internal Server Error. Motherfucker.
Posted by Becks | Link to this comment | 04-13-06 11:43 PM
Ok, one more test won't hurt...
Posted by ogged | Link to this comment | 04-14-06 12:29 AM
Come on error...
Posted by ogged | Link to this comment | 04-14-06 12:29 AM
You know you wanna...
Posted by ogged | Link to this comment | 04-14-06 12:30 AM
For crying out loud...
Posted by ogged | Link to this comment | 04-14-06 12:30 AM
Not amused...
Posted by ogged | Link to this comment | 04-14-06 12:31 AM
I can't break it!
Posted by ogged | Link to this comment | 04-14-06 12:31 AM
It loves me, like a pathetic little puppy!
Posted by ogged | Link to this comment | 04-14-06 12:32 AM
In 140, the server is the puppy.
Posted by ogged | Link to this comment | 04-14-06 12:32 AM
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.
Posted by ogged | Link to this comment | 04-14-06 12:33 AM
Not "and 'Internal Server Error," "than 'Internal Server Error."
Posted by ogged | Link to this comment | 04-14-06 12:35 AM
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.
Posted by eb | Link to this comment | 04-14-06 1:24 AM
No error for me, by the way.
Posted by eb | Link to this comment | 04-14-06 1:26 AM
My 145 gave me an error, but the comment showed up immediately when I clicked back into the thread from the mainpage.
Posted by eb | Link to this comment | 04-14-06 1:27 AM
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.
Posted by eb | Link to this comment | 04-14-06 1:29 AM
Testing.
Posted by eb | Link to this comment | 04-14-06 1:29 AM
Testing
Posted by eb | Link to this comment | 04-14-06 1:30 AM
testing
Posted by eb | Link to this comment | 04-14-06 1:30 AM
No errors on 149 or 150. I'll stop now.
Posted by eb | Link to this comment | 04-14-06 1:32 AM
testing
Posted by mealworm | Link to this comment | 04-14-06 3:26 AM
A bit slow, not terribly, and no errors.
Posted by mealworm | Link to this comment | 04-14-06 3:27 AM
Okay, that one got me an error, but just the unhelpful "Internal Server Error".
Posted by mealworm | Link to this comment | 04-14-06 3:28 AM
Hey have you guys seen this intriguing message at the bottom of the comments pages (below all the buttons)?
Also there is scads o' comment spma this A.M., I am thinking perhaps these two messages are something relating to a broken spma filter?
Posted by Teh Modesto Kid | Link to this comment | 04-14-06 5:35 AM
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?
Posted by The Modesto Kid | Link to this comment | 04-14-06 5:36 AM
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).
Posted by Matt Weiner | Link to this comment | 04-14-06 7:11 AM
No error either on 157.
Posted by Matt Weiner | Link to this comment | 04-14-06 7:14 AM
I am getting the intriguing message still. New version of Firefox on Windows XP.
Posted by Teh Modesto Kid | Link to this comment | 04-14-06 7:34 AM
Yay! It's back up! Becks is the hero!
Posted by LizardBreath | Link to this comment | 04-14-06 7:39 AM
Links to comment pages are back up, both from Google and within-blog! But links to individual comments don't seem to be working.
Posted by Matt Weiner | Link to this comment | 04-14-06 7:48 AM
Out of revenge for my ingratitude, when I posted 161 it gave me the error message reproduced in 147.
Posted by Matt Weiner | Link to this comment | 04-14-06 7:50 AM
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.
Posted by Idealist | Link to this comment | 04-14-06 7:59 AM