I'm trying to track down random lockups
Does this occur as long as you have the box?
Anything anomalous in any logs? With verbosity turned up?
Can you get a fix on the interval? If not, after aprox what period of time?
Any SAR data (atop, dstat) to check for ramping up memory, I/O etc, etc?
another similar system that does not have these lockup issues.
Exact same HW?
I inherited this system so I don't know its history
OK, what *do* you know about the box?
Is it generally okay to have multiple versions of the same package installed?
Depends on what your POV is. If it's about standarisation, minimising of risk, maintenance time then I'd say
less is more, except for kernels (and stuff you can't avoid for legacy reasons). In your list I don't see any packages I know would conflict though.
Is that a robust way to determine whether an RPM has been used recently or is there a better way to see if package X version Y is still being used by something?If I find out what files were installed with the package, can I use "find" to tell me if they've been accessed recently?
Code:
# Say you want to find out about /bin/ls:
]$ rpm -q --whatprovides --qf="%{name}\n" /bin/ls
coreutils
# ...so package coreutils requires:
]$ rpm -q --whatrequires --qf="%{name}\n" coreutils
devlabel
prelink
# now the access times of the dependent devlabel package sorted by date:
rpm -ql devlabel | xargs -iF stat -c '%N %x' 'F'| column -t | sort -rk2
This is a production system so I can't experiment much (e.g., uninstall them and see what happens).
No testbed available? Can't swap in a spare?