[
https://issues.apache.org/jira/browse/KNOX-2921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zita Dombi resolved KNOX-2921.
------------------------------
Assignee: Zita Dombi
Resolution: Duplicate
hi Pratyush Bhatt,
this was fixed by KNOX-2930, let me resolve this issue
> [Ozone-Knox] Port blocking on one OM Instance blocks all the OM UIs
> -------------------------------------------------------------------
>
> Key: KNOX-2921
> URL: https://issues.apache.org/jira/browse/KNOX-2921
> Project: Apache Knox
> Issue Type: Bug
> Reporter: Pratyush Bhatt
> Assignee: Zita Dombi
> Priority: Major
> Attachments: image (6).png, image (7).png, image (8).png
>
>
> ozone.om.https-port is set to 9875
> Blocked the port on one of the OM instance:
> {noformat}
> [root@ozn-kx4-3 ~]# sudo iptables -L
> Chain INPUT (policy ACCEPT)
> target prot opt source destination
> Chain FORWARD (policy ACCEPT)
> target prot opt source destination
> Chain OUTPUT (policy ACCEPT)
> target prot opt source destination
> [root@ozn-kx4-3 ~]# sudo iptables -A INPUT -p tcp --dport 9875 -j DROP
> [root@ozn-kx4-3 ~]# sudo iptables -L
> Chain INPUT (policy ACCEPT)
> target prot opt source destination
> DROP tcp -- anywhere anywhere tcp dpt:sapv1
> Chain FORWARD (policy ACCEPT)
> target prot opt source destination
> Chain OUTPUT (policy ACCEPT)
> target prot opt source destination{noformat}
> The affected node UI is getting 500, which is correct, but along with that
> other two OM UI Instances are also throwing the same even when the port is
> not blocked there.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
