Reference Information › CA AppLogic Support Knowledge Base › Overview of Support Knowledge Base › Working with Controller Impex Volume › How to Correct BFC Status Initializing Errors in the BFC

How to Correct BFC Status Initializing Errors in the BFC

Symptom

In the BFC 3.5.2 version, it is possible that if a customer installs the BFC and then reboots it without having configured the networks, the BFC service will not start.

The errors displayed at BFC startup,if started manually, will be the following:

service bfc start
starting bfc
bfc status: initializing
bfc status: initializing
bfc failed to start
Failure information:
bfc/system.exceeded_restarts
{0} failed restarts within {1} seconds
[5, 300]
If setting the bfc startup script in debug, it will hang around:
...
bfc status: started application 'encryption' (27 of 45)
bfc status: started application 'stream_of_consciousness' (28 of 45)
bfc status: starting application 'image_manager' (29 of 45)

Solution

This is typically observed on BFC node reboot where the BFC is not configured with backbone network and no macs added to the mac list in “manual configuration”. To sort out the problem, try restarting the BFC after deleting the file ldap_mnesia_restore.sync from (/opt/bfc/setup/ldap_files).

This behaviour has been corrected in later versions of the BFC, so it should not be observed in version 3.7 and later