Nevermind, I found the issue. This works:
./bin/start_alerts_ui.sh -p 4201 -r http://<IP>:8082 [7] This doesn't apparently: ./bin/start_alerts_ui.sh -p 4201 -r <IP>:8082 On 2017-09-27 15:58, Laurens Vets wrote: > Once the alerts-ui package has been compiled & installed where exactly would > I be able to check the proxy configuration? > > On 2017-09-27 15:37, Ryan Merriman wrote: > If you can get to that page and see the API actions, you are logged in. The > only thing I can think of is your proxy isn't setup correctly. > > On Wed, Sep 27, 2017 at 5:04 PM, Laurens Vets <[email protected]> wrote: > > I mean, I can go to the Swagger UI page on port 8082 and I see an overview of > API actions. But how can actually log on? > > On 2017-09-27 14:55, Laurens Vets wrote: > > How can I log into the Swagger UI? > > On 2017-09-27 14:38, Ryan Merriman wrote: > Nevermind it is proxying to metron1, I see it now. Please disregard. Are > you able to log into the Swagger UI? > > On Wed, Sep 27, 2017 at 4:37 PM, Ryan Merriman <[email protected]> wrote: > > Did you just update master? I merged a PR probably 15 minutes ago that > changes how this works. Your REST host is set to "localhost" which is > probably wrong (should be metron1?). Check out the metron-alerts README to > see the updated install process. MPack is coming soon for this so you won't > even have to install it manually (my guess is it makes it in a couple days > from today). > > Ryan > > On Wed, Sep 27, 2017 at 4:33 PM, Laurens Vets <[email protected]> wrote: > When I installed the Metron Alerts UI on my 0.4.0 install, I could log in > with the Metron Management UI user. > > I upgraded to 0.4.1, did the same as mentioned on > https://github.com/apache/metron/tree/apache-metron-0.4.1-release/metron-interface/metron-alerts#installing-on-an-existing-cluster > [1], but for some reason the user that works on my management UI doesn't > work for the Alerts UI. I get a 500 Internal Server error back in the Chrome > console. > > This is what I see via CLI on the host where I want to run the UI: > > [root@metron1 ~]# /usr/metron/0.4.1/bin/start_alerts_ui.sh -p 4201 -r > metron1:8082 > [HPM] Proxy created: / -> metron1:8082 > [HPM] Proxy rewrite rule created: "^/search" ~> "" > [HPM] Proxy created: / -> metron1:8082 > Metron alerts ui is listening on > MAILSCANNER HAS DETECTED A POSSIBLE FRAUD ATTEMPT FROM "127.0.0.1:4201" > CLAIMING TO BE MAILSCANNER WARNING: NUMERICAL LINKS ARE OFTEN MALICIOUS: > http://127.0.0.1:4201 [2] > MAILSCANNER HAS DETECTED A POSSIBLE FRAUD ATTEMPT FROM "10.0.0.11:4201" > CLAIMING TO BE MAILSCANNER WARNING: NUMERICAL LINKS ARE OFTEN MALICIOUS: > http://10.0.0.11:4201 [3] > MAILSCANNER HAS DETECTED A POSSIBLE FRAUD ATTEMPT FROM "172.17.42.1:4201" > CLAIMING TO BE MAILSCANNER WARNING: NUMERICAL LINKS ARE OFTEN MALICIOUS: > http://172.17.42.1:4201 [4] > MAILSCANNER HAS DETECTED A POSSIBLE FRAUD ATTEMPT FROM "10.0.0.100:4201" > CLAIMING TO BE MAILSCANNER WARNING: NUMERICAL LINKS ARE OFTEN MALICIOUS: > http://10.0.0.100:4201 [5] > [HPM] Error occurred while trying to proxy request /api/v1/user from > localhost:4201 to metron1:8082 (EINVAL) > (https://nodejs.org/api/errors.html#errors_common_system_errors [6]) > [HPM] Error occurred while trying to proxy request /api/v1/user from > localhost:4201 to metron1:8082 (EINVAL) > (https://nodejs.org/api/errors.html#errors_common_system_errors [6]) > [HPM] Error occurred while trying to proxy request /api/v1/user from > localhost:4201 to metron1:8082 (EINVAL) > (https://nodejs.org/api/errors.html#errors_common_system_errors [6]) > ^C[root@metron1 ~]# > > Those errors happen when I try to log on. > > Changing 'metron1' to the ip address doesn't resolve the issue. > > Any idea on how I can generate extra logs to troubleshoot this? Links: ------ [1] https://github.com/apache/metron/tree/apache-metron-0.4.1-release/metron-interface/metron-alerts#installing-on-an-existing-cluster [2] http://127.0.0.1:4201 [3] http://10.0.0.11:4201 [4] http://172.17.42.1:4201 [5] http://10.0.0.100:4201 [6] https://nodejs.org/api/errors.html#errors_common_system_errors [7] http://10.0.0.11:8082
