The data_engine was green but had no port nor a pid.
We then tried to run the UIM Server reinstall but the data_engine failed again.
We were able to redeploy it from the local archive or upgrade and overwrite it, and as long as we left it alone after manually installing it, it maintained its state and port and PID. We tried t workaround the issue but to no avail so we proceeded to simply manually deploy all of the other probes that belong on the UIM Server (Primary Hub).
The wasp uimhome page and installers needed to be updated so we also took care of that manually.
We are not sure why the data_engine just arbitrarily stopped and threw the nimEnd message in the log:
Jul 3 10:28:59:868 [13848] 0 de: ######################## STOP DATA ENGINE #########################
Jul 3 10:28:59:868 [13848] 2 de: nimEnd
Redeploy the data_engine from the Primary hub local archive or Right-click to upgrade the version and overwrite it.
As long as we left the data_engine alone after manually installing it, it maintained its state and port and PID.
We tried to workaround the data_engine issue by rerunning the UIM server installed and tried other means but to no avail so we proceeded to simply manually deploy all of the other probes that belong on the UIM Server (Primary Hub).
This successfully worked around the data_engine issue.