Popular forum exporters

a_5mith

psychobunny

hey @a_5mith sorry for the delay! I found the error, looks like I was pulling the wrong repo for one of the packages. pull and npm install and I think you should be good to go

a_5mith

@psychobunny Hey buddy, thanks, installed without a problem, having a few issues getting it to connect to an external mysql connection, even with remote mysql configured. Keeps timing out on me. Will battle on and report my discoveries.

luke

You guys are so awesome for testing that importer for me and working out the kinks.

a_5mith

So, anyone got any experience with this?

Error: connect ETIMEDOUT
at errnoException (net.js:904:11)
at Object.afterConnect [as oncomplete] (net.js:895:19)

Seems like it's just not connecting to the db (remote), so I added my Digital Ocean IP to my Remote MySQL page on my old host, this made no difference. I'm only doing a test run on a week old database backup, so I've got time to iron out these sorts of errors so I can minimise downtime when I take the leap.

psychobunny

Can't you set up a local copy of your DB? There isn't any throttling in the queries (ex. select 100 rows at a time), it basically does a select * per table, so if you have a really huge dataset I could see it timing out.

If not a possibility, I think you could try modifying the importer to send these commands initially to increase the timeout

a_5mith

@psychobunny

The database is about 32mb (contains both an SMF database & Wordpress), 400 users, 25k posts, but times out within about 30 seconds of Exporting Users. Could probably do it locally thinking about it, will have a go and see what happens.

psychobunny

BTW after you finished with the phpBB export: I found that there's a bit of a bottleneck with regards to the redirect stuff in the importer, so if you don't care about writing redirects for SEO purposes then you can omit that and speed it up

jonathanmh

I was going to bring up woltlab bb (I guess it's only popular in Germany), but actually first porting to phpbb sounds like a smart plan

a_5mith

Hey @psychobunny, took your advice and got mysql installed on Digital Ocean and imported it all that way, having a few issues with the final step of using the importer to actually get the data in. Following the steps, I get this error:

error: NodeBB automated setup didn't go too well.

I already have nodebb setup, I noticed that import.config.json has a setup script built in, do I have to either a) remove it, or b) fill it out with the contents of nodebbs config.json?

psychobunny

Oh awesome, congrats for getting that far! I think at this point you'll have to ask the creator of the importer, @bentael - I didn't run into that error myself. If the actual import worked but creating the config didn't, yeah maybe you could create one yourself and see what happens?

a_5mith

@psychobunny Think I got it, removing --flush and it's now going through users.

Once I'm sure I know the process, I'll create a guide on the wiki page for anyone else that needs it.

psychobunny

awesome. hope it works out, I have no idea how long its going the import process is for something as big as yours

a_5mith

@psychobunny Users went over within about 5-10 minutes, however it's only transferred 5 of my 25,000 posts. So not really sure why that is.

5 threads, and only the OP, no replies.

psychobunny

yeah I found that posts take forever, about 500 posts took 3 minutes... so a rough extrapolation would suggest it would take you two and a half hours

Not sure if there are any optimizations that could be made in the importer, I imagine that @bentael has some ideas in mind for the future. For your sake I really hope it works the first try (he has some "time machine" feature in there that lets you import just the first 100 posts or something, which I really recommend you trying to test drive everything)

a_5mith

@psychobunny The posts are there, but got an error:

Importing Topics ...
[import][warn] [c:1] skipping topic:_tid:"2" --> _cid:valid: true _uid:valid: false
[import][warn] [c:2] skipping topic:_tid:"3" --> _cid:valid: true _uid:valid: false
[import][debug] [c:3] saving topic:_tid: 4
[import][debug] [c:4] saving topic:_tid: 6
[import][debug] [c:5] saving topic:_tid: 7
[import][debug] [c:6] saving topic:_tid: 8
[import][warn] [c:7] skipping topic:_tid:"9" --> _cid:valid: true _uid:valid: false
[import][debug] [c:8] saving topic:_tid: 10

/home/a_5mith/nodebb/src/socket.io/index.js:199
var clients = io.sockets.clients();
^
TypeError: Cannot read property 'sockets' of undefined

Time taken I can live with, my forum is still running, this is a backup from last week, so have the time to check these things.

All the topics are there, it just seems that after 3 warnings it stops. I've even looked through 2 different topics one with and one without the warning, they look the same to me from a quick inspection.

psychobunny

TypeError: Cannot read property 'sockets' of undefined

hmm... my first guess is that your version of NodeBB isn't compatible with the importer. I know that it's good for 0.4.1 but not sure if anything new has broken it. Try downgrading to 0.4.1 (after the import, the upgrade command should take care of the rest)

What concerns me is the fact that an hour later you're still at tid 10 wonder what the bottleneck is in this process?

a_5mith

@psychobunny Same issue with both 0.4.1 & 0.4.0.

After tid_10 it aborts the process. Hopefully @bentael will be along soon to assist.

a_5mith

Mo progress, mo errors. Hadn't commented Topics.pushUnreadCount();

Anyway, got through the process, now receiving this error:

[import][debug] restoring configs
[import][debug] undefined
[import][error] Something went wrong while restoring your nbb configs
[import][warn] here are your backed-up configs, you do it.
[import][warn] undefined

/home/a_5mith/nodebb/node_modules/redis/index.js:516
throw callback_err;
^
Error: Error: ERR wrong number of arguments for 'hmset' command

config.json looks fine, so not sure what's going on.

bentael

@a_5mith sorry I wasn't home all day.

So, after reading this thread, i think I have an idea why this issue (in the comment) is happening, removing --flush will not flush your db and attempt to run NodeBB setup for you, this is designed to "pick up where you left off", however it assumes that you were successfuly able to run it at least once in the beginning for it to generate path/to/storage/import.backedConfig. But it looks like your initial issue is whatever caused this error: NodeBB automated setup didn't go too well.

can you tell me which OS you are using?
Also, say you do use --flush back again, (this will flush your db), the logger should've printed out a much more detailed error, I hope, see this line
could you share that part of your logs?

As for speeding post imports in, like @psychobunny mentioned, you can disable the redirect stuff, but still, there is many things that NodeBB is doing, at each record creation, my future plans is to skip the NodeBB modules usage, and hit the DB directly, but that would require mimicing almost everything that the core code does, minus the fancy unnecessary stuff for the import process.