Home

[RDK Central Wiki]

CMF

[Code Releases]

Forums

RDK Forums Home

Page tree

Skip to end of metadata
Go to start of metadata

Status

Topic

Author

# of Replies

# of Views

Last Activity Date

4 Comments

  1. Since more one day , we have build issues due to access problem to the server code.rdkcentral.com.

    From Laurenceville in USA , from Chennai in India , and from Rennes in France, we have the same issue

    Problem is completely random ….


    WARNING: halinterface-rdkb-2018q2+gitAUTOINC+f8aa4c5971-r0 do_fetch: Failed to fetch URL git://code.rdkcentral.com/r/rdkb/components/opensource/ccsp/halinterface;protocol=https;branch=rdkb-2018q2;name=halinterface, attempting MIRRORS if available


    And after


    Cloning into bare repository '/local/work/xxxxx/docsis/git/xxxxx/build/../downloads/git2/code.rdkcentral.com.r.rdkb.components.opensource.ccsp.halinterface'...

    error: RPC failed; result=35, HTTP code = 0

    fatal: The remote end hung up unexpectedly

    ERROR: halinterface-rdkb-2018q2+gitAUTOINC+f8aa4c5971-r0 do_fetch: Fetcher failure for URL: 'git://code.rdkcentral.com/r/rdkb/components/opensource/ccsp/halinterface;protocol=https;branch=rdkb-2018q2;name=halinterface'. Unable to fetch URL from any source.

    ERROR: halinterface-rdkb-2018q2+gitAUTOINC+f8aa4c5971-r0 do_fetch: Function failed: base_do_fetch

    ERROR: Logfile of failure stored in: /local/work/xxxxx/docsis/git/xxxxx/build/tmp/work/cortexa15hf-neon-vfpv4-rdk-linux-gnueabi/halinterface/rdkb-2018q2+gitAUTOINC+f8aa4c5971-r0/temp/log.do_fetch.19992

    ERROR: Task (/local/work/xxxxxx/docsis/git/xxxx/meta-rdk-broadband/recipes-ccsp/hal/halinterface.bb:do_fetch) failed with exit code '1'


    Sometime it is for

    Fatal: unable to access 'https://code.rdkcentral.com/r/rdk/components/generic/syslog_helper/': gnutls_handshake() failed: A TLS packet with unexpected length was received.

    Or

    fatal: unable to access 'https://code.rdkcentral.com/r/rdk/components/generic/rdk_logger/': gnutls_handshake() failed: A TLS packet with unexpected length was received.


    Regards

    Michel

    1. Hi Z-cosmao


      Not sure if it was a temporary error, but we see all the components are accessible now. Could you please cross check?


      $ git clone "https://code.rdkcentral.com/r/rdkb/components/opensource/ccsp/halinterface" .
      Cloning into '.'...
      remote: Counting objects: 74, done
      remote: Total 817 (delta 0), reused 817 (delta 0)
      Receiving objects: 100% (817/817), 1.28 MiB | 27.00 KiB/s, done.
      Resolving deltas: 100% (366/366), done.
      Checking connectivity... done.

      $ git clone "https://code.rdkcentral.com/r/rdk/components/generic/syslog_helper"
      Cloning into 'syslog_helper'...
      remote: Counting objects: 76, done
      Kemote: ReTotal 10c5 (deeivilta 0ng o), rbjectseused: 87 105 (delt% (92/105) a 0)
      Receiving objects: 100% (105/105), 25.27 KiB | 0 bytes/s, done.
      Resolving deltas: 100% (9/9), done.
      Checking connectivity... done.

      $ git clone "https://code.rdkcentral.com/r/rdk/components/generic/rdk_logger"
      Cloning into 'rdk_logger'...
      remote: Counting objects: 116, done
      remote: Total 584 (delta 0), reused 584Recei ving (deltobjeca 0)s: 99[K
      Receiving objects: 100% (584/584), 285.53 KiB | 49.00 KiB/s, done.
      Resolving deltas: 100% (242/242), done.
      Checking connectivity... done.

      1. yes , now it is ok ,(the fetch is done from Yocto during the compilation)

        We need to add in .gitconfig these lines :

        [http]
              lowSpeedLimit =1000
              lowSpeedTime = 20
              sslVerify = false
              proxyAuthMethod = basic
        [ssh]
              variant = ssh
        [credential]
               helper = cache --timeout=3600


        I don't know , why no need before  ...

        Perhaps a secure update on code.rdkcentral.com server ?


        Thanks you


        Regards

        Michel

        1. Hi Z-cosmao

          The git builds are working fine for us without changes. Let us check with admin team on this