Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: jjcuk on December 14, 2006, 11:43:24 AM
-
Just installed phpsysinfo and have just realised only 1 processor showing
[root@deepblack ~]# uname -a shows
Linux deepblack 2.6.9-34.ELsmp #1 SMP Wed Mar 8 00:27:03 CST 2006 i686 i686 i386 GNU/Linux
which I believe is the correct kernal for multi processor
[root@deepblack ~]# cat /proc/cpuinfo shows
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 7
model name : Pentium III (Katmai)
stepping : 3
cpu MHz : 550.049
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1101.09
running sme server 7 Final with latest updates
I have SME server 7 running on 2 servers of the same spec and both show the same results .
Compaq ProLiant 6400R's
specs here
http://h18000.www1.hp.com/products/servers/proliant6400R/
both processors showed up in SME server 6 ?
any ideas ?
-
Time to update? (YUM)
[root@teri httpd.conf]# uname -a
Linux teri 2.6.9-42.0.2.ELsmp #1 SMP Wed Aug 23 00:17:26 CDT 2006 i686 i686 i386 GNU/Linux
Processor 0 and 1 show here.
-
ok what am I doing wrong
Setting up Update Process
Setting up repositories
smeaddons 100% |=========================| 951 B 00:00
smeos 100% |=========================| 951 B 00:00
smeupdates 100% |=========================| 951 B 00:00
Reading repository metadata in from local files
No Packages marked for Update/Obsoletion
================================================================
No new rpms were installed. No additional commands are required.
================================================================
-
When YUM works it works well.
I haven't worked out why YUM doesn't always work;~/
But I'm certainly glad it does things properly when it does work.
I'll need to step aside to allow others more au fait with YUM...
Search for YUM in the forum threads, you'll find there are others
equally mystified and relieved;~)
-
well thanks for response anyway, it could easily be something silly I am doing I shall go back and re-read through forums
thanks
-
Failing that do what I then do, hit the mirrors and manually download
the new stuff into a spare directory and then yum localinstall * it all.
Seems a bit quicker that way. FWIW running the htop utility will also
show you (both) processors and what they are doing.
-
ran a yum clean all then yum update and that has given me some updates
[root@shadow ~]# uname -a then gave me
Linux shadow 2.6.9-42.0.2.ELsmp #1 SMP Wed Aug 23 00:17:26 CDT 2006 i686 i686 i386 GNU/Linux
however after a reboot i am back to
[root@shadow ~]# uname -a
Linux shadow 2.6.9-34.ELsmp #1 SMP Wed Mar 8 00:27:03 CST 2006 i686 i686 i386 GNU/Linux
-
Ah! VERY glibly... there's an update bug (possibly/allegedly).
During the reboot stop the flow at the white screen penguin
by hitting a key, manually select your kernel, continue.
The wrong kernel selection issue didn't happen again
for me after that.
See also: http://bugs.contribs.org/show_bug.cgi?id=1930
-
yes I was reading about that bug earlier
and have been manually selecting the sme ELsmp kernel which I believe is correct
for dual processor no?
-
(English language syntax ambiguous)
For my dual Xeon processors I select the smp kernel.
-
mm
well the 4 choices are
centos (2.6.9-42.0.2 ELsmp)
centos (2.6.9-42.0.2 EL)
SME server (2.6.9-34.ELsmp)
SME server (2.6.9-34.EL)
so I assume you are using centos (2.6.9-42.0.2 ELsmp) and I have been using SME server (2.6.9-34.ELsmp), however I just switched to centos (2.6.9-42.0.2 ELsmp) and the results are the same
? :shock:
-
I'm done now, the above worked for me earlier.
Recommend you join that bugzilla thread,
you'll tap into the project leaders;~)
-
yep ill have a look there thanks again
-
ah well
got a cant fix wont fix probably a kernal issue so looks like I will move back to sme 6
quote
If you are running the smp kernel and it isn't detecting both processors then
it is either going to be a hardware issue or a kernel issue. Neither one of
which we can fix. I'm closing this wontfix.
should be labeled cantfix not wont :cry:
-
Time to go shopping;~)
-
got a cant fix wont fix probably a kernal issue so looks like I will move back to sme 6
I doubt even RedHat would be interested in fixing this issue as you are using very old hardware, thats why in sme 6 it would work fine because you are using 2.4 kernel there, in sme 7 your using 2.6 kernel so the 2.6 kernel is for newer even though it may support P3 1GB or more...
-
got a cant fix wont fix probably a kernal issue so looks like I will move back to sme 6
Try installing CentOS 4.3 . SME7 is based on 4.3. Whatever works with C4.3 *should* work with SME7 .
Plus you can then ask the question on the CentOS forums.
www.centos.org
EDIT: I see you have already been there.
Bug 001619 (http://bugs.centos.org/view.php?id=1619)
-
yep already asked in the centos forums and am currently downloading the centos livecd 4.4
also contacted HP the proliant servers have support matrix's going back to red hat 6 so maybe some feedback from their will help.
Byte yes they are a bit old but still more than powerful enough for my needs
so I will persevere with them.
thanks all for pointers will update this thread with any relevant information I may get
Jim
-
ok all
Have finally solved this,
after trying sme 6.5, sme 6, centos 4.4 , red hat 7.3 mandrake 10 and debian sarge it slowly dawned on me it had to be a hardware configuration problem.
I assumed as the bios detected both processors on boot Linux should to,
However it seems the server bios needs to be set up to specifically enable linux, I had to do a system erase and re-install with smartstart 5.5 software.
after trawling the net for a week I found this gem hidden away on a free bsd forum
Here is the link and details that aided me for future reference
---------------------------
link http://lists.freebsd.org/pipermail/freebsd-current/2005-April/049371.html
---------------------------
On 04/26/05 19:50, Matthew Sullivan wrote:
> Maxime Henrion wrote:
>> Yeah, I've seen DL380 boxes that needed "Linux" as the OS type or the
>> BIOS wouldn't generate an MPTable with both CPUs.
>
> Apologies for any wasted time....
>
> This was the answer....
>
> In detail, this morning I went back into the Compaq BIOS configuration
> tool, and the OS's settable were (amongst others):
>
> OTHER
> UNIX
>
> I had set to 'UNIX'.... I changed to 'OTHER' rebooted and .. still the
> same.
>
> There was no mention of 'LINUX' ... frustrated (and sure I saw "LINUX"
> in the config previously) I did the following...
>
> 1/. Powered Down
> 2/ Undocked all SCSI drives (just popped them out of the connectors)
> 3/ Booted the Config utility
> 4/ Selected 'Erase System'
> 5/ Power cycled (as instructed)
> 6/ Booted back into the 'Smartstart' config utility.
> 7/ Followed the 'Manual Configuration and OS install'
> 8/ Selected "LINUX" (which was now on this menu.
> 9/ Went to the Smart Array Util, and exited immediately, which caused a
> spontaneous reboot.
> 10/ Powered Down
> 11/ Docked all the drives.
> 12/ Powered up, and booted back into the Smart Start util.
> 13/ Noticed the RAID 5 array and config was self configured by the
> controller.
> 14/ Checked all settings in the Configutil - noticed "LINUX" was still
> displayed as the OS type.
> 15/ Checked the Array config (very impressed that it worked out the
> config itself)
> 16/ Exited Util (no save, none necessary).
> 17/ Power cycled.
> 18/ Removed smart start CD.
> 19/ booted FreeBSD and saved the collected data in a similar place:
>
> http://scorpion.sorbs.net/SMP/after-erase/
>
> ...and as you can see, I have 2 CPU's and this time they are detected
> correctly (including the 'odd' CPU type that was reported by the
> previous config)....
>
> For this I hope someone will create a FAQ for old Compaq's, and I'm
> posting this back to the list so that people having similar problems in
> the future can reference it.
I have a single-CPU DL360 and a quad-CPU 6400R. After flashing the BIOS
to the latest version and erasing the system, both are running 5-STABLE
flawlessly with the OS type set to "Windows 2000". Prior to installing
FreeBSD, both were actually running Windows 2000. However, I was unable
to get the 6400R to boot the FreeBSD install CD without panicking until
I erased the system. I had tried almost every OS type without success.
The "Erase System" seemed to be the critical step to get up-and-running.
Jon
---------------------------------------------
Thanks to all for help, I will inform bug tracker of my error
Jim