A Robinson wrote: > doing rhn-profile-sync doesn't solve the problem unfortunately. > For information, I'm using spacewalk version 0.6 on 32bit Centos 5.3. > > Any suggestions what to do next? > Hrm. Lets do this. Connect to the Database:
# sqlplus spacewalk/spacew...@xe And then query the rhnServerDmi table: sql> select * from rhnServerDmi where server_id = 8675309; replacing 8675309 with the server's id. Do this on a 'bad' system and a 'good' system and see if there's any difference. -Justin > Thanks > > A Robinson > > On Thu, Nov 12, 2009 at 1:10 PM, Justin Sherrill <[email protected]> wrote: >> A Robinson wrote: >>> They're real Dell servers. Really odd thing is some are identical >>> hardware, -- in one case the difference being one is used as a >>> spacewalk proxy and one isn't. Since the information gets into >>> spacewalk (and is shown on the hardware tab) I was suspicious it's a >>> spacewalk problem. >> This is really odd. Does running 'rhn-profile-sync' on any of the >> clients fix the issue? >> >> -Justin >> >> >>>> On 11/11/09 4:02 PM, Colin Coe wrote: >>>>> Are they Xen para-virtualised guests? >>>> This actually happens for me as well, using RHN Satellite 5.3. I have >>>> 2x HP dc5850 systems that have their DMI Info tab fully populated in the >>>> Satellite UI, but system.getDmi returns empty, just like the OP. >>>> However, I also have some Dell systems that system.getDmi works fine for. >>>> >>>> I haven't tried with Spacewalk yet, but sounds like it is similar. >>>> >>>> Vinny >>> __ > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
