Odd issue - migtool does not complete, and ssh window closes!

Discussion in 'ISPConfig 3 Priority Support' started by craig baker, Mar 4, 2026 at 2:22 PM.

  1. craig baker

    craig baker Member HowtoForge Supporter

    I've been trying to do a migration from a rocky 9 server to a new build deb12 (with autoinstaller).
    Dry run completes fine. no problem.
    Migration live run happily gets going, and well into the proceedings it gets to where it is dumping the databases. All has gone well to this point.
    Now one of the databases IS quite large.
    at somepoint shorly after, the SSH window closes the connection, killing migtool. when I log back in, the migration log does not show any errors.

    I thought maybe some keep-alive needed to be set, but I set it in both sshd-config, and in the termius client side settings. but it always fails (no error, session simply closes).
    any ideas??
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Then this is not an issue of the migration tool; it's an issue with your SSH session. When your SSH session gets closed, ssh terminates the command running in that session, so SSH stops the migration tool, and this is why the migration does not finish.

    To keep applications running even when the SSH session gets closed, you can use e.g. the Linux program 'screen':

    https://www.howtoforge.com/how-to-use-screen-command-in-linux-system/

    First, start the screen command, and then within that screen session, you start the migration tool. So even when your ssh connection gets closed again, the migration tool will continue to run within the screen session. You can then either wait until its finished, or you can later reconnect to that running screen session to see the output of the tool.
     
  3. craig baker

    craig baker Member HowtoForge Supporter

    I will look at screen. I also though maybe we can run migtool from cron? then it wont care about ssh sessions. is there a migrate command to 'migrate - migrate not dry but use all defaults' that have been established from the prior session? then its trivial.
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Cron is not interactive and also not designed to run a program once, so it's not suited for this. The right tool for your problem is screen.
     

Share This Page