Reference Information › CA AppLogic Support Knowledge Base › Overview of Support Knowledge Base › How to Replace BFC and Controller Server SSL Certificate › Node will not Deploy AppLogic After Initial Utility Deployment

Node will not Deploy AppLogic After Initial Utility Deployment

Node will not Deploy AppLogic After Initial Utility Deployment

Sometimes, especially if a node has been redeployed multiple times or a grid has been destroyed and recreated several times, problems may arise in that a certain node will boot from the utility image, but AppLogic deployment will not go through. Typically the following messages will be reported in the node console:

  EXECUTING INSTRUCTIONS...
 etcrcS.dS7Orun: line 6: ./run: Permission denied
 BFC utility image processing is complete. Console login is disabled.
 udevd event[1000]: wait_for_sysfs: waiting for  /sys/devices/pciOOOO:OO/OOOO:
 OO:
 1f .Z. hostOtargetO:O:Oioerr_cnt  failed
 udevd-event[99?]: wait_for_sysfs: waiting for  sysdevicespciOOOO:OOOOOO:OO:1
 f.2,hostl/targetl:O:O,ioerrcnt  failed
 udevd event[1005]: wait_for_sysfs: waiting for  ,sys,devices,pciOOOO:OO,OOOO:
 OO:
 1f .Z. hostZtargetZ:O:Oioerr_cnt  failed
 [ 33.62331?] sd 0:0:0:0: Attached scsi generic sg  type 0

Resolution

That is caused by an incomplete cleanup of the old configuration in the BFC. The BFC caches the MAC addresses of the servers having been deployed and, in particular, it keeps a copy under the /boot_command/config directory. Therein you will find one file with the server's MAC address name.

Just delete that file and retry deployment.