similar to: futex hang workaround by rebooting first (?)

I'm occasionally seeing processes on my CentOS 4.3 system get hung up, which strace reveals to be waiting on a call to futex(). Previously I'd only ever seen this in mysql on RH9, and google searches for explanations haven't turned up anything useful. Any pointers to where I should look? Is this another one of those things where using the default SMP kernel with a hyperthreaded

Two identical machines, both running CentOS 4.3 plus all the errata. First one: yum update went for a while and hung. At the bottom of the yum.log file was this: Aug 31 06:58:01 Updated: control-center.i386 1:2.8.0-12.rhel4.5 Aug 31 06:58:09 Updated: iiimf-le-unit.i386 1:12.1-13.EL.5 Aug The python process was in the process list, but it was consuming no CPU time. I let it go for a couple

On Tue, Sep 25, 2018 at 11:48 AM Zube <Zube at stat.colostate.edu> wrote: > > The current mitigation for CVE-2018-14634 is a systemtap script > mentioned here: > > https://access.redhat.com/security/cve/cve-2018-14634 > > It also mentions that one can build a kernel module to distribute > to other machines, but in any case one needs the corresponding > debuginfo

All of a sudden yum hangs on a Centos 4.5 (updated to the latest patch before 4.6) when I try to use it. "clean metadata" didn't help. The output of -d5 shows it gets to the point of "Reading Local RPMDB" and then sits there. The process doesn't die, but doesn't seem to do anything from that point on. strace shows this: futex(0xb76dcae8, FUTEX_WAIT, 2, NULL I

Never had much trouble building on the Mac until this round. Trying to build 7.4p1 with openssl 1.0.2j on a MacOSX 10.12.2/3 machine. gcc --version returns clang-800.0.42.1. This is the latest Xcode. Builds fine. Upon running sshd, it seg faults with this in the logs: assertion failed 16C67: libsystem_trace.dynlib+76912 [5BD4ECD4-75CA-38EA-AF5C-B481C15955F8]: 0x0 If I run the tests, it

The current mitigation for CVE-2018-14634 is a systemtap script mentioned here: https://access.redhat.com/security/cve/cve-2018-14634 It also mentions that one can build a kernel module to distribute to other machines, but in any case one needs the corresponding debuginfo packages to do either. After enabling CentOS-Debug.repo, what I get is:

Good Day. In June, I posted a small query under the Subject of _odd smbpasswd / smbclient error from Linux to Solaris_ Briefly, a Solaris sparc server running 3.0.25a would not accept passwords from the Linux smbclient program if the password was 9 characters or greater. Instead, one would get this: session setup failed: NT_STATUS_LOGON_FAILURE but it worked fine with the Solaris sparc

Group all the "guest OS" support options together, under CONFIG_PARAVIRT. Make this a proper menu item so it looks neater on menuconfig etc, and make the wording for each prompt uniform. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> diff -r 3d3ac181380b arch/i386/Kconfig --- a/arch/i386/Kconfig Fri Sep 14 12:24:15 2007 +1000 +++ b/arch/i386/Kconfig Fri Sep 14 12:45:09

Group all the "guest OS" support options together, under CONFIG_PARAVIRT. Make this a proper menu item so it looks neater on menuconfig etc, and make the wording for each prompt uniform. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> diff -r 3d3ac181380b arch/i386/Kconfig --- a/arch/i386/Kconfig Fri Sep 14 12:24:15 2007 +1000 +++ b/arch/i386/Kconfig Fri Sep 14 12:45:09

On Sat Oct 22 08:20:24 PM, Valeri Galtsev wrote: > I should have said CentOS 7. Older ones (CentOS 6 and 5) are not vulnerable. https://bugzilla.redhat.com/show_bug.cgi?id=1384344 Comment #35 points to a link that doesn't depend on /proc/self/mem and claims to work on CentOS 6 and 5. I'm not quite sure what I should be looking for when I run the program, though. I do hope Redhat

Dear test fans, Recently a couple of cases came to light, where a test had the line REQUIRES: nowindows with the obvious expectation that it would be disabled, but only for the Windows platform. Sadly, this is not true; the "no" prefix means nothing to Lit. I've already fixed one test, within Lit's own test suite, and I've done a bunch of grepping to see what else is

OK ... there has been an awful lot of attributing problems to the 4.4 upgrade that are not really upgrade problems. The best I can tell there is really only one major problem: 1. You need to install python-sqlite before sqlite (or at nearly the same time). To accomplish this you can do this: yum update python-sqlite sqlite Then after that, a normal yum update works fine. There are 2 other

Hi, Ady wrote: > Apparently, one of the consequences seems to be that the default > checksum included in isolinux.bin doesn't seem to help those > users/programs that, for whichever reason (e.g. user lacking > knowledge), do not patch the boot info table. I agree and still riddle about the reason. > So, my question is whether there is some intentional reason for these

Good day. Thanks in advance for any help. I have a Tyan S2895 (Thunder K8WE) with 2 275 Opterons and the latest (1.02) bios. It appears to have an nVidia nForce SATA chipset which connects to a 250gb WD Caviar SATA drive. Using the CentOS 4 update 2 x86_64 DVD, the install is peachy until half-way through the "performing post install configuration" bit. Then it hangs forever. I

This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --8323328-465625440-1002298640=:29463 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: <Pine.LNX.4.33.0110051717531.29463@localhost> ---------- Forwarded message ----------

I'm trying to update my CentOS 5.6 boxes to 5.7, and on every single one of them yum is failing with a segmentation fault: the error happens when yum is checking the 'base' repository. [root at picard yum]# yum update Loaded plugins: downloadonly, fastestmirror, priorities Determining fastest mirrors * base: mirrors.ircam.fr * extras: mirrors.ircam.fr * updates:

https://bugzilla.samba.org/show_bug.cgi?id=6788 Summary: rsync does not abort early but needlessly transfers data if destination is write protected Product: rsync Version: 3.0.5 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core

Excuse me in advance for my poor english I have noted a small bug on OpenSSH 3.5p1. When user root is not permitted to log in a system (PermitRoot no) and a correct password is submitted for it to server, a RST packet is issued from server to client: [root at xxx root]# ssh victim root at victim's password: Permission denied, please try again. root at victim's password: Permission

On Tue Feb 16 03:35:06 PM, John R Pierce wrote: Thanks to both you and Mark Roth for chiming in and thank you for the lsi-raidinfo script. > On 2/16/2016 3:23 PM, Zube wrote: > >Does anyone know what program can be used to query the RAID status > >from the OS for an on-board LSI SAS 2308-4i? > > the 2308 isn't actually a megaraid, Right, that is in agreement with both

Hi, i just want to ask whether somebody else has this problem of mine and if it can be solved. Many of my ( 30+ ) puppet installation freeze up after some time. The process is waiting for some private futex, but it stays like that forever. This is what strace looks like when the problem occures: [pid 29173] futex(0x3d35ce7a84, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406739,