anchor.diff:  * Access logs: `/var/log/nginx/access.log`
   * Error logs: `/var/log/nginx/error.log`
   
  -**System Diagnostics**
  -
  -In order to get some support, the first thing we would require is some information about your deployment. We have created a `diagnostic` command for that effect:
  +=== System Diagnostics
  +
  +If support is needed, we may require some additional detailed information about your deployment. We have created a `diagnostic` command for this purpose. to run this command:
   
   ```
   # Login as 'tomcat'
   > sudo su - tomcat
   #
  -# Assume a 'bob/lazar' tenant
  -# Assume some credentials 'admin/password'
  +# Set your access credentials. This example
  +#   assumes the default credentials are used:
   #
   > kpm  diagnostic \
     --killbill-credentials=admin password \
  
positive.code: 
  The `Let's Encrypt` certifcates are only valid 90 days and will therefore neeed to be renewed. `certbot` will create a cron entry under `/etc/cron.d/certbot` to make this process transparent.
  
  === Kill Bill
  
  Kill Bill global properties are defined in `/var/lib/killbill/config/killbill.properties`. For example, this is where you can change the MySQL credentials. Take a look at our https://docs.killbill.io/latest/userguide_configuration.html[configuration guide] for more details.
  
  This is also where you can change the default Kill Bill admin credentials: specify `org.killbill.security.shiroResourcePath=/var/lib/killbill/config/shiro.ini` and create the `shiro.ini` file accordingly (see our https://docs.killbill.io/latest/user_management.html[RBAC guide] for more details).
  
  == TroubleShooting Section
  
  
  After launching the EC2 instance, the full stack should come up, with all services enabled and running, that is:
  
negative.code: * A instance of Kaui listening on `127.0.0.1:3000` (and receiving external traffic through nginx on port `443`)
  * A local `mysql` server running on port `3306`
  
  
  In this section, we will provide some tips to verify the operation of the system, and what to do when things are not working.
  
  === System Health
  
  
  To verify the overall health of the Kill Bill server instance, you can issue the following command:
  
  ```
  curl http://127.0.0.1:8080/1.0/healthcheck
  ```
  
  This will return a series of messages giving the health of various system components.
  
  A detailed system information report is available using the following command:
  
  ```
  curl -u <ADMIN>:<PASSWORD> http://127.0.0.1:8080/1.0/kb/nodesInfo
  ```
  Here <ADMIN> and <PASSWORD> are your administrator access credentials.
  
  The Kill Bill single-tier option is composed of four services. The status of each service can be checked by the following commands:
  
  * Kill Bill service: `sudo service killbill status`
  * KAUI service: `sudo service kaui status`
  * Nginx service: `sudo service nginx status`
  * Mysql service: `sudo service mysql status`
  
  For each report there should be a line near the top with the following form:
  
  ```
  Active: active (running) since Sat 2020-10-24 20:13:43 UTC; 1 day 1h ago
  ```
  
  
  Similarly you can `start` or `stop` the services using similar commands, such as `sudo service kaui stop` to stop KAUI.
  
  
  === Log Files
  
  The system maintains a series of logfiles that should be helpful when troubleshooting is needed.
  
  Tomcat logs are under `/var/lib/tomcat/logs/`:
  
  