Planning Analytics

Planning Analytics

Get AI-infused integrated business planning

 View Only

  • 1.  PAW not starting after upgrade (Linux)

    Posted 02/27/22 07:54 AM

    Hi,

     

    I had an issue when I upgraded PAW from version 63 to version 73; some services are not starting via the administration tool. Below services status is not changing from 'restarting'.

     

    • Content Delivery
    • Gateway
    • Share Proxy
    • workspace proxy

     

    I have tried uninstalling (scripts/paw.sh down --rmi all -v) and reinstalling PAW after removing all networks (docker network rm <network-id>)  before reinstalling.  

    Can anyone direct me to what should be my next steps to resolve this?

     

    Server version

    Distributor ID: Ubuntu

    Description:    Ubuntu 16.04.3 LTS

    Release:        16.04

    Codename:       xenial

     

     

     

    Any guidance is appreciated.

     

    Regards,

    Nuwan Fernando


    #PlanningAnalyticswithWatson


  • 2.  RE: PAW not starting after upgrade (Linux)

    Posted 02/28/22 10:11 AM
    Hi Nuwan,

    can you provide more information like the log of the restarting containers?
    Has it worked as expected before on Ubuntu? Ubuntu isn't officially supported for PAW...

    Regards

    ------------------------------
    Dominik
    ------------------------------



  • 3.  RE: PAW not starting after upgrade (Linux)

    Posted 02/28/22 09:56 PM
    Hi Dominik,

    Yes, this has worked well with all past versions.

    Unfortunately, I don't have the 'restarting' containers logs since I had to re-instate the prod-server from a snapshot.

    Let me know if you need anything else?

    Regards
    Nuwan

    ------------------------------
    nuwan fernando
    ------------------------------

    Original Message


  • 4.  RE: PAW not starting after upgrade (Linux)
    Best Answer

    Posted 03/04/22 03:49 PM
    Edited by System Admin 01/20/23 04:25 PM
    Nuwan,

    Check disk space. use "df -h" in an ssh session and see if anything has a use% over 90%.

    Have you run /scripts/clean.sh for prior releases after you upgrade and validate a newer release? Old images can accumulate and waste disk. See: https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=local-upgrade-planning-analytics-workspace  about clean.sh

    By default, Docker will build everything under /var/lib/docker/ that is typically on a system volume rather than a on a separately mounted and larger data volume. If you never ran clean.sh then there can be a bunch of old images hanging around eating up disk space. I vaguely recall seeing where PAW only partially started because it was out of disk space, and several services kept restarting. If the /etc/docker/daemon.json has not been created or does not contain a data-root setting pointing to an empty-ish data volume then you have some cleaning to do since all the images will be accumulating in /var/lib/docker/.

    ------------------------------
    Walter Coffen
    Technology Manager
    QueBIT Consulting, LLC
    ------------------------------

    Original Message


Related Content