can you attach the bldeploy and targetmanager logs ?
yeah - it's strange, so here:
04/29/17 01:59:51.162 DEBUG bldeploy - Updating Package Tracking 04/29/17 01:59:51.162 INFO bldeploy - Registering DDA plugin 04/29/17 01:59:51.162 INFO bldeploy - Registered DDA plugin
it should be updating the 'blpackage tracking database' that's on the rscd and then finish out the deploy. but for some reason it's dying right there. is it possible something else was running against the box at the same time that killed the bldeploy ?
No. The deploy was unique execution on server.
I have the same problem, only on Oracle Solaris SPARC box. Never on Windows or Linux.
great, where are the bldeploy logs ?
Same problem trying to patch a RHEL server.
Patch Remediation BLDeploy Logs attached.
something went wrong here:
07/18/19 13:08:26.545 INFO bldeploy - [remediate-2203502-Analisis_repezca2019-05-14 10-37-44-539+02002019-07-18 13-06-42-630+0200] Executing command: "mkdir -p blrepos/repo ; tar -C blrepos/repo -xzf 3750773.1/repodata.tar.gz"
07/18/19 13:08:27.876 DEBUG bldeploy - [remediate-2203502-Analisis_repezca2019-05-14 10-37-44-539+02002019-07-18 13-06-42-630+0200] Apply for assetName 'CUSTOMSOFTWARE' returned '1'
in this step it's extracting the catalog metadata to the staging directory on the target before starting the redhat patch install. it's not clear where the error came from though.