Server Crashes & Errors

Use this guide to learn more about how to gather and send info on Server Crashes and Errors.

For gathering info on Server Initialization-related Behaviors, see Server Initialization Logs.

To learn how to gather and send Android-related logs, see Android Crash & Error Logs.

To learn how to gather and send iOS-related logs, see iOS Crash & Error Logs.

To learn how to gather and send Browser-related logs, see Browser Exception & Error Logs.

Crashes & Hanging Unexpected Behaviors

Please follow the following steps to get us a thread dump of your crash or hang:

Use GNU Debugger

  • If 'gdb' is available, this is the easiest path to getting a thread dump.

  • Run the following command, replacing [PID] with your Application's process id:

    • gdb -p [PID] -ex "thread apply all bt" -ex "info proc mappings" -batch

Send crash log report

  • Update what is logged by running this command ulimit -c unlimited before your application is started.
  • Inspect your Application’s log output to find the details of where it has stored the error log. It will be named hs_err_pidXXXX.log.

Send a core dump

  • Core dumps are generated by the Java Runtime when certain crash conditions occur. To enable usable crash dumps, you must set ulimit -c unlimited before your application runs.

  • Run kill -11 [PID] from the command line, replacing [PID] with your Application's process id.

  • The core dump error log will likely be several hundred megabytes, but it will be much smaller after zipping. Please provide us the ZIP file.

Sharing Logs with FaceTec via a Support Request

Please collect the following information before Sending us a Support Request:

  1. The FaceTec Server version. 
  2. The Operating System of the Server.
  3. A screenshot of the Server's Specs.