Cannot connect to retrieve Database/current.zip
I just completed a patch upgrade on the Solaris 10 machine that runs our local patch
server. It needed several hundred patches, as it hadn't been patched since September.
After that, the behavior of our Solaris 10 patch clients has changed. For example, on one
client a few days earlier `smpatch analyze' had reported 218 patches. Now it reports only
these three:
119255-27 SunOS 5.10_x86: Install and Patch Utilities Patch
121119-08 SunOS 5.10_x86: Sun Update Connection System Client 1.0.8
119789-07 Synopsis: SunOS 5.10_x86: Sun Update Connection Proxy 1.0.9
Our clients currently use `http://xxxxxx.yyyy.tld:3816/solaris/' as their patch source.
Dropping the `solaris/' results in this error, complete with HTML tags, from
`smpatch analyze':
Failure: Cannot connect to retrieve Database/current.zip: <h1>/ Not Found</h1>
The resource identified by / could not be found.
With the original patch source, `smpatch update' does apply the three patches. The
next `smpatch analyze' reports that no patches are required, which is certainly
incorrect! By dropping the `solaris/' again, `smpatch analyze' reports 221 patches.
Suddenly, patching has become a very complicated process. We have to patch,
change the patch source, and patch again. There's no longer a way to use the installed
`smpatch' to obtain a list of required patches or to download them all. What can be
done to solve this problem?
