If your backups on EngineYard cloud are zero length, maybe it is a permissions problem.

We have a client that uses EngineYard cloud and has more than one application hitting the same database.

As part of this, he needs access, and it turns out that some of the views and tables were not owned by the deploy user.

This causes the eybackup to backup a file that is zero length and push it to the S3 backup but still return successfully. This is a problem because a cursory examination shows the backups are working all fine.

While EngineYard go about fixing this, the solution is simple, just make sure the owner of all the tables in the system belong to the deploy user, or alternatively make sure the deploy user can read all the tables in the database.

If you are using postgres you can do this with a simple SQL command:

psql> ALTER TABLE <table name> OWNER TO deploy;

MySQL has a similar simple command to handle this issue.

blogLater

Mikel

  1. burewadvi Says:

    Good idea! time zones difference become a problem in big team, such tool really helps. thanks

  2. Richard Says:

    I have been having this problem since two days before when I tampered with the ‘permissions’ in the settings. I had been using this EngineYard cloud and knew some cloud computing companies for a long time and I have never had this problem before. Now it is generating me backups of zero length and that bugs me. It is literally wasting a lot of time from my working hours. Now, from this post, I guess that problem arose because I tampered with the ‘permissions’ two days before.

  3. Richard Says:

    I have been having this problem since two days before when I tampered with the ‘permissions’ in the settings. I had been using this EngineYard cloud and knew some cloud computing companies for a long time and I have never had this problem before. Now it is generating me backups of zero length and that bugs me. It is literally wasting a lot of time from my working hours. Now, from this post, I guess that problem arose because I tampered with the ‘permissions’ two days before.

  4. dfgasg Says:

    This causes the eybackup to backup a file that is zero length and push it to the S3 backup but still return successfully. This is a problem because a cursory examination shows the backups are working all fine<href=http://www.google.com>google
    I had been using this EngineYard cloud and knew some cloud computing companies for a long time and I have never had this problem before.

  5. dfgasg Says:

    This causes the eybackup to backup a file that is zero length and push it to the S3 backup but still return successfully. This is a problem because a cursory examination shows the backups are working all finegoogle
    I had been using this EngineYard cloud and knew some cloud computing companies for a long time and I have never had this problem before.

  6. dfgasg Says:

    This causes the eybackup to backup a file that is zero length and push it to the S3 backup but still return successfully. This is a problem because a cursory examination shows the backups are working all finemichael jackson iphone 4 case

    I had been using this EngineYard cloud and knew some cloud computing companies for a long time and I have never had this problem before.

  7. dfgasg Says:

    This causes the eybackup to backup a file that is zero length and push it to the S3 backup but still return successfully. This is a problem because a cursory examination shows the backups are working all fine<href=“http://www.google.com”>google
    I had been using this EngineYard cloud and knew some cloud computing companies for a long time and I have never had this problem before.

  8. dfgasg Says:

    This causes the eybackup to backup a file that is zero length and push it to the S3 backup but still return successfully. This is a problem because a cursory examination shows the backups are working all finegoogle
    I had been using this EngineYard cloud and knew some cloud computing companies for a long time and I have never had this problem before.

  9. dd Says:

    This causes the eybackup to backup a file that is zero length and push it to the S3 backup but still return successfully. This is a problem because a cursory examination shows the backups are working all finemichael jackson iphone 4 casehad been using this EngineYard cloud and knew some cloud computing companies for a long time and I have never had this problem before.

  10. dasfg3dv Says:

    This causes the eybackup to backup a file that is zero length and push it to the S3 backup but still return successfully. This is a problem because a cursory examination shows the backups are working all fine oucjucdmp sg adpuxdipv hg elvteoqbe te godwete

    I had been using this EngineYard cloud and knew some cloud computing companies for a long time and I have never had this problem before.

Leave a Reply