Replication hangs

[Luuk de Waal Malefijt]

After setting up the database, I ran ./mbslave-sync.py.

It did a few, but it hangs on the same packet. How can I debug this?

[Lukáš Lalinský]

Well, what exactly does "hang" mean? Do you see activity in the PostgreSQL database (CPU usage, logs, pg_stat_activity)? What traceback do you see when you interrupt it? Maybe the database is just too slow? Which packet number is it?

[Luuk de Waal Malefijt]

Sorry! I think I've figured it out based on your comment. My SSH session kept ending with 'broken pipe' error, due to the length of the process. It also terminated the session process so this big packet wouldn't probably finish.

[Luuk de Waal Malefijt]

Increase SSH heartbeat to not lose the process half-way.

[Lukáš Lalinský]

If you are running the process over SSH, it's generally a good idea to start it inside tmux or screen. That way you can log off, it will continue to work and when you log in and attach the session, you will be back where you were before you logged off.