Menu
▾
▴
#4304 yum update w/ 1650 rpm (after "1652" SNAT patch) to 1660 does not complete
using: rpm update 1660-1
from: download.webmin.com
since this update is not in the regular webmin notification of an update to itself, it appears in the general pkg update list and was run from there.
the webmin execution of the yum-based update recognizes as far as the 'Running Transaction' stage and then stalls (i.e., the displaying of yum's progress stops).
in actuality, the update succeeds which can be confirmed by ignoring that yum supposedly never finished and clicking over to the main sys info page where one will see that the new version is installed.
--
thank you,
johann
If you run "pstree", does it show any processes that have been forked off by yum and are blocking its completion?
i am sorry, the title was poorly written. i do mention in the substance of the report that yum DOES complete, but webmin never notices the completion and appears to indicate that yum is stalled.
So the page in Webmin in which you installed the RPM never stops loading?
no, actually, webmin repeats all of the yum lines down through 'processing transaction' and then nothing else. yum actually completes the installation, but webmin does not catch those lines from yum or pickup yum's completion code.
it seems to break where you are substituting your own completion lines for what yum issues.
i think (now that is a novelty) that what happened is that once the rpm completes in the general update process that webmin must have to re-start since there are obvious file changes and the page is abandoned. your status persistence enables the re-start of webmin while the page remains intact on the client instead of webmin clicking over to the sys info page or whatever.
in the normal process of an installation from the webmin update notification on the sys info page none of this would normally happen. it is just this unique interim phase you mentioned where it is possible to find the update in the repo and install it from there amongst all the other pkg's that might exist.
Yes, I think the output on that page is probably being terminated due to Webmin restarting itself for upgrade.
So other than that, did the upgrade complete OK and leave Webmin in a running and usable state?
yes. as i mentioned, clicking over to any other page is fine and webmin is continuing in the same manner as if it were updated from the sys info page notification.
unless you exclude webmin updates from being processed through the general pkg updating proc or catch such an update in that proc so you can alter the display, the probably not-unheard-of client that would process a webmin update in the general proc would likely be confused and think the updating failed.
another thing, if webmin is not the end of the update list of pkg's, those that fall after webmin do not get processed since webmin's re-start interrupts.
I looked into this further, and there is indeed a bug here - webmin shouldn't kill the process doing the upgrade. I'll fix that in the next release (1.680).
thank you.