This section describes common problems that you might encounter when using Patch Manager to perform the following tasks:
Analyze systems to determine the list of appropriate patches
Download the patches to the system
Apply the patches to the system
This section covers general Patch Manager errors.
When running the smpatch update command, any of the following errors appear:
Cannot connect to retrieve patchdb: Connection refused
Or:
Cannot connect to retrieve patchdb: Connection timed out
Or:
Unknown host (host-name) connecting to http://host-name/
This problem might be caused by a network failure between the client and the patch server, or the patch server is down.
Ensure that patchpro.patch.source points
to a valid patch source.
Check the condition of the network.
If the problem is between your system and Sun, wait for the issue to be resolved.
When running smpatch in remote mode or trying to restart the Solaris WBEM services, the following error messages appear:
#smpatch analyze -u rootAuthenticating as user: root Type /? for help, pressing <enter> accepts the default denoted by [ ] Please enter a string value for: password ::root-passwordThere is no Solaris Management Console Server running on pserver2. #/etc/init.d/init.wbem statusSolaris Management Console server not running on port 898. #/etc/init.d/init.wbem start#/etc/init.d/init.wbem statusSolaris Management Console server not running on port 898.
Manually stop the Solaris WBEM services before restarting them.
#/etc/init.d/init.wbem stop#/etc/init.d/init.wbem start#/etc/init.d/init.wbem statusSolaris Management Console server version 2.1.0 running on port 898.
When you run any smpatch subcommand, you see the following error message:
# smpatch analyze
Error occurred during initialization of VM
java.lang.Error: Properties init: Could not determine current
working directory.
Change directories and retry the command.
#cd /#smpatch analyze