On Tue, Mar 10, 2015 at 08:15:38PM -0700, Dave Johansen wrote:
On Tue, Mar 10, 2015 at 7:53 PM, Dave Johansen davejohansen@gmail.com wrote:
On Tue, Mar 10, 2015 at 5:10 AM, Michal Schmidt mschmidt@redhat.com wrote:
On 03/10/2015 03:13 AM, Dave Johansen wrote:
#0 0xb76debac in __kernel_vsyscall () #1 0xb7510d03 in __waitpid_nocancel () from /lib/libpthread.so.0 #2 0xb6fa4842 in rpmScriptRun () from /lib/librpm.so.3 #3 0xb6f83c53 in runScript () from /lib/librpm.so.3 #4 0xb6f8434f in runInstScript () from /lib/librpm.so.3 #5 0xb6f8531b in rpmpsmRun () from /lib/librpm.so.3 #6 0xb6f9a3cb in rpmteProcess () from /lib/librpm.so.3 #7 0xb6fa1714 in rpmtsRun () from /lib/librpm.so.3 [...] It looks like yum is waiting on some process.
It's waiting for a package scriptlet to finish.
Here's the contents of the script that it's waiting on: if [ $1 -eq 0 ] ; then # Package removal, not upgrade systemctl --no-reload disable minetest@default.service > /dev/null 2>&1 || : systemctl stop minetest@default.service > /dev/null 2>&1 || : fi
Sorry for the multiple emails. It's stuck on the call to stop the service. When I run status, I prints the following: . minetest@default.service - Minetest multiplayer server w/ default.conf server config Loaded: loaded (/usr/lib/system/system/minetest@.service; disabled) Active: inactive (dead)
Any recommendations on what I should do next to diagnose the source of the problem?
How long does it stay in this state? systemctl times out connections after a timeout (25s ?), so even if it fails to communicate with PID1 for any reason, rpm should still continue at some point.
pstree -ap <pid-of-rpm> should show a list of processes. If it's systemctl that is hanging, can you post the backtrace?
Zbyszek