---

Subject:	Take a look at this post to
Author:	[Not Specified]
Posted:	2014-04-15 11:57

Take a look at this post to see if it helps: http://zenoss.org/forum/756

Hydruid

---

Subject:	Wouldn't hurt to compare the
Author:	[Not Specified]
Posted:	2014-04-15 14:06

Wouldn't hurt to compare the "400 Bad Request" event to this: http://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html , perhaps it will help you narrow down the issue.

Hydruid

---

Subject:	I agree with you but I see
Author:	[Not Specified]
Posted:	2014-04-15 15:30

I agree with you but I see there are list of Error code under that HTTP status code and in the zenpython.log i only see entry as "ERROR zen.AWS: xxxxxx: AWS: 400 Bad Request", how do I check what error code is causing to throw 400 bad Request does is show in any log response in particular zen logs stating what exactly is causing it to throw error I don't see any credentials issue here since it discovers all the instances, subnets, VPC etc. but i could be wrong. sorry i am new to zenoss

Thanks
Vaibhav

---

Subject:	Try finding more info in all
Author:	[Not Specified]
Posted:	2014-04-16 08:53

Try finding more info in all of the logs to see if you can narrow it down:

cd $ZENHOME/log
grep "Bad Request" *

Hydruid

---

Subject:	Perhaps you should jump on
Author:	[Not Specified]
Posted:	2014-04-16 12:49

Perhaps you should jump on IRC #zenoss and post your question there, I wish I had an AWS account to dig deeper but I don't.

You can try starting the zenpack daemon with increased verbosity, something like this:
$ZENHOME/bin/zenperfsnmp run -v 10

Hydruid