Thanks for looking at this, Glenn.
In the first directory (.../webwork2/htdocs), the npm ci command runs to completion and shows no errors.
In the second one (.../pg/htdocs), the npm ci command starts and then hangs. It seems like that command normally offers play-by-play comments on what it is doing. The last thing that worked was something like
reify: jsxgraph: timing reifyNode:node_modules/caniuse-lite Completed in 2843ms
After that I get cryptic log messages with timestamps. One says, "INFO: task iou-sqp-18377:18385 blocked for more than 245 seconds." The next line says what kernel I have and the third one says what to do to disable the message. The quoted message comes back from time to time, reporting a longer blocking duration every time.
... time passes ...
I have tried a number of variations on the approach above, without success. The package manager hangs every time. Doing the same steps lead to the same results in spite of the following modified approaches ...
- saying "systemctl stop webwork2" and "systemctl stop webwork2-job-queue" before giving the "npm ci" command,
- compounding the above commands with a "rm -rf node_modules" in the working directory, and then saying "npm install",
- doing all of the above and additionally using the "--no-progress" option on the "npm install" command, and
- Installing yarn and trying "yarn install" instead of "npm install" [this one also stalls and says that iou-sqp is blocking].