From: "Jonathan Horne" <jhorne(a)skopos.us>
To: "Eli Mesika" <emesika(a)redhat.com>
Sent: Tuesday, November 20, 2012 3:37:00 PM
Subject: Re: [Users] power management issues
Well, as a test, I enabled telnet and it started working.
Then, I removed it, added it back, and now it just reboots over and
over
with unable to communicate errors.
Also, before I enabled telnet, it was refusing to use SSH (SSH is the
preferred method by default on a drac5). The secure tick box on the
power
management page was not "sticking" when I clicked ok.
On 11/19/12 4:06 PM, "Eli Mesika" <emesika(a)redhat.com> wrote:
>
>
>----- Original Message -----
>> From: "Jonathan Horne" <jhorne(a)skopos.us>
>> To: users(a)ovirt.org
>> Sent: Monday, November 19, 2012 4:54:04 PM
>> Subject: Re: [Users] power management issues
>>
>> Del 2950s are equipped with DRAC5, so I set it for drac5 in the
>> web
>> UI.
>
>Looking at the fence_drac5 man page , I see that he has a
>login_timeout
>option :
>from the man page:
>**************************
>login_timeout
> Wait X seconds for cmd prompt after login (Default
> Value: 5)
>**************************
>
>As you see , the default is 5 seconds , so I really suspect this may
>be a
>timeout problem since all the authentication data is valid.
>Please try to put in the options field for Power Management :
>login_timeout=30 and check if the problem is resolved.
>
>
>>
>>
>>
>>
>> On 11/19/12 8:51 AM, "Eli Mesika" <emesika(a)redhat.com> wrote:
>>
>> >
>> >
>> >----- Original Message -----
>> >> From: "Jonathan Horne" <jhorne(a)skopos.us>
>> >> To: users(a)ovirt.org
>> >> Sent: Monday, November 19, 2012 4:04:08 PM
>> >> Subject: [Users] power management issues
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> I am gearing up to deploy this to our production environment
>> >> soon.
>> >> I
>> >> am not using the servers that will be the production
>> >> deployment,
>> >> but
>> >> they are vaguely similar. My 3 test machines are 3 Dell 2950s.
>> >>
>> >>
>> >> I have done several builds and then tear down the whole thing
>> >> and
>> >> start over to ensure that I understand the whole process.
>> >> Random
>> >> builds, I get power management working,
>> >
>> >Jonathan, which Power Management agent are you using (i.e. apc,
>> >rsa
>> >...)
>> >
>> > and sometimes I get "power
>> >> management test failed unable to log into fencing device"
>> >
>> >Since this message is returned from vdsm , ccing danken
>> >
>> >safe to
>> >> say I am using identical PM settings from build to build. my
>> >> ovirt
>> >> manager system is running fence-agents-3.1.10-1.fc17.x86_64
>> >> which
>> >> appears to be the latest, is there some other piece I might be
>> >> missing that completes this functionality?
>> >>
>> >>
>> >> Thanks,
>> >> jonathan
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> This is a PRIVATE message. If you are not the intended
>> >> recipient,
>> >> please delete without copying and kindly advise us by e-mail of
>> >> the
>> >> mistake in delivery. NOTE: Regardless of content, this e-mail
>> >> shall
>> >> not operate to bind SKOPOS to any order or other contract
>> >> unless
>> >> pursuant to explicit written agreement or government initiative
>> >> expressly permitting the use of e-mail for such purpose.
>> >> _______________________________________________
>> >> Users mailing list
>> >> Users(a)ovirt.org
>> >>
http://lists.ovirt.org/mailman/listinfo/users
>> >>
>>
>>
>> ________________________________
>> This is a PRIVATE message. If you are not the intended recipient,
>> please delete without copying and kindly advise us by e-mail of
>> the
>> mistake in delivery. NOTE: Regardless of content, this e-mail
>> shall
>> not operate to bind SKOPOS to any order or other contract unless
>> pursuant to explicit written agreement or government initiative
>> expressly permitting the use of e-mail for such purpose.
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>>
________________________________
This is a PRIVATE message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the
mistake in delivery. NOTE: Regardless of content, this e-mail shall
not operate to bind SKOPOS to any order or other contract unless
pursuant to explicit written agreement or government initiative
expressly permitting the use of e-mail for such purpose.