Comment 3 for bug 531833

The slon log for one of the slaves, when correctly filtered, provides the relevant information.

When making changes, slonik first applies all the db patches to the master. If they succeed, the patches are then applied in sequence to each of the slaves. So patch1 on slave1, patch1 on slave2, patch2 on slave1, patch2 on slave2 etc.

The following seems good to follow what is happening:

tail -f /var/log/slon/slon-launchpad_prod_1.log | grep -v '] DEBUG2'

I'm leaving the DEBUG1 messages as they are not that noisy, happening regularly enough to let you know things haven't crashed but not so often it obscures the more useful information such as the DDL statements being applied.