Latest post Fri, Jan 4 2019 12:25 PM by matev. 7 replies.
Page 1 of 1 (8 items)
Sort Posts: Previous Next
  • Tue, Dec 18 2018 3:18 PM

    we cannot connect to new 201811 ver. cloudux

    We can not connect to the newly updated cloudux server and don't know how we can do that.
    So our cloudux version 201811 updated from 20189 yesterday. It seems the newly installed DMS services avoid to login us.

    Like the logs said:
    {"log":"\u0009at com.avid.interplay.osgi.webservice.impl.InterplayClientImpl$ConnectionRunner$1.call(InterplayClientImpl.java:822)\n","stream":"stdout","time":"2018-12-18T14:51:21.585730096Z"}
    {"log":"\u0009... 4 more\n","stream":"stdout","time":"2018-12-18T14:51:21.585741096Z"}
    {"log":"2018-12-18 14:51:21.663Z [INFO] [c.a.p.b.BaseJXDKUtils] [] {source=} Connecting to Interplay host: avid-interplay with client host: 89.101.202.126 and user: george and token: OWIxOTAwNTktYjQ5MC00OTQ3LWJhMGQtYmI0NjEyZDA4MzI5 using service license\n","stream":"stdout","time":"2018-12-18T14:51:21.664442923Z"}
    {"log":"2018-12-18 14:51:22.227Z [ERROR] [c.a.p.s.i.SubclipBusServiceImpl] [] {source=} an error occured\n","stream":"stdout","time":"2018-12-18T14:51:22.230219617Z"}
    {"log":"com.avid.central.interplay.osgi.webservice.InterplayException: com.avid.central.interplay.osgi.webservice.AuthenticationFailedInterplayException: com.avid.interplay.osgi.webservice.impl.InterplaySystemAuthenticationException: net.nxn.JXDK.AuthentificationFailedException: Username or password is invalid.\n","stream":"stdout","time":"2018-12-18T14:51:22.230261018Z"}
    {"log":"\u0009at com.avid.pam.base.BaseJXDKUtils.createInterplayClient(BaseJXDKUtils.java:1022)\n","stream":"stdout","time":"2018-12-18T14:51:22.230277218Z"}

    Do we need to do something ? Based on the documentation no. Which settings needed to be done and where ?
    I just followed the upgrade instructions.

    Filed under:
  • Tue, Dec 18 2018 3:20 PM In reply to

    Re: we cannot connect to new 201811 ver. cloudux

    I mean the problem is to connect to Avid Interplay.

    --

    George

  • Wed, Dec 19 2018 1:49 PM In reply to

    • VadymG
    • Not Ranked
    • Joined on Thu, Aug 16 2018
    • Posts 6
    • Points 90

    Re: we cannot connect to new 201811 ver. cloudux

    Hello George.

    Could you please describe what have you done for upgrade CloudUX? have you upgraded platform? and feature packs too?

    Do you see version  2018.11 for all platform and application packages (after executing command - helm ls)?

     

    Thanks,

    Vadym G.

  • Wed, Dec 19 2018 2:18 PM In reply to

    Re: we cannot connect to new 201811 ver. cloudux

    Yes I did.

    First is the host upgraded as described in the doc. Then the packages.

    NAME        REVISION    UPDATED                     STATUS      CHART                                        NAMESPACE
    core        15          Tue Dec 18 14:23:22 2018    DEPLOYED    platform-core-2018.11.0-0164-G705cfa1        default 
    core-app    15          Tue Dec 18 14:23:58 2018    DEPLOYED    platform-core-app-2018.11.0-0164-G705cfa1    default 
    ingest      1           Tue Dec 18 11:51:20 2018    DEPLOYED    platform-ingest-2018.11.0-0164-G705cfa1      default 
    mam         1           Tue Dec 18 11:50:10 2018    DEPLOYED    platform-mam-2018.11.0-0164-G705cfa1         default 
    pam         14          Tue Dec 18 14:24:27 2018    DEPLOYED    platform-pam-2018.11.0-0164-G705cfa1         default 
    playback    15          Tue Dec 18 14:24:09 2018    DEPLOYED    platform-playback-2018.11.0-0164-G705cfa1    default 
    search      15          Tue Dec 18 14:24:19 2018    DEPLOYED    platform-search-2018.11.0-0164-G705cfa1      default

     

  • Thu, Dec 20 2018 3:05 PM In reply to

    Re: we cannot connect to new 201811 ver. cloudux

    We have found in the error log:

    {"log":"2018-12-20 14:46:35.686 [INFO   ] REQUEST: locationsFolder : %2F  attributes : null \n","stream":"stderr","time":"2018-12-20T14:46:35.687726469Z"}
    {"log":"2018-12-20 14:46:35.686 [INFO   ] New login on ProjectNode for user null \n","stream":"stderr","time":"2018-12-20T14:46:35.68775657Z"}
    {"log":"2018-12-20 14:46:35.974 [SEVERE ]  Unable to login to server avid-interplay with UserIdentity [accessToken=Token(tokenString=ZTJmYmVhYjktMzViYy00ZTZjLWIyNzMtMWU5ZDkyNDhjMTU3, upstreamHost=cloudux.
    overcasthq.com, clientMachineId=5.15.184.109, ipHostHint=)]: Username or password is invalid.\n","stream":"stderr","time":"2018-12-20T14:46:35.978322153Z"}
    {"log":"PAMCTCException [errorCode=401, message=com.avid.pam.impl.data.exception.PAMCTCException:  Unable to login to server avid-interplay with UserIdentity [accessToken=Token(tokenString=ZTJmYmVhYjktMzV
    iYy00ZTZjLWIyNzMtMWU5ZDkyNDhjMTU3, upstreamHost=cloudux.overcasthq.com, clientMachineId=5.15.184.109, ipHostHint=)]: Username or password is invalid.]\n","stream":"stderr","time":"2018-12-20T14:46:35.9783
    63453Z"}
    {"log":"\u0009at com.avid.pam.impl.data.asset.ProjectNodeCache.makeProjectNodeLoginHandlerCore(ProjectNodeCache.java:155)\n","stream":"stderr","time":"2018-12-20T14:46:35.978378954Z"}
    {"log":"\u0009at com.avid.pam.impl.data.asset.ProjectNodeCache.lambda$makeProjectNodeLoginHandler$2(ProjectNodeCache.java:131)\n","stream":"stderr","time":"2018-12-20T14:46:35.978390754Z"}
    {"log":"\u0009at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1626)\n","stream":"stderr","time":"2018-12-20T14:46:35.978402254Z"}
    {"log":"\u0009at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)\n","stream":"stderr","time":"2018-12-20T14:46:35.978428555Z"}
    {"log":"\u0009at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)\n","stream":"stderr","time":"2018-12-20T14:46:35.978441555Z"}
    {"log":"\u0009at java.lang.Thread.run(Thread.java:745)\n","stream":"stderr","time":"2018-12-20T14:46:35.978452555Z"}
    {"log":" \n","stream":"stderr","time":"2018-12-20T14:46:35.978463556Z"}

    So the username is: null \n - which is not correct (or I don't know)

    We have found it in pam-ctc log.

    Probably it helps to you to find the problem what I need to solve ASAP.

    --
    George

  • Wed, Dec 26 2018 3:22 PM In reply to

    • VadymG
    • Not Ranked
    • Joined on Thu, Aug 16 2018
    • Posts 6
    • Points 90

    Re: we cannot connect to new 201811 ver. cloudux

    Hello George.

    please try to:

    1/ delete pam-feature by executing the following command - helm delete pam

    2/ verify pam.config (/etc/avid/config/pam.conf)

    3/ deploy pam feature againe: avidctl platform deploy -i

     

    Thanks,

    Vadym G.

  • Thu, Dec 27 2018 6:57 PM In reply to

    Re: we cannot connect to new 201811 ver. cloudux

    Hi Vadym,

    Thanks for the answer. I tried that before and done it once again, but it did not help.
    We have got the same maseage. What is strange that username is "null" instead of the used "george".
    Does something changed in the authentication ? The error is logged in on pam-ctc container.

    (I'd like to upload screenshots, but the "my files" is not working currently.)

    --
    George

  • Fri, Jan 4 2019 12:25 PM In reply to

    • matev
    • Not Ranked
    • Joined on Tue, Aug 2 2016
    • Posts 4
    • Points 40

    Re: we cannot connect to new 201811 ver. cloudux

    Hello guys,

    we have exactly the same problem. In addition we tried to connect the same cloudux to MC|Production v2018.11 and it went well (just I had to manualy import the users in Interplay Administrator from the MediaCentral Platform authentication provider)! However when we reconfigure the cloudux to use Inteprlay Production 3.8.1 then we get the same error massge as George posted.

    Anyi ideas?

Page 1 of 1 (8 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller