Skip to main content
Version: Next

Troubleshooting

This page provides general troubleshooting steps for both Standalone and Clustered ASI deployments.
These checks apply to every environment and should be your first point of investigation when diagnosing issues.

Core Diagnostic Tools​

ToolPurpose
asiStatusShows the status of all ASI modules running on the node
systemctlChecks whether system services are active, failed, or restarting
isshealthShows environment, cluster/member health and internal connectivity
Log filesLocated in /opt/ISS/logs/asi — primary source for detailed error messages

1. Services Not Starting​

Check ASI service group​

sudo systemctl status iss-asi.target

Check individual module status​

# as ppadmin
/opt/ISS/asi/bin/asiStatus

View service logs​

sudo journalctl -u 'iss-*' -xe

If a specific module is failing, inspect its logs under:

/opt/ISS/logs/asi/

2. Database Connection Issues​

Database issues usually appear as connection timeouts, refused connections, authentication failures, or missing extensions.

Manual connectivity test​

psql -h <db-host> -U <user> -d <database>

Validate the following​

  • Database host reachable over the network
  • Port 5432 open
  • Correct username/password

3. TLS / Certificate Issues​

Common causes include incorrect file paths, missing CA certificates, wrong permissions, or failing handshakes.

Verify permissions​

ls -l /opt/ISS/config/security/

Inspect certificate content​

openssl x509 -in /opt/ISS/config/security/server.pem -text -noout

Check certificate chain against your certificatre​

openssl verify -CAfile /etc/pki/tls/certs/ca-bundle.crt /opt/ISS/config/security/server.pem

4. Network or Connectivity Errors​

If ASI modules cannot talk to each other or the database:

Check hostname resolution​

ping <hostname>

Validate port accessibility​

nc -vz <host> <port>

Review firewalls​

  • iptables / nftables
  • OS-level firewall
  • Cloud network rules (security groups, NACLs)

5. isshealth​

Run isshealth to get the status of the services and applications running on the node:

isshealth

This validates:

  • environment
  • Node-to-node communication
  • Module health
  • Cluster membership state

If a node is unhealthy:

  • Check local ASI services (systemctl, asiStatus)
  • Review logs under /opt/ISS/logs/asi
  • Ensure the node can reach peers (clustered)

6. Reviewing Log Files​

All ASI logs are stored in:

/opt/ISS/logs/asi

Look for:

  • Database connection failures
  • TLS handshake or certificate errors
  • Startup/configuration parsing issues
  • Inter-node communication errors
  • Service restarts/crashes

7. When to Contact Support​

Before contacting support, gather:

Diagnostic output​

# as ppadmin user
/opt/ISS/asi/bin/asiStatus

isshealth output:

isshealth

Include:​

  • Copies of relevant log files
  • Recent configuration changes (TLS, DB, load balancer)
  • Node role (standalone or cluster member)