On Thu, Oct 13, 2016 at 11:28 AM, Martin Polednik wrote:
> On 13/10/16 09:01 +0300, Dan Kenigsberg wrote:
>>
>> On Thu, Oct 13, 2016 at 11:52:17AM +1100, David Pinkerton wrote:
>>>
>>> Nir,
>>>
>>> Looks like its crashing on the dmidecode system call.
>>>
>>> I've attached
On Thu, Oct 13, 2016 at 12:29 PM, David Pinkerton wrote:
> Good News.
>
> I installed the fedora 24 version of python-dmidecode and was able to
> successfully add the host to my cluster...
>
> Thanks you to everyone who looked at this. I owe you a beer or at least
> some
Good News.
I installed the fedora 24 version of python-dmidecode and was able to
successfully add the host to my cluster...
Thanks you to everyone who looked at this. I owe you a beer or at least
some reward points :-)
On Thu, Oct 13, 2016 at 7:28 PM, Martin Polednik
python-dmidecode-3.10.13-11.el7.x86_64
I cut and pasted your python code into a file and ran python file no
workie
I did find the attached dmidump.py on github. It segfaults after printing
bios on line 64.
Also attached is a dump from the AMIDEDOS utility.
Happy to do whatever is
On 13/10/16 09:01 +0300, Dan Kenigsberg wrote:
On Thu, Oct 13, 2016 at 11:52:17AM +1100, David Pinkerton wrote:
Nir,
Looks like its crashing on the dmidecode system call.
I've attached the output from gbd as well as a dmidecode text dump,
dmidecode binary dump and each keywords run
On Thu, Oct 13, 2016 at 11:52:17AM +1100, David Pinkerton wrote:
> Nir,
>
> Looks like its crashing on the dmidecode system call.
>
> I've attached the output from gbd as well as a dmidecode text dump,
> dmidecode binary dump and each keywords run individually.
>
> >From the keywords it look
Nir,
Looks like its crashing on the dmidecode system call.
I've attached the output from gbd as well as a dmidecode text dump,
dmidecode binary dump and each keywords run individually.
>From the keywords it look like my dmi info is corrupted. I have download a
AMI dmi editor but this only
On Tue, Oct 11, 2016 at 11:59 PM, David Pinkerton wrote:
> Logs attached
According vdsm.log and supervdsm.log, each time vdsm try to call
getHardwareInfo,
supervdsm show the start of the call and then it show no logs for 10 seconds,
and than we see the startup message.
So
On Mon, Oct 10, 2016 at 5:05 AM, Charles Kozler
wrote:
> Possibly stupid question but are you doing this on a base empty
> centos/rhel 7?
>
> On Oct 9, 2016 9:48 PM, "David Pinkerton" wrote:
>
>>
>> I've spent the weekend trying to get to the bottom of
Possibly stupid question but are you doing this on a base empty centos/rhel
7?
On Oct 9, 2016 9:48 PM, "David Pinkerton" wrote:
>
> I've spent the weekend trying to get to the bottom of this issue.
>
> Adding a Host fails:
>
> From RHVM
>
>
> VDSM rhv1 command failed:
I've spent the weekend trying to get to the bottom of this issue.
Adding a Host fails:
>From RHVM
VDSM rhv1 command failed: Connection reset by peer
Could not get hardware information for host rhv1
VDSM rhv1 command failed: Failed to read hardware information
Host rhv1 installed
Network
11 matches
Mail list logo