Libvirt event for disk change is not being registered by DomainEventRegisterAny() - kvm

I am writing an application which would monitor the changes on the domain on the KVM hypervisor through libvirt events.
Recently I have upgraded my libvirt from 9.4 to 9.10 and I have this issue.
While de-registering for DomainEventDiskChangeCallback, I get a libvirt error saying
libvirtError: internal error domain event 2 not registered;
where 2 is the callbackid returned by virConnectDomainEventRegisterAny() for the disk change event type.
This error didn’t occur when I used libvirt 0.9.4-23.el6_2.6
Can you please enlighten me on the recent changes that has been made?
Also, is the diskchange event a part of the domains life cycle event?
Any help on this issue will be highly appreciated.
Thanks and regards,
Abhishek

There is nothing wrong in what you do.
This was a bug which is now fixed.
Diskchange is not a lifecycle event as it has nothing to do with the domain being started, killed, stopped, rebooted, etc.

Related

Hyper-v Machine shuts down unexpectedly, Hyper-V log shows an Error:"DM operation add for the virtual machine"

This cause me a big production problems, please help me.
one virtual machine shutted down unexpectly.
The Hype-v log shows:
DM operation add for the virtual machine 'XXXXName' failed with error: Unspecified error (0x80004005) (Virtual machine ID 7EDDD39A-F963-4FAA-8854-6179B7611AC3).
could it be possible if nobody touch the Hype-v and DM error happened??? please tell me how to fix this problem.
DM is "dynamic memory". Your virtual machine tried to add memory and failed. A human didn't trigger this, you've just run out of memory.
https://social.technet.microsoft.com/Forums/windowsserver/en-US/f60b2767-dbfc-41d0-8019-24039aab187d/dynamic-memory-issue-dm-add-fails-with-0x800705aa?forum=winserverhyperv
Edit: the reason it failed, the error code, is explained here. It's possible there was a permission problem trying to allocate more memory. But still, essentially, you ran out of memory.
https://appuals.com/solved-how-to-fix-error-0x80004005/

Distributed Tensorflow: The worker does not responded

I am running Tensorflow Distributed mode on AWS instances. PS is on one machine and each worker is on a different machine. I am running in the following problem:
tensorflow/core/distributed_runtime/master.cc:267] CreateSession still waiting for response from worker: /job:ps/replica:0/task:0
I found somebody already posts exactly the same problem that I face right now but his answer is not clear for me, Tensorflow distributed: CreateSession still waiting for response from worker: /job:ps/replica:0/task:0.
Can anybody suggest what might be the solution?
Now, after I solved my error, I will share my solution. It was not a bug in the TF code but one of two things that I tried solved my problem stated above. Because I am working on EC2 instances, the firewall prevents the connection between nodes. So, I made the rule to accept all the traffics to the instances. Second, I was using only IP-address:port-No in the command line. Instead, I wrote it like this, ec2-IP.compute-1.amazonaws.com:2222.

Unable to add apache Nifi in ambari?

I am trying to add Apache Nifi in ambari but continuously failing with error Error occured during stack advisor command invocation:
Unable to delete directory /var/run/ambari-server/stack-recommendations/1.
There is a similar thread with the same error in hortonworks community, I have tried everything mentioned in that thread but unable to fix it. My sandbox is installed in vmware workstation 12 player. I also tried to create and remove directory manually but it is failing with the error invalid argument. Created a thread for this error also on stackexchange. Please help!!!
Here is a link to Hortonworks forum thread. And it seems like sandbox is just broken:
This is due to a docker issue in this 2.5 sandbox build. It will be
fixed in next revision of the sandbox.
There are also some workarounds described (like use older HDP 2.4 or establishing own cluser based on the HDP 2.5 docker image)
Updated sandbox arrived: http://hortonworks.com/downloads
Trust me, active member of community see your posts in multiple locations. In a good, no Big Brother ways :) but cross-posting is an old as world ... Well, you got it.
Did you see a notice for this service in Ambari? Telling it's been deprecated? Same note in the github. There's a good reason for that, it's now been implemented properly by the dev team and with many more features. I.e. all the action is there now.
I think I replied a similar question, though not sure it was yours, take a look in HCC.

RDO unable to boot VM with disk size specified

I have packstack-allinone setup on my RHEL7.1 trial for Juno release.
I am facing problem while launching VM(for ex: cirros) with a disk size mentioned in flavor. If there is 0gb disk size then VM are getting launched but not for higher flavor sizes.
I also observe that when I do this, openstack-nova-compute service goes down which I observed when I checked using nova-manage service list with nova-compute being XXX making me restart the service everytime I try this scenario. The compute logs doesn't throw any error, it just gets stuck at "Creating image".
Is there any Filesystem issue which i missing to be configured? I am new to this, so please help.
PS: I run all commands with "root" user.
The problem was with esxi. Esxi needs to be 5.5v to support RHEL7x Since mine was 5.1v it only supported RHEL6x.
After upgrading esxi5.1 to 5.5v it worked fine.

Redis server not starting - Forked Process did not respond in a timely manner

Redis server which was working fine got stopped suddenly and the error is:
BeginForkOperation: system error caught. error code=0x00000000, message=Forked
Process did not respond in a timely manner.
Not able to figure out why it is happening, and also when I am restarting my machine then
if I start the redis-server it's working fine.
Please help me in this regard.
You should try updating your Redis version, the guys from MSOpenTech fixed a lot of bugs in the last months and this one looks related, at least the error message is identical: https://github.com/MSOpenTech/redis/issues/144