Infrastructure at your Service

David Hueber

ODA X7-2S/M update-repository fails after re-image

While playing with a brand new ODA X7-2M, I faced a strange behaviour after re-imaging the ODA with the latest version Basically after re-imaging and doing the configure-firstnet the next step is to import the GI clone in the repository before creating the appliance. Unfortunately this command fails with an error DCS-10001:Internal error encountered: Fail to start hand shake to localhost:7070. Why not having a look on how to fix it…

First of all doing a re-image is really straight forward and work very well. I simply access to the ILOM remote console to attach the ISO file for the ODA, in this case the patch 23530609 from the MOS, and restart the box on the CDROM. After approx. 40 minutes you have a brand new ODA running the latest release.

Of course instead re-imaging, I could “simply” update/upgrade the DCS agent to the latest version. Let say that I like to start from a “clean” situation when deploying a new environment and patching a not installed system sound a bit strange for me ;-)

So once re-imaged the ODA is ready for deployment. The first step is to configure the network that I can SSH to it and go ahead with the create appliance. This takes only 2 minutes using the command configure-firstnet.

The last requirement before running the appliance creation is to import the GI Clone, here the patch p27119393_122120, in the repository. Unfortunately that’s exactly where the problem starts…

Screen Shot 2018-02-19 at 12.11.23

Hmmm… I can’t get it in the repository due to a strange hand shake error. So I will check if the web interface is working at least (…of course using Chrome…)

Screen Shot 2018-02-19 at 12.11.14

Same thing here, it is not possible to come in the web interface at all.

While searching a bit for this error, we finally landed in the Know Issue chapter of the ODA Release Note, which sounds promising. Unfortunately none of the listed error did really match to our case. However doing a small search in the page for the error message pointed us the following case out:

Screen Shot 2018-02-19 at 12.12.28

Ok the error is ODA X7-2HA related, but let’s give a try.


Once DCS is restarted, just re-try the update-repository


Here we go! The job has been submitted and the GI clone is imported in the repository :-)

After that the CREATE APPLIANCE will run like a charm.

Hope it helped!




  • Thomas Beetz says:


    i’ve the same problem, but stop and start initdcsagent doesn’t work for me. Which patch version you have November 2017 or January 2018?

    Regards Thomas

    • David Hueber says:

      Hi Thomas,

      I’m running which is the last one from begin of 2018 but this problem is part of the known issue of the release Therefore it should work for both versions.
      just to give a try, did you test a full reboot. I already had some strange behaviors sometimes.

  • Thomas Beetz says:

    Hi David,

    first i miss PRODUCT and TYPE setting in /etc/grub.conf. Then odacli works, and now i have the DCS-10001 error.
    In dcs-agent.log i see the following entry.

    2018-02-27 06:50:49,896 WARN [dw-225] [] o.e.j.h.HttpParser: Illegal character 0x16 in state=START for buffer HeapByteBuffer@9f524df0[p=1,l=172,c=8192,r=171]={\x16<<>>\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00…\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00}
    2018-02-27 06:50:49,896 WARN [dw-225] [] o.e.j.h.HttpParser: badMessage: 400 Illegal character 0x16 for HttpChannelOverHttp@288e6f7b{r=0,c=false,a=IDLE,uri=-}

    Regards Thomas

    • David Hueber says:

      Hi Thomas,

      one colleague of mine had the same issue in grub than you. This came because there was a wrong configuration on iLOM side where the hostname was entered in the System Identifier. The consequence was the missing information in grud which finally drive to regular DCS crashes. I’m not really convienced that this could be linked to your issue but I would still check it. You can easily do a test by running odaadmcli show env_hw



  • Thomas Beetz says:

    Hi David,

    you are right, the problem is the hardware detection

    [root@oak ~]# odaadmcli show env_hw
    BM ODA X7-2 Small

    that’s wrong it should be

    [root@dbshc110 network-scripts]# odaadmcli show env_hw
    BM ODA X7-2 Medium



Leave a Reply

David Hueber
David Hueber

Chief Executive Officer (CEO), Principal Consultant