In order to troubleshoot the cartridge related errors, Check the Topology view of application in ppaas console to get the ipaddress of the particular instanceThe below steps help you troubleshoot cartridges when running Private PaaS on a virtual machine.
Obtain the IP address of the specific cartridge instance.
Info 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.
SSH into the
...
selected instance.
Code Block ssh -i <keyname> <username>@<ip>Info - The
keynamerefers to the file path when you are using the EC2 or OpenStack IaaS. - The
iprefers to the IP address of your virtual machine.
- The
- Navigate to the
tmpfolder, which is in the<PRIVATE_PAAS_HOME>directory. Scan through these logs to identify anyERRORorWARNmessages which caused the erroneous state.- The
puppet-init.log
- The
...
- file contains the details on the instance boot script.
...
The puppet_log
...
file contains the details of the Puppet agent logs
...
.
Info This file can be used to troubleshoot the cartridges only if you have used Puppet to deploy Private PaaS.
- The
agent.screen.log
...
filecontains the Python agent logs.
Scan through these logs to identify any ERROR or WARN messages which caused the erroneous state.
- Optionally, you can scan through the following files in the
mntfolder to to cross check whether all the packs and configurations are staged successfully when running Private PaaS 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
- If the cartridge is functioning as expected the following files will be staged through Puppet.
...
/mnt/ppaas-configurator-4.1.0-SNAPSHOT
...
/mnt/<ipaddress>/
...
<product>
- The
wso2carbon.logfile, which is in the/mnt/<ipaddress>/<product/repository/logs
...
- directory contains the product specific logs.