Skip to end of metadata
Go to start of metadata

The below steps help you troubleshoot cartridges when running Private PaaS on a virtual machine.

  1. Obtain the IP address of the specific cartridge instance.

    You can get the IP address by login into the PPaaS console and navigating to the applications page to view the runtime information of a specific application.

    For more information see Getting the Runtime Topology of an Application.

  2. SSH into the selected instance.

    ssh -i <keyname> <username>@<ip>
    • The keyname refers to the file path when you are using the EC2 or OpenStack IaaS.
    • The ip refers to the IP address of your virtual machine.
  3. Navigate to the tmp folder, which is in the <PRIVATE_PAAS_HOME> directory.  Scan through these logs to identify any  ERROR  or  WARN  messages which caused the erroneous state.
    • The puppet-init.log file contains the details on the instance boot script.
    • The puppet_log file contains the details of the Puppet agent logs.

      This file can be used to troubleshoot the cartridges only if you have used Puppet to deploy Private PaaS.

    • The agent.screen.log file contains the Python agent logs.
  4. Optionally, you can scan through the following files in the mnt folder to cross check whether all the packs and configurations are staged successfully when running PPaaS on a virtual machine:
    • If the cartridge is functioning as expected the following files will be staged through Puppet.
      • /mnt/apache-stratos-python-cartridge-agent-4.1.3
      • /mnt/ppaas-configurator-4.1.0
      • /mnt/<ipaddress>/<product> 
    • The wso2carbon.log file, which is in the /mnt/<ipaddress>/<product/repository/logs directory contains the product specific logs.
  • No labels