Some pads are re-created as empty after switching to MySQL

I am trying to migrate from dirtydb to mysql, but for some reason after switching, several Pads are lost. Migration was done with the included script bin/migrateDirtyDBtoMySQL.js after shutting down EP and changing the config to MySQL.

For example a pad X which I created about 1 week ago and last edited yesterday is shown as newly created if I access it after restarting Etherpad with the MySQL config.

...
[2014-11-13 19:02:27.705] [INFO] ueberDB - Flushed 1 values
[2014-11-13 19:02:27.804] [INFO] socket.io - handshake authorized 'eYPi7Au9EE-AU6yaUcv-'
[2014-11-13 19:02:27.805] [INFO] ueberDB - Flushed 1 values
[2014-11-13 19:02:27.958] [INFO] access - [CREATE] Pad "Nice_Rides": Client eYPi7Au9EE-AU6yaUcv- with IP "148.251.*.*" created the pad

When looking at the store table, the contents of pad X is there. But for some reason Etherpad decides to ignore that and create an empty pad instead. If I switch back to dirtydb, the existing content of the Pad is correctly shown.

In settings.json only the DB config was touched. Using EP 1.4.1

What can I do?

[tykling]

I also have this issue and have tried a bunch of times to get a dirty.db migrated to Postgres using bin/migrateDirtyDBtoRealDB.js

The output from the migration script looks promising, it counts down to 0 and then waits a while and says it has flushed a bunch of lines:

[etherpad@pad2 ~/etherpad-lite]$ node bin/migrateDirtyDBtoRealDB.js 
[2018-02-26 22:13:31.094] [INFO] console - Waiting for dirtyDB to parse its file.
[2018-02-26 22:13:51.278] [INFO] console - Loaded 153755 records, processing now.
[2018-02-26 22:13:51.281] [INFO] console - Records not yet flushed to database:  153700
[2018-02-26 22:13:51.283] [INFO] console - Records not yet flushed to database:  153600
...
[2018-02-26 22:13:53.533] [INFO] console - Records not yet flushed to database:  200
[2018-02-26 22:13:53.533] [INFO] console - Records not yet flushed to database:  100
[2018-02-26 22:13:53.534] [INFO] console - Records not yet flushed to database:  0
[2018-02-26 22:13:53.534] [INFO] console - Please wait for all records to flush to database, then kill this process.
[2018-02-26 22:17:25.677] [INFO] ueberDB - Flushed 153755 values

This is with 1.6.3 but I had this same issue when I tried to migrate about a year ago. After faffing about with it for a few days I just gave up and stuck with dirty.db.

I am very interested in getting this working. It seems like not all the data is making it to Postgres for some reason. This means that many of the pads are created as new pads when I open them on the new server.

Any suggestions?

[rhansen]

@JCMais Please file a new bug report. I’m surprised John saw your comment on this 7-year-old bug that is unlikely to be related to your issue.