Taskforce.sh
  • Documentation
  • Getting started
    • Direct Redis Connection
    • Taskforce connector
  • Account
    • Settings
  • Connections
    • Queues
    • Jobs
    • Workers
  • Metrics
  • Monitoring
    • Enable notifications
      • Slack
      • Pagerduty
    • Connection monitor
    • Failed jobs monitor
    • Missing workers monitor
    • Max Memory monitor
    • Backlog Monitor
  • Alerts
  • Organizations
  • BullMQ Pro
    • Connector Pro
  • On Premises
    • AWS
      • Launch AWS AMI.
      • Create role with SSM permissions
      • Assign SSM Role
      • Configure your instance
        • Create a PostgreSQL instance
        • Configure Auth0
          • Configure API
        • Configure Mailgun
      • Setup loadbalancer
      • Setup route 53
      • Monitors
      • Upgrading
      • Troubleshooting
    • Docker
      • Docker registry
      • Environment variables
      • Docker compose
    • Using the taskforce connector
  • Security primer
  • Troubleshooting
Powered by GitBook
On this page

Was this helpful?

  1. On Premises
  2. AWS

Troubleshooting

PreviousUpgradingNextDocker

Last updated 2 years ago

Was this helpful?

As there are quite a lot of steps to get the instance working it is easy that things goes wrong. In this section we will provide some tips in order to help troubleshooting.

Check logs

It is possible to SSH to the instance running Taskforce.sh and use in order to get the logs. You can start by running:

pm2 list

You should get an output like this:

Now you can use the id (0 in this case to fetch the logs):

pm2 logs 0 --lines 500
pm2