Hi I have just installed a lot of updates on a CentOS 4 box and w appears to have stopped working -- this machine has 3 or 4 people connected via ssh, yet this is all that is outputted: # w 20:46:32 up 301 days, 3:21, 0 users, load average: 0.02, 0.03, 0.04 USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT "rpmverify procps" returns nothing so the package hasn't been messed with. I don't want to reboot the server -- does any have any suggestions what could be done to get w working again? Thanks Chris -- Chris Croome <chris at webarchitects.co.uk> web design http://www.webarchitects.co.uk/ web content management http://mkdoc.com/
On 4/6/06, Chris Croome <chris at webarchitects.co.uk> wrote:> Hi > > I have just installed a lot of updates on a CentOS 4 box and w appears > to have stopped working -- this machine has 3 or 4 people connected via > ssh, yet this is all that is outputted: > > # w > 20:46:32 up 301 days, 3:21, 0 users, load average: 0.02, 0.03, 0.04 > USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT > > "rpmverify procps" returns nothing so the package hasn't been messed > with. > > I don't want to reboot the server -- does any have any suggestions what > could be done to get w working again?What kernel are you running, and which version version of procps are you running? -- Any sufficiently advanced technology is indistinguishable from magic. -Arthur C. Clarke
On Thu, 2006-04-06 at 21:18 +0100, Chris Croome wrote:> Hi > > I have just installed a lot of updates on a CentOS 4 box and w appears > to have stopped working -- this machine has 3 or 4 people connected via > ssh, yet this is all that is outputted: > > # w > 20:46:32 up 301 days, 3:21, 0 users, load average: 0.02, 0.03, 0.04 > USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT > > "rpmverify procps" returns nothing so the package hasn't been messed > with. > > I don't want to reboot the server -- does any have any suggestions what > could be done to get w working again? >We are tracking this issue as a bug. Basically ... it seems that for w to continue to work, you have to have the latest version of opsnssh, audit and audit-libs installed. With those installed and a CentOS kernel, everything seems fine (Even older CentOS kernels and those from CentOS Plus). Other external kernels (some fedora ... some kernel.org) seems to break w. Here is the bug: http://bugs.centos.org/view.php?id=1245 We won't be patching code to fix this unless it is fixed from upstream. (This is one of the reasons I don't recommend building your own kernels ... but that thread is probably better left dead :) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.centos.org/pipermail/centos/attachments/20060406/d54dc2d2/attachment-0001.sig>
Hi On Thu 06-Apr-2006 at 03:40:11PM -0500, Johnny Hughes wrote:> On Thu, 2006-04-06 at 21:18 +0100, Chris Croome wrote: > > > > I have just installed a lot of updates on a CentOS 4 box and w appears > > to have stopped working -- this machine has 3 or 4 people connected via > > ssh, yet this is all that is outputted: > > > > # w > > 20:46:32 up 301 days, 3:21, 0 users, load average: 0.02, 0.03, 0.04 > > USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT > > > > "rpmverify procps" returns nothing so the package hasn't been messed > > with. > > > > I don't want to reboot the server -- does any have any suggestions what > > could be done to get w working again? > > We are tracking this issue as a bug. > > Basically ... it seems that for w to continue to work, you have to have > the latest version of opsnssh, audit and audit-libs installed. With > those installed and a CentOS kernel, everything seems fine (Even older > CentOS kernels and those from CentOS Plus). > > Other external kernels (some fedora ... some kernel.org) seems to break > w. > > Here is the bug: > > http://bugs.centos.org/view.php?id=1245 > > We won't be patching code to fix this unless it is fixed from upstream. > (This is one of the reasons I don't recommend building your own > kernels ... but that thread is probably better left dead :)Ah, OK, I guess I should add to that bug report... I'm running a CentOS kernel and have the latest opsnssh, audit and audit-libs as far as I'm aware. # rpm -qi openssh Name : openssh Relocations: (not relocatable) Version : 3.9p1 Vendor: CentOS Release : 8.RHEL4.12 Build Date: Wed 08 Mar 2006 14:13:09 GMT Install Date: Fri 10 Mar 2006 21:01:09 GMT Build Host: build-i386 # rpm -qi audit Name : audit Relocations: (not relocatable) Version : 1.0.12 Vendor: CentOS Release : 1.EL4 Build Date: Sun 01 Jan 2006 19:22:39 GMT Install Date: Fri 10 Mar 2006 20:58:27 GMT Build Host: build-i386 # rpm -qi audit-libs Name : audit-libs Relocations: (not relocatable) Version : 1.0.12 Vendor: CentOS Release : 1.EL4 Build Date: Sun 01 Jan 2006 19:22:39 GMT Install Date: Fri 10 Mar 2006 20:58:23 GMT Build Host: build-i386 #rpm -qi kernel Name : kernel Relocations: (not relocatable) Version : 2.6.9 Vendor: CentOS Release : 5.0.5.EL Build Date: Wed 20 Apr 2005 01:16:34 BST Install Date: Wed 25 May 2005 19:23:52 BST Build Host: guru.build.karan.org # uname -srvpi Linux 2.6.9-5.0.5.ELsmp #1 SMP Wed Apr 20 00:16:40 BST 2005 i686 i386 Chris -- Chris Croome <chris at webarchitects.co.uk> web design http://www.webarchitects.co.uk/ web content management http://mkdoc.com/