Denise (
denise) wrote in
dw_maintenance2009-04-18 06:19 pm
![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
Import issues
There are three commonly-reported issues we're seeing with importing your journal right now:
* Some icons are not transfering over -- the message will say that they're successful, but only the keywords/comments will come over, not the userpic itself.
* Entries will appear to have no comments, until you click through to the entry itself, at which point the comments will be visible.
* Tags will appear not to import, until you wait for a little while.
We're aware of all three problems, and are working on diagnosing and fixing them. There's no need to open a support request about these problems.
The other issues described in this news post still apply.
The geeky bits, for those who care:
The first problem is happening because the userpics are in the database, but not in MogileFS, our image-storage filesystem. We know what's happening, but haven't figured out what's causing it yet. Once we do, we'll fix it from happening again, and we'll likely be able to fix it automatically for every affected account (although we can't say that for sure until we locate the root cause).
We think that the second and third problems are happening because of memcached, the function we use to store commonly-accessed information in memory to drastically increase site performance. It may turn out to be something else entirely, of course, but our leading theory right now is that the information is making its way to our database, the database is just not telling memcached that the information's been updated. We're looking into the best ways to solve it. In the meantime, viewing the comment page and then returning to your journal will cause the comment counts to display properly, and some people have reported that viewing the Manage Tags page and then returning to your tags list will cause your tags to show up.
EDIT, 2300 EDT 18 April: We believe we've figured out what was causing these problems. Future imports (anything scheduled after now) should no longer display these symptoms, and we're working out the best way to fix accounts that were affected. We'll make a new
dw_maintenance post with the postmortem once we've deployed the fix.
* Some icons are not transfering over -- the message will say that they're successful, but only the keywords/comments will come over, not the userpic itself.
* Entries will appear to have no comments, until you click through to the entry itself, at which point the comments will be visible.
* Tags will appear not to import, until you wait for a little while.
We're aware of all three problems, and are working on diagnosing and fixing them. There's no need to open a support request about these problems.
The other issues described in this news post still apply.
The geeky bits, for those who care:
The first problem is happening because the userpics are in the database, but not in MogileFS, our image-storage filesystem. We know what's happening, but haven't figured out what's causing it yet. Once we do, we'll fix it from happening again, and we'll likely be able to fix it automatically for every affected account (although we can't say that for sure until we locate the root cause).
We think that the second and third problems are happening because of memcached, the function we use to store commonly-accessed information in memory to drastically increase site performance. It may turn out to be something else entirely, of course, but our leading theory right now is that the information is making its way to our database, the database is just not telling memcached that the information's been updated. We're looking into the best ways to solve it. In the meantime, viewing the comment page and then returning to your journal will cause the comment counts to display properly, and some people have reported that viewing the Manage Tags page and then returning to your tags list will cause your tags to show up.
EDIT, 2300 EDT 18 April: We believe we've figured out what was causing these problems. Future imports (anything scheduled after now) should no longer display these symptoms, and we're working out the best way to fix accounts that were affected. We'll make a new
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
no subject
I've tried twice to import comments, waiting three or so days in between, and they're still queued. (I filed a support ticket for this.) Maybe it's me... b/c people who've created accounts since I did have their comments.
You guys are amazing! It's all so happening, and people are chomping at the bit to be part of it! yay! please remember to sleep, eat, breathe, smile, and take a day off once in a while!
no subject
no subject
no subject
you guys are truly amazed and it must be so gratifying to see all the interest. my f list are all chomping at the bit to be let in here to run and play. lol. i hope your servers are ready for a huge flood of cash of April 30; hundreds of people will be hitting them at once. :D. Massive congratulations.
no subject
i feel so moved in now.
you can cross me off your to do list. i'll just be potting around here investigating happily; the next thing I'm all agog about is the crossposting function.
i'm happy with one of the templates for my layout so far, and am content to use an off the rack style later when more choices are available.
Again let me express my amazement and delight at what you guys are doing. It's so incredible to watch this happening. I never expected to be part of something like this and yet here I am. Do take good care of yourself, take breaks and eat. We're all in it for the long haul now. Love you.
no subject
no subject
lol I don't know if that helps you/anyone at all, but that was my experience.
no subject
no subject
Should I file a support request or is this a known problem? Should I just run the importer again?
no subject
no subject
no subject
no subject
no subject
no subject
no subject
Or was there a limit on the number of icons that could be imported?
no subject
no subject
That's why I was wondering about the icon limit. I have 143 on LJ and it was my icons that were more recently added to LJ that didn't import at all.
ETA: Number wise, I have 143 icons on LJ and only 65 transferred and the last one that did transfer didn't get the keywords/descriptions with it.
no subject
no subject
no subject
no subject
Really sorry about this...
Re: Really sorry about this...
no subject
Having just received notice of my entries and comments being imported (yay!), I noticed that my tags list seems to include three extras that were not part of my original tags: "after all," "could be twisted and molded into somethi," and "ever since ritsuka found out how soubi f."
All three of these tags link to the same post. The text for these tags comes from an entirely different post.
So far, the comments seem to be all there. :) Thumbs up, guys!
no subject
The other day, I was playing around with the importer to see how it handled inactive icons, so I imported from a small LJ account. Everything seemed fine.
Today, with the crossposter going into alpha, I decide to import my actual journal. When I do, I notice that a block of seventeen entries from the very beginning of my journal did not carry over. ("Nap Bites Man" to "This is getting personal." on my LJ archive.) I make a note to post a bug report about it.
Before I do, I decide to get rid of the information from the dummy imports. I clear out the extra icons, then I start deleting the entries. I delete 7 of them before I notice that the next one has comments. This is odd, because they didn't have comments in the original journal, and I hadn't been notified of new comments on DW.
I look at the entry, and I see that the comments that have been added to the post from the dummy LJ are the comments from one of the missing entries of my actual LJ. (Compare the LJ entry with the DW entry.) Several other comments got transferred over to the other dummy-lj entries; and there were, in fact, 17 entries transferred from the dummy LJ remaining on my DW. (There was an 18th entry that I deleted before the import, which may be why the first entry of my real LJ wasn't affected.)
So, that looks like a bug, one which could be a problem if people start consolidating journals.
I'm leaving everything as it is for now. Support in getting those seventeen entries would be appreciated, but I figure I can copy over seventeen posts pretty easily. I can re-date and copy over the posts that had the misplaced comments (though one of the entries I deleted apparently had a misplaced comment), so very little of those are lost. But it's still a wacky bug.
no subject
no subject
no subject
Is this normal/intended behavior?
Having checked this post, it does seem to be normal, but I'm glad to see that more work is planned. :)
no subject
no subject
no subject
no subject
Since you last tried importing 10 days ago, and since we have made changes to the importer since then, go ahead and try running your import again. If the comments don't come over in about 24h, open a support request.
no subject
no subject
No hurry but it would be nice to be able to migrate entirely...
no subject
no subject
Thanks for all the great work you're doing here.
no subject
no subject
no subject
No message in my mail, either.
Thanks
no subject
no subject
Incidentally, the comments were PARTIALLY imported during that import session. Nothing suggests in what I read that the import may be interrupted and a new queue may originate in the middle of an import.
What I am trying to say, is that there is clearly a technical problem on your side.
Thanks again
bgmt
no subject
I used not being able to contact the remote site as an example -- it's not the only thing that can block an import! A technical issue is entirely possible, but since other imports are completing successfully, it's not a guarantee and if an issue does exist, it's only an issue with importing from your LJ account. (Most commonly, because something about the data in your LJ account is irregular, malformed, or otherwise unexpected -- after ten years, the importer is pretty hardened against "stuff it didn't expect to find", but LJ's been accepting data for so long and has gone through so many changes in terms of what's accepted, what's cleaned, and what's rejected that even after a decade we're still being presented with edge-case data.) In cases like that, the problem will need one-on-one troubleshooting and debugging that can take hours and needs to be done by one of two people, both of whom are very busy, and it can take a long time for one of them to have the time to troubleshoot an i ndividual import problem. Please wait out the 7 day cycle, check your on-site inbox (https://www.dreamwidth.org/inbox) for any error messages -- they won't necessarily be sent to your email -- and then open a support request, including the text of any inbox messages you've gotten.
The "your previous import job will be aborted" applies only if the past job has been scheduled but not started. If some, but not all, of your comments have been imported, scheduling a new import doesn't abort the old one, because otherwise someone will lose their place in the import queue. I took a look, and the comments task for the first import you scheduled a few days ago did fail and is waiting out the delay for the next retry. There should be a message in your inbox to give you more information.