> >>It seems to be something else. Looks like stopping the migration job after > >>successful > >>migration causes a long timeout. > > >>Someone else notice this bug so far? > > Look at user log, it seem to be exactly what I said previously: But why does it happen only on 5.0 (and not with 4.x)?