You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Author Name: Christian Wehrlin (Christian Wehrlin)
Original Redmine Issue: 5199, https://dev.opennebula.org/issues/5199
Original Date: 2017-06-22
Original Assignee: Vlastimil Holer
If you have a KVM-Hypervisor in your setup, that has reached, or is about to reach the ulimit, OpenNebula will probably fail trying to do the run_probes, but instead of throwing an error, it will simply report that the machine was successfully monitored.
While trying to open a remote shell manually, you'll get the Error:
Of course, the quick fix is to increase the ulimits on the Hypervisor to more suitable values, nonetheless, it should be expected for OpenNebula to report an issue when trying to remote-execute run_probes
The text was updated successfully, but these errors were encountered:
Author Name: Christian Wehrlin (Christian Wehrlin)
Original Redmine Issue: 5199, https://dev.opennebula.org/issues/5199
Original Date: 2017-06-22
Original Assignee: Vlastimil Holer
If you have a KVM-Hypervisor in your setup, that has reached, or is about to reach the ulimit, OpenNebula will probably fail trying to do the run_probes, but instead of throwing an error, it will simply report that the machine was successfully monitored.
While trying to open a remote shell manually, you'll get the Error:
@resource temporarily unavailable@
But in the oned.log, all you just see is basically something like
@Wed Jun 21 12:36:54 2017 [Z0][InM][D]: Host node18.blafasel (23) successfully monitored.@
Of course, the quick fix is to increase the ulimits on the Hypervisor to more suitable values, nonetheless, it should be expected for OpenNebula to report an issue when trying to remote-execute run_probes
The text was updated successfully, but these errors were encountered: