Problem Node Manager fails to start after SP upgrade and SETCAP has been run

Resolution

After the Gateway has been upgraded it may lose the CAP_NET_BIND capability for the vshell. This can be restored by running:

/usr/sbin/setcap 'cap_net_bind_service=+ep cap_sys_rawio+ep' /opt/apigateway/platform/bin/vshell

If, after these actions, there is a problem starting the Node Manager (trace log shows JNI problem) then there may be a problem in the JVM settings.

Specifically the java.library.path (used by java to get to find native libraries) needed to be reset. It was causing a problem when trying to start the Node Manager. We reset these with the following command:

sed -i -e '/<JVMSettings/a\\n <!-- Set by appliance rpm to allow correct library load after setting CAP_NET_BIND_SERVICE on vshell -->\n <VMArg name="-Djava.library.path=$VDISTDIR/$DISTRIBUTION/jre/lib/amd64/server:$VDISTDIR/$DISTRIBUTION/jre/lib/amd64:$VDISTDIR/$DISTRIBUTION/lib/engines:$VDISTDIR/ext/$DISTRIBUTION/lib:$VDISTDIR/ext/lib:$VDISTDIR/$DISTRIBUTION/jre/lib:system/lib:$VDISTDIR/$DISTRIBUTION/lib"/>' /opt/apiserver/system/conf/jvm.xml