ZenPacks, JSON API, and Integrations

Expand all | Collapse all

serviced snapshot commit

  • 1.  serviced snapshot commit

    Posted 03-06-2019 04:05 PM
    Hello,
    I am installing the toolbox,
    when I try a commit, here's the message back !

    API error (500): {"message":"max depth exceeded"}

    I have a multiple node configuration:
    1 control center
    2 resources pool

    Regard




    ------------------------------
    JOANA SIANARD
    SYSADMIN
    GLOBECAST
    PARIS FRANCE
    Zenoss 5.3.3 r419
    Control Center ControlCenter 1.4.2
    ------------------------------


  • 2.  RE: serviced snapshot commit

    Posted 03-07-2019 01:19 PM
    Hello
    Did you follow the steps described in this article (Permanent or Semi-Permanent)?
    https://support.zenoss.com/hc/en-us/articles/207610516-How-to-add-tools-or-scripts-into-a-Resource-Manager-5-x-Docker-Container

    ------------------------------
    Arthur
    ------------------------------



  • 3.  RE: serviced snapshot commit

    Posted 03-07-2019 04:27 PM
    hello
    I have the same problem when I install a zenpack or I restore !

    INFO:zen.ZenPackCmd:Successfully restored zenpacks!
    FATA[0339] Unable to commit container containerid=b8236d11c88d6ec302d0c9b2881f053a0b0fccdf2f05a2c34232f2eafea9cb80 containername=4jpVZOxxuVDkEB9egl44Dw error=API error (500): {"message":"max depth exceeded"}
    location=shell.go:264 logger=cli.api

    ------------------------------
    JOANA SIANARD
    SYSADMIN
    GLOBECAST
    PARIS FRANCE
    Zenoss 5.3.3 r419
    Control Center ControlCenter 1.4.2
    ------------------------------



  • 4.  RE: serviced snapshot commit

    Posted 03-08-2019 03:35 PM
    Can you post the output of the following commands:

    # docker info && serviced volume status
    # img=$(docker images |grep core |grep latest | awk {'print $1'}) && docker history $img

    ​​​​

    ------------------------------
    Arthur
    ------------------------------



  • 5.  RE: serviced snapshot commit

    Posted 03-08-2019 05:05 PM
    Hello Arthur,

    the files.

    Regards,
    JOANA

    ------------------------------
    JOANA SIANARD
    GLOBECAST
    ------------------------------

    Attachment(s)

    txt
    docker-history.txt   13K 1 version
    txt
    docker-info.txt   1K 1 version
    txt
    volume-status.txt   647B 1 version


  • 6.  RE: serviced snapshot commit

    Posted 03-09-2019 02:01 AM
    Hello Joana

    It looks like your image has too many layers (126). As I haven't seen this message so far this is onl my assumption and I can't give you a solution yet. You can google for docker AND "message":"max depth exceeded" for example to find some help how to solve it.

    Anyhow I would be interested about your solution/findings. If I have some free time I'll try to reproduce it, but I can't give you any date so far.

    ------------------------------
    Arthur
    ------------------------------



  • 7.  RE: serviced snapshot commit

    Posted 03-13-2019 01:35 PM

    This happens when your docker container has a lot of layers.  Have you added a lot of things to this before?  (Zenpacks etc).  I would suggest flattening it if so.  Note that you may lose the ability to roll back.  

    https://tuhrig.de/flatten-a-docker-container-or-image/



    ------------------------------
    Andrew Kirch
    Senior Solutions Engineer
    GoVanguard
    ------------------------------