Bug 262348 - Unkillable processes during TeX upgrade
Summary: Unkillable processes during TeX upgrade
Status: Closed Unable to Reproduce
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 13.0-STABLE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2022-03-04 21:28 UTC by Hubert Tournier
Modified: 2024-02-23 09:18 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hubert Tournier 2022-03-04 21:28:15 UTC
My system gets stuck during TeX upgrade.
When I interrupt portuprade, the only way to kill the related processes is to reboot. Kill command doesn't do anything. ^Z & kill %1 neither.
Without reboot, the system ends up getting clogged with a lots of processes (1750+ at last reboot, with periodic tasks)

# kill -9 96945 22652 2745 5974
# ps -aux
USER     PID  %CPU %MEM     VSZ     RSS TT  STAT STARTED       TIME COMMAND
[...]
root   96945   0,7  1,2  506100  406904  0- D+   19:41      2:52,69 /usr/local/sbin/pkg-static register -d -i /usr/ports/print/texlive-texmf/work/stage -m /usr/ports/print/texlive-tex
[...]
root   22652   0,3  0,0   16936    6384  2- D    20:08      1:59,26 fetch -q http://update1.freebsd.org/13.0-RELEASE/amd64/latest.ssl
[...]
root    5974   0,2  0,0   22336   10592  1- D    19:50      2:29,09 pkg audit -F
[...]
root    2745   0,1  0,0   22336   10592  3- D    22:11      0:01,07 pkg audit -F
[...]

Very strange situation. Never encountered that since I started with 386BSD and FreeBSD 1.0!
Comment 1 Muhammad Moinur Rahman freebsd_committer freebsd_triage 2022-03-05 04:02:38 UTC
It's a huge port; 1.1G around for texlive-texmf. Are you sure that somehow it's still not being downloaded in the background.
And so far I have comeup it's best to delete previous packages and reinstall from scratch. :(
Comment 2 Hubert Tournier 2022-03-05 05:53:04 UTC
Yes, I'm sure that I already had all the distfiles downloaded (including the 3.4 GB texlive-20210325-texmf.tar.xz in /usr/ports/distfiles/TeX) and the first time I did the upgrade it got stuck for 2 days on a big server before I interrupted the upgrade (after compiling successfully texlive-texmf and attempting to install it).

I made several tries after that, each time getting to this strange side effect, including tries where I previously wiped every trace of protobuf-c, doxygen and TeX on my system before restarting.

This may be disk related, as I see that all the stuck processes are in D state, which "Marks a process in disk (or other short term, uninterruptible) wait" but there are no interesting messages in /var/log/messages.

Only meaningful traces in /var/log/messages are:
Mar  4 22:38:56 arche7 pkg-static[74773]: tex-kpathsea-6.3.3 installed
Mar  4 22:39:03 arche7 pkg-static[19603]: tex-ptexenc-1.3.9 installed
Mar  4 22:39:38 arche7 pkg-static[68651]: tex-web2c-20210325 installed
Mar  4 22:40:14 arche7 pkg-static[67889]: tex-basic-engines-20210325 installed
Mar  4 22:41:07 arche7 pkg-static[91101]: texlive-tlmgr-20210325_1 installed
Mar  4 22:44:41 arche7 pkg-static[34486]: texlive-base-20210325 installed

I worked around the issue by cutting the "LaTeX support" in doxygen or the "Build documentation with Doxygen" in protobuf-c, and then 

So one of:
# cd /usr/ports/devel/doxygen ; make config
# cd /usr/ports/devel/protobuf-c ; make config

But I see this more as a worrying system side effect, than as an issue with a port upgrade that I don't really need.
Comment 3 Hubert Tournier 2024-02-23 09:18:36 UTC
This PR is no longer relevant. Let's close it!