pg transfer failure - Githubissues

hgmnz commented 12 years ago

From @fdr:

the cause of such failures is so mysterious that it doesn't make sense to know whether to retry or not?

heroku pg:migrate -a bestdamnburger-production
Checking for pgbackups addon... done, already present
Installing heroku-postgresql:dev... done, attached as HEROKU_POSTGRESQL_COBALT
Entering maintenance mode on application bestdamnburger-production... done
Scaling process web to 0... done
WARNING: 'heroku run' processes are not cancelled at this time
Transferring... 
Pg_dump... 68.4kB -
ERROR: Transfer failed, aborting
Restoring process web scale to 1... done
Leaving maintenance mode on application bestdamnburger-production... done

Trying a second time worked:

heroku pg:migrate -a bestdamnburger-production
Checking for pgbackups addon... done, already present
Installing heroku-postgresql:dev... done, attached as HEROKU_POSTGRESQL_BROWN
Entering maintenance mode on application bestdamnburger-production... done
Scaling process web to 0... done
WARNING: 'heroku run' processes are not cancelled at this time
Transferring... 
Pg_dump... 68.4kB -
done
Binding new database configuration to: SHARED_DATABASE_URL, DATABASE_URL... done
Restoring process web scale to 1... done
Leaving maintenance mode on application bestdamnburger-production... done

fdr commented 12 years ago

I suspect Adam had this problem also, reported to me via email, although we didn't get a chance to prove it because he subsequently did a manual migration.

wuputah commented 12 years ago

Fails every time on app=tnh-aspen.

Transferring...
Pg_dump... 353kB /
ERROR: Transfer failed, aborting.

wuputah commented 12 years ago

Another example:

% heroku pg:migrate -a redis-example-bamboo
...
Transferring... 
Pg_dump... 3.96kB |
ERROR: Transfer failed, aborting.

fdr commented 12 years ago

Thanks for the reproducing cases. Consider them acked (but not fixed)

heroku / heroku-pgmigrate

pg transfer failure #1