monasca team mailing list archive

[Oguz Yarimtepe <oguzyarimtepe@xxxxxxxxx>]

Hi,

After working a bit here is my current problem. I tested the jar file, 
the output is same. Since i am using HP's ansible cookbooks, jars are 
downloaded from Apache.

It seems there is problem with storm. When i restarted the 
monasca-thresh, after a while the topology is gone and i am seeing

2016-01-05 14:37:06 b.s.m.n.Client [ERROR] connection attempt 28 to 
Netty-Client-gateway.foo.com:6701 failed: 
java.nio.channels.UnresolvedAddressException
2016-01-05 14:37:06 b.s.m.n.Client [ERROR] connection attempt 28 to 
Netty-Client-gateway.foo.com:6702 failed: 
java.nio.channels.UnresolvedAddressException
2016-01-05 14:37:06 o.a.s.c.r.ExponentialBackoffRetry [WARN] maxRetries 
too large (300). Pinning to 29
messages at

/var/log/storm/worker-6701.log

and then service monasca-thersh is displaying no topology.

there is no host definition at the monasca machine for gateway.foo.com, 
i couldn't find why it is trying to connect that machine. It seems the 
storm workers are dying after a while and i don't know the reason. I 
removed eveything related with storm, kafka and zookeper and reapply the 
cookbook, nothing changed. Even i purged the mysql database.

I also see  messages at the storm logs
2016-01-06 07:54:11 o.a.s.c.r.ExponentialBackoffRetry [WARN] maxRetries 
too large (60). Pinning to 29
2016-01-06 07:54:12 o.a.s.c.CuratorZookeeperClient [WARN] session 
timeout [3000] is less than connection timeout [15000]
2016-01-06 07:54:13 o.a.s.c.r.ExponentialBackoffRetry [WARN] maxRetries 
too large (60). Pinning to 29
2016-01-06 07:54:13 o.a.s.c.CuratorZookeeperClient [WARN] session 
timeout [3000] is less than connection timeout [15000]

So, how does the netty-client connecting a host? I checked the conf 
files, right IP adress is defined but still i see a connection try to 
wrong host.

Also, when i add my localhost's ip ad gateway.foo.com to /etc/hosts file
2016-01-06 07:54:11 o.a.s.c.r.ExponentialBackoffRetry [WARN] maxRetries 
too large (60). Pinning to 29
2016-01-06 07:54:12 o.a.s.c.CuratorZookeeperClient [WARN] session 
timeout [3000] is less than connection timeout [15000]
2016-01-06 07:54:13 o.a.s.c.r.ExponentialBackoffRetry [WARN] maxRetries 
too large (60). Pinning to 29
2016-01-06 07:54:13 o.a.s.c.CuratorZookeeperClient [WARN] session 
timeout [3000] is less than connection timeout [15000]
2016-01-06 07:54:14 o.a.s.c.r.ExponentialBackoffRetry [WARN] maxRetries 
too large (300). Pinning to 29
2016-01-06 07:54:14 o.a.s.c.r.ExponentialBackoffRetry [WARN] maxRetries 
too large (300). Pinning to 29
2016-01-06 07:54:14 o.a.s.c.r.ExponentialBackoffRetry [WARN] maxRetries 
too large (300). Pinning to 29
2016-01-06 07:54:21 o.a.s.c.r.ExponentialBackoffRetry [WARN] maxRetries 
too large (300). Pinning to 29
2016-01-06 07:54:21 b.s.m.n.Client [ERROR] connection to 
Netty-Client-localhost/127.0.0.1:6701 is unavailable
2016-01-06 07:54:21 b.s.m.n.Client [ERROR] dropping 1 message(s) 
destined for Netty-Client-localhost/127.0.0.1:6701

is what i see at the worker file.

Any idea?

On 01/05/2016 09:26 PM, Bryant, Craig W (HP Cloud Service) wrote:
> Hi Oguz,
> The class m.yammer.metrics.Metrics should be in monasca-thresh.jar. 
> Can you verify if it is? Use:
>
> vagrant@mini-mon:/opt/monasca$ jar -tvf 
> /opt/monasca/monasca-thresh.jar | grep com/yammer/metrics/Metrics
>
>    526 Thu Nov 05 18:57:18 UTC 2015 com/yammer/metrics/Metrics$1.class
>
>   7567 Thu Nov 05 18:57:18 UTC 2015 com/yammer/metrics/Metrics.class
>
>
> You first might need to install openjdk-7-jdk using:
>
>
> sudo apt-get install openjdk-7-jdk
>
>
> You should see an output like:
>
>    526 Thu Nov 05 18:57:18 UTC 2015 com/yammer/metrics/Metrics$1.class
>
>   7567 Thu Nov 05 18:57:18 UTC 2015 com/yammer/metrics/Metrics.class
>
>
> If it is not there, where did you get your monasca-thresh.jar from?
>
>
> Craig Bryant
>
> Monasca