Ideally, we thought this way we would be able to minimize the amount of edits transferring needed.
After moving them to /var/tmp/, we used rpm2cpio to extract the files. Which puts the httpd files in the current directory. However, we were concerned that yum reinstall would overwrite the entire httpd directory: there were some (not many) Wellesley specific edits (nf) that we didn’t want to overwrite, so we backed them up in the sysadmin account…but then found this article ! The yum downloadonly flag makes yum only download the package and not install/update them.
Trying again: we thought maybe we should just redownload a copy of nf (using yum reinstall). Then it failed and wanted another module. We first tried just commenting out the module in nf. Did this actually help? We were still confused. After grepping through the yum.logs, we saw that httpd had last updated on october 14th. Scott did some detective work in the rsnapshots since April, saw that the other nf files hadn’t needed to load mod_file_cache.so. Our problem: When we tried to restart httpd, we got an error that it “cannot load httpd/modules/mod_file_cache.so.” We had restarted apache the previous Wednesday to test out varnish on puma, so this was peculiar. For context, on our machines, we edit the nf file in the sysadmin account and use a script to update the tempest server’s nf. When we attempted to download varnish on 11/8, we hit some issues with our nf file that was just outdated/incorrect (for reasons unknown, problem revealed later). Part I: What to do if you think you screwed up a config file
Two very very late posts about what to do if you think you screwed up a config file or other system file (you do not necessarily an update - might affect other dependencies) and how to set up varnish.