APAC
The next table lists all error codes related to the Navajo and Apache integration.
| Major | Minor | Message | Details |
|---|---|---|---|
| APAC | 0001 | httpd has not been running by Navajo. | Contact support. |
| 0002 | Apache not ready yet. | Contact support. | |
| 0003 | Apache Monitor failed. | See the log for further details. Contact support. | |
| 0004 | Apache Monitor failed (unknown exception). | Contact support. | |
| 0005 | An Apache httpd error occurred. | See the log for further details. | |
| 0006 | child-exit of the service failed. | See the log for further details. Contact support. | |
| 0007 | child-exit of the service failed (unknown exception). | Contact support. | |
| 0008 | child-exit of the httpd process failed. | See the log for further details. Contact support. | |
| 0009 | child-exit of the httpd process failed (unknown exception). | Contact support. | |
| 0010 | navajo_pre_connection failed. | See the log for further details. Contact support. | |
| 0011 | navajo_pre_connection failed (unknown exception). | Contact support. | |
| 0012 | navajo_cleanup_connection failed. | See the log for further details. Contact support. | |
| 0013 | navajocleanup connection failed (unknown exception). | Contact support. | |
| 0014 | Bad request. | The frontend sent an invalid request. Check the log for further details. | |
| 0015 | navajo_handler failed. | See the log for further details. Contact support. | |
| 0016 | navajo_handler failed (unknown exception). | Contact support. | |
| 0017 | The server configuration and the Navajo configuration are not consistent: Secure <Connector> for insecure port configured. | Check your configuration (navajo.xml). | |
| 0018 | The server configuration and the Navajo configuration are not consistent: No insecure <Connector> for port found. | Check your configuration (navajo.xml). | |
| 0019 | An SSL error occurred. | See the log for further details. | |
| 0020 | An HSM error occurred. | See the log for further details. | |
| 0028 | StatusServlet: requestImpl or responseImp not found. | Contact support. | |
| 0029 | StatusServlet: Unexpected class for requestImpl or responseImp. | Contact support. | |
| 0030 | StatusServlet: Unsupported requestAdapter/responseAdapter. | Contact support. | |
| 0031 | An Apache mutex error occurred. | See the log for further details. | |
| 0032 | Illegal server name. | See the log for further details. Contact support. | |
| 0033 | No in headers found. | A request without headers has been received. Contact support. | |
| 0034 | Invalid header field. | A request with an invalid header name has been received. Contact support. | |
| 0035 | Duplicated header field. | A request with a duplicated header name has been received. Contact support. | |
| 0036 | Could not open the PKCS#11 library. | The PKCS#11 library could not be loaded. Check the log for more details. Possible causes: file permission, name miss-spelled, etc. | |
| 0037 | Could not find the function C_GetFunctionList in the PKCS#11 library. | The PKCS#11 library does not contain the function C_GetFunctionList. Make sure that the library is correct. | |
| 0038 | C_GetFunctionList failed in the PKCS#11 library. | The PKCS#11 library returned an error while calling the function C_GetFunctionList. Check the log of the PKCS#11 library for more information. | |
| 0039 | C_Initialize failed in the PKCS#11 library. | The PKCS#11 library returned an error while calling C_Initialize. Check the log of the PKCS#11 library for more information. | |
| 0040 | C_GetSlotList failed in the PKCS#11 library. | The PKCS#11 library returned an error while calling C_GetSlotList. Check the log of the PKCS#11 library for more information. | |
| 0041 | C_GetSlotList did not return any slot. The HSM may not be ready yet. | The PKCS#11 did not return any slot while calling C_GetSlotList. Check the log of the PKCS#11 library for more information. | |
| 0042 | The (forked) passphrase not stored. | Contact support. | |
| 0043 | Error reading user input. | Contact support. | |
| 0044 | Store session failed. | Check the log for further details. Contact support. | |
| 0045 | Store session failed, fatal. | Contact support. | |
| 0046 | Retrieve session failed. | Check the log for further details. Contact support. | |
| 0047 | Retrieve session failed, fatal. | Contact support. | |
| 0048 | Remove session failed. | Check the log for further details. Contact support. | |
| 0049 | Remove session failed, fatal. | Contact support. | |
| 0050 | Allocating BIO_s_mem() failed. | Contact support. | |
| 0051 | Store session failed for a host. | Check the log for further details. Contact support. | |
| 0052 | An Apache error occurred. | Check the log (navajo.log, apache-log) for more information. | |
| 0053 | Apache configuration generation is disabled. | Note that there is no support when the attribute generateCarrierConfig is set to "false". This attribute is part of the nevisProxy server configuration. | |
| 0054 | An apache emergency error occurred | Most probably the proxy could not be started and will not work correctly. Check the log file for further details. | |
| 0055 | An apache alert occurred | Most probably the proxy could not be started and will not work correctly. Check the log file for further details. | |
| 0056 | An apache critical error occurred | Most probably the proxy will not work correctly. Check the log file for further details. | |
| 0057 | panic: mod_navajo init failed | Most probably the proxy will not work correctly. Check the log file for further details. | |
| 0058 | panic: mod_navajo init failed for some unknown reason | Most probably the proxy will not work correctly. Check the log file for further details. | |
| 0059 | panic: child_init init failed | Most probably the proxy will not work correctly. Check the log file for further details. | |
| 0060 | panic: child_init init failed for some unknown reason | Most probably the proxy will not work correctly. Check the log file for further details. | |
| 0061 | panic: setup_modssl failed | Most probably the proxy will not work correctly. Check the log file for further details. | |
| 0062 | panic: setup_modssl failed for some unknown reason | Most probably the proxy will not work correctly. Check the log file for further details. |