Error upgrading 3.0.1 archive node

[nateless]

Getting an error processing DB from 3.0.1 Archive. Works for around 3H and then fails:

Migrating database from v15 (3.0 series) to v16 (3.1 series).
CAUTION: This will update the database in a non reversible way. A backup is recommended.
type I AGREE to proceed > I AGREE
- opening the database...
Error: Io(Custom { kind: Other, error: Error { message: "Invalid argument: Column family not found: : col5" } })

[rakita]

This error is at the opening of DB, the script didn't do anything on data yet.

    println!("- opening the database...");
    let db = kvdb_rocksdb::Database::open(
        &DatabaseConfig::with_columns(columns),
        &database_path(db_path.clone()).to_string_lossy(),
    )?;

[Legogris]

@adria0 any ideas on this? Seems to be specific for archive nodes (which have the most need for this tool)

[adria0]

@adria0 any ideas on this? Seems to be specific for archive nodes (which have the most need for this tool)

so, are you migrating from 3.0.1 to 3.2.1 ?

[Legogris]

@adria0 any ideas on this? Seems to be specific for archive nodes (which have the most need for this tool)

so, are you migrating from 3.0.1 to 3.2.1 ?

indeed - haven't gotten to the part of actually starting 3.2.1 yet though, due to the above

[adria0]

3.2.x and 3.1.x shares the same database schema.
I tried an archive node from 3.0.1' to 3.2.1` and worked for me.

Migrating database from v15 (3.0 series) to v16 (3.1 series).
CAUTION: This will update the database in a non reversible way. A backup is recommended.
type I AGREE to proceed > I AGREE
- opening the database...
- removing light chain data.
- removing private transaction data.
- updating version.
- migration completed.

I do not know, maybe could be related to previous migrations. Which series versions have you previously used?

[Legogris]

@adria0 Straight-up 3.0.1 from the start here as well, actually.
Was yours fully synced as well? It took several hours until the error appeared and the process aborted.
Any additional information (config etc) or commands I can run that could be useful in tracking this down?

[adria0]

"It took several hours until the error appeared and the process aborted."

What took several hours? The migration process? Are you executing the tool with openethereum running?

[Legogris]

"It took several hours until the error appeared and the process aborted."

What took several hours? The migration process? Are you executing the tool with openethereum running?

Openethereum is not running - I am talking about the migration process running this tool. Nothing else is accessing the database during the migration process.

It stops at

- opening the database...

(not hanging , there is still disk- and CPU activity during this time, disk is enterprise SATA SSD)
After a couple of hours the exact same error message as in issue description.

[epheph]

I have also experienced this error, with the same timing. The tool ran for several hours, openethereum was definitely not running

Migrating database from v15 (3.0 series) to v16 (3.1/3.2 series).
CAUTION: This will update the database in a non reversible way. A backup is recommended.
type I AGREE to proceed > I AGREE
- opening the database...
Error: Io(Custom { kind: Other, error: Error { message: "Invalid argument: Column family not found: : col5" } })