logs not downloading
Closed this issue · 5 comments
I am unable to successfully retrieve logs. Running the awsebtlogs task does appear to result in a new 'last 100 lines of logs' file appearing (in aws console for ebt). However, the file itself is never downloaded.
In order to get the awsebtdeploy task to function I had to specify the s3 bucket option for the particular bucket associated with my application. It looks the actual log files created are associated with that same bucket (under resources/environment/...../.../).
Any tips on how to debug why the logs aren't downloading? I looked at the logs but didn't see anything that shed light :)
This plugin is unmaintained as I haven't worked with AWS AB for months now. The most likely cause is that the EB API has changed, so I would not rely too much on this plugin any longer, in its current state at least. That said, the implementation is trivial once you figure out how to use the AWS API and the plumbing is in place already, so debugging should mainly be a matter of placing some console.log in the code and figuring out why the logs aren't downloaded.
Thanks for the heads up.
On Sat, Dec 6, 2014 at 8:18 PM, Simone Busoli notifications@github.com
wrote:
This plugin is unmaintained as I haven't worked with AWS AB for months
now. The most likely cause is that the EB API has changed, so I would not
rely too much on this plugin any longer, in its current state at least.
That said, the implementation is trivial once you figure out how to use the
AWS API and the plumbing is in place already, so debugging should mainly be
a matter of placing some console.log in the code and figuring out why the
logs aren't downloaded.—
Reply to this email directly or view it on GitHub
#9 (comment)
.
NP. Sorry not to be of much help but I would have to set the whole thing up from scratch, which is quite time consuming, and also one of the reasons why I moved away from EB.
Any tips based on what you moved on to? Another AWS service or something else entirely? I've been using Google App Engine and now just getting started with AWS EB and so far I see many differences - but no clearly easier/better path as far as maintenance/setup.
For my needs at the time I wrote this plugin Heroku was an easier alternative.