VMware Cloud Community
Erik_Gross
Contributor
Contributor

vCenter Ops Manager fails - Error 'Cannot initialize CIQ database'

I first had this error after attempting to update from 5.0.0 to 5.0.1.

I've since tried powering off and deleting the vApp from disk and redeploying from the OVA but get the same error.  The Analytics VM loads and boots with no issues, but the UI VM fails when starting the 'vami-sfcbd'.  Actual messages are:

Starting vami-sfcbd: done.
Checking vami-sfcbd status: ^........... failed, restarting vami-sfcbd.
Shutting down vami-sfcbd: failed.
Starting vami-sfcbd: done.
Checking vami-sfcbd status: ............ failed, restarting vami-sfcbd.
Shutting down vami-sfcbd: failed.
Starting vami-sfcbd: done.
Checking vami-sfcbd status: ............ failed, restarting vami-sfcbd.
Shutting down vami-sfcbd: failed.
Starting vami-sfcbd: done.
Checking vami-sfcbd status: ........

This repeats about 15 times and finally fails, at which time the boot completes, but the console displays:

vCOPs-error.jpg

Any help is greatly appreciated.

Erik G.

Reply
0 Kudos
6 Replies
Erik_Gross
Contributor
Contributor

I have confirmed that both VMs are able to resolve each other (internal and external interfaces) as well as the vCenter server.

I've also confirmed both have only about 1% usage on the /data volume.

EG

Reply
0 Kudos
gradinka
VMware Employee
VMware Employee

strange, never seen that issue :smileyconfused:

when you loging with "ádmin", if you can generate a log bundle (vcops-admin diag-bundle), post it for here to look at it...

alternatively, look at this thread for some hints/logs to check:

http://communities.vmware.com/message/1713448

Reply
0 Kudos
agrandville
VMware Employee
VMware Employee

I have a customer that is experiencing the same behavior. Did we ever get to the bottom of this ?

Reply
0 Kudos
Erik_Gross
Contributor
Contributor

I did finally figure this out.

It turns out our problem was due to the fact that we did not have a DNS on the same subnet as we had defined for the vAPP IP addresses (in the IP Pool).

Once we had the DNS on the same subnet, all the problems went away.  I reported this up through our account reps and the issue was confirmed.

Hope this helps.

Erik G.

(Marking this as 'answered' even though i found the answer myself).

Reply
0 Kudos
agrandville
VMware Employee
VMware Employee

Thanks Erik !

Al-

Reply
0 Kudos
Jakobwill
Enthusiast
Enthusiast

We have the exact same error after upgrading 5.0.1 to 5.0.2.

But also when trying to clean install vCops 5.02 from OVF.

We have DNS and resolve on same subnet, but are there other strange stuff here we dont know about?

Reply
0 Kudos