[SOLVED] Current hangs in shutdown on fuser command

bassmadrigal · 07-09-2021, 11:34 AM

Is there an /mn mount or is that for loop getting an incorrect mount point?

Also, maybe you could try grabbing the sources for procps-ng from 14.2 and build that package to see if the issue exists there as well.

vulcan59 · 07-09-2021, 11:48 AM

OK. I did some reading and it seems that ps -o can truncate the command if other things are specified after it. I changed your code to

ps -hq $i -o user,command

I removed the hard coded /mnt/slackware from the fuser command, letting it use $dir again

At the hang, the display of uncompleted background tasks showed this

root /usr/bin/fuser -k -M -m /mnt/slackware

So the command is correct but not completing.

vulcan59 · 07-09-2021, 12:51 PM

Quote:

Originally Posted by bassmadrigal

Also, maybe you could try grabbing the sources for procps-ng from 14.2 and build that package to see if the issue exists there as well.

I am trying to do that but running up against a problem in configure.

error : C preprocessor "/lib/cpp" fails sanity check

bassmadrigal · 07-09-2021, 12:52 PM

Quote:

Originally Posted by vulcan59

OK. I did some reading and it seems that ps -o can truncate the command if other things are specified after it. I changed your code to

ps -hq $i -o user,command

I removed the hard coded /mnt/slackware from the fuser command, letting it use $dir again

At the hang, the display of uncompleted background tasks showed this

root /usr/bin/fuser -k -M -m /mnt/slackware

So the command is correct but not completing.

That makes a lot of sense. Good catch!

I think the next step is to see if this issue exists with other versions of procps-ng. You could try grabbing the source from 14.2 and build that to see if the problem still occurs.

Code:

wget -r -nH --no-parent --reject="index.htm*" --cut-dirs=4 https://mirror.slackbuilds.org/slackware/slackware64-14.2/source/a/procps-ng/
cd procps-ng
sh procps-ng.SlackBuild
upgradepkg /tmp/procps-ng-3.3.11-*.txz

vulcan59 · 07-09-2021, 03:31 PM

I am trying to compile the 14.2 procps-ng but running up against a problem in configure.

error : C preprocessor "/lib/cpp" fails sanity check

There may be something not compatible with the newer compiler in current I guess.

vulcan59 · 07-10-2021, 07:28 AM

I am unable to get the 14.2 procps-ng to compile on current. However, 14.2 installed on another machine does not have the shutdown problem and it backgrounds the fuser kill command.

bassmadrigal · 07-10-2021, 09:42 AM

Maybe try the version in 14.2's patches/ directory. It's only 2 versions behind -current's version and may compile. Just change the cut-dirs to 5 instead of 4.

Code:

https://mirror.slackbuilds.org/slackware/slackware64-14.2/patches/source/procps-ng/

I'm trying to determine if it's from the program or something else in -current. If it's the program, we'd need to file a bug report with them.

vulcan59 · 07-11-2021, 06:15 AM

I have not been able to compile the procps-ng from 14.2 patches on current. It fails with this

Code:

/usr/bin/ld: fuser.o in function `init_mntinfo':
fuser.c:(.text.startup+0x1bf4): undefined reference to `makedev'

procps-ng on current has psmisc 23.3 while 14.2 has 22.21. It is psmisc which builds fuser.

I am not sure what more I can do now.

volkerdi · 07-12-2021, 12:04 AM

Quote:

Originally Posted by vulcan59

I am not sure what more I can do now.

You say you are not using an SMP machine. But have you tried the SMP kernel? Unless it won't work for some reason it's the preferred kernel to use.

vulcan59 · 07-13-2021, 04:44 AM

Quote:

Originally Posted by volkerdi

You say you are not using an SMP machine. But have you tried the SMP kernel? Unless it won't work for some reason it's the preferred kernel to use.

I have tried both the huge and generic kernels as provided with no mods. Currently on 5.12.15. I always understood that the huge kernel has SMP support built in now or have I missed another kernel somewhere?

bassmadrigal · 07-13-2021, 10:04 AM

If you're running 32bit -current, there's regular and smp versions of both the generic and huge kernels (along with the associated modules).

Code:

Sun Jul 11 18:23:51 UTC 2021
a/kernel-generic-5.12.16-i586-1.txz:  Upgraded.
a/kernel-generic-smp-5.12.16_smp-i686-1.txz:  Upgraded.
a/kernel-huge-5.12.16-i586-1.txz:  Upgraded.
a/kernel-huge-smp-5.12.16_smp-i686-1.txz:  Upgraded.
a/kernel-modules-5.12.16-i586-1.txz:  Upgraded.
a/kernel-modules-smp-5.12.16_smp-i686-1.txz:  Upgraded.

vulcan59 · 07-13-2021, 02:41 PM

Quote:

Originally Posted by bassmadrigal

If you're running 32bit -current, there's regular and smp versions of both the generic and huge kernels (along with the associated modules).

Code:

Sun Jul 11 18:23:51 UTC 2021
a/kernel-generic-5.12.16-i586-1.txz:  Upgraded.
a/kernel-generic-smp-5.12.16_smp-i686-1.txz:  Upgraded.
a/kernel-huge-5.12.16-i586-1.txz:  Upgraded.
a/kernel-huge-smp-5.12.16_smp-i686-1.txz:  Upgraded.
a/kernel-modules-5.12.16-i586-1.txz:  Upgraded.
a/kernel-modules-smp-5.12.16_smp-i686-1.txz:  Upgraded.

I am running 64 bit.

igadoter · 07-13-2021, 02:54 PM

Switch to run level 1. Say if your problem diagnosis is correct you shouldn't be able to do that. I mean this command

Code:

# telinit 1

also should hang.

vulcan59 · 07-13-2021, 04:26 PM

telinit 1 works as I would expect. It drops to runlevel 1 and a login prompt.

igadoter · 07-13-2021, 05:10 PM

So login. Switch to run level 0. But before list all active processes and mounts. If shutting down system in run level 1 works - then I think problem is somewhere else. Besides what do you do to shutdown system? From inside GUI, session manager, switching run level or directly by shutdown command?