I’m running the mybb.rb script as described by @elberet and the script is running and returns successfully, but no changes result. The script contains the correct remote host name, db name, pw, etc. The remote server is configured to allow remote mysql from the IP of the current Discourse install. I’m not sure why nothing is imported. Can anyone shed any light? [image](I believe the three users mentioned here are the existing users already in the Discourse to which I am trying to import)

It’s hard to tell without debugging the import script… The only thing I can think of is, that all record are skipped during the import. Try removing all lines which start with next if all_records_exist? from the import script.

I commented out the next if all_records_exist? as suggested, and: It’s working - thanks! Interestingly, the user count starts going up: [image] but when it reaches it’s total, it pings back to “3 / 3”: [image] Perhaps this is part of the issue. No matter, I suppose. However, when the posts-total is reached (or the batch-size total, for a large batch size), the script prematurely aborts with “MySQL server has gone away” which sounds very sad :wink: So we’re making progress. But - come back, MySQL server :persevere: I want the script to finish! It seems there are a lot of reasons this could happen, according the the Internet, but I fixed this issue by simply dramatically reducing the BATCH_SIZE in myrb.bb (to 50). Then the remaining parts of the script ran as well. I’m there! I imported my mybb db! After 3 days of trying! :blush: :rolling_eyes: @gerhard, thanks SO much for your tips.

For others wishing to import a mybb MySQL database, here’s what worked for me, from start to finish. My mybb was hosted on a server with cpanel. I used a live fresh-install of Discourse on DigitalOcean. It is advised elsewhere to import into a local developer Discourse and then backup that Discourse and restore into the live one. However that is rather involved if you’re not a regular Github and Vagrant user (see this and this). So if the live Discourse is new, why not import right into it. If everything breaks, I can start over and have Discourse back up in 30 mins. Start by performing a new Discourse backup through admin pages, and download it. Then you need to allow remote MySQL connections from the new (Discourse) server. I used cpanel where my mybb forum is hosted, and clicked on “Remote MySQL” and entered the Discourse server IP there. Then collect the mybb database connection details. In cpanel you can see these under “MySQL databases”. Note the database name, the user, and look up in your records the password for that user (you did make a record of that, right?!) For the IP of the server where your mybb forum resides, you may be able to just do a DNS lookup on the domain name. But my hosting provider advised using a different IP for the server where the shared hosting resides. (Both may work, I am not sure.) If your table prefix is not “mybb_”, you’ll need to edit that too (you can check in phpMyAdmin from cpanel). Now, ssh to your Discourse install. I did this as root, with PuTTY. Then, cd /var/discourse/ ./launcher enter app apt-get update apt-get install libmysqlclient-dev nano gem install mysql2 su - discourse cd /var/www/discourse/script/import_scripts bundle install nano mybb.rb …and edit the connection details (MYBB_DB, host, username, password). I also needed to comment out the two lines beginning next if, and reduce the BATCH_SIZE to 50 (see above in this topic for more info). To save the file in nano, ctrlO. To exit nano, ctrlX. Now go back to your mybb admin page and put the board into offline mode, in the Configuration tab. Now back in your ssh window to your Discourse install, RAILS_ENV=production ruby mybb.rb At this point, for me, the script executed successfully. Check your Discourse install - is everything there? (Don’t be fooled by the Dashboard stats, they may not update for a while) In the online Discourse admin UI, perform another backup, and download it. There now may be some manual cleanup of posts required (links, attachments etc). Once the import is complete, exit out of the discourse login exit out of the Rails app If you now ./launcher rebuild app the libmysqlclient-dev, nano, and mysql2 gem installations should be removed, as well as your edits to mybb.rb. Thanks to @elberet, @dandv and @gerhard for their posts on this task

Something else I edited, might be useful to others was the SQL queries. These changes to the mybb.rb script achieve the following: do not import any users in the “Awaiting Activation” group do not import users who have (1) never posted and (2) haven’t visited the forum for 365 days or longer. total_count = mysql_query("SELECT count(*) count FROM #{TABLE_PREFIX}users u JOIN #{TABLE_PREFIX}usergroups g ON g.gid = u.usergroup WHERE g.title != 'Banned' AND g.title != 'Awaiting Activation' AND !((postnum 365) ) ;").first['count'] batches(BATCH_SIZE) do |offset| results = mysql_query( "SELECT uid id, email email, username, regdate, g.title `group` FROM #{TABLE_PREFIX}users u JOIN #{TABLE_PREFIX}usergroups g ON g.gid = u.usergroup WHERE g.title != 'Banned' AND g.title != 'Awaiting Activation' AND !((postnum 365) ) ORDER BY u.uid ASC LIMIT #{BATCH_SIZE} OFFSET #{offset};")

[image] precessor: RAILS_ENV=production ruby mybb.rb What would you recommend in this case? loading existing groups... loading existing users... loading existing categories... loading existing posts... loading existing topics... /usr/local/lib/ruby/gems/2.3.0/gems/mysql2-0.4.8/lib/mysql2/client.rb:89:in `connect': Access denied for user 'root'@'localhost' (using password: NO) (Mysql2::Error) from /usr/local/lib/ruby/gems/2.3.0/gems/mysql2-0.4.8/lib/mysql2/client.rb:89:in `initialize' from mybb.rb:31:in `new' from mybb.rb:31:in `initialize' from mybb.rb:304:in `new' from mybb.rb:304:in ` '

Set a password for your MySQL connection, most likely.

And yet… Access denied for user 'root'@'localhost' (using password: NO)

I change my mysql root password with the new. That command: mysqladmin -u root -p'oldpass' password 'newpass' And tried again. RAILS_ENV=production ruby mybb.rb Output: discourse@discourse-gameofthronestr-app:/var/www/discourse/script/import_scripts$ RAILS_ENV=production ruby mybb.rb loading existing groups... loading existing users... loading existing categories... loading existing posts... loading existing topics... /usr/local/lib/ruby/gems/2.3.0/gems/mysql2-0.4.8/lib/mysql2/client.rb:89:in `connect': Access denied for user 'root'@'localhost' (using password: YES) (Mysql2::Error) from /usr/local/lib/ruby/gems/2.3.0/gems/mysql2-0.4.8/lib/mysql2/client.rb:89:in `initialize' from mybb.rb:31:in `new' from mybb.rb:31:in `initialize' from mybb.rb:304:in `new' from mybb.rb:304:in ` '

You have to provide your login/password as environment variables when running the import script.

I set db and password variables. Except this there is no variable in Mybb.rb. How can I provide variables?

Mybb.rb imports nothing

Product Support Migration

smaffulli (Stefano Maffulli) July 31, 2017, 7:58pm 23

Are you setting the DB variables as shell environment variables? Before running the script, you should run the export commands in your shell.

Topic		Replies	Views
Migrate a MyBB forum to Discourse Sysadmins how-to	21	9448	March 21, 2023
Migrating from mybb Product Support	45	14864	November 16, 2019
Members problem on importing Mybb to Discourse Migration mybb	25	3751	September 4, 2017
MyBB importer script failing at creating users stage Migration mybb	2	1688	September 29, 2015
How to use mybb.ru 2 import script? Migration mybb	6	1548	January 25, 2020

Mybb.rb imports nothing

Related topics