Re: chances of PPC64 build?
On Thu, 9 Jun 2011, Jeremy Enos wrote: Hi there- Suppose I'm assembling a list of OS candidates to run on a very large PPC64 based supercomputer- what are the odds of seeing a SL6 PPC64 version? Not much chance. TUV does not have a PPC64 version. -Connie Sieh thx- Jeremy Enos
Re: value of RAM reported not correct in SLC 5.6
On Thursday, June 09, 2011 07:22:56 PM you wrote: That's a significant chunk of RAM for such an old codebase. Is there any reason not to simply update to SL 6.0 and avoid the support problems? What are you talking about, being large for an old codebase? On x86_64 upstream has supported far more than 48GB since version 3 days (128GB to be exact, according to http://www.redhat.com/rhel/compare/ ). While I don't have a machine with more than 32GB of RAM currently, I wouldn't have any problem using CentOS or SL 5.6 (or either SLC or SLF) on x86_64 with that much RAM. The EL5.6 kernel isn't aged yet, not by a long shot. SLC5 to SLC6 is not an update, it is a major upgrade. There may be very significant reasons to not upgrade for the OP. In any case, this doesn't answer the OP's question of why SLC5.6 doesn't see the same thing as upstream EL5.6 but being built from the same source. I would ask the OP to see what both SL (non-C) and CentOS 5.6 say about the machine and see if either see things like SLC or like upstream. It should be a pretty simple and quick test, especially if the OP uses the LiveCD to do it (which should work ok, assuming all the tools are there).
Re: SL6: NIS, AUTOFS incompatible with NetworkManager
On Thursday, June 09, 2011 07:21:29 PM you wrote: The curses based, text compatible system-config-network needs everything a typical desktop or server needs. It lacks some of the foofiness of NetworkManager, but that's both unnecessary and dangerous on a stable desktop or server, as we've seen happen repeatedly for new installations of RHEL based systems over the last 5 years or so. Heh. Why would you want to stick with such an old codebase, Nico? The TUI system-config-network is deprecated in upstream EL6 and will at some point in time be removed, once the NM config tools are able to duplicate all functionality. And they are most definitely getting closer. This is part of what going to EL6 is and will be about.
Re: Login fails in GDM, SL 6rolling
On Thu, 9 Jun 2011, Chris Tooley wrote: Hello everyone! OK still trying to get graphical login working with SSSD + GDM, so here's more information about my system setup, with which I cannot login using an LDAP account through GDM. * I am using 6rolling * I am using base 6rolling install - nothing customized. * I am using SSSD (sssd-1.5.1-34.el6.x86_64) with LDAP for authentication and identification purposes. * I can log in as root * I can log in as a local user, created by root * Both the local user and root can log in using GDM (root, after editing pam.d/gdm) * I can log in with an LDAP account using SSH. * I can log in with an LDAP account into a terminal on the computer * When I go into runlevel 3 with init 3 from a root account on a terminal, and log in as a user on another terminal, I can start X11 with the startx command. When I attempt to login using an LDAP account, here is the behaviour that I get: I click other, enter my username, enter my password. The busy cursor appears, and then the screen blacks out and returns me back to my login screen. I figure there is something weird going on with GDM. Unfortunately, GDM is being coy with any possible errors, and, even when I set debug=true in /etc/gdm/custom.conf I get a plethora of debugging messages, none of which seem to hint to any errors. I can attach /etc/messages to an email if requested but I cannot see any errors. Here is what id ctooley returns when I run it as root btw: [root@heplw44 gdm]# id ctooley uid=110233(ctooley) gid=110233 groups=110233,34244(hep) Any clues in this would be immensely appreciated :) Thanks! -Chris Tooley Did this work under SL 6.0? -Connie Sieh
Re: value of RAM reported not correct in SLC 5.6
On Wednesday, June 08, 2011 07:49:08 PM you wrote: The problem we have is that once the os is installed slc56 top, free and vmstat only reports 32Gb. All the yum updates were performed. To check we booted with the rescue mode, SLC 5.6 and all the commands report 48Gb . Hmm, perhaps it won't be as simple as checking with a LiveCD. Can you give the output of 'uname -svrmpio' (or uname -a, without the hostname). The output of dmidecode could be useful as well, and dmesg (either send privately or use pastebin rather than to the list, however).
Re: value of RAM reported not correct in SLC 5.6
we are running SL5.6 x86_64 (2.6.18-238.9.1) on a 96GB machine without issues. does the bios report 48GB of ram when the OS sees 32? (we had an other machine with bad ram/memcontroller that reported varying amounts of ram after every reboot) and how much ram is seen by dmidecode? stijn On Thursday, June 09, 2011 07:22:56 PM you wrote: That's a significant chunk of RAM for such an old codebase. Is there any reason not to simply update to SL 6.0 and avoid the support problems? What are you talking about, being large for an old codebase? On x86_64 upstream has supported far more than 48GB since version 3 days (128GB to be exact, according to http://www.redhat.com/rhel/compare/ ). While I don't have a machine with more than 32GB of RAM currently, I wouldn't have any problem using CentOS or SL 5.6 (or either SLC or SLF) on x86_64 with that much RAM. The EL5.6 kernel isn't aged yet, not by a long shot. SLC5 to SLC6 is not an update, it is a major upgrade. There may be very significant reasons to not upgrade for the OP. In any case, this doesn't answer the OP's question of why SLC5.6 doesn't see the same thing as upstream EL5.6 but being built from the same source. I would ask the OP to see what both SL (non-C) and CentOS 5.6 say about the machine and see if either see things like SLC or like upstream. It should be a pretty simple and quick test, especially if the OP uses the LiveCD to do it (which should work ok, assuming all the tools are there). -- http://hasthelhcdestroyedtheearth.com/
Re: chances of PPC64 build?
On 6/9/2011 5:43 PM, Jeremy Enos wrote: Hi there- Suppose I'm assembling a list of OS candidates to run on a very large PPC64 based supercomputer- what are the odds of seeing a SL6 PPC64 version? As Connie mentioned, RH dropped ppc/power support in 6. Which I think is sad. For the record, however, I've used OpenBSD and Gentoo on ppc/power5 systems and have had great luck! Randy
Re: chances of PPC64 build?
On 6/10/2011 10:49 AM, Randal T. Rioux wrote: On 6/9/2011 5:43 PM, Jeremy Enos wrote: Hi there- Suppose I'm assembling a list of OS candidates to run on a very large PPC64 based supercomputer- what are the odds of seeing a SL6 PPC64 version? As Connie mentioned, RH dropped ppc/power support in 6. Which I think is sad. For the record, however, I've used OpenBSD and Gentoo on ppc/power5 systems and have had great luck! Randy RH actually has an IBM POWER build upstream (I should have been more specific). Will CentOS make a build if RH does? thanks- Jeremy
Re: chances of PPC64 build?
On 6/10/2011 12:10 PM, Jeremy Enos wrote: On 6/10/2011 10:49 AM, Randal T. Rioux wrote: On 6/9/2011 5:43 PM, Jeremy Enos wrote: Hi there- Suppose I'm assembling a list of OS candidates to run on a very large PPC64 based supercomputer- what are the odds of seeing a SL6 PPC64 version? As Connie mentioned, RH dropped ppc/power support in 6. Which I think is sad. For the record, however, I've used OpenBSD and Gentoo on ppc/power5 systems and have had great luck! Randy RH actually has an IBM POWER build upstream (I should have been more specific). Will CentOS make a build if RH does? Correction, I meant will SL make a build if RH does.
Re: Login fails in GDM, SL 6rolling
I have about 35GB free on the partition I'm using. -Chris On 11-06-10 1:09 AM, Zoran Ovcin wrote: Is your / partition full? Or nearly full? On 06/10/2011 02:50 AM, Chris Tooley wrote: Hello everyone! OK still trying to get graphical login working with SSSD + GDM, so here's more information about my system setup, with which I cannot login using an LDAP account through GDM. * I am using 6rolling * I am using base 6rolling install - nothing customized. * I am using SSSD (sssd-1.5.1-34.el6.x86_64) with LDAP for authentication and identification purposes. * I can log in as root * I can log in as a local user, created by root * Both the local user and root can log in using GDM (root, after editing pam.d/gdm) * I can log in with an LDAP account using SSH. * I can log in with an LDAP account into a terminal on the computer * When I go into runlevel 3 with init 3 from a root account on a terminal, and log in as a user on another terminal, I can start X11 with the startx command. When I attempt to login using an LDAP account, here is the behaviour that I get: I click other, enter my username, enter my password. The busy cursor appears, and then the screen blacks out and returns me back to my login screen. I figure there is something weird going on with GDM. Unfortunately, GDM is being coy with any possible errors, and, even when I set debug=true in /etc/gdm/custom.conf I get a plethora of debugging messages, none of which seem to hint to any errors. I can attach /etc/messages to an email if requested but I cannot see any errors. Here is what id ctooley returns when I run it as root btw: [root@heplw44 gdm]# id ctooley uid=110233(ctooley) gid=110233 groups=110233,34244(hep) Any clues in this would be immensely appreciated :) Thanks! -Chris Tooley
Re: chances of PPC64 build?
On 6/10/2011 1:10 PM, Jeremy Enos wrote: On 6/10/2011 10:49 AM, Randal T. Rioux wrote: On 6/9/2011 5:43 PM, Jeremy Enos wrote: Hi there- Suppose I'm assembling a list of OS candidates to run on a very large PPC64 based supercomputer- what are the odds of seeing a SL6 PPC64 version? As Connie mentioned, RH dropped ppc/power support in 6. Which I think is sad. For the record, however, I've used OpenBSD and Gentoo on ppc/power5 systems and have had great luck! Randy RH actually has an IBM POWER build upstream (I should have been more specific). Will CentOS make a build if RH does? thanks. To quote myself: RH dropped ppc/power support in 6
Re: chances of PPC64 build?
On Friday, June 10, 2011 02:47:19 PM you wrote: To quote myself: RH dropped ppc/power support in 6 Then someone needs to update http://www.redhat.com/rhel/server/compare/ to reflect that. Also http://www.redhat.com/rhel/compare/ which correctly lists IA64's being dropped. POWER is on the list, with specifications for supported maximums, for version 6.
Re: chances of PPC64 build?
On 6/10/2011 4:52 PM, Lamar Owen wrote: On Friday, June 10, 2011 02:47:19 PM you wrote: To quote myself: RH dropped ppc/power support in 6 Then someone needs to update http://www.redhat.com/rhel/server/compare/ to reflect that. Also http://www.redhat.com/rhel/compare/ which correctly lists IA64's being dropped. POWER is on the list, with specifications for supported maximums, for version 6. *hangs head in shame* What the crap!? They sent an email to me last year saying they were discontinuing support for the POWER platform. My apologies :-) Randy ...off to download RHEL6 for POWER...
SL6.1alpha kickstart difficulty - /mt/source gone?
Hi. Did the kickstart in SL6.1 stop mounting the installation tree on /mnt/source? I am just not finding the answer after googling and reading and experimenting for 2hrs so I figure I'm doing something less bright. But today I've come acrosss mention of more significant changes in RHEL6 than I had thought from earlier reading, so maybe it's not listed in the RHEL 6 migration guide but is well-known by others? I thought /mnt/source was a standard location during the kickstart to find the installation media. Today I was quickly trying to get kickstart configured with SL6.1a by copying our successful SL5.4 kickstart files and modifying as necessary to change paths. (And stop using the few deprecated terms in the kickstart config file like mouse.) I had previously divided up my ks files into various parts and then %included them where necessary to try to generalize yet cope with our various administrative domains needing different configurations, package lists, etc. It worked well for me. I believe I can work around my present problem by creating single ks files, but I don't want to go backwards like that. This is an NFS distribution of the package files. First line of my ks file looks like: nfs --server hidden.hostname.domain.edu --dir /export/sysadmin1/kickstart/sl61/i386 PXE booting a 32 bit machine works fine with sl61 image. Anaconda runs and then dies when it encounters references to /mnt/source in several places in my kickstart file. I see in the alternate consoles that the first line of my ks file is being correctly parsed for the hostname and the directory to mount, but anaconda fails with errors about being unable to access /mnt/source/blah mentioned in lines like: %include /mnt/source/ks-sl61/i386.incl.domain and then I see in the shell running in an alternate console that the only NFS mounts are of /mnt/stage2 and /mnt/disk-image, neither of which contains the rpm package files (they are deeper subdirectories of /export/sysadmin1/kickstart/sl61/i386). So NFS and host resolution etc is all working but /mnt/source just seems to be gone, with no errors that I can see in the alternate consoles. Trying to work around this issue, I'm unsuccessful at specifying a %include using an url, which I saw mentioned was now available in RHEL6. (I assumed that it could be an NFS reference, maybe that was my flaw there...) None of these forms have worked: %include nfs:hostname:/path/to/file %include hostname:/path/to/file %include IP:/path/to/file %include IP /path/to/file %include nfs://IP/path/to/file hmmm, that last effort failed with PYCURL ERROR 1 - Protocol nfs not supported or disabled in libcurl. Anyway, that's all fighting a battle which maybe I can avoid by knowing whether /mnt/source is a standard that is failing to work for some reason or is no longer available. Thanks, and have a good weekend!
Re: Login fails in GDM, SL 6rolling
On 11-06-09 6:14 PM, Stephen John Smoogen wrote: On Thu, Jun 9, 2011 at 20:50, Chris Tooleyctoo...@uvic.ca wrote: Hello everyone! OK still trying to get graphical login working with SSSD + GDM, so here's more information about my system setup, with which I cannot login using an LDAP account through GDM. * I am using 6rolling * I am using base 6rolling install - nothing customized. * I am using SSSD (sssd-1.5.1-34.el6.x86_64) with LDAP for authentication and identification purposes. * I can log in as root * I can log in as a local user, created by root * Both the local user and root can log in using GDM (root, after editing pam.d/gdm) * I can log in with an LDAP account using SSH. * I can log in with an LDAP account into a terminal on the computer How does the LDAP bind, and can you try not using sssd to see if it is that which is cachig a bad answer? I am going to say that I don't think this is GDM as much as pam getting a DO NOT GO PAST GO somewhere. I would try putting debug statements in /etc/pam.d/system-auth I checked, and system-auth (part of what gdm uses) and password-auth (part of what sshd uses) are exactly the same. I would expect the problem to exist somewhere in gdm's authentication, but there are no useful (to me) messages spit out by GDM when I enable gdm debugging. So far I have not been able to get debugging enabled for PAM. Has anyone done that before? -Chris
Re: Login fails in GDM, SL 6rolling
On 11-06-10 7:56 AM, Connie Sieh wrote: On Thu, 9 Jun 2011, Chris Tooley wrote: Hello everyone! OK still trying to get graphical login working with SSSD + GDM, so here's more information about my system setup, with which I cannot login using an LDAP account through GDM. * I am using 6rolling * I am using base 6rolling install - nothing customized. * I am using SSSD (sssd-1.5.1-34.el6.x86_64) with LDAP for authentication and identification purposes. * I can log in as root * I can log in as a local user, created by root * Both the local user and root can log in using GDM (root, after editing pam.d/gdm) * I can log in with an LDAP account using SSH. * I can log in with an LDAP account into a terminal on the computer * When I go into runlevel 3 with init 3 from a root account on a terminal, and log in as a user on another terminal, I can start X11 with the startx command. When I attempt to login using an LDAP account, here is the behaviour that I get: I click other, enter my username, enter my password. The busy cursor appears, and then the screen blacks out and returns me back to my login screen. I figure there is something weird going on with GDM. Unfortunately, GDM is being coy with any possible errors, and, even when I set debug=true in /etc/gdm/custom.conf I get a plethora of debugging messages, none of which seem to hint to any errors. I can attach /etc/messages to an email if requested but I cannot see any errors. Here is what id ctooley returns when I run it as root btw: [root@heplw44 gdm]# id ctooley uid=110233(ctooley) gid=110233 groups=110233,34244(hep) Any clues in this would be immensely appreciated :) Thanks! -Chris Tooley Did this work under SL 6.0? -Connie Sieh Well, the thing is, I don't know, because there was a separate problem which plagued SSSD versions lower than 1.4, to do with groups - so I never tried logging in with gdm... I have a separate LDAP server which I will try on Monday to see if it's something with the LDAP server or just my configuration. Thanks, -Chris
Re: SL6: NIS, AUTOFS incompatible with NetworkManager
On Fri, Jun 10, 2011 at 10:55 AM, Lamar Owen lo...@pari.edu wrote: On Thursday, June 09, 2011 07:21:29 PM you wrote: The curses based, text compatible system-config-network needs everything a typical desktop or server needs. It lacks some of the foofiness of NetworkManager, but that's both unnecessary and dangerous on a stable desktop or server, as we've seen happen repeatedly for new installations of RHEL based systems over the last 5 years or so. Heh. Why would you want to stick with such an old codebase, Nico? The TUI system-config-network is deprecated in upstream EL6 and will at some point in time be removed, once the NM config tools are able to duplicate all functionality. And they are most definitely getting closer. This is part of what going to EL6 is and will be about. Because it works well over SSH remote connections, headless serial port based access for clusters, virtualized system consoles where GUI's are ill supported and burden the VM and the host, micro-installations, and systems where some sucker installed NVidia drivers, updated their OpenGL libraries, and broke X but hard. It's dealing with flat text files in a well devined, shell compatible format: there is no XML or complex databases to deal with, just some simple configuration files. And if you make a mistake in the network configuration, you again break X services. Should I go on? This is an old subject, and I've got plenty more reasons.
Re: value of RAM reported not correct in SLC 5.6
On Fri, Jun 10, 2011 at 10:55 AM, Lamar Owen lo...@pari.edu wrote: On Thursday, June 09, 2011 07:22:56 PM you wrote: That's a significant chunk of RAM for such an old codebase. Is there any reason not to simply update to SL 6.0 and avoid the support problems? What are you talking about, being large for an old codebase? On x86_64 upstream has supported far more than 48GB since version 3 days (128GB to be exact, according to http://www.redhat.com/rhel/compare/ ). It can work, I've done it. It's problematic, especially if one leaves the 32-bit versions of components and libraries dual-installed with the 64-bit, deletes one and not the other. The codebase for SL 5 and RHEL 5 uses significantlyou out of date kernels, glibc, and other core utilities. so yes: if you stretch the environment beyond the common resources at the time it was originally designed, you can enter the world of surprising corner cases. It's worse with old systems: kernel patches to deal with outlier, wierd hardware aren't necessarily backported, they're more likely to get in the much more recent kernel codebase, and scheduling downtime to do BIOS updates gets even harder when someone keeps saying n-o-o-o! I've got an uptime of 635 days, we can't reboot it! prove to me that this will fix things first! While I don't have a machine with more than 32GB of RAM currently, I wouldn't have any problem using CentOS or SL 5.6 (or either SLC or SLF) on x86_64 with that much RAM. The EL5.6 kernel isn't aged yet, not by a long shot. SLC5 to SLC6 is not an update, it is a major upgrade. There may be very significant reasons to not upgrade for the OP. In any case, this doesn't answer the OP's question of why SLC5.6 doesn't see the same thing as upstream EL5.6 but being built from the same source. I would ask the OP to see what both SL (non-C) and CentOS 5.6 say about the machine and see if either see things like SLC or like upstream. It should be a pretty simple and quick test, especially if the OP uses the LiveCD to do it (which should work ok, assuming all the tools are there). The LiveCD is a good idea.
Re: SL6: NIS, AUTOFS incompatible with NetworkManager
On Fri, Jun 10, 2011 at 10:55:33AM -0400, Lamar Owen wrote: On Thursday, June 09, 2011 07:21:29 PM you wrote: The curses based, text compatible system-config-network needs everything a typical desktop or server needs. It lacks some of the foofiness of NetworkManager, but that's both unnecessary and dangerous on a stable desktop or server, as we've seen happen repeatedly for new installations of RHEL based systems over the last 5 years or so. Heh. Why would you want to stick with such an old codebase, Nico? I think the wrong question was asked and a different wrong question was answered. One issue is GUI vs TUI. Gui is okey when you are standing in front of the computer console and the X11 graphics are working and you have a working monitor of reasonable size. If you do not have a working monitor of reasonable size, the GUIs tend to fail (usually the OK buttons are below the bottom of the screen). If X11 graphics do not work, GUI is no good (no image on monitor, or monitor complains about out-of-range video settings, etc). (Yes, I can spend the day fixing X11 graphics, but I have better things to do). If you are not standing in front of the computer, you have to tunnel X11 graphics through an ssh tunnel. Okey for a computer in the office next door, but good luck doing this through a trans-Atlantic or trans-Pacific link. (You say use VNC!, well good luck getting a VNC connection to a computer behind a firewall on the other side of a VPN connection. Hint - it can be done by tunneling a reverse connection (server to client) through an ssh tunnel). On my side, I have the instructions for setting up new computers written up on a web page. I want to be able to cut-and-paste them to a command line, so authconfig --enablenis --nisdomain xxx --update is cool, but run system-config-users, then push these buttons with mouse is not cool. -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
