Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi all
I've installed Talend Data Fabric 7.1. I've created user for MDM Web UI in TAC, but can't to log in the MDM Web UI.
I use address http://<myhost>:8180/talendmdm, but after click on Login button I see message Oops.. bad request (screenshot is attached)
Have anybody any idea?
I've solved my problem.
I used solution from https://community.talend.com/t5/Installation/Authentication-failed-in-Data-Stewardship/ta-p/36316
I added line
iam.additionalTLDs=lan,eeee,dddd,cccc,bbbbb,aaaa
and restarted iam service
Hello,
Are you able to access the user interface from this link : http://localhost:8180/talendmdm/ui or http://localhost:8180/talend/TalendPort ?
Best regards
Sabrina
Hi
I have tried
http://localhost:8180/talendmdm/ui - the same result
http://localhost:8180/talend/TalendPort - 404 not found
Hello,
Is your MDM server up and running?
Best regards
Sabrina
Yes, of course
Hello,
This issue cannot be reproduced on V 7.1.1 from our side. We suspect there is something wrong with your installation. Have you tried to reinstall your MDM to see if it work?
Best regards
Sabrina
Yes.
I tried 2 times using CentOS 7.
At the first time I missed last installation messages, but at the second time installation was aborted. Where I can find an installation log?
This is installer output
----------------------------------------------------------------------------
Please wait while Setup installs Talend modules on your computer.
Installing
0% ______________ 50% ______________ 100%
########about to fork child process, waiting until server is ready for connections.
forked process: 4627
child process started successfully, parent exiting
################################Installation Aborted!
There are some Talend system services installed. Should the installer remove these services?
[Y/n]:
If I choose Y all installed services will be stopped and removed.
If I choose N:
Error: There has been an error.
Error running /bin/systemctl start talend-kibana-7.1.1 : Job for
talend-kibana-7.1.1.service failed because the control process exited with error
code. See "systemctl status talend-kibana-7.1.1.service" and "journalctl -xe"
for details.
[root@talenddf talend]# systemctl status talend-kibana-7.1.1.service ● talend-kibana-7.1.1.service - Talend Kibana service Loaded: loaded (/etc/systemd/system/talend-kibana-7.1.1.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2019-01-08 12:41:53 MSK; 5min ago Process: 7671 ExecStart=/opt/Talend-7.1.1/logserv/start_kibana_daemon.sh (code=exited, status=1/FAILURE) Jan 08 12:40:32 talenddf systemd[1]: Starting Talend Kibana service... Jan 08 12:41:53 talenddf systemd[1]: talend-kibana-7.1.1.service: control process exited, code=exite...tus=1 Jan 08 12:41:53 talenddf systemd[1]: Failed to start Talend Kibana service. Jan 08 12:41:53 talenddf systemd[1]: Unit talend-kibana-7.1.1.service entered failed state. Jan 08 12:41:53 talenddf systemd[1]: talend-kibana-7.1.1.service failed. Hint: Some lines were ellipsized, use -l to show in full.
[root@talenddf talend]# journalctl -xe Jan 08 12:40:12 talenddf systemd[1]: Configuration file /etc/systemd/system/talend-runtime-7.1.1.service is Jan 08 12:40:22 talenddf systemd[1]: Reloading. Jan 08 12:40:23 talenddf systemd[1]: Configuration file /etc/systemd/system/talend-runtime-7.1.1.service is Jan 08 12:40:32 talenddf systemd[1]: Starting Talend Kibana service... -- Subject: Unit talend-kibana-7.1.1.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit talend-kibana-7.1.1.service has begun starting up. Jan 08 12:41:53 talenddf start_kibana_daemon.sh[7671]: failed to start Elasticsearch Jan 08 12:41:53 talenddf systemd[1]: talend-kibana-7.1.1.service: control process exited, code=exited status Jan 08 12:41:53 talenddf systemd[1]: Failed to start Talend Kibana service. -- Subject: Unit talend-kibana-7.1.1.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit talend-kibana-7.1.1.service has failed. -- -- The result is failed. Jan 08 12:41:53 talenddf systemd[1]: Unit talend-kibana-7.1.1.service entered failed state. Jan 08 12:41:53 talenddf systemd[1]: talend-kibana-7.1.1.service failed. Jan 08 12:44:39 talenddf run-parts(/etc/cron.daily)[7913]: finished man-db.cron Jan 08 12:44:40 talenddf run-parts(/etc/cron.daily)[7915]: starting mlocate lines 2789-2811/2811 (END) -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-11.scope has finished starting up. -- -- The start-up result is done. Jan 08 12:40:03 talenddf systemd[1]: Starting Session 11 of user root. -- Subject: Unit session-11.scope has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-11.scope has begun starting up. Jan 08 12:40:03 talenddf CROND[7625]: (root) CMD (/usr/lib64/sa/sa1 1 1) Jan 08 12:40:11 talenddf systemd[1]: Reloading. Jan 08 12:40:12 talenddf systemd[1]: Configuration file /etc/systemd/system/talend-runtime-7.1.1.service is Jan 08 12:40:22 talenddf systemd[1]: Reloading. Jan 08 12:40:23 talenddf systemd[1]: Configuration file /etc/systemd/system/talend-runtime-7.1.1.service is Jan 08 12:40:32 talenddf systemd[1]: Starting Talend Kibana service... -- Subject: Unit talend-kibana-7.1.1.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit talend-kibana-7.1.1.service has begun starting up. Jan 08 12:41:53 talenddf start_kibana_daemon.sh[7671]: failed to start Elasticsearch Jan 08 12:41:53 talenddf systemd[1]: talend-kibana-7.1.1.service: control process exited, code=exited status Jan 08 12:41:53 talenddf systemd[1]: Failed to start Talend Kibana service. -- Subject: Unit talend-kibana-7.1.1.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit talend-kibana-7.1.1.service has failed. -- -- The result is failed. Jan 08 12:41:53 talenddf systemd[1]: Unit talend-kibana-7.1.1.service entered failed state. Jan 08 12:41:53 talenddf systemd[1]: talend-kibana-7.1.1.service failed. Jan 08 12:44:39 talenddf run-parts(/etc/cron.daily)[7913]: finished man-db.cron Jan 08 12:44:40 talenddf run-parts(/etc/cron.daily)[7915]: starting mlocate lines 2780-2811/2811 (END)
Looking at Network requests and see http 400 for the following request
http://<myhots>:9080/idp/federation/up?wa=wsignin1.0&wreply=http://<myhots>:9080/oidc/login&wtrealm=urn:org:apache:cxf:fediz:oidc&wct=2019-01-08T12:40:52.302Z&wctx=a9e59ec5-46b6-4b55-82b1-40c71ae97cdd&auth_app=<application+xmlns="http://iam.talend.org/application">mdm</application>
Additional info:
I used Advanced installation option and configure PostgreSQL as database for Administrator, MDM, Data Quality.
Also I've created another VM with CentOS 7 and use the Easy installation option. In this case a can connect to MDM Web UI.
Hi @alfim,
I have the same problem. I used Advanced and Easy installation on VM CentOS 7 and in both mode I could't access the MDM Web UI. In VM Windows all services works fine.
Did you get any solutions?
Talend Data Fabric 7.1
CentOS 7
Thanks
Hello,
With your subscription solution, would you mind creating a case on talend support portal so that we can give you a remote assistance through support cycle with priority?
https://login.talend.com/support-login.php
Best regards
Sabrina