带有Elastic Beanstalk的AWS上的Web应用程序未在日志中显示输出

Question

This is sort of an in-depth question, so I'll try to explain it as best I can.

I've built a small API service in Go that I'm trying to deploy to AWS using the relatively new AWS Elastic Beanstalk Docker support.

Here's what I've done (the code is all open source, so you can follow along if you'd like):

$ git clone https://github.com/rdegges/ipify-api.git
$ cd ipify-api
$ git fetch origin aws:aws
$ git checkout aws
$ eb init
$ eb create
$ eb deploy

This will use elastic beanstalk to create a new app (with docker), and deploy it.

If I then run eb open to open my web app, I'll see my public IP address displayed (this is the correct behavior), so I know that my application is running / functional.

Now, in my source code, I've got several lines of debugging output:

fmt.Println("WOOOOOOOOOOOO")

The above statement just prints "WOO…" to the console. This is run every time a new request is made.

Unfortunately, when I run eb logs to view my instance logs, this debug line never shows up – and I can't figure out why.

I've tried printing to STDERR, printing to STDOUT, etc. – but I'm absolutely unable to get any output.

I've scoured the internet looking for solutions, but have yet to find any.

Answer 1

I think import "github.com/rdegges/ipify-api/api" is being built from the copy on Github, not from the local copy. The most recent commit of the api package doesn't have the extraneous fmt statements. Also, the log statement in main.go works fine, as does the fmt.Fprintf already in the api package. Try to verify the api package is getting built from the source you think it is.

EDIT 6/1/2015:

All my tests indicate this is a problem stemming from having an internal subpackage, and the remote service having trouble with that. The api package is not getting built from the local copy. fmt.Print works just fine from main.go, and moving GetIP from the api package to the main package lets fmt print just fine to stdout during web requests.

Basically, all changes made to the local api subpackage are getting ignored.

The EB logs probably say something about which packages are being downloaded remotely; mine did.

I'm not a Godep pro, so maybe a Godep pro can elaborate. But FWIW, it seems like it might be related to this issue, tangentially. It might also be a problem with the remote service not building with godep go build, but like I said, I'm not a Godep pro, so I'm unsure.