Traffic Recognition Issue on Single-Core Machine/Connection Timed Out

While single-core machines are not recommended for a production environment, they can be a resourceful way to test and demo with the open-apspec. If the agent is failing to recognize traffic on a single-core machine, and you observe a connection timed-out error in the NGINX error logs (/var/log/nginx/error.log), please follow the steps below to resolve the issue:

  1. Check NGINX Logs:

    • Open the NGINX error logs using the following command:

      cat /var/log/nginx/error.log
    • Look for any connection timed-out errors. This will provide valuable information about the issue.

  2. Navigate to Configuration File:

    • Locate the configuration file at /dev/shm/cp_nano_http_attachment_conf.

  3. Update Registration Thread Timeout:

    • Open the configuration file and find the parameter registration_thread_timeout_msec.

    • Change the value from 100 to 200.

      registration_thread_timeout_msec 200;
  4. Restart NGINX:

    • After making the changes, restart NGINX to apply the configuration updates.

      sudo service nginx restart

These steps should help address the issue of traffic recognition on a single-core machine when using the open-appsec. However, it's strongly recommended to use hardware that meets the recommended system requirements for optimal WAF performance in a production environment.

Last updated