Migration failes

OttoDeploy
1

I have one file which failes the migration with following error:

unknown deployment error.Command was killed with SIGKILL (Forced termination): /opt/FileMaker/FileMaker Server/Database Server/bin/FMDataMigration -src_path /opt/FileMaker/FileMaker Server/Data/Databases/test/testDB.fmp12 -src_account admin -src_pwd *** -clone_path /opt/FileMaker/FileMaker Server/Data/Backups/OttoFMS/inbox/build_WnCbjVkfo0PO/testDB.fmp12 -clone_account developerx -clone_pwd *** -target_path /opt/FileMaker/FileMaker Server/Data/Backups/OttoFMS/inbox/build_WnCbjVkfo0PO/testDB_otto_migrated.fmp12 -target_local -rebuildindexes -force 2024-01-30 14:19:02.827 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN idx= 0 ,parent level= 12 2024-01-30 14:19:02.827 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN idx= 0 ,parent level= 12 2024-01-30 14:19:02.827 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN idx= 0 ,parent level= 12 2024-01-30 14:19:02.827 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN idx= 0 ,parent level= 12 2024-01-30 14:19:02.827 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN idx= 0 ,parent level= 12 2024-01-30 14:19:02.827 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN idx= 0 ,parent level= 12 2024-01-30 14:19:02.827 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN idx= 0 ,parent level= 12 2024-01-30 14:19:02.827 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN idx= 0 ,parent level= 12 2024-01-30 14:19:02.827 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN idx= 0 ,parent level= 12 2024-01-30 14:19:02.828 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN idx= 0 ,parent level= 12 2024-01-30 14:19:02.828 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN idx= 0 ,parent level= 12 2024-01-30 14:19:02.828 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN idx= 0 ,parent level= 12 2024-01-30 14:19:02.828 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN idx= 0 ,parent level= 12 2024-01-30 14:19:02.828 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN idx= 0 ,parent level= 12 2024-01-30 14:19:02.828 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN idx= 0 ,parent level= 12 2024-01-30 14:19:02.828 +0100 [Main_7fbaeb65fd80] HPage::NumChildren childN is 0! child1 idx= 0 ,childN

Any ideas why this happens? The migration works local under mac os.

2

Hello and welcome to our community :slight_smile:

Did you configure a Swap File for your linux server? A swap file provides virtual memory. Not all linux distributions will automatically set them up for you. If you don’t have a swap file, and your server doesn’t have much memory, and your file is very large, The linux operating system will kill any process using too much memory.

We recommend this for a minimum on a server that will be performing deployments

  • 4 CPU cores
  • 8GB RAM
  • Available virtual memory or swap file.

We’ll add some more notes to the docs. We had a page in the Otto 3 docs about swap files but we haven’t moved it over to the ottofms docs yet. We will fix that

The other option is file corruption. But I doubt that’s it. But it might be worth running recovery on the file just to see what turns.

Let us know about your server configuration and File size and corruption status.

Thanks

Todd

2 Likes
3

Thanks Todd

I found the problem. It was a corrupt .bmp from back in the days, which was a background of a layout part.

1 Like
4

Thanks for letting us know what you have.

Todd