Re: SL 6.3 doesn't no network present until user logs in on GUI
Konstantin Olchanski wrote: This disables the super-clever extra-useful network manager feature where it enables networking when a user logs in into the console and helpfully disables the networking when a user logs out from the console. Do I grok this aright - you set up an SL workstation to do network stuff in the background, i.e: dhcp renewal, ntp, wee-hours automatic security updates, possibly other things (overnight backups? rsync of data to central server?); but if no one's logged onto the console, those all just stop working bcs NM has shut off the network? TUV thinks this is a good idea?! astonish It seems badly thought, if someone's not logged on overnight, no security updates. Or does yum rerun its wee-hours cron if someone logs in at the console during daytime?
User proc uses all RAM+swap = kernel panic - shouldn't OS not allow?
Greetings, Several times over past few years I've seen user processes go mad (programming error) use all RAM, then all swap (as ganglia so vividly shows), then the box ends up at a kernel panic. (Server OS is SL5.x 64-bit BTW) What's puzzling is, shouldn't the OS by default not allow users to do something bad enough to cause grief to the OS? Possibly some sort of tuning can fix this, but one expects that, out of the box, this should not be needed, users just can't bring OS down. In the past on SL4 I did see oom come into play when box too loaded (killing the mysqld process for instance) am wondering why this isn't happening on SL5 with badly behaved user processes. Grateful for advice!
Re: SL6.2 no boot from degraded RAID1 / with fix / Re: dracut update
Happy Friday! re: 004-283 was a fastbug for RHEL 6.3 . Since we have not released SL 6.3 yet it is only available in the 6rolling tree. We have to deploy an important SL server by 1 Oct and we'd like it to be SL6.2. We intend it to have Linux Software RAID1 pair of OS disks, but this dreadful problem is of much concern. We already have some SL6.2 servers (with hardware RAID1) so would like to go with SL6.2 - we're familiar with it don't wish to yet go with SL6.3 (very little site support available, can't risk any too new problems) Naturally we'd like to ready+test new important server well before 1 Oct. What's the probability that a fixed dracut will be released for SL6.2 Very Soon (any ETA?) so that an SL6.2 build on this new server in few weeks wouldn't be vulnerable to this can't boot from degraded Linux Software RAID1 dracut bug? Many thanks!
Re: SL6.2 no boot from degraded RAID1... with fix...
FYI, as a regression from SL6.0 and SL6.1, SL6.2 does not boot from degraded RAID1 devices. Apologies for the question but is this true of Linux Software RAID1 only, or of hardware RAID1 as well?
Re: What's diff btw yum-autoupdate and yum-cron?
Stephen_Isard wrote Hope that's helpful. It was very helpful, thank you. The info you cited seems true for SL5, though; SL6 appears quite different. In SL6, root@vm-37-00 rpm -ql yum-autoupdate /etc/cron.daily/yum-autoupdate /etc/sysconfig/yum-autoupdate Whereas yum-cron contains many more config files etc, has to be chkconfig'd on, etc. yum-autoupdate config file has an exclude line in it; yum-cron's doesn't. So it looks like for simplicity functionality, yum-autoupdate on SL6 gives what's wanted - can exclude things, get the daily automatic update, much less config cruft. Thank you for your help.
What's diff btw yum-autoupdate and yum-cron?
Happy Friday! What is the difference between the packages yum-autoupdate and yum-cron? rpm -qi yum -cron says Install this package if you want auto yum updates nightly via cron. rpm -qi yum-autoupdate says Automatically update your machine daily via yum. The 2 pkgs seem to do the same thing (I just got bit by an automatic update when I knew yum-cron had not been installed). Apols for not having time to dig, but do experts know the few-sentence summary of the differences between these 2 pkgs? Many many thanks!
Re: hang umounting file systems on reboot
SL6 systems, we can't reboot reliably, particularly if someone is logged on the console or if the user initiates the shutdown from the desktop. Have not seen one hang if no automounts are mounted. The last messages on the console are: Unmounting file systems: [ OK ] /home: rcercrcrcrcrcrcrcrcrcrcrcrcrc[...]rcrce init: rc main process (19211) killed by KILL signal The rc is repeated for about 3.5 console lines (note e near beginning and at end is not a typo). Something simliar happened here 27 Dec 2010 on a batch of SL5.x 64-bit cluster WN, in run level 3 (no Desktop), no automount or NIS (local pool accounts only), but they did have an NFS mount for /software, and they were multiclustered with a gpfs storage cluster to mount the /gpfs storage. The WN were running kernel-2.6.18-194.11.4.el5.x86_64 After yum update to kernel-2.6.18-194.26.1.el5.x86_64 (they skipped kernel-2.6.18-194.17.1 update) then shutdown -r now to make them boot into new kernel, they all hung coming down with this on console: sbin: rcercrcrcrcrcrcrcrcrcr INIT: no more processes left in this runlevel /bin: rcercrcrcrcrcrcrcrcrcrcr Could not kill process 2050: no such process Had never seen that before. Poke reset button - they all rebooted fine. On a 2nd batch of WN (headless) they also did exactly the same, updating from kernel-2.6.18-194.11.4 to kernel-2.6.18-194.32.1 in Feb'11. (In both cases in-between kernel updates were skpped; unsure if relevant). Never happened since. It was v curious but no time to look into it. Sympathies if you're seeing this repeatedly.
Re: How to convert a standar apps, to a Service
On Wed, 27 Apr 2011 Alec T. Habig wrote snip - much good advice logging (have it log status information, ideally with customizeable log levels, to the appropriate place), What about the logrotate part to correctly rotate logs so they don't grow infinitely NB I notice SL5 by default rotates on size not date (as SL4 did); this is good. Rather a few not-too-big logfiles (good default) than many mostly empty rotated dutifully but pointlessly once a week or whatever.
Unable to SL5 rescue mode - always borks
Some time ago someone said You could have used rescue mode of the install cd's to fix your issue vs doing a new install. The rescue mode of SL5 has never worked for me - all I ever get is a kernel panic. 32-bit, 64-bit, various hardware. Is there anyone out there that can test/confirm rescue mode works with SL5.5 install media? If so what version of SL5? I'm using SL5.5 32-bit DVD. Rescue mode works in SL4, but SL4 won't necessarily recognize newer SATA controllers. :(
Re: INFO: task blocked for more than 120 seconds.
Good day, Someone in our local LUG recently posed about this, he was seeing Jul 21 07:39:04 linux kernel: INFO: task mount:5258 blocked for more than 120 seconds. Jul 21 07:39:04 linux kernel: echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Jul 21 07:39:04 linux kernel: mount D 0002 0 / 5258 4842 0x0080 Jul 21 07:39:04 linux kernel: 880037b4fb28 0082 / 880037b4fa78 812d6ea0 Jul 21 07:39:04 linux kernel: 880037b4fad8 812ef2f9 / 880037b4ffd8 880037b4ffd8 He found a solution: Googling around suggests that it might be a recurrent kernel bug (as it appears to come and go between versions) and that it might be related to the method the kernel uses to idle the processor. The most power-efficient technique is to use the MWAIT instruction, which is the default on systems that support it. The least power-efficient (and most performant) is use a polling idle loop. In between is to use the HALT instruction. Since starting to boot my kernel with idle=halt (and pcie_aspm=off, FWIW, but I don't think my system was using it anyway), I haven't had any recurrance. Does that help?
Re: TESTING - rrdtool for SL4 and SL5
On Mon, 8 Feb 2010 Troy Dawson wrote Looks like we didn't get enough testing done, and maybe rrdtool doesn't really need to be in the plain SL release. I have no problem pulling it out of the release and having people just install it from dag or EPEL, whichever they prefer. Since it hasn't gotten into any final release, this isn't that much of a problem, I just need to take it out of the repositories. Does anyone *really* need it in the release? Is there any real reasons why people can't get it from dag and/or EPEL after they are installed? Someone answered: If these packages *need* the particular version of rrdtool I suggest that it might not be ready for an SL release. If they only have tight dependencies because the package build put precise version into the package, then those packages ought to be remade. So no, I don't feel that SL needs to have rrdtool. Is there ever going to be a solution? Now installing ganglia, the gmetad node never can nightly yum update except by hand, due to rrdtool version clashes in public SL mirrors.
rescue mode from SL5.3 DVD seems broken
Good day, Using a fresh-written SL.53.031809.DVD.i386.disc1.iso linux rescue ends up fast at: running /sbin/loader [loading ata_piix driver] (on the blue screen) loader received SIGSEGV! Backtrace: [0x8048cf4] (several of those, different hex) Install exited abnormally [1/1] blah blah you may safely reboot your system Can anyone else reproduce this? SL4 rescue is fine; SL5.3 not (don't have time to try SL5.2/1/0) The DVD image was downloaded from http://ftp.scientificlinux.org/linux/scientific/53/iso/i386/DVD/SL.53.031809.DVD.i386.disc1.iso and the md5sum is correct. It's the same result on any machine tried with several writ SL5.3 DVDs, so not specific to hardware or DVD. Is there something I can do/try to make it work? (Otherwise have to retain SL4 DVDs for rescue mode) (used yesterday on office SL5.3 Dell laptop to reinstall grub after badness - whew) Grateful for advice. BTW, in the page https://www.scientificlinux.org/distributions/5x/53/limitations it says smartctl: The smartctl tool cannot properly read SMART parameters from SATA devices. smartctl for SATA disks looks to work fine on all our SL5.x boxen (the single SL5.2 box requires -d ata, SL5.3 don't, it just works)
Re: rescue mode from SL5.3 DVD seems broken
On Tue, 20 Oct 2009, Patrick Moelands wrote: There the installation ended in the same way. This might be related? Bugreport with details: https://bugzilla.redhat.com/show_bug.cgi?id=520199 Thanks for that, but doesn't seem related. No promise sata controllers here. On most recent test box in my office (tried this morning), it's IDE not SATA. ALT+F4 screen (Unsure if relevant) ends at 7ISO 9660 Extensions: Microsoft Joliet Level 3 4Unable to load NLS charset utf8 4Unable to load NLS charset utf8 7ISO 9660 Extensions: RRIP_1991A 4Unable to identify CD-ROM format. 4VFS: Can't find an ext2 filesystem on dev loop0 on ALT+F3 it ends at load module set done trying to mount CD device hdc 513724kb are available mntloop loop0 on /mnt/runtime as /tmp/ramfs/stage2.img fd is 10 Haven't looked at screens at other (SATA) SL5 but they're busy being servers. Does any of that indicate where the problem is? PS SL is fantastic. Thanks**N to the builders+maintainers.
Re: Logo Contest for SL6 extended
Is there going to be an official web page for voting, or is email to the SL-user's list = one's vote? FWIW, my vote is #12, 4, 5 or 11 (in that order) Don't like #1, 9, or either 13.
kernel-2.6.18-164.el5 released 2 Sept by RHEL - SL version?
Good day, On 2 Sept RHEL released a new RHEL 5 kernel: Important RHSA-2009:1243 Important: Red Hat Enterprise Linux 5.4 kernel security and bug fix update 2009-09-02 It's kernel-2.6.18-164.el5 It's not yet at http://ftp.scientificlinux.org/linux/scientific/53/x86_64/updates/security/ so also not at our usuaul SL mirror. Is it in the pipeline soon so to speak?
Problems with afs latest 2.6.9-89.0.3 kernel SL4.x
Dear SL gurus, Our SL4 AFS clients are unable to update to latest kernel, the error is Transaction Check Error: package kernel-module-openafs-2.6.9-78.0.13.EL-1.4.7-68.2.SL4 (which is newer than kernel-module-openafs-2.6.9-78.0.13.EL-1.4.7-68.SL4) is already installed package kernel-module-openafs-2.6.9-78.0.13.ELsmp-1.4.7-68.2.SL4 (which is newer than kernel-module-openafs-2.6.9-78.0.13.ELsmp-1.4.7-68.SL4) is already installed Can someone advise on the fix? I've tried yum clean all; yum update - same error (wasn't likely to work, but -) Also tried change /etc/yum.repos.d/sl-errata.repo sl.repo to point from our SL4.4 4.5 mirror to using SL's own repos (in case the problem is our mirror server), yum clean all, yum update - same error On one SL4.4 afs client (where it isn't critical that AFS works), openafs was removed, then yum update worked, but now can't reinstall openafs - it wants kernel 2.6.9-11 installed! Why?? r...@bsesrv3 yum install openafs-client Loading kernel-module plugin Setting up Install Process Setting up repositories Reading repository metadata in from local files Parsing package install arguments Resolving Dependencies -- Populating transaction set with selected packages. Please wait. --- Package openafs-client.x86_64 0:1.4.7-68.2.SL4 set to be updated -- Running transaction check -- Processing Dependency: openafs = 1.4.7 for package: openafs-client -- Processing Dependency: openafs-kernel for package: openafs-client -- Restarting Dependency Resolution with new changes. -- Populating transaction set with selected packages. Please wait. --- Package openafs.x86_64 0:1.4.7-68.2.SL4 set to be updated --- Package kernel-module-openafs-2.6.9-11.EL.x86_64 0:1.4.7-68.2.SL4 set to be updated -- Running transaction check -- Processing Dependency: kernel-x86_64 = 2.6.9-11.EL for package: kernel-module-openafs-2.6.9-11.EL -- Finished Dependency Resolution Beginning Kernel Module Plugin --- Package kernel-module-openafs-2.6.9-78.0.17.ELsmp.x86_64 0:1.4.7-68.2.SL4 set to be installed --- Package kernel-module-openafs-2.6.9-78.0.22.ELsmp.x86_64 0:1.4.7-68.2.SL4 set to be installed --- Package kernel-module-openafs-2.6.9-89.0.3.ELsmp.x86_64 0:1.4.7-68.2.SL4 set to be installed --- Package kernel-module-openafs-2.6.9-78.0.13.ELsmp.x86_64 0:1.4.7-68.SL4 set to be installed --- Package kernel-module-openafs-2.6.9-78.0.22.EL.x86_64 0:1.4.7-68.2.SL4 set to be installed --- Package kernel-module-openafs-2.6.9-89.0.3.EL.x86_64 0:1.4.7-68.2.SL4 set to be installed --- Package kernel-module-openafs-2.6.9-78.0.13.EL.x86_64 0:1.4.7-68.SL4 set to be installed --- Package kernel-module-openafs-2.6.9-78.0.17.EL.x86_64 0:1.4.7-68.2.SL4 set to be installed Finished Kernel Module Plugin Error: Missing Dependency: kernel-x86_64 = 2.6.9-11.EL is needed by package kernel-module-openafs-2.6.9-11.EL r...@bsesrv3 rpm -qa | grep 2.6.9-11 /* nothing */ r...@bsesrv3 rpm -qa | grep ^kernel | sort kernel-2.6.9-78.0.13.EL.x86_64 kernel-2.6.9-78.0.17.EL.x86_64 kernel-2.6.9-78.0.22.EL.x86_64 kernel-2.6.9-89.0.3.EL.x86_64 kernel-smp-2.6.9-78.0.13.EL.x86_64 kernel-smp-2.6.9-78.0.17.EL.x86_64 kernel-smp-2.6.9-78.0.22.EL.x86_64 kernel-smp-2.6.9-89.0.3.EL.x86_64 kernel-smp-devel-2.6.9-78.0.13.EL.x86_64 kernel-smp-devel-2.6.9-78.0.17.EL.x86_64 kernel-smp-devel-2.6.9-78.0.22.EL.x86_64 kernel-smp-devel-2.6.9-89.0.3.EL.x86_64 kernel-utils-2.4-14.1.117.2.1.x86_64 Can anyone advise on a fix. Please + thank you very much!
FIXED Re: Problems with afs latest 2.6.9-89.0.3 kernel SL4.x
Dear All, Dr Solomin very kindly advised: yum --exclude=kernel-module-openafs-2.6.9-78.0.13.ELsmp-1.4.7-68.SL4 \ --exclude=kernel-module-openafs-2.6.9-78.0.13.EL-1.4.7-68.SL4 update works fine, and for the box where openafs was removed, yum install kernel-module-openafs-2.6.9-89.0.3.EL allows openafs-client to be reinstalled. Thank you very much Dr Solomin!
kernel-2.6.9-78.0.17 only in 40rolling? And SL4=5 upgrade : clean?
Dear All,
Ever since RHEL released kernel-2.6.9-78.0.17 on 12 March I've been
expecting it to be available for our SL4 machines - but nothing yet.
In looking at the Kent mirror, kernel-2.6.9-78.0.17 appears in
40rolling/${basearch}/errata/SL/RPMS dated 13 March, but not in SL44 to 47,
or 4x (presumably 4x is just a pointer to 47)
Is there some problem with kernel-2.6.9-78.0.17 that it's not released for
SL44 to 47?
Also, has anyone done an upgrade SL4 = 5 via anaconda? Is it clean
or messy, recommended or disrecommended?
On a test machine long ago I did SL3 = SL4 upgrade via anaconda it was
messy. Too much had changed, the cleanup from 3 to 4 left a lot of old SL3
cruft about, so decided fresh SL4 rebuild for our SL3 servers.
Now we have more SL4 servers, so if upgrade to SL5 via anaconda is
acceptably tidy we could try - if it's tidy it will be less work than
complete rebuild chase down cumulative config tweaks... as you do.
Re: Problem with ftp://ftp.scientificlinux.org/?
Greetings all, Is similar happening again? Our lftp hung again last night although ftp.scientificlinux.org = linux21.fnal.gov pings, it seems inaccessible otherwise. Many thanks to the maintainers of Scientific Linux!! On Mon, 11 Feb 2008, Winnie Lacesso wrote: Greetings, Is there some problem with ftp://ftp.scientificlinux.org//linux/scientific/ http://ftp.scientificlinux.org/linux/scientific/ ? I can't seem to get to any of them, some of our nightly yum updates hung also our nightly mirror hung for the last 2 nights. I do beg your pardon, there didn't seem to be any scheduled downtime that could be found under News or Scientific-Linux-Announce archives. Many thanks to the excellent maintainers of Scientific Linux. And someone said maintenance was a thankless task. Not!! Grateful Unit
Problem with ftp://ftp.scientificlinux.org/?
Greetings, Is there some problem with ftp://ftp.scientificlinux.org//linux/scientific/ http://ftp.scientificlinux.org/linux/scientific/ ? I can't seem to get to any of them, some of our nightly yum updates hung also our nightly mirror hung for the last 2 nights. I do beg your pardon, there didn't seem to be any scheduled downtime that could be found under News or Scientific-Linux-Announce archives. Many thanks to the excellent maintainers of Scientific Linux. And someone said maintenance was a thankless task. Not!! Grateful Unit
sata_nv/ahci drivers in SL3 for nvidia MCP55 SATA controller?
Greetings, We'll buy server hardware soon to run a critical app that requires SL3. Upgrade to SL4 later is probably a go, but initially it must be SL3. So SL308 would load with 2.4.21-47.0.1.ELsmp yum update to 2.4.21-50.ELsmp. The hardware may have Tyan S2925G2NR mobo which has nvidia nForce Pro 3400 chipset, with nvidia MCP55 SATA controller. Some hunting shows: . SL3.0.8 release notes: Nvidia Nforce(motherboard chipset) drivers: IDE is supported. NO SUPPORT for ethernet, audio, sata. That sounds bad. But: . Newer NVIDIA chipsets are AHCI, and use the ahci driver not sata_nv . both sata_nv ahci drivers in SL3 . both sata_nv ahci driver said production maturity . libata AHCI driver ahci became available starting 2.4.29-preX ... (that's later than SL308 kernel) Questions: . would the version of the ahci driver in SL3 be older than the version in SL4? . If it is older, would an older ahci driver version in SL3 have any problem driving the nvidia MCP55 (or possibly even newer if a newer mobo) SATA controller? . If ahci can't or won't, will SL3 understand to use sata_nv driver instead? And would sata_nv have any problem driving the nvidia MCP55 (or possibly even newer if a newer mobo) SATA controller? many many thanks
