vdsm service won't start
I am currently evaluating Red Hat Enterprise Virtualization and have managed to set up the management server and the bare metal hypervisor. Now I'm trying to add a regular box running RHEL server 6.5 to the data center as a host. The add new host process starts fine and installs all the packages successfully. But after a certain time it fails saying network communication failure. From /var/log/ovirt-engine/engine.log I figured out this was caused by vdsmd service not restarting properly on the target. And indeed when I manually try to start the service at the host itself, it fails.
# service vdsmd status
VDS daemon is not running, and its watchdog is running
# service vdsmd start
vdsm: already running [ OK ]
vdsm start [ OK ]
# service vdsmd status
VDS daemon is not running, and its watchdog is running
The log has the following error:
Jul 8 16:34:46 respawn: slave '/usr/share/vdsm/vdsm --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave
Jul 8 16:34:47 python: vdsm user could not manage to run sudo operation: (stderr: ['sudo: sorry, you must have a tty to run sudo']). Verify sudoer rules configuration
I tried commenting out and removing the "Defaults requiretty" line in /etc/sudoers file, but I keep getting the same error.
As i'm evaluating RHEV, I am not entitled to Red Hat support and have to fix it myself.
Any ideas on what to do ?
linux rhel libvirtd rhev
edited Jul 9 '14 at 11:38
polym
6,77143158
asked Jul 8 '14 at 11:24
user1600936user1600936
2826
bumped to the homepage by Community♦ 3 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am currently evaluating Red Hat Enterprise Virtualization and have managed to set up the management server and the bare metal hypervisor. Now I'm trying to add a regular box running RHEL server 6.5 to the data center as a host. The add new host process starts fine and installs all the packages successfully. But after a certain time it fails saying network communication failure. From /var/log/ovirt-engine/engine.log I figured out this was caused by vdsmd service not restarting properly on the target. And indeed when I manually try to start the service at the host itself, it fails.
# service vdsmd status
VDS daemon is not running, and its watchdog is running
# service vdsmd start
vdsm: already running [ OK ]
vdsm start [ OK ]
# service vdsmd status
VDS daemon is not running, and its watchdog is running
The log has the following error:
Jul 8 16:34:46 respawn: slave '/usr/share/vdsm/vdsm --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave
Jul 8 16:34:47 python: vdsm user could not manage to run sudo operation: (stderr: ['sudo: sorry, you must have a tty to run sudo']). Verify sudoer rules configuration
I tried commenting out and removing the "Defaults requiretty" line in /etc/sudoers file, but I keep getting the same error.
As i'm evaluating RHEV, I am not entitled to Red Hat support and have to fix it myself.
Any ideas on what to do ?
linux rhel libvirtd rhev
edited Jul 9 '14 at 11:38
polym
6,77143158
asked Jul 8 '14 at 11:24
user1600936user1600936
2826
bumped to the homepage by Community♦ 3 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am currently evaluating Red Hat Enterprise Virtualization and have managed to set up the management server and the bare metal hypervisor. Now I'm trying to add a regular box running RHEL server 6.5 to the data center as a host. The add new host process starts fine and installs all the packages successfully. But after a certain time it fails saying network communication failure. From /var/log/ovirt-engine/engine.log I figured out this was caused by vdsmd service not restarting properly on the target. And indeed when I manually try to start the service at the host itself, it fails.
# service vdsmd status
VDS daemon is not running, and its watchdog is running
# service vdsmd start
vdsm: already running [ OK ]
vdsm start [ OK ]
# service vdsmd status
VDS daemon is not running, and its watchdog is running
The log has the following error:
Jul 8 16:34:46 respawn: slave '/usr/share/vdsm/vdsm --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave
Jul 8 16:34:47 python: vdsm user could not manage to run sudo operation: (stderr: ['sudo: sorry, you must have a tty to run sudo']). Verify sudoer rules configuration
I tried commenting out and removing the "Defaults requiretty" line in /etc/sudoers file, but I keep getting the same error.
As i'm evaluating RHEV, I am not entitled to Red Hat support and have to fix it myself.
Any ideas on what to do ?
linux rhel libvirtd rhev
edited Jul 9 '14 at 11:38
polym
6,77143158
asked Jul 8 '14 at 11:24
user1600936user1600936
2826
I am currently evaluating Red Hat Enterprise Virtualization and have managed to set up the management server and the bare metal hypervisor. Now I'm trying to add a regular box running RHEL server 6.5 to the data center as a host. The add new host process starts fine and installs all the packages successfully. But after a certain time it fails saying network communication failure. From /var/log/ovirt-engine/engine.log I figured out this was caused by vdsmd service not restarting properly on the target. And indeed when I manually try to start the service at the host itself, it fails.
# service vdsmd status
VDS daemon is not running, and its watchdog is running
# service vdsmd start
vdsm: already running [ OK ]
vdsm start [ OK ]
# service vdsmd status
VDS daemon is not running, and its watchdog is running
The log has the following error:
Jul 8 16:34:46 respawn: slave '/usr/share/vdsm/vdsm --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave
Jul 8 16:34:47 python: vdsm user could not manage to run sudo operation: (stderr: ['sudo: sorry, you must have a tty to run sudo']). Verify sudoer rules configuration
I tried commenting out and removing the "Defaults requiretty" line in /etc/sudoers file, but I keep getting the same error.
As i'm evaluating RHEV, I am not entitled to Red Hat support and have to fix it myself.
Any ideas on what to do ?
linux rhel libvirtd rhev
linux rhel libvirtd rhev
edited Jul 9 '14 at 11:38
polym
6,77143158
asked Jul 8 '14 at 11:24
user1600936user1600936
2826
edited Jul 9 '14 at 11:38
polym
6,77143158
asked Jul 8 '14 at 11:24
user1600936user1600936
2826
edited Jul 9 '14 at 11:38
polym
6,77143158
edited Jul 9 '14 at 11:38
polym
6,77143158
edited Jul 9 '14 at 11:38
polym
6,77143158
6,77143158
asked Jul 8 '14 at 11:24
user1600936user1600936
2826
asked Jul 8 '14 at 11:24
user1600936user1600936
2826
asked Jul 8 '14 at 11:24
user1600936user1600936
2826
2826
bumped to the homepage by Community♦ 3 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 3 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Under evaluation, there is no support, but what you describe sounds like a bug. I would ask this question in the RHEV user groups at access.redhat.com, you will probably get response from support and engineering both.
answered May 26 '15 at 0:38
dyasnydyasny
94248
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f141319%2fvdsm-service-wont-start%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Under evaluation, there is no support, but what you describe sounds like a bug. I would ask this question in the RHEV user groups at access.redhat.com, you will probably get response from support and engineering both.
answered May 26 '15 at 0:38
dyasnydyasny
94248
add a comment |
Under evaluation, there is no support, but what you describe sounds like a bug. I would ask this question in the RHEV user groups at access.redhat.com, you will probably get response from support and engineering both.
answered May 26 '15 at 0:38
dyasnydyasny
94248
add a comment |
Under evaluation, there is no support, but what you describe sounds like a bug. I would ask this question in the RHEV user groups at access.redhat.com, you will probably get response from support and engineering both.
answered May 26 '15 at 0:38
dyasnydyasny
94248
Under evaluation, there is no support, but what you describe sounds like a bug. I would ask this question in the RHEV user groups at access.redhat.com, you will probably get response from support and engineering both.
answered May 26 '15 at 0:38
dyasnydyasny
94248
answered May 26 '15 at 0:38
dyasnydyasny
94248
answered May 26 '15 at 0:38
dyasnydyasny
94248
answered May 26 '15 at 0:38
dyasnydyasny
94248
94248
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f141319%2fvdsm-service-wont-start%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
