Only getting 'No results received' about goad

[danielmotaleite]

today i manage to test a little more and i notice that the goad role is created, but the goad-lambda-role-policy policy is not.

I just created a new policy with this info:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "sqs:SendMessage"
            ],
            "Effect": "Allow",
            "Resource": "arn:aws:sqs:*:*:goad-*"
        },
        {
            "Action": [
                "logs:CreateLogGroup",
                "logs:CreateLogStream",
                "logs:PutLogEvents"
            ],
            "Effect": "Allow",
            "Resource": "arn:aws:logs:*:*:*"
        }
    ]
}

And then add the "goad-lambda-role" role to the entity tab of the "goad-lambda-role-policy" policy... test it and now everything works fine... fine :)

So it is working for you because you already have the policy created and, on new users, goad doesn't work because it fails to create the policy for unknown reasons. it is also why there is no logs, no permissions are set to log anything

[sdsykes]

Something broke, investigating. The downloadable binaries should still work ok though.

[sdsykes]

It seems it's likely that there was an old version of the lambda function on your AWS. Please check in your AWS console and delete any goad function that is there. (We are adding a feature to support versioned lambda functions soon.)
With a clean AWS, and a clean checkout of goad (note you'll want to use Go 1.6 now) then it should work.

Closing, but get back if you still have a problem.

[adimarco]

I'm still seeing this behavior with the latest 64-bit Linux binaries. I'm running it from a box that has AdministratorAccess IAM permissions and no Lambda functions defined in any region.

$  aws --region us-east-1 lambda list-functions
{
    "Functions": []
}
$  aws --region eu-west-1 lambda list-functions
{
    "Functions": []
}
$ ./goad -n 1000 -c 5 -r us-east-1,eu-west-1 -m GET -u "https://goad.io"
No results received

[sdsykes]

Likely because we didn't update the binaries like we should have, we will do that shortly.

[webteknik]

Hi,
I am having the same problem. I first tried with the binary from releases, then I tried with go get ..., but I still get "No results recevied" even after deleting the lambda functions.

goad -version
1.1.0.pre

aws --region eu-west-1 lambda list-functions
{
    "Functions": [
        {
            "Version": "$LATEST",
            "CodeSha256": "/gjkXSwnHmLHXd8fA72WcLgRvlboWhVvU0Frw+i2src=",
            "FunctionName": "goad",
            "MemorySize": 1536,
            "CodeSize": 3007895,
            "FunctionArn": "arn:aws:lambda:eu-west-1:726671005420:function:goad",
            "Handler": "index.handler",
            "Role": "arn:aws:iam::726671005420:role/goad-lambda-role",
            "Timeout": 300,
            "LastModified": "2016-04-01T13:13:58.667+0000",
            "Runtime": "nodejs",
            "Description": ""
        }
    ]
}

[sdsykes]

I just tested the latest and it's working. I also made some new binaries so please try those, check under Releases. Let us know if it doesn't work.

[stigkj]

I tried with the new binaries, but still does not work. I also tried to delete the lambda function first, but no luck. I've listed the version and function below. I'm running this on OS X. Do you need any more information from me to reproduce?

> goad -version
1.1.0.pre

> aws --region eu-west-1 lambda list-functions
{
    "Functions": [
        {
            "Version": "$LATEST",
            "CodeSha256": "FmT+OdVtRRdaZYaVMihiqBsta6ft1pJHwZnybikpAcQ=",
            "FunctionName": "goad",
            "MemorySize": 1536,
            "CodeSize": 2994063,
            "FunctionArn": "arn:aws:lambda:eu-west-1:879238767243:function:goad",
            "Handler": "index.handler",
            "Role": "arn:aws:iam::879238767243:role/goad-lambda-role",
            "Timeout": 300,
            "LastModified": "2016-04-03T22:18:01.535+0000",
            "Runtime": "nodejs",
            "Description": ""
        }
    ]
}

[webteknik]

When I try, I see that requests keep coming to my web server even after goad cli exits and prints "No results received". So is it possible that lambda function does not end or deliver its results properly to the cli? I deleted the rest of the comment, because I realized it is not an error handler callback.

[michaeljs1990]

I'm getting this as well after pulling down the latest binary

[danielmotaleite]

also the same thing here.
tried go 1.5 and go 1.6 and both v1.1.0.pre and gopher-gala, always with the same result (actually go 1.5 + v1.1.0.pre crashed)

i see the goad being created in the lambda and the invocation count increasing, but in the end all we got is "No results received".

I'm using a standard debian micro instance in aws, so should be easy to replicate

edit: i don't see any SQS queue created, so the problem might be there... goad is not creating the queue, so nothing to read in the end

[jcxplorer]

Good to know that the lambda is being invoked. Are you able to see any logs
from that invocation? If so, could you share them with us?

On Fri, 22 Apr 2016 at 19:37, Daniel Mota Leite [email protected]
wrote:

also the same thing here.
tried go 1.5 and go 1.6 and both v1.1.0.pre and gopher-gala, always with
the same result (actually go 1.5 + v1.1.0.pre crashed)

i see the goad being created in the lambda and the invocation count
increasing, but in the end all we got is "No results received".

I'm using a standar debian micro instance in aws, so should be easy to
replicate

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#15 (comment)

[danielmotaleite]

well, clicking in the lambda "View logs in CloudWatch" i go the a non-existent "/aws/lambda/goad" log group... i created it, but still no logs.

In the command line, we see no error or messages

[danielmotaleite]

correction, i found that goad creates the SQS queue, then remove it later

[danielmotaleite]

Trying to use the goad-lambda i get this:

 ./data/lambda/goad-lambda  -c 5 -n 100  -r eu-west-1   -u https://www.example.com/
Using a timeout of 15s
Using a reporting frequency of 15s
Will spawn 5 workers making 100 requests to https://www.example.com/
Spawning workersâ¦..... done.
Waiting for resultsâ¦
100.00% done (100 requests out of 100)MissingRegion: could not find region configuration

Yayð  - 100 requests completed

but i do have a region defined...

[jcxplorer]

@danielmotaleite that error is most likely coming from the fact that you didn't specify the region for the SQS queue (https://github.com/goadapp/goad/blob/master/lambda/lambda.go#L42).

Could you check for lambda logs once again? They sometimes take a few minutes to show up...

You could also try creating an SQS queue by hand, and specifying the SQS queue region with that -q flag and also the queue URL with -s. After that, the SQS queue should have some messages inside. It would be helpful to know if the messages are getting written to the queue correctly :)

[danielmotaleite]

This seems to work, i get some messages to the goad-12345 queue:

$ data/lambda/goad-lambda -c 100 -n 10000 -r eu-west-1 -q eu-west-1 -s https://sqs.eu-west-1.amazonaws.com/315417893466/goad-12345 -f 5s -u https://www.example.com/

For the logs, i created the "/aws/lambda/goad" log group, but i have no log stream and have no idea what name it should have... either way, it is still empty

OK, after several tests, i found the source of the problem... the queue is created, but without permissions. If after the queue creation i quickly add permissions for everyone, the output show up in to the running cli output

So there is some bug in the queue creation or the default sqs permissions changed and right now the lambda can not access the sqs queue

[jcxplorer]

@danielmotaleite thanks a lot for looking into this. It'll definitely help in reproducing and getting it fixed!

I should have some time next week to look into this.

[sdsykes]

Thanks again. Am trying to reproduce and fix this now.

[jeberly]

I am still seeing "No results received" problem and I pulled and compiled the latest code with c203783

[danielmotaleite]

remove any goad policy in aws, you probably have a old, incorrect policy there...
also check for any stale sqs

[SophisticaSean]

@danielmotaleite thank you so much. without your help and your policy comment I probably never would have had goad working correctly. This is when i built goad from source too. Someone should add a pull request to the README so people know they have to set up the policy and goad-lambda-role before goad will work.