heartbleed and openssl update
I see this link relative to openssl and heartbleed exploit... https://www.openssl.org/news/secadv_20140407.txt A missing bounds check in the handling of the TLS heartbeat extension can be used to reveal up to 64k of memory to a connected client or server. Only 1.0.1 and 1.0.2-beta releases of OpenSSL are affected including 1.0.1f and 1.0.2-beta1. Affected users should upgrade to OpenSSL 1.0.1g. Users unable to immediately upgrade can alternatively recompile OpenSSL with -DOPENSSL_NO_HEARTBEATS. 1.0.2 will be fixed in 1.0.2-beta2. My SL 6.5 lists openssl-1.0.1e-16.el6_5.7.x86_64 openssl098e-0.9.8e-17.el6_2.2.x86_64 openssl-devel-1.0.1e-16.el6_5.7.x86_64 so, it is a vulnerable version of openssl. Question 1 I enabled fastbugs in sl-other.repo and well as usual enables in sl.repo, however, do not see an update for openssl. Will there be one forthcoming from SL or have I missed the proper repository to get it? I have no server on this PC, so I am not worried yet. Question 2 I surmise that older versions of openssl on older SLs are not impacted such as openssl-0.9.8e-26.el5_9.1.i686 Bill Lutter
SL6 won't boot. Is this related to xorg issue?
Wouldn't you know it, I just rebooted my SL6.0 or 6.1 linux PC prior to leaving town for a week and it hangs on all 3 of the available kernels. I see a black screen with white letters "Scientific Linux 6." I've not tried start up options. No problem with this PC. I did have a matlab issue using lots of cpu with java machine which is why I rebooted, that was a minor irritant. Is the reboot hang related to the xorg update issue? As I can't access this PC remotely (I can't ping it), any suggestions on how I fix this? Thanks for any advice, Bill Lutter
Re: blank screen this morning on SL6.1 PC, no obvious error messages
Oops, it was indeed the ASUS monitor. Never seen one fail like that. Bill Lutter
blank screen this morning on SL6.1 PC, no obvious error messages
Today a SL6.1 with kernel (Linux mu2 2.6.32-220.13.1.el6.x86_64 #1 SMP Tue Apr 17 15:16:22 CDT 2012 x86_64 x86_64 x86_64 GNU/Linux) on an optiplex 980 has a blank screen. I rebooted to 2.6.32-220.13.1 (it was using 17.1) and you see the asus (monitor) and dell logos. You see the kernel selection briefly then nothing. I can remote login to the PC. I don't see anything of note in the dmesg or /var/log/ Xorg log files except the usual messages:Jun 18 08:54:07 mu2 NetworkManager[1319]: [1340027647.919205] [nm-manager.c:1360] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name 'org.freedesktop.NetworkManagerUserSettings': no such name which is always in the messages log files. Every 5-10 minutes, I can hit spacebar 4-5 times and I briefly see the login screen then it blanks out. Then you have to wait another say 10 minutes. It has a intel integrated graphics mobo chip lspci 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02) 00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 00:19.0 Ethernet controller: Intel Corporation 82578DM Gigabit Network Connection (rev 05) 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) 00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 05) 00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation 5 Series Chipset LPC Interface Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05) [fetus@mu2 log]$ When I look at yum log, I don't see anything graphics related (I think) Jun 07 04:12:42 Updated: xulrunner-10.0.5-1.el6_2.x86_64 Jun 07 04:12:46 Updated: firefox-10.0.5-1.el6_2.x86_64 Jun 08 05:51:24 Updated: 32:bind-libs-9.7.3-8.P3.el6_2.3.x86_64 Jun 08 05:51:24 Updated: 32:bind-utils-9.7.3-8.P3.el6_2.3.x86_64 Jun 14 05:50:25 Updated: expat-2.0.1-11.el6_2.x86_64 Jun 14 05:50:31 Updated: 1:java-1.6.0-openjdk-1.6.0.0-1.48.1.11.3.el6_2.x86_64 Jun 14 05:50:32 Updated: expat-2.0.1-11.el6_2.i686 Jun 19 04:17:22 Updated: python-libs-2.6.6-29.el6_2.2.x86_64 Jun 19 04:17:29 Updated: python-2.6.6-29.el6_2.2.x86_64 Must be software related. Any advice? Bill Lutter
work around for the ehci_hcd error
As reported, I couldn't mount a Cavalry external usb2 hard drive and following this got tons of dmesg lines of form: hub 2-1:1.0: hub_port_status failed (err = -110) >From /var/log/messages, so every 5 seconds. Apr 15 03:29:03 mu2 kernel: hub 2-1:1.0: hub_port_status failed (err = -110) Apr 15 03:29:08 mu2 kernel: hub 2-1:1.0: hub_port_status failed (err = -110) Apr 15 03:29:13 mu2 kernel: hub 2-1:1.0: hub_port_status failed (err = -110) I got this to stop by unbinding and binding ehci_hcd device files as in this link http://www.geekdevs.com/2010/04/solved-unable-to-enumerate-usb-device-disabling-ehci_hcd/ So, I did cd /sys/bus/pci/drivers/ehci_hcd/ find ./ -name ":00:*" -print ./:00:1a.0 ./:00:1d.0 sudo sh -c 'echo -n ":00:1a.0" > unbind' and still got the dmesg messages, so did sudo sh -c 'echo -n ":00:1d.0" > unbind' which knocked out my usb2 mouse and keyboard #!@# so, I had to remote log in and then rebind them sudo sh -c 'echo -n ":00:1d.0" > bind' which returned my mouse and keyboard, so feeling lucky I did sudo sh -c 'echo -n ":00:1a.0" > bind' and no more scummy messages of form hub 2-1:1.0: hub_port_status failed (err = -110) >From what I read, usb2 don't always work supposedly with old stuff. Didn't >think my ext usb2 hd was THAT old. Knocking out 1d.0 probably throws me to usb1 speeds. I'll see if this issue comes back. If so, I'll try upgrading to SL6.2 Bill Lutter
usb device "cannot reset port" error
Friday, on a desktop running SL 6.1, I tried mounting an external USB hard drive and got hub port status errors. External USB HD is a Cavalry CAXM3701T0 Series 1 TB USB 2.0 / eSATA device. It worked fine with older linux SL (4.9) immediately after the SL6.0 error. It has worked in past on SL5.3 SL5.7. It worked on SL6 (same machine a week earlier). I automounted it, unmounted it, added a line to fstab and mounted at /mnt/usbhd. /dev/sdb1 /mnt/usbhd ext3 noauto,user,rw 0 0 This time (on SL6.1) when I get the messages, I had the fstab line uncommented and would have mounted it at /mnt/usbhd except I got the hub port messages below and sdb didn't show up at all via fdisk. (from /var/log/messages) Apr 13 12:55:08 mu2 kernel: usb 2-1.3: new high speed USB device using ehci_hcd and address 11 Apr 13 12:55:13 mu2 kernel: usb 2-1.3: device descriptor read/all, error -110 Apr 13 12:55:14 mu2 kernel: hub 2-1:1.0: cannot disable port 3 (err = -110) ... Apr 13 12:55:31 mu2 kernel: hub 2-1:1.0: cannot reset port 3 (err = -110) Apr 13 12:55:31 mu2 kernel: hub 2-1:1.0: Cannot enable port 3. Maybe the USB cable is bad? Apr 13 12:55:32 mu2 kernel: hub 2-1:1.0: cannot disable port 3 (err = -110) Apr 13 12:55:32 mu2 kernel: hub 2-1:1.0: unable to enumerate USB device on port 3 Apr 13 12:55:33 mu2 kernel: hub 2-1:1.0: cannot disable port 3 (err = -110) Apr 13 12:56:54 mu2 kernel: hub 2-1:1.0: hub_port_status failed (err = -110) ... Apr 16 10:19:37 mu2 kernel: hub 2-1:1.0: hub_port_status failed (err = -110) Apr 16 10:19:42 mu2 kernel: hub 2-1:1.0: hub_port_status failed (err = -110) Apr 16 10:19:47 mu2 kernel: hub 2-1:1.0: hub_port_status failed (err = -110) I've not had trouble with USB external hard drives before. Any advice on how to get this working without having to reboot, which I've not tried yet. Bill Lutter
Can I skip minor revisions in a SL5 upgrade
basic question... It's not clear to me from the FAQ http://www.scientificlinux.org/documentation/howto/upgrade.5x Can I skip from SL5.0 to 5.6 or do I need to go through the intermediate minor updates 5.0->5.1->5.2...? For instance if I jump from 5.0 to 5.6, could I just do "For the more cautious" step 6: rpm -Uvh ftp://ftp.scientificlinux.org/linux/scientific/56/i386/misc/RPMS/yum-conf-latest.SL.noarch.rpm Bill Lutter
Re: Gnome panel missing after glibc update on 6th of April
Ditto, except I've had two problems - both showed up around same time early 4/7 - the second one may or may not be related. 1. With gnome panel, following glibc update on SL 5.0 Boron with kernel 2.6.18-238.5.1-el5 (several reboots and logins done yesterday) a) "I've detected a panel running" with blank (for this PC lower) gnome panel. b) or panel shows up but is unresponsive fix is to do 1 or 2 killall gnome-panel (if it then disappears, execute gnome-panel). Problem might not show up for a login or reboot then reappears. 2. Problem #2 which I can't duplicate or get to repeat in a limited # tries a) the PC SL5.0 lost network the morning after (4/7) glibc update (eth0 can be stopped and started without error), but can't ping anything successfully) from yum.log Apr 06 06:09:27 Updated: glibc-common-2.5-58.el5_6.2.i386 Apr 06 06:09:57 Updated: glibc-2.5-58.el5_6.2.i686 Apr 06 06:09:58 Updated: nscd-2.5-58.el5_6.2.i386 Apr 06 06:10:00 Updated: glibc-headers-2.5-58.el5_6.2.i386 Apr 06 06:10:01 Updated: glibc-devel-2.5-58.el5_6.2.i386 b) switched to earlier kernel last night and things worked 2.6.18-194.26.1.el5 (could ping etc). c) this morning went back to latest kernel 2.6.18-238.5.1-el5 and no network connectivity d) rebooted with same kernel 2.6.18-238.5.1-el5 and this time there was network connectivity. Wild, anyone have a comment? Bill Lutter
smart statistics issue
I have a desktop PC at work that shows a bad block. PC runs Scientific LInux 5.0 and is a 2 TB WD Green Technology 2 Tb HD (Caviar Green WD2CSRTL). This one has worked fine out of the box for several months. No problems. Yesterday, the SMART diagnostics program smartctl (version 5.36) showed a bad block. Deciding to waste some time on it, I used http://smartmontools.sourceforge.net/badblockhowto.html approach. So, I unmounted, figured out the block and that it had a file associated with it, determined the ext3 file system inode. But, I could not deduce the file as it could not read the next file inode. I zeroed out the position using dd and then rerunning smartctl that it showed another bad block: # 3 Extended offlineCompleted: read failure 90% 2151 3764125871 # 4 Short offline Completed without error 00% 2151 - # 5 Short offline Completed without error 00% 2150 - # 6 Short offline Completed: read failure 90% 2146 3764125865 # 7 Extended offlineCompleted without error 00% 2097 The LBA is in the one partition on the HD Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System /dev/sdb1 63 3907024064 1953512001 83 Linux Since, it's a new HD and not expecting catastrophic failure, I did not run ddrescue. Having a copy of spinrite around, I ran that and the HD came out squeaky clean. I use spinrite occasionally on windows xp and linux HD where I expect only one bad block. Never had problems with it. Spinrite did not find any more bad blocks. Of course, I had zeroed out the original one. Rebooting and running e2fsck, the file system is clean. Running smartctl again, I again find a bad block at LBA 3764125871 # 1 Extended offlineCompleted: read failure 90% 2169 3764125871 # 2 Short offline Completed without error 00% 2169 - ... ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051Pre-fail Always - 0 3 Spin_Up_Time0x0027 100 253 021Pre-fail Always - 0 4 Start_Stop_Count0x0032 100 100 000Old_age Always - 6 5 Reallocated_Sector_Ct 0x0033 200 200 140Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000Old_age Always - 0 9 Power_On_Hours 0x0032 098 098 000Old_age Always - 2169 10 Spin_Retry_Count0x0032 100 253 000Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000Old_age Always - 5 192 Power-Off_Retract_Count 0x0032 200 200 000Old_age Always - 3 193 Load_Cycle_Count0x0032 195 195 000Old_age Always - 15614 194 Temperature_Celsius 0x0022 115 111 000Old_age Always - 37 196 Reallocated_Event_Count 0x0032 200 200 000Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000Old_age Always - 1 198 Offline_Uncorrectable 0x0030 200 200 000Old_age Offline - 0 199 UDMA_CRC_Error_Count0x0032 200 200 000Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000Old_age Offline - 0 Now, there are reported issues with WD Green Technology drives (parking the heads) and lag time issues with smartctl, although I can't find the web link where I saw this several months ago. I'm a bit confused. I've never had an issue like this that didn't clear up (descrepency between smartctl and spinrite for instance). Could it be the green technology drive not playing properly with smartactl (people report this)? Should I run a bad block check with e2fsck? A nondestructive test would e2fsck -ccv /dev/sdb Advice? Bill Lutter
Terrabyte file systems and SL5.0
For the first time I will be using a 1-2 Terrabyte hard drive on any SL release, in particular, on an older SL5.0 (boron) OS. There's plenty on the web about pros and cons for larger file systems (resier, xfs, ext3, ext4, ...). I've usually stayed with ext3 (200-500 Gb HD that are NFS mounted to linux or windows using MS windows for unix). So, vanilla; not too splashy a set up. No clusters. I've not used LVM. I think my question is which of these choices is as well developed, mature, and easy to use as ext3 for the SL5.0 boron version of SL? I'm most familiar with ext3 and do these stray IT tasks as needed, so I've not kept up on the latest and greatest. Thanks for any comments, Bill Lutter
SL archives and indexed postings not accessible
I find that on both firefox linux and IE winxp that I can't access either archived messages or Indexed links in the listserv.fnal.gov emails. I get a MS "The page cannot be found" screen. Uh, am I missing some new development? I figure everyone should also have this problem. It's been occuring the last week? both at work and on my home, so I don't think it is a firewall issue. But, then again, I don't see anyone else mentioning this... Bill Lutter
Fwd: Re: SL5.4 and Asus eee S101 netbook
I've installed the suggested kernel kernel-2.6.18-189.el5.jwltest.105.i686.rpm. > This may be of help for the wireless (ath9k). > http://linuxwireless.org/en/users/Drivers/ath9k/RHEL5 No go. My supervisor prefers the netbook not have internet capability, so not an issue. I will provide this feedback. The wireless adaptor in network configuration now is identified as atheros AR928X. It is unknown still in lspci output. Starting the device via network configuration menus yields a siocsifflags unknown error 132. Or, sudo ifconfig wlan0 up SIOCSIFFLAGS: Unknown error 132 Ubuntu forums suggest rfkill. I surmise rfkill is an ubuntu hack that kills wifi drivers. Lots of web exchanges on this. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/464559 Thanks for the suggestions, Bill Lutter --- Begin Message --- William Lutter wrote: I've installed SL5.4 on an ASUS eee S101 netbook that my lab has purchased. Reviews say Fedora 10 and Ubuntu 9.10 work "flawlessly" (Ubuntu). http://www.newegg.com/Product/Product.aspx?Item=N82E16834220595 I usually use SL, so I've installed 5.4. lscpi indicates that the ethernet controler is Atheros (AR8121 ...) and wireless is atheros (AR928X). There are no "atheros" entries in the other card adaptor lists in the network configuration submenus. So, neither the ethernet card nor wireless adaptors are recognized? The README file from downloading atheros driver from madwifi shows latest download is 2/08. README says lspci should show it as "unknown" and a 0x168x vendor ID. lspci -v indicates both ethernet (8324) and wireless (1a3b:1067) are unknown devices. I'm guessing madwifi is not going to not work. Looks like I need special software. For lab usage, I don't need networking. It would be nice to update software etc. I'd install ubuntu if it gave me networking capability and which is not available via current RHEL5 SL distro. thoughts? Bill Lutter This may be of help for the wireless (ath9k). http://linuxwireless.org/en/users/Drivers/ath9k/RHEL5 My guess is some more googling could shed light on the wired interface as well. Cheers, Mark -- Mr. Mark V. Stodola Digital Systems Engineer National Electrostatics Corp. P.O. Box 620310 Middleton, WI 53562-0310 USA Phone: (608) 831-7600 Fax: (608) 831-9591 --- End Message ---
SL5.4 and Asus eee S101 netbook
I've installed SL5.4 on an ASUS eee S101 netbook that my lab has purchased. Reviews say Fedora 10 and Ubuntu 9.10 work "flawlessly" (Ubuntu). http://www.newegg.com/Product/Product.aspx?Item=N82E16834220595 I usually use SL, so I've installed 5.4. lscpi indicates that the ethernet controler is Atheros (AR8121 ...) and wireless is atheros (AR928X). There are no "atheros" entries in the other card adaptor lists in the network configuration submenus. So, neither the ethernet card nor wireless adaptors are recognized? The README file from downloading atheros driver from madwifi shows latest download is 2/08. README says lspci should show it as "unknown" and a 0x168x vendor ID. lspci -v indicates both ethernet (8324) and wireless (1a3b:1067) are unknown devices. I'm guessing madwifi is not going to not work. Looks like I need special software. For lab usage, I don't need networking. It would be nice to update software etc. I'd install ubuntu if it gave me networking capability and which is not available via current RHEL5 SL distro. thoughts? Bill Lutter
most straightforward way to suspend/hibernate laptop (compaq evo N620c
I am using SL4.4 kernel 2.6.9-80.0.20.EL on an old Compaq Evo N620c laptop that I would like to suspend or hibernate.What is the easiest way to do this perferrably without recompiling kernel?I see http://www.linux.com/archive/feed/54610Since, cat /sys/power/state yields 'standby mem disk' and in my config file, 'CONFIG_ACPI_SLEEP' is set to yes 'y'. So I tried the script on the link 'suspend.sh'. which powered off OK but could not find a key to resume laptop operation. Email from 2004 indicates a problem with firmware or something with N620c (reporting same problem). Other web sites discuss older apm, swsusp, tuxonice etc. Other websites have laptop compatibility info for various things so the trail spreads out.Back to my initial question. What is the easiest or recommended way to implement suspend and/or hibernate on an older laptop such as COMPAQ EVO N620c?Bill Lutter