Review app creation in my heroku pipeline are broken. I get the error, 'source blob is not a valid tarball'. I don't get any logs, hence can't investigate into or fix anything myself.
Any ideas on a fix, or how to dig deeper?
Related
One of our test apps got deleted recently. We're trying to track down how/why (suspicion is an error in an API call that we've made). Is there a way to get any logs from Heroku that shows who/when/how an app was deleted?
I'm trying to push a Laravel installation from development to a live-environment on a Laravel Forge-server. When pushing, I'm getting an error, that I'm not getting on my local environment.
I can't figure out, how I connect directly to the provisioned server (through FTP or SFTP), to change single files manually (to debug).
Which means that in order to try something, then I need to make a new commit and an entirely new deployment, for every thing I want to test. Quite tedious and it clutters my git history!
... I can't even do a commit --amend, since that gives me the error:
fatal: refusing to merge unrelated histories
Attempt 1) I can't find anything about it in the Forge knowledge base.
Attempt 2) I've found several articles talking about a good guide, but that guide gives an error 404:
It's this one: https://freek.dev/2016/03/let-your-clients-use-sftp-on-a-forge-provisioned-server/
Am I missing something obvious? Or is the commit-n-push really the way to go? Is this normal for automated deployment systems?
For others who find this question, then Forge-support got back to me really quickly and linked to this blogpost, explaining how to get sftp-access to a Forge-provisioned server
What I did wrong, was that I didn't use the username: forge (I was using my email).
I'm trying to update my app on heroku using node heroku client, but it fails with the message
Unable to fetch source from: https://my-aws-account.s3.amazonaws.com/source.tar.gz?AWSAccessKeyId=...&Expires=...&Signature=...
The source code gzipped tarball is public and fresh during the deploy.
The node-heroku-client seems to follow build api properly. This error occurs after the build has began.
It seems to be a bug on heroku build servers, but I would like to know if someone else had this problem before...
It's a known issue with at heroku, the upstream provider is working on fix https://status.heroku.com/
I am trying to install cloudant on my vulcan based app.
However when I try to add the free version of cloudant through the heroku addons I get the following error:
Could not communicate with vendor, please try again later
Want to confirm if this is a temporary vendor issue or is it something with my app?
I contacted Heroku support and was told Heroku is in the process of removing the add-on. I don't know any further details, but it looks like in order to have Cloudant work on Heroku you'll need to set the account up yourself.
This sounds like an error in the brokering between Heroku and Cloudant. If you can file a ticket with support#cloudant.com (including account information and time of the failure) we can track it down on our side and see if there's action we can take. Alternatively, you can always signup directly at cloudant.com as a short-term work around.
I started a migration on Heroku last night that gave me no feedback for hours, and which I eventually stopped because it wasn't clear if the system was even doing anything.
Ever since, it's been a nightmare. I cannot access the relevant database tables in heroku console, I can't migrate, rollback, or use pgbackups.
Helpfully, pgbackups gave me a one line explanation just now:
a transfer is currently in progress
This I assume is the migration I tried to execute hours ago. How can I stop whatever Heroku is doing so I can do a quick restore and get back up and running?
You can remove the problem backup stuck in the "a transfer is currently in progress" by finding the name of the backup and then destroying it. E.g.
heroku pgbackups
My problem backup was listed like this:
b210 | 2013/01/02 12:29.33 | unknown | DATABASE_URL
So to destroy it I just did:
heroku pgbackups:destroy b210
It removed the problem backup for me so I could get on with using pgbackups again properly.
I just had this problem too. Found an easier way of fixing it - briefly remove the pgbackups addon.
heroku addons:remove pgbackups
heroku addons:add pgbackups
WARNING as mentioned in the comments below, this will destroy all extant backups!
I accidentally did a transfer from my COLOR_URL database to my DATABASE_URL which was the same database. heroku pgackups:transfer let this happen which caused the main database to get stuck in
a transfer is currently in progress
I fixed it by looking at the process list pg:ps and killing all connections pg:killall
After doing this and looking at pg:ps the process list was empty and I was free to use the main database again with pgbackups.
NOTE this could be a destructive operation so make sure you have a snapshot before you do this.
The real solution is to contact Heroku support and have them kill the rogue process for you. They say they are re-architecting pgbackups to give users more control.
It never became clear what happened - after a day or so I was able to interact with heroku console, but I was never able to run another migration. This is what I did:
Renamed my app to something else.
Created a new app in its place, checking the stack was the same, and copying over all add-ons and domains.
I restored the database from pgbackups (highly recommended if you're not using this add-on).
This fixed the problem. Note: Be careful to check that your pgbackup doesn't cause unacceptable data loss.