Out of memory
If you see the following error, it might be a sign that your environment needs more memory. Typically >1GB is required to build Plaid.
collect2: fatal error: ld terminated with signal 9 [Killed] compilation terminated. CMakeFiles/oadrsd.dir/build.make:5892: recipe for target 'liboadrsd.so' failed make: *** [liboadrsd.so] Error 1 make: *** Deleting file 'liboadrsd.so' CMakeFiles/Makefile2:257: recipe for target 'CMakeFiles/oadrsd.dir/all' failed make: *** [CMakeFiles/oadrsd.dir/all] Error 2 Makefile:127: recipe for target 'all' failed make: *** [all] Error 2
VEN Registration Issues
This is a list of common issues you might find when connecting to a VTN.
SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol
The VTN might not support your version of SSL. This is common for Honeywell VTNs. In the config file, replace the
tlsVersion with an earlier version, such as
TLSv1_0, and replace
SSL Certification problem: Handshake failure
[ NOVA EXCEPTION ]: Error executing job (will retry): ven.registration: Registration failed (will retry): error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
This can also be due to the wrong version of SSL. In this case, it may be that the VTN requires a later version of SSL. Change the fields
"cipherList": "AES128-SHA256:ECDHE-ECDSA-AES128-SHA256", "tlsVersion": "TLSv1_2".
SSL certificate problem: self signed certificate in certificate chain
This is an indication that the CA bundle isn't correct. Make sure the path in the config file is correctly configured. You might need to make sure you are using the production certificate
ven_cacerts_prod.pem, if the VTN requires it, even if you are using test certificates from Kyrio.
SSL certificate problem: could not load PEM client certification
[ NOVA EXCEPTION ]: Error executing job (will retry): ven.registration: Registration failed (will retry): could not load PEM client certificate, OpenSSL error error:02001002:system library:fopen:No such file or directory, (no key found, wrong pass phrase, or wrong file format?)
This is a common error, if the certpath or keypath are not correct. Make sure the files are properly formatted as described in connecting to a VTN and the paths to the files are correct. Remember the path should be relative to where the build happens.
404 / not found
Ensure that the VTN url is correct in the VEN config