Yes, tcpdump does capture the output when making a wget.
De : Jonathan Hurley [mailto:jhur...@hortonworks.com]
Envoyé : samedi 23 mai 2015 06:14
À : user@ambari.apache.org
Objet : Re: Restarting nodes to avoid HTTP 403
What if you make a connection locally using wget; does tcpdump capture output
cpdump returns nothing.
De : Jonathan Hurley [mailto:jhur...@hortonworks.com]
Envoyé : mardi 19 mai 2015 14:42
À : user@ambari.apache.org<mailto:user@ambari.apache.org>
Objet : Re: Restarting nodes to avoid HTTP 403
It might be because you’re using the loopback adapter. Your command should
With your command I have got the exact same result : tcpdump returns nothing.
De : Jonathan Hurley [mailto:jhur...@hortonworks.com]
Envoyé : mardi 19 mai 2015 14:42
À : user@ambari.apache.org
Objet : Re: Restarting nodes to avoid HTTP 403
It might be because you're using the loopback ad
ing.
Does that help you ?
If you want any additional information, feel free to ask.
Regards,
Loïc
De : Jonathan Hurley [mailto:jhur...@hortonworks.com]
Envoyé : mercredi 13 mai 2015 23:39
À : user@ambari.apache.org<mailto:user@ambari.apache.org>
Objet : Re: Restarting nodes to avoid HTT
...@hortonworks.com]
Envoyé : lundi 18 mai 2015 21:19
À : user@ambari.apache.org
Objet : Re: Restarting nodes to avoid HTTP 403
That's kind of what I expected. I believe that the web request isn't even
making it to the host; that there's something in your environment redirecting
y
ailto:jhur...@hortonworks.com]
Envoyé : mercredi 13 mai 2015 23:39
À : user@ambari.apache.org<mailto:user@ambari.apache.org>
Objet : Re: Restarting nodes to avoid HTTP 403
Well, I’m really baffled by this. Restarting the agents before installing a
cluster fixes the issue as well? So it seems like after agen
bjet : Re: Restarting nodes to avoid HTTP 403
Well, I'm really baffled by this. Restarting the agents before installing a
cluster fixes the issue as well? So it seems like after agents are installed
they are not able to make connections from python without getting a 403
forbidden until
s will help understand where the problem comes from.
Have a nice day,
Loïc
De : Jonathan Hurley [mailto:jhur...@hortonworks.com]
Envoyé : jeudi 7 mai 2015 18:53
À : user@ambari.apache.org<mailto:user@ambari.apache.org>
Objet : Re: Restarting nodes to avoid HTTP 403
All of this really seems
previous emails.
Hope this will help understand where the problem comes from.
Have a nice day,
Loïc
De : Jonathan Hurley [mailto:jhur...@hortonworks.com]
Envoyé : jeudi 7 mai 2015 18:53
À : user@ambari.apache.org
Objet : Re: Restarting nodes to avoid HTTP 403
All of this really seems to point
e.org
Objet : Re: Restarting nodes to avoid HTTP 403
All of this really seems to point to some kind of firewall/proxy issue on the
agent hosts. From your agent named
"vm-03cfbc97-f027-46fe-8e65-cb8c54edf377.frida.priv.atos.fr<http://vm-03cfbc97-f027-46fe-8e65-cb8c54edf377.frida.priv.atos
e Internet via the proxy)
3) Which stack are you deploying?
--> I am deploying HDP-2.2.4.2-2
Have a nice weekend,
Loïc
De : Jonathan Hurley [mailto:jhur...@hortonworks.com]
Envoyé : jeudi 7 mai 2015 17:34
À : user@ambari.apache.org<mailto:user@ambari.apache.org>
Objet : Re: Restart
4.2-2
Have a nice weekend,
Loïc
De : Jonathan Hurley [mailto:jhur...@hortonworks.com]
Envoyé : jeudi 7 mai 2015 17:34
À : user@ambari.apache.org
Objet : Re: Restarting nodes to avoid HTTP 403
The logs indicate that the alerts are running correctly and are simply hitting
a 403. Normally, you might enc
l me if you need any complementary information about my problem,
Thanks,
Loïc
De : Jonathan Hurley [mailto:jhur...@hortonworks.com]
Envoyé : mercredi 6 mai 2015 16:24
À : user@ambari.apache.org<mailto:user@ambari.apache.org>
Objet : Re: Restarting nodes to avoid HTTP 403
OK, so I think I
ementary information about my problem,
Thanks,
Loïc
De : Jonathan Hurley [mailto:jhur...@hortonworks.com]
Envoyé : mercredi 6 mai 2015 16:24
À : user@ambari.apache.org
Objet : Re: Restarting nodes to avoid HTTP 403
OK, so I think I have a clear picture of how you get to this situation. I&#x
so, how long before new warnings start to show up
--> Restarting the agent totally resolves the problem. It does not happen
anymore, and everything run quite normally.
De : Jonathan Hurley [mailto:jhur...@hortonworks.com]
Envoyé : mardi 5 mai 2015 17:36
À : user@ambari.apache.org<mailto:user@a
me if something remains unclear.
Thanks,
De : Jonathan Hurley [mailto:jhur...@hortonworks.com]
Envoyé : mardi 5 mai 2015 20:38
À : user@ambari.apache.org
Objet : Re: Restarting nodes to avoid HTTP 403
If restarting the agents fixes everything, can you explain when you first
encounter the
s start to show up
--> Restarting the agent totally resolves the problem. It does not happen
anymore, and everything run quite normally.
De : Jonathan Hurley [mailto:jhur...@hortonworks.com]
Envoyé : mardi 5 mai 2015 17:36
À : user@ambari.apache.org<mailto:user@ambari.apache.org>
Objet
com]
Envoyé : mardi 5 mai 2015 17:36
À : user@ambari.apache.org
Objet : Re: Restarting nodes to avoid HTTP 403
Can you provide some more information on your environment, such as:
1) Version of Ambari
2) Whether the environment is kerberized
3) Are you running the Ambari agent as root, or another
Can you provide some more information on your environment, such as:
1) Version of Ambari
2) Whether the environment is kerberized
3) Are you running the Ambari agent as root, or another user.
4) Any information from the ambari-agent.log file that might seen to indicate a
problem
5) You said that
Hi,
I have currently some issues with cluster nodes. According to the Ambari web
User Interface, I have 11 alerts linked to the fact that all nodes (except the
monitoring one) return HTTP 403 response for services such as NameNode web UI,
DataNode web UI, or NodeManager Health.
The first weird
20 matches
Mail list logo
